You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Thomas McKiernan (JIRA)" <ji...@apache.org> on 2006/06/22 09:04:31 UTC

[jira] Created: (SANDESHA2-4) shutdown might finish before threads stop

shutdown might finish before threads stop
-----------------------------------------

         Key: SANDESHA2-4
         URL: http://issues.apache.org/jira/browse/SANDESHA2-4
     Project: Apache Sandesha2
        Type: Improvement

 Environment: WinXP
    Reporter: Thomas McKiernan
    Priority: Minor


At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


Re: [jira] Updated: (SANDESHA2-4) shutdown might finish before threads stop

Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Thomas,

This patch seems to hv been created from an old revision and cannot be
applied to the current code base. Could you send a new one based on the
latest revision.

Chamikara


On 6/22/06, Thomas McKiernan (JIRA) <ji...@apache.org> wrote:
>
>      [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]
>
> Thomas McKiernan updated SANDESHA2-4:
> -------------------------------------
>
>     Attachment: patch.txt
>
> this is a fix for the problem
>
> > shutdown might finish before threads stop
> > -----------------------------------------
> >
> >          Key: SANDESHA2-4
> >          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
> >      Project: Apache Sandesha2
> >         Type: Improvement
>
> >  Environment: WinXP
> >     Reporter: Thomas McKiernan
> >     Priority: Minor
> >  Attachments: patch.txt
> >
> > At the moment it is possible for the module shutdown path to return
> while the Sender and Invoker threads are still running.
> > This means that even after the module has shutdown transactional work
> might be attempted. The effects of this are unpredictable and should be
> avoided.
> > Therefore I suggest that the shutdown path is changed so that, if the
> server and/or invoker threads are running, it blocks until they have
> finished.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>

Re: [jira] Updated: (SANDESHA2-4) shutdown might finish before threads stop

Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Thomas,

This patch seems to hv been created from an old revision and cannot be
applied to the current code base. Could you send a new one based on the
latest revision.

Chamikara


On 6/22/06, Thomas McKiernan (JIRA) <ji...@apache.org> wrote:
>
>      [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]
>
> Thomas McKiernan updated SANDESHA2-4:
> -------------------------------------
>
>     Attachment: patch.txt
>
> this is a fix for the problem
>
> > shutdown might finish before threads stop
> > -----------------------------------------
> >
> >          Key: SANDESHA2-4
> >          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
> >      Project: Apache Sandesha2
> >         Type: Improvement
>
> >  Environment: WinXP
> >     Reporter: Thomas McKiernan
> >     Priority: Minor
> >  Attachments: patch.txt
> >
> > At the moment it is possible for the module shutdown path to return
> while the Sender and Invoker threads are still running.
> > This means that even after the module has shutdown transactional work
> might be attempted. The effects of this are unpredictable and should be
> avoided.
> > Therefore I suggest that the shutdown path is changed so that, if the
> server and/or invoker threads are running, it blocks until they have
> finished.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>

[jira] Resolved: (SANDESHA2-4) shutdown might finish before threads stop

Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]
     
Chamikara Jayalath resolved SANDESHA2-4:
----------------------------------------

    Resolution: Fixed

Issue was resolved after applying the patch from Thomas

> shutdown might finish before threads stop
> -----------------------------------------
>
>          Key: SANDESHA2-4
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
>      Project: Apache Sandesha2
>         Type: Improvement

>  Environment: WinXP
>     Reporter: Thomas McKiernan
>     Priority: Minor
>  Attachments: patch.txt, stopThreads
>
> At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
> This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
> Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SANDESHA2-4) shutdown might finish before threads stop

Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]

Thomas McKiernan updated SANDESHA2-4:
-------------------------------------

    Attachment: patch.txt

this is a fix for the problem

> shutdown might finish before threads stop
> -----------------------------------------
>
>          Key: SANDESHA2-4
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
>      Project: Apache Sandesha2
>         Type: Improvement

>  Environment: WinXP
>     Reporter: Thomas McKiernan
>     Priority: Minor
>  Attachments: patch.txt
>
> At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
> This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
> Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SANDESHA2-4) shutdown might finish before threads stop

Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]

Thomas McKiernan updated SANDESHA2-4:
-------------------------------------

    Attachment: stopThreads

This patch has been built on top of latest code as of 26/06/2006.
Please disregard the previous patch as it is now out of date.


> shutdown might finish before threads stop
> -----------------------------------------
>
>          Key: SANDESHA2-4
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
>      Project: Apache Sandesha2
>         Type: Improvement

>  Environment: WinXP
>     Reporter: Thomas McKiernan
>     Priority: Minor
>  Attachments: patch.txt, stopThreads
>
> At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
> This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
> Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SANDESHA2-4) shutdown might finish before threads stop

Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]

Thomas McKiernan updated SANDESHA2-4:
-------------------------------------

    Attachment: stopThreads

This patch has been built on top of latest code as of 26/06/2006.
Please disregard the previous patch as it is now out of date.


> shutdown might finish before threads stop
> -----------------------------------------
>
>          Key: SANDESHA2-4
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
>      Project: Apache Sandesha2
>         Type: Improvement

>  Environment: WinXP
>     Reporter: Thomas McKiernan
>     Priority: Minor
>  Attachments: patch.txt, stopThreads
>
> At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
> This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
> Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Resolved: (SANDESHA2-4) shutdown might finish before threads stop

Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]
     
Chamikara Jayalath resolved SANDESHA2-4:
----------------------------------------

    Resolution: Fixed

Issue was resolved after applying the patch from Thomas

> shutdown might finish before threads stop
> -----------------------------------------
>
>          Key: SANDESHA2-4
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
>      Project: Apache Sandesha2
>         Type: Improvement

>  Environment: WinXP
>     Reporter: Thomas McKiernan
>     Priority: Minor
>  Attachments: patch.txt, stopThreads
>
> At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
> This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
> Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org


[jira] Updated: (SANDESHA2-4) shutdown might finish before threads stop

Posted by "Thomas McKiernan (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/SANDESHA2-4?page=all ]

Thomas McKiernan updated SANDESHA2-4:
-------------------------------------

    Attachment: patch.txt

this is a fix for the problem

> shutdown might finish before threads stop
> -----------------------------------------
>
>          Key: SANDESHA2-4
>          URL: http://issues.apache.org/jira/browse/SANDESHA2-4
>      Project: Apache Sandesha2
>         Type: Improvement

>  Environment: WinXP
>     Reporter: Thomas McKiernan
>     Priority: Minor
>  Attachments: patch.txt
>
> At the moment it is possible for the module shutdown path to return while the Sender and Invoker threads are still running.
> This means that even after the module has shutdown transactional work might be attempted. The effects of this are unpredictable and should be avoided.
> Therefore I suggest that the shutdown path is changed so that, if the server and/or invoker threads are running, it blocks until they have finished. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org