Bug 777556 (SOA-60)

Summary: Unclean ESB server shutdown - extraneous EPR records remain in MySQL jUDDI DB
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Len DiMaggio <ldimaggi>
Component: JBossESBAssignee: Kurt Stam <kurt.stam>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR2   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-60
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
soa-standalone.zip (oct 12007) RHEL5 java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04, mixed mode)
Last Closed: 2007-11-02 13:40:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2007-10-22 19:59:50 UTC 
Date of First Response: 2007-10-30 10:28:33
project_key: SOA

I'm not sure if there will be a way to prevent this from happening if a user decides to kill (kill -9) the ESB server process - but the problem is reproducible.

Steps:

1) With a MySQL 5 jUDDI database - and a running ESB server
2) Deploy an ESB archive (for example, helloworld.esb)
3) Verify that in the database there are (4) records in the BINDING_TEMPLATE table - 3 for the server - one for the deployed app/archive
4) Kill the ESB server process (kill -9 PID#)
5) Startup the ESB server 
6) Verify that in the database there are (4) records in the BINDING_TEMPLATE table - 3 for the server - one for the deployed app/archive
7) Undeploy and then deploy the archive
8) Verify that in the database there are now (8) records in the BINDING_TEMPLATE

I haven't been able to observe a functional problem running a quickstart manually with these duplicate records - but if the sendesb test is modified to send multiple messages thru a single ServiceInvoker, these errors show up in the log:

13:46:37,371 ERROR [ExceptionUtil] SessionEndpoint[24] createQueue [5c4o24w-9ihnh1-f83a42ls-1-f83a620r-y]
javax.jms.JMSException: There is no administratively defined queue with name:queue/quickstart_helloworld_Request_esb

Note - I have not been able to recreate the problem with the hsqldb database.
Comment 1 Kurt Stam 2007-10-30 14:28:33 UTC 
This is not a bug, but works as designed

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=96389&postdays=0&postorder=asc&start=10