Bug 777595 (SOA-103) - Standalone ESB server - on RHEL shutdown with ctrl/C fails - ctrl/Z and kill -9 needed
Summary: Standalone ESB server - on RHEL shutdown with ctrl/C fails - ctrl/Z and kill ...
Keywords:
Status: CLOSED WORKSFORME
Alias: SOA-103
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 IR6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 IR8
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-06 19:25 UTC by Len DiMaggio
Modified: 2007-11-28 01:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-28 01:48:29 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-1366 0 None None None Never
Red Hat Issue Tracker SOA-103 0 None None None Never

Description Len DiMaggio 2007-11-06 19:25:17 UTC 
Date of First Response: 2007-11-06 14:44:07
project_key: SOA

Standalone ESB server - on RHEL shutdown with ctrl/C fails - ctrl/Z and kill -9 needed

We're seeing this problem repeatedly. It's not clear if it is DB-dependent, or due to a queue backlog or what just yet. 

This JIRA is initially assigned to ldimaggi - we'll add more details as we find them and then assign it to a developer.
Comment 3 Jiri Pechanec 2007-11-08 13:05:26 UTC 
Another observation, it happends mostly with full SOA platform, not with ESB standalone
Comment 4 Jiri Pechanec 2007-11-08 15:41:47 UTC 
The shutdown process hangs and prints messages
13:55:14,989 WARN  [ServerInvoker] SocketServerInvoker[127.0.0.1:4457] can not process invocation requests since is not in started state!
13:55:15,013 WARN  [ServerInvoker] SocketServerInvoker[127.0.0.1:4457] can not process invocation requests since is not in started state!
13:55:15,019 WARN  [ServerInvoker] SocketServerInvoker[127.0.0.1:4457] can not process invocation requests since is not in started state!
13:55:15,025 WARN  [ServerInvoker] SocketServerInvoker[127.0.0.1:4457] can not process invocation requests since is not in started state!
13:55:15,053 WARN  [ServerInvoker] SocketServerInvoker[127.0.0.1:4457] can not process invocation requests since is not in started state!
13:55:17,687 WARN  [ServerInvoker] SocketServerInvoker[127.0.0.1:4457] can not process invocation requests since is not in started state!
Comment 6 Len DiMaggio 2007-11-27 13:53:16 UTC 
Link: Added: This issue related JBESB-1366
Comment 7 Len DiMaggio 2007-11-28 01:48:29 UTC 
Cannot reproduce this bug - will reopen if we find a way to reproduce it.
Note You need to log in before you can comment on or make changes to this bug.