[jboss-jira] [JBoss JIRA] (WFLY-2719) NullPointerException on first request after deployment using beans.xml
Jozef Hartinger (JIRA)
issues at jboss.org
Tue Jan 21 07:56:29 EST 2014
[ https://issues.jboss.org/browse/WFLY-2719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jozef Hartinger updated WFLY-2719:
----------------------------------
Fix Version/s: 8.0.0.Final
> NullPointerException on first request after deployment using beans.xml
> ----------------------------------------------------------------------
>
> Key: WFLY-2719
> URL: https://issues.jboss.org/browse/WFLY-2719
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, Web (Undertow)
> Affects Versions: 8.0.0.CR1
> Reporter: James Bodkin
> Assignee: Stuart Douglas
> Priority: Minor
> Fix For: 8.0.0.Final
>
> Attachments: dew.zip
>
>
> A NullPointerException occurs on the first request to the WildFly AS if the war package already exists and has been deployed via maven on both occasions causing an 500 Internal Server Error on the client.
> Removing the beans.xml from WEB-INF stops the error from occurring but services aren't injected.
> 02:36:11,177 ERROR [io.undertow.request] (default I/O-3) Blocking request failed HttpServerExchange{ GET /}: java.lang.NullPointerException
> at org.jboss.weld.context.http.HttpConversationContextImpl.getRequestAttribute(HttpConversationContextImpl.java:47)
> at org.jboss.weld.context.http.HttpConversationContextImpl.getRequestAttribute(HttpConversationContextImpl.java:13)
> at org.jboss.weld.context.AbstractConversationContext.copyConversationIdGeneratorAndConversationsToSession(AbstractConversationContext.java:177)
> at org.jboss.weld.context.AbstractConversationContext.sessionCreated(AbstractConversationContext.java:185)
> at org.jboss.weld.servlet.ConversationContextActivator.sessionCreated(ConversationContextActivator.java:187)
> at org.jboss.weld.servlet.HttpContextLifecycle.sessionCreated(HttpContextLifecycle.java:122)
> at org.jboss.weld.servlet.WeldInitialListener.sessionCreated(WeldInitialListener.java:107)
> at io.undertow.servlet.core.ApplicationListeners.sessionCreated(ApplicationListeners.java:256)
> at io.undertow.servlet.core.SessionListenerBridge.sessionCreated(SessionListenerBridge.java:36)
> at io.undertow.server.session.SessionListeners.sessionCreated(SessionListeners.java:32)
> at io.undertow.server.session.InMemorySessionManager.createSession(InMemorySessionManager.java:121)
> at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:677)
> at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:691)
> at io.undertow.servlet.handlers.SessionRestoringHandler.handleRequest(SessionRestoringHandler.java:110)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:56)
> at io.undertow.server.handlers.NameVirtualHostHandler.handleRequest(NameVirtualHostHandler.java:57)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:76)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:43)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:158)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:142)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:46)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.0.Beta4.jar:3.2.0.Beta4]
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:531) [xnio-nio-3.2.0.Beta4.jar:3.2.0.Beta4]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list