[
https://issues.jboss.org/browse/JBJCA-1341?page=com.atlassian.jira.plugin...
]
Martin Simka edited comment on JBJCA-1341 at 3/13/17 9:13 AM:
--------------------------------------------------------------
I'm working on test for this and I think it would be better to trim each configured
message and also each message obtained from exception. Also there is obvious limitation
that configured message cannot contain char *_,_*
[~iweiss] [~maeste] What do you think about message trimming?
was (Author: simkam):
I'm working on test for this and I think it would be better to trim each configured
message and also each message obtained from exception. Also there is obvious limitation
that configured message cannot contain char *_,_*
Account for additional DB2 FATAL connection errors
--------------------------------------------------
Key: JBJCA-1341
URL:
https://issues.jboss.org/browse/JBJCA-1341
Project: IronJacamar
Issue Type: Enhancement
Components: Validator
Reporter: Ingo Weiss
Assignee: Ingo Weiss
Original Estimate: 2 days
Time Spent: 2 days
Remaining Estimate: 0 minutes
Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException.
Not all -99999 errors are fatal. For those variations that are known to be fatal, a
check should be added to treat as such.
One example would be the -99999 error that indicates "Connection is closed"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)