[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4607) Enabling Debug page on WebLogic

Markos Fragkakis (JIRA) jira-events at lists.jboss.org
Tue Mar 23 07:55:37 EDT 2010 

     [ https://jira.jboss.org/jira/browse/JBSEAM-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Markos Fragkakis updated JBSEAM-4607:
-------------------------------------

    JBoss Forum Reference:   (was: http://seamframework.org/Community/DebugPageHell)


> Enabling Debug page on WebLogic
> -------------------------------
>
>                 Key: JBSEAM-4607
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4607
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.2.0.GA
>         Environment: Windows XP 32-bit
> BEA JRockit 1.6.0_14
> Weblogic 10.3.2 (11g)
> JSF 1.2 (bundled with Weblogic AS)
> JBoss Seam 2.2.0 GA
> Facelets 1.1.14
> Richfaces 3.3.2.SR1
>            Reporter: Markos Fragkakis
>
> In a EAR application, with the Weblogic-specific jboss-seam.jar (2.2.0.GA) containing 5 EJB modules (incl. Seam) and a WAR module. 
> The structure of the application .ear is the following:
> application.ear
> |--> APP-INF
> |      |--> classes
> |--> lib                                   (all jar dependencies go here, including the WAR dependencies, EJB module dependencies)
> |-->META_INF
> |      |--> application.xml
> |      |--> data-sources.xml
> |      |--> MANIFEST.MF
> |      |--> weblogic.xml
> |      |--> weblogic-application.xml
> |--> jboss-seam-2.2.0.GA.jar
> |--> myEjbModule1.jar
> |--> myEjbModule2.jar
> |--> myEjbModule3.jar
> |--> myEjbModule4.jar
> |--> myWar.war                                        (NO libraries in WEB-INF/lib, finds everything in EAR/lib)
> When deploying .ear application WITHOUT debug enabled (not including the jboss-seam-debug.jar in the ear), the application is loaded correctly.
> When deploying WITH jboss-seam-debug.jar in the EAR (EAR/lib directory), the application does not appear, but ONLY the debug page with the following exception (stacktrace at the end):
> Exception during request processing:
> Caused by java.lang.IllegalStateException with message: "No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed)"
> When "JBoss-izing" the same EAR (remove hibernate jars, which are provided by JBoss, and move all libraries from EAR/lib to EAR root), the application loads correctly. BOTH the application AND the debug page appear correctly.
> Full stack trace:
> org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:163)
> org.jboss.seam.contexts.PageContext.isBeforeInvokeApplicationPhase(PageContext.java:175)
> org.jboss.seam.contexts.PageContext.getCurrentWritableMap(PageContext.java:91)
> org.jboss.seam.contexts.PageContext.remove(PageContext.java:105)
> org.jboss.seam.Component.newInstance(Component.java:2141)
> org.jboss.seam.Component.getInstance(Component.java:2021)
> org.jboss.seam.Component.getInstance(Component.java:2000)
> org.jboss.seam.Component.getInstance(Component.java:1994)
> org.jboss.seam.Component.getInstance(Component.java:1967)
> org.jboss.seam.Component.getInstance(Component.java:1962)
> org.jboss.seam.faces.FacesPage.instance(FacesPage.java:92)
> org.jboss.seam.core.ConversationPropagation.restorePageContextConversationId(ConversationPropagation.java:84)
> org.jboss.seam.core.ConversationPropagation.restoreConversationId(ConversationPropagation.java:57)
> org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:391)
> org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:230)
> org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:196)
> com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:175)
> com.sun.faces.lifecycle.Phase.doPhase(Phase.java:114)
> com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:104)
> com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
> javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
> weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
> weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
> weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
> weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:530)
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
> org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
> org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
> org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
> org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
> org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53)
> org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
> org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
> weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
> weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
> weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
> weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
> weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
> weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
> weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
> weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the seam-issues mailing list