Clustered services - EPRs not created in registry DB ---------------------------------------------------- Key: JBESB-1066 URL: http://jira.jboss.com/jira/browse/JBESB-1066 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.2.1 IR1 Environment: ESB: svn update Updated to revision 15241. RHEL5: uname -a Linux 2.6.18-47.el5xen #1 SMP Tue Sep 11 18:14:21 EDT 2007 i686 athlon i386 GNU/Linux Java: 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) MySQL: mysql-5.0.22-2.1.0.1 mysql-connector-odbc-3.51.12-2.2 Reporter: Len DiMaggio Assigned To: Mark Little Fix For: 4.2.1 IR1 Attachments: summary.txt In setting up clustered services, where the registry is stored in a MySQL DB, the EPRs are not created in the regisry DB for any but the first instance of the clustered service. The test config is: Server 1 - Running ESB1 ("stacks2") Server 2 - Running ESB2 ("stacks3") Server 3 - Running MySQL DB - registry (stacks4") ESB1 and ESB2 are using this data source definition(trunk/product/build/jbossesb-server-4.2.1IR1/server/default/deploy/jbossesb.sar/juddi-ds.xml) ---------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <datasources> <local-tx-datasource> <jndi-name>juddiDB</jndi-name> <connection-url>jdbc:mysql://stacks4.lab.boston.redhat.com:3306/juddi</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>juddi</user-name> <password>juddi</password> <min-pool-size>5</min-pool-size> <max-pool-size>20</max-pool-size> <idle-timeout-minutes>0</idle-timeout-minutes> <prepared-statement-cache-size>32</prepared-statement-cache-size> </local-tx-datasource> </datasources> ---------------------------------------------- The scenario is as follows: 1) ESB1 deploys helloworld qs app - the server log shows: 12:30:12,114 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld.esb 12:30:12,126 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_esb] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:30:12,133 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_gw] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:30:12,264 INFO [JDBCDataStore] Generated token 'authToken:C2A4FC60-6796-11DC-AA5A-8371AA2924EF' for user: 'jbossesb/JBoss ESB User' 12:30:12,295 INFO [JDBCDataStore] Generated token 'authToken:C2A94220-6796-11DC-AA5A-83233359B3DF' for user: 'jbossesb/JBoss ESB User' 12:30:12,397 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. And the DB shows: INSERT INTO `BINDING_TEMPLATE` VALUES ('E2596650-6795-11DC-AA5A-DAA94D56131C','E275C7F0-6795-11DC-AA5A-D531BE5DD5B4' (Truncated for this JIRA - full details are in an attachmemt) INSERT INTO `SERVICE_DESCR` VALUES ('E2596650-6795-11DC-AA5A-DAA94D56131C',0,'en','Service which sends a CommandMessage with statistics'),('E28FB890-6795-11DC-AA5A-EF9DAEBC3B81',0,'en','Dead Messages can be send to this service, which is configured to store and/or notify'),('E4723430-6795-11DC-AA5A-BCF00979EC66',0,'en','Service that files data into the database'),('C2A6F830-6796-11DC-AA5A-DB3317067ABF',0,'en','Hello World'); 2) ESB2 deploys helloworld qs app - the server log shows: 12:33:38,210 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld.esb 12:33:38,229 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_esb] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:33:38,242 INFO [QueueService] Queue[/queue/quickstart_helloworld_Request_gw] started, fullSize=200000, pageSize=2000, downCacheSize=2000 12:33:38,399 INFO [JDBCDataStore] Generated token 'authToken:3D8262B0-6797-11DC-A39C-D76A93B1812F' for user: 'jbossesb/JBoss ESB User' 12:33:38,662 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. No additional records are written to the SERVICE_DESCR table in the registry DB. Additional notes: 1) The same error is seen if the order of the deployment (fisrt ESB2, then ESB1) is reversed. 2) On one occasion, the ESB2 server raised the exception listed in an attachment to this JIRA - this exception hasn't turned out to be reproducible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira