https://issues.apache.org/bugzilla/show_bug.cgi?id=55618
Bug ID: 55618
Summary: Possible class loading issue in tomcat 8 RC3..?
Product: Tomcat 8
Version: 8.0.0-RC3
Hardware: PC
OS: Linux
Status: NEW
Severity: regression
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: sander.sonaj...@gmail.com
Hi,
I'm looking at the Tomcat 8.0.0-RC3 release and trying to make sure that our
product (ZeroTurnaround's JRebel) still works nicely against it.
While testing out framework integrations, I came across an issue with JBoss
Seam 2 (present for all 2.0, 2.1 and 2.2). Yes, sorry, of course you are not
Seam support forum, but I have reasons to believe that the error I'm getting is
a symptom of some sort of a regression in Tomcat 8 as compared to Tomcat 7..
something not specific to Seam, although I cannot put my finger on it right
now.
The application I'm attaching is basically our integration test that we run for
numerous containers. It is a very simple maven build.. you'll get it deployed
in 60 seconds. Yes, Seam is mainly meant to be run on JBoss itself, but it has
been running quite well across a whole bunch of containers. This application
works in our integration test suite against numerous webspheres, glassfishes,
weblogics, etc, and also on various versions of Tomcat 6.x and 7.x. If you run
it on Tomcat 8 RC3, you'll get
/../
02-Oct-2013 15:30:09.879 WARNING [localhost-startStop-2]
org.jboss.seam.jsf.SeamPhaseListener.<init> There should only be one Seam phase
listener per application
/../
02-Oct-2013 15:30:12.539 WARNING [http-nio-8080-exec-2]
org.jboss.seam.jsf.SeamPhaseListener.afterPhase uncaught exception, passing to
exception handler
java.lang.IllegalStateException: No phase id bound to current thread (make
sure you do not have two SeamPhaseListener instances installed)
at org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:163)
...
It is a Seam-specific error that happens quite typically (if you google for
it).. when people forget 2 seam libraries into the classpath or something like
that. In current case, you can obviously see that there is just 1 seam library
in classpath.
Yes this is just a symptom, but I have a feeling that something in the way
classes get loaded or in your class loader hierarchies is .. at least not how
it used to be. Maybe your implementation is 100% compatible with the JEE spec
and maybe just Seam guys are taking advantage of something non-standard. But..
maybe not, as this application is not suffering from this issue in 20+ other
web containers we test against in our company.
I'd be happy if you could take a quick look into this or at least give me some
hint where to start from... have you changed something in the way classes get
loaded since tomcat 7? (Read changelog, didn't find much). Thanks if you can
look into this! :)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
