Would you be able to send me a deployable, may be a stripped down version of what you are using, for us to reproduce? You can send directly to me at pjhaATredhatDOTcom.
this is a maven project. In the ulbak/ulbak directory is a master POM which
should call the others as well. This on produces a single ear-file which I simply move to the farm-directory.
You also need a datasource, you'll find the persistence.xml in the ejb-subproject. It's configured for a DB2 database.
I think I will give it another try with JBP 2.6.6 but I can't say when. So far
I've shutdown all but one cluster node to stabilize the app.
Thanks and best wishes
I was thinking that you might have missed the pom at ubalk directory level (not ubalk/ubalk).
Looking at more carefully, I see that your ear include portlet bridge 1.0.0.B3.jar and the latest one is 1.0.0.B6.jar. New one has lots of fixes but it does not seem like it will fix this.
Looking at http://anonsvn.jboss.org/repos/portletbridge/trunk/core/portletbridge-impl/src/main/java/org/jboss/portletbridge/application/PortletStateHolder.java,
this class needs to be marked serializable. That should fix it.
Thanks for your help!
Can you try to upgrade to B6 and let us know if you are getting the error? Just check here for config details http://www.jboss.org/files/portletbridge/docs/1.0.0.B6/en/html_single/index.html#configuration ... it should not be complicated, and for some reason if it is, let me know how I can help.
The reason is, even if we do make certain session classes serializable, you will still need to use trunk until we release the latest version.
Also, the error is still in B6. But is it actually causing the application to break? or is it just showing up in the error log?
Every time the bridge gets an instance, the object is checked (See factory method in PortletStateHolder). Watch PBR-75 for the fix.
Ouch, I simply denied the fact I reconfigured the apache loadbalancer. I
moved the configuration to a virtual host and the application broke!!!
I really can't believe, but moving back to the original configuration without
virtual hosts let the application work in the cluster again. :-(
I'm sorry about this.
Ok, as long I don't use virtual hosts all is working fine. As I already stated in
PortletBridge forum, I've some issues with PB beta 6 but I guess I'll have to reconfigure my app in near future. I thank you for your help in this matter.