[
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.
Load balancing configuration can result in extraneous "invalid
session" messages
--------------------------------------------------------------------------------
Key: TEIID-2172
URL:
https://issues.jboss.org/browse/TEIID-2172
Project: Teiid
Issue Type: Bug
Components: JDBC Driver, Server
Affects Versions: 7.4.4
Environment: Clustered environment with load balancing enabled for the Teiid data
source
Reporter: Marc Shirley
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.2
When set up in a load balancing configuration with "SET NEW INSTANCE" as the
check valid connection SQL in the datasource definition, repeated messages indicating an
invalid session are created, similar to:
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.
Not sure if this would be a defect in regards to the conditions that are resulting in the
messages to be generated (ie, the old session id shouldn't be being reused), or an
enhancement to clarify or adjust the log message or priority to indicate whether this will
actually affect the query being submitted.
--
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