March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3468) JMS Connection starts ping thread before ClientID is set resulting in the ClientMonitorInterceptor to close the connection after client timeout

by Francis Labaere (JIRA)

JMS Connection starts ping thread before ClientID is set resulting in the ClientMonitorInterceptor to close the connection after client timeout ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3468 URL: http://jira.jboss.com/jira/browse/JBAS-3468 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.2 Final Environment: Windows XP Reporter: Francis Labaere Assigned To: Adrian Brock Priority: Minor Fix For: JBossAS-4.0.5.GA When creating a JMS connection using HTTPConnectionFactory for a user without preconfigured ClientID, mq.Connection starts the ping thread before the ClientID of the Connection is set (explicitely using setClientID or implicitely). The ping thread starts pinging the server with ConnectionToken/@ClientID equal to null. The ClientMonitorInterceptor adds this ConnectionToken to its clients HashMap. When the ClientID of the Connection is set (e.g. to XXX) later, the next call to the server will add the updated ConnectionToken to the ClientMonitorInterceptor's clients HashMap with the same SessionID as the previous one. When the ClientMonitorInterceptor checks timedout clients, it will close the session for the first ConnectionToken. Subsequent calls to the server will generate exceptions: User session is not valid. On the JBoss server, the ClientMonitorInterceptor closes the client with ConnectionToken:null/0e9cae0c268a6d4aeb393f40552ce059 2006-08-04 11:53:12,261 DEBUG [org.jboss.mq.server.ClientMonitorInterceptor] Checking for timedout clients. 2006-08-04 11:53:12,261 DEBUG [org.jboss.mq.server.ClientMonitorInterceptor] Disconnecting client due to inactivity timeout: ConnectionToken:null/0e9cae0c268a6d4aeb393f40552ce059 2006-08-04 11:53:12,261 TRACE [org.jboss.mq.il.http.HTTPClientIL] close() 2006-08-04 11:53:12,261 TRACE [org.jboss.mq.il.http.HTTPClientILStorageQueue] getInstance() 2006-08-04 11:53:12,261 TRACE [org.jboss.mq.il.http.HTTPClientILStorageQueue] put(HTTPILRequest asynchClose(), String 105) 2006-08-04 11:53:12,261 DEBUG [org.jboss.mq.il.http.HTTPClientILStorageQueue] ClientIL #105 has existing storage queue, adding request to it. Later (e.g. after sending a JMS message) the SecurityInterceptor checks the connection with the same sessionID ,but different ClientID: ConnectionToken:ID:4/0e9cae0c268a6d4aeb393f40552ce059 subId=-2147483648 2006-08-04 13:17:57,294 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] Checking receive authorize on ConnectionToken:ID:4/0e9cae0c268a6d4aeb393f40552ce059 subId=-2147483648 2006-08-04 13:17:57,294 TRACE [org.jboss.mq.server.TracingInterceptor] EXCEPTION : receive: javax.jms.JMSSecurityException: User session is not valid at org.jboss.mq.security.SecurityManager.authorize(SecurityManager.java:230) at org.jboss.mq.security.ServerSecurityInterceptor.authorizeRead(ServerSecurityInterceptor.java:233) at org.jboss.mq.security.ServerSecurityInterceptor.receive(ServerSecurityInterceptor.java:98) at org.jboss.mq.server.ClientMonitorInterceptor.receive(ClientMonitorInterceptor.java:231) at org.jboss.mq.server.TracingInterceptor.receive(TracingInterceptor.java:579) at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:226) at org.jboss.mq.il.http.servlet.HTTPServerILServlet.processRequest(HTTPServerILServlet.java:204) at org.jboss.mq.il.http.servlet.HTTPServerILServlet.doPost(HTTPServerILServlet.java:287) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) 2006-08-04 13:17:57,294 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : receive 2006-08-04 13:17:57,294 DEBUG [org.jboss.mq.il.http.servlet.HTTPServerILServlet] Threw an exception of type 'javax.jms.JMSSecurityException' with a message of 'User session is not valid.' This exception is being propogated to the client as a HTTPILResponse. 2006-08-04 13:17:57,404 TRACE [org.jboss.mq.il.http.servlet.HTTPServerILServlet] doPost() defers to processRequest, see the parameters in its trace. 2006-08-04 13:17:57,404 TRACE [org.jboss.mq.il.http.servlet.HTTPServerILServlet] processRequest(HttpServletRequest org.apache.catalina.connector.RequestFacade@2bac2b, HttpServletResponse org.apache.catalina.connector.ResponseFacade@1343c2a) On the Client side: following stacktrace is visible 13:17:57 [MessageListenerThread - MyTopic] WARN org.jboss.mq.SpyMessageConsumer - Message consumer closing due to error in listening thread. javax.jms.JMSSecurityException: User session is not valid at org.jboss.mq.security.SecurityManager.authorize(SecurityManager.java:230) at org.jboss.mq.security.ServerSecurityInterceptor.authorizeRead(ServerSecurityInterceptor.java:233) at org.jboss.mq.security.ServerSecurityInterceptor.receive(ServerSecurityInterceptor.java:98) at org.jboss.mq.server.ClientMonitorInterceptor.receive(ClientMonitorInterceptor.java:231) at org.jboss.mq.server.TracingInterceptor.receive(TracingInterceptor.java:579) at org.jboss.mq.server.JMSServerInvoker.receive(JMSServerInvoker.java:226) at org.jboss.mq.il.http.servlet.HTTPServerILServlet.processRequest(HTTPServerILServlet.java:204) at org.jboss.mq.il.http.servlet.HTTPServerILServlet.doPost(HTTPServerILServlet.java:287) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:307) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:385) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) mq.Connection should start the ping thread after the ClientID is known. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

