[
https://issues.apache.org/jira/browse/OPENJPA-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Bauer reopened OPENJPA-2236:
-----------------------------------
> Trace of connection info can cause class transform/enhancement to fail
> ----------------------------------------------------------------------
>
> Key: OPENJPA-2236
> URL: https://issues.apache.org/jira/browse/OPENJPA-2236
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
> Fix For: 2.3.0, 2.2.1
>
>
> While transforming persistent classes, if a specific DBDictionary is not
> provided, OpenJPA attempts to detect and set up a dictionary. Within this
> process, DBDictionary.connectedConfiguration() is called (to determine the DB
> type) when a connection is obtained. If trace is enabled, information about
> the connection is traced. I hit a case where one of the methods that is
> called on the connection to gather trace data threw an exception, resulting
> in classes not being enhanced. The simple (but not always possible)
> workaround is to specify the db dictionary type. Regardless, a trace point
> should not cause a catastrophic failure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
