[
http://jira.jboss.com/jira/browse/JBSEAM-2482?page=comments#action_12412254 ]
Jay Balunas commented on JBSEAM-2482:
-------------------------------------
Hi Christian,
I'm actually looking at it right now :)
I have tested your fix, and it does solve the initial issue. What I'm seeing is that
searches from the hotel search input box is failing with the same basic error.
The problem is that this goes through the "ClientSideInterceptor" not the
"SessionBeanInterceptor". So your changes are not processed.
One concern I have with your change is that it basically reinitialized the interceptor
every call. It might not be too costly, but it could have other implications.
Another path I'm going down is that the issue is related to the weblogic auto
generated classes that it creates from the EJBs. This might be why reinitializing every
time seems to help. The first time through the interceptors are caching the original bean
classes, but when called the generated ones are in there.
In either case I think that postConstruct is not being called, and from what I'm read
and debugged is that weblogic is pretty bad at swallowing errors and logging output. Also
that these errors can cause processing of annotations to stop.
I am trying to get something for this out for 2.0.2.GA - the timing is tight - but
hopefully it is will come down to a weblogic deployment option ;)
Thanks,
-Jay
Possible work around for Weblogic "varargs" EJB issue
-----------------------------------------------------
Key: JBSEAM-2482
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2482
Project: Seam
Issue Type: Task
Components: Documentation Issues, Examples, Platform interoperability
Affects Versions: 2.0.1.CR1
Reporter: Jay Balunas
Assigned To: Jay Balunas
Priority: Minor
Fix For: 2.0.2.GA, 2.1.0.BETA1
Attachments: full-stack-of-ejb-transient-error.txt
There is a know issue with weblogic and support for EJBs that use variable arguments.
This is documented in the reference guide for more details.
I've attached the full stack trace from the console.
The main errors revolve around EJB3 timers - there may be a way to disable timers through
the weblogic.xml deployment descriptor, or perhaps a different file.
There are other warnings around EJB synchronization, but they may still function.
If solved the reference docs should be updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira