[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Marc Shirley updated TEIID-2172: -------------------------------- Steps to Reproduce: (was: To reproduce: 1) Install to the production profile 2) Create two profiles/nodes from the enabled profile (for example, copy the 'production' profile to 'prod1' and 'prod2') 3) Place the contents of the included deploy directory into the deploy directory of the two nodes created in step 2 4) Edit the Teiid-ds.xml to point the datasource to the connection details for the two nodes, 'prod1' and 'prod2' 5) Start both nodes run.sh -c prod1 -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-default run.sh -c prod2 -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-01 6) Run the attached client in 'JMSClusterClient.jar', substituting the appropriate addresses for nodes 'prod1' and 'prod2' java -jar JMSClusterClient.jar 127.0.0.1:1100 127.0.0.1:1200 7) Observe the server.log entries to view the recorded invalid session messages with mixed session ids. In some brief testing it appears to be occurring at a frequency of 2-5% (5-10 occurrences in the test's 200 connections). bq. 2012-08-24 10:39:58,818 WARN [org.teiid.SECURITY] (New I/O server worker #1-3) Processing exception 'The specified session ID "5Wt/6zzmsLy2" is invalid. It cannot be found in the userbase.' for session R8ZxYqjZzf/S. Exception type org.teiid.client.security.InvalidSessionException thrown from org.teiid.services.SessionServiceImpl.getSessionInfo(SessionServiceImpl.java:315). Enable more detailed logging to see the entire stacktrace.) -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2172: ---------------------------------- Component/s: Server -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2172: ---------------------------------- Priority: Critical (was: Major) Workaround Description: Set the org.teiid.sockets.maxCachedInstances to 0 in teiid-client-settings.properties on the client classpath. Workaround: Workaround Exists There is actually a bad interaction between instance pooling and load balancing causing this exception. The workaround is to disable instance pooling, but given the increase in cost of creating new connections I'm upping the priority to critical. -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2172: ---------------------------------- Workaround Description: Set the org.teiid.sockets.maxCachedInstances property to 0 as a system property or in teiid-client-settings.properties on the client classpath. (was: Set the org.teiid.sockets.maxCachedInstances to 0 in teiid-client-settings.properties on the client classpath.) -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Steven Hawkins reopened TEIID-2172: ----------------------------------- The workaround is not valid. Because the session is not disassociated, setting the cached instances to 0 will result in the sessions being logged off prematurely. -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2172. ----------------------------------- Resolution: Done opted for proactively disassociating of the session via assertIdentity(null). that does add overhead to load-balancing as an additional synch remote call is being made. on the other hand it means that server will rarely accumulate invalid sessions. another approach would have been to not do a logoff in the socketclientinstance disconnection, however that would lead more orphan sessions waiting to be cleaned up via the sessionservice monitor. this behavior could be made configurable later if seems necessary to remove the extra remote call. also tightened ping monitoring bounds on the server side to kill after 3 missed pings instead of 5 and to monitor every 4 minutes instead of 10. -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2172: ------------------------------------------- Bugzilla Update: Perform -- 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

[ https://issues.jboss.org/browse/TEIID-2172?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2172. --------------------------------- -- 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