[jira] [Commented] (OFBIZ-11312) DatabaseUtil.getColumnInfo(...) does not retrieve primary keys due to connection-locks

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-11312) DatabaseUtil.getColumnInfo(...) does not retrieve primary keys due to connection-locks

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045219#comment-17045219 ]

ASF subversion and git services commented on OFBIZ-11312:
---------------------------------------------------------

Commit 4697bf5faa7672152e9d59f49456ebb03a950645 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=4697bf5 ]

Fixed: DatabaseUtil.getColumnInfo(...) does not retrieve primary keys due to
connection-locks
(OFBIZ-11312)

The method DatabaseUtil.getColumnInfo(...) uses an elaborate algorithm using a
List<Future<AbstractCountingCallable>> object. This does not work properly as it
runs into connection-locks. When debugging the error does not occur. I assume
that the slower pace of debugging prevents the error.

Thanks: Benjamin Jugl


> DatabaseUtil.getColumnInfo(...) does not retrieve primary keys due to connection-locks
> --------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-11312
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11312
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework/webtools
>    Affects Versions: Trunk
>            Reporter: Benjamin Jugl
>            Assignee: Jacques Le Roux
>            Priority: Minor
>         Attachments: OFBIZ-11312_getColumnInfo_connection_locks_001.patch
>
>
> The method DatabaseUtil.getColumnInfo(...) uses an elaborate algorithm using a  List<Future<AbstractCountingCallable>> object. This does not work properly as it runs into connection-locks. When debugging the error does not occur. I assume that the slower pace of debugging prevents the error.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)