aspose file tools
The moose likes Portals and Portlets and the fly likes JSR-286 Problem: setEvent(), processEvent() Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » Portals and Portlets
Reply Bookmark "JSR-286 Problem: setEvent(), processEvent()" Watch "JSR-286 Problem: setEvent(), processEvent()" New topic
Author

JSR-286 Problem: setEvent(), processEvent()

Hub Fel
Greenhorn

Joined: Oct 21, 2009
Posts: 10
Hi,
I have problems with processEvent()

I have a portlet B , loaded on startup but not visible (not displayed).
Portlet A sends an event to portlet B.
Portlet B receives it in processEvent() , does some stuff(creates a workflow with opensymphony/osworkflow) and would like to be rendered then ---but nothing happens. I do not notice that any portlet is rendered at all. Instead I see (visuall feedback from browser) that a request is pending, which times out after a while.
Creating a new request by pressing "home" interrupts the pending request and all works fine again. But I think the request is still pending somewhere.

If I don't do anything in processEvent(), the portlet get's rendered (doView()).
Sometimes (rarely) it works, although I do my stuff in processEvent() (create the workflow).
Sometimes my breakpoints in doView() are triggered, if I stop my application (Ctrl C), which brought me to the idea that I am locking something.

While stopping the application I then see following output on the console
[TomcatDeployer] undeploy, ctxPath=/pluto, warUrl=.../deploy/pluto.war/
[StandardWrapper] Waiting for 1 instance(s) to be deallocated
[StandardWrapper] Waiting for 1 instance(s) to be deallocated
[StandardWrapper] Waiting for 1 instance(s) to be deallocated
[[/pluto]] Closing Spring root WebApplicationContext

The more requests I generated, the more "Waiting ..." I see.

I am running on JBoss 4.2.2 GA

Are there some restrictions on what is allowed in processEvent()?
Could somebody please help me to isolate the problem?

Thank you for helping

Regards
Hubert
Hub Fel
Greenhorn

Joined: Oct 21, 2009
Posts: 10
...well, it looks like it was my fault.
The thread that locked the whole thing was "com.sun.jndi.ldap.Connection".
And it locked, because I left a DirContext open in my application. Closing this solved the problem.

hub
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JSR-286 Problem: setEvent(), processEvent()
 
Similar Threads
Application Hang Problem.
Waiting for instance(s) to be deallocated
Tomcat causing application to hang
Waiting for 292 instance(s) to be deallocated
Waiting for 292 instance(s) to be deallocated