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.