Petals ESB Container

Create the .locked first

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Won't Fix
Affects Version/s: 3.1.1
Fix Version/s: 4.0.0
Component/s: None
Security Level: Public

Description:

Hide

Nowadays, the .locked file is created when the container is fully launched with all the components and SA redeployed. This behavior is kinda problematic in production environment, since we have no way to kill the process (if it comes to a crash). The only way to kill the process is to manually perform a ps and select the right instance of JVM to kill it.

It would be way simpler to create the .locked with the process PID first.

Show
Nowadays, the .locked file is created when the container is fully launched with all the components and SA redeployed. This behavior is kinda problematic in production environment, since we have no way to kill the process (if it comes to a crash). The only way to kill the process is to manually perform a ps and select the right instance of JVM to kill it. It would be way simpler to create the .locked with the process PID first.

Environment:

Petals-ESB

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

1m 49s

1

Charles Casadei

Wed, 8 Sep 2010 - 11:14:19 +0200

Open

In Progress

72d 8h 14m

1

Sébastien André

Fri, 19 Nov 2010 - 18:29:16 +0100

In Progress

Resolved

3m 7s

1

Sébastien André

Fri, 19 Nov 2010 - 18:32:23 +0100

People

Assignee:

Sébastien André

Reporter:

Charles Casadei
Watchers:

0

Dates

Created:

Wed, 8 Sep 2010 - 11:12:30 +0200

Updated:

Fri, 19 Nov 2010 - 18:32:23 +0100

Resolved:

Fri, 19 Nov 2010 - 18:32:23 +0100