Appclient applications fail with messge: Reason : [C4052]: Client ID is already in use

ari-ban / test2

0 stars 0 forks source link

Appclient applications fail with messge: Reason : [C4052]: Client ID is already in use #3

Closed arinban closed 14 years ago

arinban commented 19 years ago

We have a test application that use a connection factory with a configfured clientID. Both server side component (ejb and web components) and appclient use this connection factory. The test application , however, makes sure that no two connections are open at the same time in either of the components.

However when the test application is executed multiple times for few minutes, it fails eventually throwing the following exception message.

Error in allocating a connection. Cause: [C4052]: Client ID is already in use

The exception happens only in the appclient component.

Environment

Operating System: All Platform: All

Affected Versions

[0.9]

arinban commented 6 years ago

Issue Imported From: https://github.com/ari-ban/test1/issues/3
Original Issue Raised By:@arinban
Original Issue Assigned To: @glassfishrobot
Original Issue Closed By:@arinban

arinban commented 6 years ago

@arinban Commented

Issue Imported From: https://github.com/ari-ban/glassfish-genericjmsra/issues/3
Original Issue Raised By:@arinban
Original Issue Assigned To: @glassfishrobot
Original Issue Closed By:@arinban

arinban commented 6 years ago

@arinban Commented @arinban Commented

Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/3
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To: @glassfishrobot
Original Issue Closed By:@glassfishrobot

arinban commented 19 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented Reported by binod

arinban commented 19 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: The max-pool-size of the connection pool involved is just 1 and each connection obtained from the pool that has a clientID set on it will be destroyed as soon as application closes the connection. Thus pool does not keep a connection with a clientID set on it.

However the resizer thread of connection pool gets activated after some time (as per pool config) and that causes a connection in the pool to have use a clientID. Subsequently in appclient when a connection is obtained , a connection will be created there also with same clientID causing the exception.

arinban commented 19 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: Modified RA to set clientID on the underlying physical connection, only when it is accessed for the first time. Thus even if the resizer thread creates the ManagedConnection, connection will not have clientID set on it. Effectively allowing appclient to use the clientID.

arinban commented 19 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented binod said: Adding fixed1.0 keyword

arinban commented 19 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented Was assigned to binod

arinban commented 7 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-3

arinban commented 14 years ago

@arinban Commented @arinban Commented @glassfishrobot Commented Marked as fixed on Sunday, September 5th 2010, 8:21:08 pm