Java deadlock between LogicalConnection40 and ClientXAConnection40
--
Key: DERBY-5560
URL: https://issues.apache.org/jira/browse/DERBY-5560
Project: Derby
Issue Type: Bug
Race conditions in LogicalConnection checking for a null physical connection
Key: DERBY-5561
URL: https://issues.apache.org/jira/browse/DERBY-5561
Project: Derby
I created https://issues.apache.org/jira/browse/DERBY-5560 and am seeing this
in production.
Basically what is happening is that the LogicalConnection.close() is being
called which attempts to recycle the physical connection by calling
ClientPooledConnection.recycleConnection(). At the same
[Auto-generated mail]
*Daily* 1224946/2011-12-27 18:00:07 MET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.7*
lin
01471014710 0 .% suitesAll
01515 0 .% jdbcapiAutoLoad
014
[
https://issues.apache.org/jira/browse/DERBY-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176727#comment-13176727
]
Kathey Marsden commented on DERBY-5561:
---
Do you have multiple threads accessing the
There are two threads accessing the same connection but this is because of the
connection pool. When you configure a connection pool in Glassfish you can
configure error handling on the pool. One option that can be configured is to
configure the connection pool such that any error on any
[
https://issues.apache.org/jira/browse/DERBY-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176747#comment-13176747
]
Kathey Marsden commented on DERBY-5561:
---
Makes sense. Thanks for the explanation.
[
https://issues.apache.org/jira/browse/DERBY-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176749#comment-13176749
]
Brett Bergquist commented on DERBY-5560:
Partial stack trace of first thread:
[
https://issues.apache.org/jira/browse/DERBY-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176753#comment-13176753
]
Kathey Marsden commented on DERBY-5561:
---
Just realized Brett's explanation is not in
I have to get in the habit of putting the responses and stuff in the Jira. I
did not realize that your message was from updating the Jira and just hit
Reply. I will be better in the future but I am still an egg :)
-Original Message-
From: Kathey Marsden (Commented) (JIRA)
[
https://issues.apache.org/jira/browse/DERBY-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176764#comment-13176764
]
Kathey Marsden commented on DERBY-5560:
---
Some discussion regarding this issue is in
On 12/28/2011 10:52 AM, Bergquist, Brett wrote:
I have to get in the habit of putting the responses and stuff in the Jira. I
did not realize that your message was from updating the Jira and just hit
Reply. I will be better in the future but I am still an egg :)
No worries. It is nice to have
[
https://issues.apache.org/jira/browse/DERBY-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176800#comment-13176800
]
Brett Bergquist commented on DERBY-5560:
From my looking at the code, the
I am pursuing a bug where when the Network Client receives a Lock Timeout
exception in
PreparedStatement.java:
public int executeUpdate() throws SQLException {
try
{
synchronized (connection_) {
if (agent_.loggingEnabled()) {
On Wed, Dec 28, 2011 at 4:08 PM, Bergquist, Brett bbergqu...@canoga.com wrote:
I am pursuing a bug where when the Network Client receives a Lock Timeout
exception in
PreparedStatement.java:
public int executeUpdate() throws SQLException {
try
{
[
https://issues.apache.org/jira/browse/DERBY-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13176912#comment-13176912
]
Myrna van Lunteren commented on DERBY-5558:
---
The need for setting emma.active=
On 12/28/2011 4:08 PM, Bergquist, Brett wrote:
I am pursuing a bug where when the Network Client receives a Lock
Timeout exception in
if (agent_.loggingEnabled()) {
agent_.logWriter_.traceEntry(this, executeUpdate);
}
This code fails
17 matches
Mail list logo