5
8
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-155) java.io.IOException: No context factory for vfsfile

by Scott M Stark (JIRA)

java.io.IOException: No context factory for vfsfile --------------------------------------------------- Key: JBMICROCONT-155 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-155 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 The following org.jboss.test.virtual.test.FileVFSUnitTestCase: /** * Test that one can go from a file uri to VirtualFile and obtain the * same VirtualFile using VirtualFile vfsfile uri * @throws Exception */ public void testVFSFileURIFactory() throws Exception { URL rootURL = getClass().getProtectionDomain().getCodeSource().getLocation(); VFS rootVFS0 = VFS.getVFS(rootURL.toURI()); VirtualFile root0 = rootVFS0.getRoot(); VFS rootVFS1 = VFS.getVFS(root0.toURI()); VirtualFile root1 = rootVFS1.getRoot(); assertEquals(root0, root1); } fails with: java.io.IOException: No context factory for vfsfile:/home/svn/JBossMC/vfs/target/test-classes/ at org.jboss.virtual.VFS.getVFS(VFS.java:83) at org.jboss.test.virtual.test.FileVFSUnitTestCase.testVFSFileURIFactory(FileVFSUnitTestCase.java:104) The VFSContextFactory uri mappings need to be updated to include the vfs* forms of the known handlers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker

by Ron Sigal (JIRA)

Check if jbossweb can replace tomcat jars for the http server invoker --------------------------------------------------------------------- Key: JBREM-713 URL: http://jira.jboss.com/jira/browse/JBREM-713 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Bluto) Reporter: Ron Sigal Assigned To: Tom Elrod Fix For: 2.2.0.Beta2 (Bluto) See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker. See JBREM-705. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

1
6
0 / 0

[JBoss JIRA] Created: (BPEL-204) Add org.jbpm.webapp.servlet.UploadServlet as part of the bpel distribution.

by Kartik Mecheri (JIRA)

Add org.jbpm.webapp.servlet.UploadServlet as part of the bpel distribution. ---------------------------------------------------------------------------- Key: BPEL-204 URL: http://jira.jboss.com/jira/browse/BPEL-204 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kartik Mecheri Assigned To: Alejandro Guizar Please add org.jbpm.webapp.servlet.UploadServlet as part of the bpel distribution. This will enable us to deploy a bpel process on a remote server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-675) Problems with Servlet invoker

by Tom Elrod (JIRA)

Problems with Servlet invoker ----------------------------- Key: JBREM-675 URL: http://jira.jboss.com/jira/browse/JBREM-675 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 1.4.6.GA, 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Attachments: ServletServerInvoker.java Several problems with servlet invoker: 1) There can't be two servlet invokers (it's necessary, for example, if you want to use them for JBoss Messagning and for EJBs - they require separate connectors) because ObjectName is hard-coded in ServletServerInvoker.java 2) Null returns from invokers are sent to client as empty 204 responses and custom marshallers have no change to process return value. This breaks JBoss Messaging which expects that EVERY message contains at least two bytes (version tag and format tag). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-835) Simple test suite configuration

by Tim Fox (JIRA)

Simple test suite configuration ------------------------------- Key: JBMESSAGING-835 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-835 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta2 Reporter: Tim Fox Assigned To: Ovidiu Feodorov Fix For: 1.2.0.GA The test suite configuration needs to be simplified. Currently, the same settings can be specified in enrvironment variables, properties file, build.xml, system properties, and in container.xml, with a complex precedence hierarchy determining which setting overrides another setting. Also some settings are specified redundantly - e.g. test database is inferred from the jdbc connection url but is already specified in the container.xml. We should have one place and one place only where configuration settings are specified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-754) Allow for multiple service containes to be started in same VM

by Tim Fox (JIRA)

Allow for multiple service containes to be started in same VM ------------------------------------------------------------- Key: JBMESSAGING-754 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-754 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.CR1 ServerManagement currently allows multiple remote ServiceContainers to be started and stopped, but it does not allow multiple ServiceContainers to be started and stopped in the same VM. This means tests like the bridge tests can only be run in remote mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-574) In memory replication of persistent messages

by Tim Fox (JIRA)

In memory replication of persistent messages -------------------------------------------- Key: JBMESSAGING-574 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-574 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 We should enable an option whereby persisted messages can be replicated between nodes rather than persisted to disk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-3704) Add a notion of available interfaces to org.jboss.test.util.server.*

by Scott M Stark (JIRA)

Add a notion of available interfaces to org.jboss.test.util.server.* -------------------------------------------------------------------- Key: JBAS-3704 URL: http://jira.jboss.com/jira/browse/JBAS-3704 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Reporter: Scott M Stark Fix For: JBossAS-4.0.6.CR1 An issue with automating testing involving binding to specific addresses is that there is no predefined set of properties a testsuite descriptor can reference. The qa env has MYTESTIP_1 type of env vars set, and java 1.4.2+ has java.net.NetworkInterface, that could be used as the basis for defining jboss.server.iface.0..N system properties that configurations could rely on for setting one or more bind interfaces. We need to add this functionality to the server startup tasks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

5
10
0 / 0

[JBoss JIRA] Created: (JBREM-718) Support for more message-based protocols

by Mark Little (JIRA)

Support for more message-based protocols ---------------------------------------- Key: JBREM-718 URL: http://jira.jboss.com/jira/browse/JBREM-718 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Little Assigned To: Tom Elrod It would be good if Remoting supported more message-oriented protocols, such as JMS, FTP, email etc. RPC semantics could be layered on those, or simply say that the one-way approach is all that is supported. One slight worry might be if a supported plugin implementation for JBoss Remoting itself used JBoss Remoting (e.g., plugging JBoss Messaging into JBoss Remoting). This may set up some interesting circularities. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 6 months

4
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007