[seam-dev] java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed))

[Snjezana Peco]

I have tested a Seam project using the following:

JBoss Seam 2.0.2.SP1 and 2.1.1.GA
JBoss AS 4.2.2.GA,4.2.3.GA, EAP 4.3.0.GA_CP03 and 5.0.1.GA

When adding jboss-seam.jar to WEB-INF/lib, the application doesn't work 
with Seam 2.0/2.1 on AS 4.2.3/5.0.1/4.3.0.GA_CP03.
Seam doesn't set namespaces correctly (it doesn't set the 
org.jboss.seam.framework, org.jboss.seam.security and 
org.jboss.seam.transaction package, for instance)
and returns the following warning message:
"No phase id bound to current thread (make sure you do not have two 
SeamPhaseListener instances installed)"

If jboss-seam.jar isn't in WEB-INF/lib, everything works correctly.

When using JBoss 4.2.2.GA, Seam works correctly even if jboss-seam.jar 
is in WEB-INF/lib
Some changes in the JBoss AS classloader, somewhere between JBoss AS 
4.2.2 and JBoss AS 4.2.3, cause this issue. The issue isn't related to 
JBoss Tools.

A workaround is removing jboss-seam.jar from WEB-INF/lib

Snjeza

Max Rydahl Andersen wrote:
> It only happens for special people....
>  
> Before it were for projects with a capital letter - I haven't 
> identified the trigger yet for this round.
>  
> /max
>
> *From:* Dan Allen <mailto:dan.j.allen at gmail.com>
> *Sent:* Tuesday, April 07, 2009 8:32 PM
> *To:* Max Rydahl Andersen <mailto:manderse at redhat.com>
> *Cc:* Pete Muir <mailto:pmuir at redhat.com> ; seam-dev at lists.jboss.org 
> <mailto:seam-dev at lists.jboss.org>
> *Subject:* Re: [seam-dev] java.lang.IllegalStateException: No phase id 
> bound to current thread (make sure you do not have two 
> SeamPhaseListener instances installed))
>
> On Tue, Apr 7, 2009 at 1:37 PM, Dan Allen <dan.j.allen at gmail.com 
> <mailto:dan.j.allen at gmail.com>> wrote:
>
>     On Tue, Apr 7, 2009 at 1:30 PM, Max Rydahl Andersen
>     <manderse at redhat.com <mailto:manderse at redhat.com>> wrote:
>
>
>         ----- "Dan Allen" <dan.j.allen at gmail.com
>         <mailto:dan.j.allen at gmail.com>> wrote:
>
>         > > Replace JSF with an up to date version. JSF lives in
>         server/default/
>         > > deploy/jboss-web.deployer/jsf-libs/{jsf-api.jar,
>         jsf-impl.jar}.
>         >
>         > Thanks, I'll get that into our FQA.
>         >
>         > Isn't the "two listeners installed" just a warning? Seam
>         still works
>         > as far as I know. I see this same message when deploying to
>         Tomcat.
>         >
>
>         Error Message:
>         23:56:56,423 ERROR [SeamPhaseListener] uncaught exception
>         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:162)
>         at
>         org.jboss.seam.contexts.PageContext.isBeforeInvokeApplicationPhase(PageContext.java:174)
>         at
>         org.jboss.seam.contexts.PageContext.getCurrentWritableMap(PageContext.java:90)
>         at
>         org.jboss.seam.contexts.PageContext.remove(PageContext.java:104)
>
>         Looks like an exception to me ;)
>
>
>     Hmm, so when the app starts it probably lists a warning too. I
>     actually haven't deployed to 4.2.3.GA <http://4.2.3.GA> yet. I
>     wonder if I deployed an app if I would see this or if there is
>     something specific about the user's app.
>
>
> I can't reproduce. I wonder what else I need to do to replicate the 
> user's situation. Created EAR w/ JBoss Tools 3.0.0.CR2.
>
> -Dan
>
> -- 
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://in.relation.to/Bloggers/Dan
>
> NOTE: While I make a strong effort to keep up with my email on a daily
> basis, personal or other work matters can sometimes keep me away
> from my email. If you contact me, but don't hear back for more than a 
> week,
> it is very likely that I am excessively backlogged or the message was
> caught in the spam filters.  Please don't hesitate to resend a message if
> you feel that it did not reach my attention.
> ------------------------------------------------------------------------
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>