Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JBJCA-1341] Account for additional DB2 FATAL connection errors #611

Merged
merged 1 commit into from Mar 24, 2017

Conversation

iweiss
Copy link
Contributor

@iweiss iweiss commented Mar 17, 2017

Issue: https://issues.jboss.org/browse/JBJCA-1341

I refactored the code a bit to make it less prone to issues.

@simkam
Copy link
Contributor

simkam commented Mar 17, 2017

I think it should trim both messages, from Exception and from StringTokenizer. Also I think contains won't work now as configured messages are changed to upper case. Also contains can match two different messages with the same base, I think it would be better to use equals

@iweiss
Copy link
Contributor Author

iweiss commented Mar 17, 2017

I see. Trimming shouldn't make a difference since contains won't care for trailing spaces, the custom messages will already being trimmed. About the upper case, you are right. Let me refresh this.

@maeste maeste merged commit 6703c57 into ironjacamar:1.0 Mar 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants