-
1. Re: IJ000612: Destroying connection that could not be successfully matched
ramiseesniblic Jul 6, 2015 3:54 AM (in response to ramiseesniblic)Can anyone suggest any reasons / fixes for this?
-
2. Re: IJ000612: Destroying connection that could not be successfully matched
abhijithumbe Jul 6, 2015 4:18 AM (in response to ramiseesniblic)When the ping invocation in isValidConnection() -- org/jboss/jca/adapters/jdbc/extensions/mysql/MySQLValidConnectionChecker.java fails, it returns an SQLException the message Destroying connection that could not be successfully matched is logged.
It is good to use validate-on-match rather than background-validation to reduce the risk at application code encountering a connection failure (validate-on-match will be enforced on each connection request whereas background-validation runs only periodically). The use of background validation is recommended only in cases where a very high frequency of connection requests occurs (in which case validation might be costly) but background validation has a higher risk that the application code may be given an invalid connection (since no check is done at the time of the request).
-
3. Re: IJ000612: Destroying connection that could not be successfully matched
ramiseesniblic Jul 6, 2015 4:25 AM (in response to abhijithumbe)Hello. Thank you for your reply.
I think that this message is not being caused by a SQLException as the warning is from the Websphere MQ connection pool. (Which is a resource adapter). Is there any way that I can configure connection validation in the "connection-definition" section of my resource adapter?
-
4. Re: IJ000612: Destroying connection that could not be successfully matched
ramiseesniblic Sep 1, 2015 7:04 AM (in response to ramiseesniblic)Does anyone else have an in-site into this warning?
-
5. Re: IJ000612: Destroying connection that could not be successfully matched
ramiseesniblic Sep 8, 2015 3:40 AM (in response to ramiseesniblic)Ok. Found the issue. It was when I was opening and then immediately closing the connection the WSMQ without sending any data. For some unknown reason, this was causing the warning to appear.