You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jamie goodyear (JIRA)" <ji...@apache.org> on 2010/02/24 15:24:28 UTC

[jira] Created: (FELIX-2129) [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.

[Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.
--------------------------------------------------------------------------------

                 Key: FELIX-2129
                 URL: https://issues.apache.org/jira/browse/FELIX-2129
             Project: Felix
          Issue Type: Bug
          Components: Karaf
         Environment: Oracle XE Database backend for Karaf JDBC locking.
            Reporter: Jamie goodyear


Possible hang with slave instances of Karaf when using Oracle JDBC lock.

If we start up the master and slave as normal, then try to stop the slave, it does not release its attempted JDBC lock, and therefore hangs during shutdown. If we then stop the master, the slave throws an error and finally exits.


The problem is in the FOR UPDATE statement in setUpdateCursor, adding NOWAIT resolves the issue.

I'll be supplying a patch for this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (FELIX-2129) [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Custine resolved FELIX-2129.
----------------------------------

       Resolution: Fixed
    Fix Version/s: karaf 1.6.0

> [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> --------------------------------------------------------------------------------
>
>                 Key: FELIX-2129
>                 URL: https://issues.apache.org/jira/browse/FELIX-2129
>             Project: Felix
>          Issue Type: Bug
>          Components: Karaf
>         Environment: Oracle XE Database backend for Karaf JDBC locking.
>            Reporter: Jamie goodyear
>            Assignee: Chris Custine
>             Fix For: karaf 1.6.0
>
>         Attachments: felix2129.txt
>
>
> Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> If we start up the master and slave as normal, then try to stop the slave, it does not release its attempted JDBC lock, and therefore hangs during shutdown. If we then stop the master, the slave throws an error and finally exits.
> The problem is in the FOR UPDATE statement in setUpdateCursor, adding NOWAIT resolves the issue.
> I'll be supplying a patch for this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FELIX-2129) [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear updated FELIX-2129:
----------------------------------

    Attachment: felix2129.txt

File: felix2129.txt

Contains a one line change to add the NOWAIT directive to the FOR UPDATE statement.

This will allow slave instances to gracefully skip blocking on a locked table.

> [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> --------------------------------------------------------------------------------
>
>                 Key: FELIX-2129
>                 URL: https://issues.apache.org/jira/browse/FELIX-2129
>             Project: Felix
>          Issue Type: Bug
>          Components: Karaf
>         Environment: Oracle XE Database backend for Karaf JDBC locking.
>            Reporter: Jamie goodyear
>         Attachments: felix2129.txt
>
>
> Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> If we start up the master and slave as normal, then try to stop the slave, it does not release its attempted JDBC lock, and therefore hangs during shutdown. If we then stop the master, the slave throws an error and finally exits.
> The problem is in the FOR UPDATE statement in setUpdateCursor, adding NOWAIT resolves the issue.
> I'll be supplying a patch for this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (FELIX-2129) [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Custine reassigned FELIX-2129:
------------------------------------

    Assignee: Chris Custine

> [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> --------------------------------------------------------------------------------
>
>                 Key: FELIX-2129
>                 URL: https://issues.apache.org/jira/browse/FELIX-2129
>             Project: Felix
>          Issue Type: Bug
>          Components: Karaf
>         Environment: Oracle XE Database backend for Karaf JDBC locking.
>            Reporter: Jamie goodyear
>            Assignee: Chris Custine
>         Attachments: felix2129.txt
>
>
> Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> If we start up the master and slave as normal, then try to stop the slave, it does not release its attempted JDBC lock, and therefore hangs during shutdown. If we then stop the master, the slave throws an error and finally exits.
> The problem is in the FOR UPDATE statement in setUpdateCursor, adding NOWAIT resolves the issue.
> I'll be supplying a patch for this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FELIX-2129) [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840573#action_12840573 ] 

Chris Custine commented on FELIX-2129:
--------------------------------------

Applied patch from Jamie Goodyear.

> [Karaf] Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> --------------------------------------------------------------------------------
>
>                 Key: FELIX-2129
>                 URL: https://issues.apache.org/jira/browse/FELIX-2129
>             Project: Felix
>          Issue Type: Bug
>          Components: Karaf
>         Environment: Oracle XE Database backend for Karaf JDBC locking.
>            Reporter: Jamie goodyear
>            Assignee: Chris Custine
>             Fix For: karaf 1.6.0
>
>         Attachments: felix2129.txt
>
>
> Possible hang with slave instances of Karaf when using Oracle JDBC lock.
> If we start up the master and slave as normal, then try to stop the slave, it does not release its attempted JDBC lock, and therefore hangs during shutdown. If we then stop the master, the slave throws an error and finally exits.
> The problem is in the FOR UPDATE statement in setUpdateCursor, adding NOWAIT resolves the issue.
> I'll be supplying a patch for this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.