[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Servlet transport problem
trustin
do-not-reply at jboss.com
Tue Apr 28 17:53:46 EDT 2009
The tunneling client now works fine without JBAS-6814 fixed - CPU stays calm.
One remaining question though is: why are two HTTP connections created when I run the 'servlet-transport' example?
The first connection is created by ConnectionFactory.createConnection() in step 4, and the second connection is created by Connection.createSession() in step 5. Is this expected? It seems like the two connections are closed correctly in the end though.
AND I also have found a different issue perhaps related with JBossWeb. It throws NPE on undeploy:
10:10:08,230 WARNING [HttpTunnelingChannelHandler] Unexpected exception
| java.lang.NullPointerException
| at org.apache.catalina.session.StandardSession.expire(StandardSession.java:730)
| at org.apache.catalina.session.StandardSession.expire(StandardSession.java:660)
| at org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1115)
| at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:150)
| at org.jboss.netty.channel.socket.http.HttpTunnelingChannelHandler.channelClosed(HttpTunnelingChannelHandler.java:144)
| at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:105)
| at org.jboss.netty.channel.Channels.fireChannelClosed(Channels.java:564)
| at org.jboss.netty.channel.local.DefaultLocalChannel.closeNow(DefaultLocalChannel.java:102)
| at org.jboss.netty.channel.local.LocalClientChannelSink.eventSunk(LocalClientChannelSink.java:66)
| at org.jboss.netty.channel.Channels.close(Channels.java:1043)
| at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:185)
| at org.jboss.netty.channel.socket.http.HttpTunnelingServlet.streamResponse(HttpTunnelingServlet.java:99)
| at org.jboss.netty.channel.socket.http.HttpTunnelingServlet.doRequest(HttpTunnelingServlet.java:62)
| at org.jboss.netty.channel.socket.http.HttpTunnelingServlet.doPost(HttpTunnelingServlet.java:195)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
Of course, it does not affect JBM because the connections were closed already.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227370#4227370
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227370
More information about the jboss-dev-forums
mailing list