| Best to keep discussion on the list since there are smarter guys (such as Chuck and David(s)) on the list......
Then go try and debug using the suggestions for application deadlock in the previous mail.
Probably you have an (1) EOEditingContext deadlock or a (2) SessionStore deadlock
which means you have
(1) done something wrong in your code with respect to EC lock handling or
(2) you upgraded Wonder, possibly installed on top of old installation, mixed old rev jars with new rev jars in some frameworks and you are missing a class needed by your version of Jasper library which is now failing in appendToresponse causing a Session store deadlock .... or something like that. (been there, done that one time)
Also, check out Wonder's Session store deadlock detection feature (with concurrent request handling off since it only works that way because Anjo could not get it to work with concurrent request handling on ;-) )
If it was me, the first thing I would try is concurrent request handling OFF and sessionstore deadlock detection ON and see if I get a meaningful stack trace/error.....
-Kieran On Sep 21, 2010, at 11:40 AM, Venu A wrote: It is a application dead lock, The printJasperReports method is executing, it goes in to the try block and start the JasperRunManager.runReportToPdf(--,--,--) then it goes to the dead lock.
public WOComponent printJasperReports() {
-------
-------- try{
byte[] bytes=JasperRunManager.runReportToPdf(reportURL.getPath(),map,source);
page.data = "">
}catch(Exception e){
e.printStackTrace();
}
return page; }
I have used a simple hypher link to execute the code(generate a pdf), in this case also the application goes to dead lock state(in JasperRunManager.runReportToPdf(reportURL.getPath(),map,source);).
On Tue, Sep 21, 2010 at 7:00 PM, Kieran Kelleher <email@hidden> wrote:
I am not sure from your symptoms description whether you are experiencing browser _javascript_ deadlock or an Application deadlock.
... for _javascript_ browser deadlock......
- Use FireBug to see if you have _javascript_ errors associated with the page or upon executing the action from the JSModalWindow (which I have never used myself)
- Try running the action temporarily from a plain WOHyperlink
- Try using AjaxModalDialog from Ajax framework instead of JSModalWindow
.... for application deadlock..... try....
- Turning on ERXEC lock tracing
- use ERXStatisticsStore to grab stack traces in middle of the problem request
- Do a dump of all thread stack traces after the app has frozen to see the state of the threads using jstack
On Sep 21, 2010, at 8:32 AM, Venu A wrote: Hi Kelleher ,
Thanks for quick reply,
Iam using WebObjects 5.4.3 with Project wonder. In the application iam generating pdf's using JasperReports.
Previously i used old Ajax.framework,ErExtentions.framework,in this case all of the PrintPdf's was working fine.
Now am updated my Ajax.framework,ErExtentions.framework,in this case PrintPdf is not working means the application
is strucked(I coud not click on any tab or any link and the pdf is not generated), I need to relaunch the application. My print pdf code
is as follows
public WOComponent printJasperReports() {
String buString=null;
HashMap map = new HashMap();
URL reportURL = application().resourceManager().pathURLForResourceNamed("Reports/Invoice/MyReport.jasper", "CCBViewJava", null);
String basePath = reportURL.getPath().substring(0,reportURL.getPath().lastIndexOf('/'));
WOResourceManager manager = application().resourceManager();
String imagePath = CCBUtilities.getBasePath("SampleWrapper",manager);
map.put("imagePath",imagePath);
map.put("basePath",basePath);
JRDataSourceScriptlet source = new JRDataSourceScriptlet(new NSArray(bill));
JRPDFPage page = (JRPDFPage)pageWithName("JRPDFPage");
try{
byte[] bytes=JasperRunManager.runReportToPdf(reportURL.getPath(),map,source);
page.data = "">
}catch(Exception e){
e.printStackTrace();
}
return page;
}
in wod:
-----------
ModalWindowBottom: JSModalWindow {
isResizable = true;
showScrollbars = true;
action = "">
height = 640;
width = 576;
windowName = "_blank";
}
If i replace the old frameworks for the application it is working fine without change any code.
I have updated my frameworks for AjaxFlexibleFileUpload to use in my application.
Thanks
Venu
On Tue, Sep 21, 2010 at 5:11 PM, Kieran Kelleher <email@hidden> wrote:
Venu,
more details?
On Sep 21, 2010, at 4:57 AM, Venu A wrote:
Hi All,
When I used old Ajax.framework with WebObjects 5.4.3 wonder frameworks, JasperReport's JasperRunManager.runReportToPdf method
is working correctly, and producing PDF.
But When I used new Ajax.framework, JasperReport's JasperRunManager.runReportToPdf is getting struck in this method itself and
after re-launch only app is working, until that it is in idle state.
How to resolve this?
Thanks in advance,
Venu
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
This email sent to email@hidden
|