[ http://jira.jboss.com/jira/browse/JBMESSAGING-1200?page=all ] Clebert Suconic updated JBMESSAGING-1200: ----------------------------------------- Description: First time the Session.executor is called, it will initialized a thread. That thread will assume the parent's contextClassLoader, and it will hold it for the entire life cycle of the executor. This could be a problem on the application server, as the JCA adapter will cache the session, reusing it between different applications. When the session is used by another application, the executor's thread will have a reference to the previously used JAR, and ThreadContextClassLoader is used on ObjectInputStream operations. (ObjectInputStreamWithClassLoader). To fix this, we need to cleanup to set and clear the ContextClassLoader on every invocation. was: The Session.executor is holding the first ClassLoader reference on its ThreadContextClassLoader. This is also causing invalid classLoader usages when the first ClassLoader used was undeployed, and could lead to other problems on ObjectMessages and StreamMessages. (things like ClassNotFound becuase it's using the wrong classLoader on the executor). -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1200?page=all ] Clebert Suconic updated JBMESSAGING-1200: ----------------------------------------- Description: First time the Session.executor is called, it will initialized a thread. That thread will assume the parent's contextClassLoader, and it will hold it for the entire life cycle of the executor. This could be a problem on the application server, as the JCA adapter will cache the session, reusing it between different applications. When the session is used by another application, the executor's thread will have a reference to the previously used JAR, and ThreadContextClassLoader is used on ObjectInputStream operations. (ObjectInputStreamWithClassLoader). This pattern will also cause problems when the application is undeployed. When the Session is reused again it will have the reference to an invalid classLoader, what could lead to uncaught exception on the ClientConsumer, what could leave messages in some uncertain condition. To fix this, we need to set and clear the ContextClassLoader on every invocation. was: First time the Session.executor is called, it will initialized a thread. That thread will assume the parent's contextClassLoader, and it will hold it for the entire life cycle of the executor. This could be a problem on the application server, as the JCA adapter will cache the session, reusing it between different applications. When the session is used by another application, the executor's thread will have a reference to the previously used JAR, and ThreadContextClassLoader is used on ObjectInputStream operations. (ObjectInputStreamWithClassLoader). This pattern will also cause problems when the application is undeployed. When the Session is reused again it will have the reference to an invalid classLoader, what could lead to uncaught exception on the ClientConsumer, what could leave messages in some uncertain condition. To fix this, we need to cleanup to set and clear the ContextClassLoader on every invocation. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1200?page=all ] Tim Fox reopened JBMESSAGING-1200: ---------------------------------- -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1200?page=all ] Tim Fox closed JBMESSAGING-1200. -------------------------------- Resolution: Done -- 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