[
https://issues.apache.org/jira/browse/OPENJPA-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039699#comment-13039699
]
Michael Dick commented on OPENJPA-2005:
---------------------------------------
Just checked in the changes to trunk. If you enable trace logging you'll still
see some messages - but at least they won't include the stack trace. If having
trace messages is an issue reopen the JIRA and I'll remove at least one of
them.
> PostgresDictionary.isOwnedSequence needs a null check
> -----------------------------------------------------
>
> Key: OPENJPA-2005
> URL: https://issues.apache.org/jira/browse/OPENJPA-2005
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.1.0
> Reporter: Mark Lilback
> Assignee: Michael Dick
> Priority: Minor
> Fix For: 2.2.0
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> In PostgresDictionary.java, Line 430 calls buildNames(strName) to get a
> String[][]. Right below this, a for loop references namePairs.length.
> However, buildNames can return null, which results in a NullPointerException.
> While this is inside a try/catch, it still fills my logs up with warning
> messages (10 stack traces at launch for a single table with a sequence).
> Skipping the loop when namePairs is null would solve this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
