[JBoss JIRA] Created: (JBESB-1009) Message Trace: The ability to follow the path of a message through the system
by Burr Sutter (JIRA)
Message Trace: The ability to follow the path of a message through the system
-----------------------------------------------------------------------------
Key: JBESB-1009
URL: http://jira.jboss.com/jira/browse/JBESB-1009
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.2
Reporter: Burr Sutter
Assigned To: Mark Little
Fix For: 4.2.1
A very common request is to know the path followed by a message and its final resting place. This is particularly important in a federated architecture (multiple ESB nodes, hosting different services) where routing, filtering and the DLQ and redelivery service may be involved. The ESB already performs logging so this is more a matter of testing & documentation so that an administrator knows what knobs to turn and what levers to pull to enable system-wide logging of inflight messages.
- The tracing should also include which EPR was selected during load-balancing, fail-over, by the ServiceInvoker, etc. The expectation is that if a message fails to reach its final destination it is important to know which EPR specifically was the problem.
The log should be human readable. The most common use case is that a message will arrive in the ESB's Dead Letter Queue/Service (not the underlying JMS provider) and we (the system admin) will need to be able to backtrack it to the action, service and EPR (service instance) that had the failure.
Related requests:
- Tracing on a message by message basis, some are tracked others are not.
- Ideally this is something that can be turned on or off at runtime without interruption to the inflight messages
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-1066) Clustered services - EPRs not created in registry DB
by Len DiMaggio (JIRA)
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-1056) Management console in ESB server uses JBossMQ instead of JBoss Messaging
by Martin Vecera (JIRA)
Management console in ESB server uses JBossMQ instead of JBoss Messaging
------------------------------------------------------------------------
Key: JBESB-1056
URL: http://jira.jboss.com/jira/browse/JBESB-1056
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 4.2.1 IR1
Environment: Sun JVM, ant 1.6.5
Reporter: Martin Vecera
Assigned To: Mark Little
I've checked out the ESB from trunk and run 'ant dist'.
The file product/build/jbossesb-server-4.2.1IR1/server/default/deploy/management.esb contains jbmq-queue-service.xml instead of jbm-queue-service.xml. This is because product/tools/console/management-esb/build.xml is checking for JBoss Messaging in deploy directory before Messaging is installed there and therefore it switches to JBossMQ. Using JBossMQ in management.esb causes an exception being thrown during server startup.
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBESB-1063) ESB server (default) hang on startup - at "schema export complete"
by Len DiMaggio (JIRA)
ESB server (default) hang on startup - at "schema export complete"
------------------------------------------------------------------
Key: JBESB-1063
URL: http://jira.jboss.com/jira/browse/JBESB-1063
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1 IR1
Environment: [root@atlantis trunk]# uname -a
Linux atlantis.boston.redhat.com 2.6.18-8.el5xen #1 SMP Fri Jan 26 14:42:21 EST 2007 i686 i686 i386 GNU/Linux
(RHEL5)
[root@atlantis trunk]# java -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode)
svn update
Updated to revision 15241.
Reporter: Len DiMaggio
Assigned To: Mark Little
Fix For: 4.2.1 IR1
Attachments: server.log.fragment, server.log.gz
I'm seeing the ESB server (default) hang on startup - at schema export complete
I've attached the server.log file. The messages displayed on stdout (I used run.sh to start the server) are hung on:
------------------------------------------------------------------------------
15:07:29,249 INFO [STDOUT] Hibernate: call identity()
15:07:30,844 INFO [SessionFactoryObjectFactory] Not binding factory to JNDI, no JNDI name configured
15:07:30,915 INFO [SchemaExport] Running hbm2ddl schema export
15:07:30,919 INFO [SchemaExport] exporting generated schema to database
15:07:30,995 INFO [SchemaExport] schema export complete
------------------------------------------------------------------------------
In the server log - look for the pattern listed here - it is repeated in an infinite loop until the server is stopped.
Removing the hypersonic dir does not solve this problem.
------------------------------------------------------------------------------
2007-09-19 15:05:27,369 DEBUG [org.jbpm.job.executor.JobExecutorThread] acquiring jobs for execution...
2007-09-19 15:05:27,369 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]'
2007-09-19 15:05:27,369 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@6fadc122
2007-09-19 15:05:27,369 DEBUG [org.jbpm.persistence.db.DbPersistenceServiceFactory] creating persistence service
2007-09-19 15:05:27,369 DEBUG [org.jbpm.persistence.db.DbPersistenceService] creating hibernate session
2007-09-19 15:05:27,369 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 4875176867303424
2007-09-19 15:05:27,369 DEBUG [org.jbpm.persistence.db.DbPersistenceService] beginning hibernate transaction
2007-09-19 15:05:27,369 DEBUG [org.hibernate.transaction.JDBCTransaction] begin
2007-09-19 15:05:27,369 DEBUG [org.hibernate.jdbc.ConnectionManager] opening JDBC connection
2007-09-19 15:05:27,369 DEBUG [org.hibernate.transaction.JDBCTransaction] current autocommit status: true
2007-09-19 15:05:27,369 DEBUG [org.hibernate.transaction.JDBCTransaction] disabling autocommit
2007-09-19 15:05:27,369 DEBUG [org.jbpm.persistence.db.DbPersistenceService] begun hibernate transaction org.hibernate.transaction.JDBCTransaction@21712712
2007-09-19 15:05:27,370 DEBUG [org.jbpm.job.executor.JobExecutorThread] querying for acquirable job...
2007-09-19 15:05:27,370 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
2007-09-19 15:05:27,370 DEBUG [org.hibernate.SQL] select top ? job0_.ID_ as ID1_30_, job0_.VERSION_ as VERSION3_30_, job0_.DUEDATE_ as DUEDATE4_30_, job0_.PROCESSINSTANCE_ as PROCESSI5_30_, job0_.TOKEN_ as TOKEN6_30_, job0_.TASKINSTANCE_ as TASKINST7_30_, job0_.ISSUSPENDED_ as ISSUSPEN8_30_, job0_.ISEXCLUSIVE_ as ISEXCLUS9_30_, job0_.LOCKOWNER_ as LOCKOWNER10_30_, job0_.LOCKTIME_ as LOCKTIME11_30_, job0_.EXCEPTION_ as EXCEPTION12_30_, job0_.RETRIES_ as RETRIES13_30_, job0_.NAME_ as NAME14_30_, job0_.REPEAT_ as REPEAT15_30_, job0_.TRANSITIONNAME_ as TRANSIT16_30_, job0_.ACTION_ as ACTION17_30_, job0_.GRAPHELEMENTTYPE_ as GRAPHEL18_30_, job0_.GRAPHELEMENT_ as GRAPHEL19_30_, job0_.NODE_ as NODE20_30_, job0_.CLASS_ as CLASS2_30_ from JBPM_JOB job0_ where (job0_.LOCKOWNER_ is null or job0_.LOCKOWNER_=?) and job0_.RETRIES_>0 and job0_.DUEDATE_<=? and job0_.ISSUSPENDED_<>1 order by job0_.DUEDATE_ asc
2007-09-19 15:05:27,370 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open ResultSet (open ResultSets: 0, globally: 0)
2007-09-19 15:05:27,370 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close ResultSet (open ResultSets: 1, globally: 1)
2007-09-19 15:05:27,370 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
2007-09-19 15:05:27,370 DEBUG [org.hibernate.engine.StatefulPersistenceContext] initializing non-lazy collections
2007-09-19 15:05:27,370 DEBUG [org.jbpm.job.executor.JobExecutorThread] no acquirable jobs in job table
2007-09-19 15:05:27,370 DEBUG [org.jbpm.JbpmContext] closing JbpmContext
2007-09-19 15:05:27,370 DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@264d107e
2007-09-19 15:05:27,370 DEBUG [org.jbpm.persistence.db.DbPersistenceService] committing hibernate transaction org.hibernate.transaction.JDBCTransaction@21712712
2007-09-19 15:05:27,370 DEBUG [org.hibernate.transaction.JDBCTransaction] commit
2007-09-19 15:05:27,371 DEBUG [org.hibernate.transaction.JDBCTransaction] re-enabling autocommit
2007-09-19 15:05:27,371 DEBUG [org.hibernate.transaction.JDBCTransaction] committed JDBC Connection
2007-09-19 15:05:27,371 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
2007-09-19 15:05:27,371 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
2007-09-19 15:05:27,371 DEBUG [org.jbpm.persistence.db.DbPersistenceService] closing hibernate session
2007-09-19 15:05:27,371 DEBUG [org.jbpm.svc.Services] closing service 'tx': org.jbpm.tx.TxService@d75d3d7
2007-09-19 15:05:27,371 DEBUG [org.jbpm.job.executor.JobExecutorThread] obtained locks on following jobs: []
2007-09-19 15:05:27,371 DEBUG [org.jbpm.configuration.JbpmContextInfo] creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]'
2007-09-19 15:05:27,371 DEBUG [org.jbpm.JbpmContext] creating org.jbpm.JbpmContext@32a6cf28
2007-09-19 15:05:27,371 DEBUG [org.jbpm.persistence.db.DbPersistenceServiceFactory] creating persistence service
2007-09-19 15:05:27,371 DEBUG [org.jbpm.persistence.db.DbPersistenceService] creating hibernate session
2007-09-19 15:05:27,371 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 4875176867311616
2007-09-19 15:05:27,371 DEBUG [org.jbpm.persistence.db.DbPersistenceService] beginning hibernate transaction
2007-09-19 15:05:27,371 DEBUG [org.hibernate.transaction.JDBCTransaction] begin
2007-09-19 15:05:27,371 DEBUG [org.hibernate.jdbc.ConnectionManager] opening JDBC connection
2007-09-19 15:05:27,371 DEBUG [org.hibernate.transaction.JDBCTransaction] current autocommit status: true
2007-09-19 15:05:27,371 DEBUG [org.hibernate.transaction.JDBCTransaction] disabling autocommit
2007-09-19 15:05:27,372 DEBUG [org.jbpm.persistence.db.DbPersistenceService] begun hibernate transaction org.hibernate.transaction.JDBCTransaction@2c11b4c2
2007-09-19 15:05:27,372 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
2007-09-19 15:05:27,372 DEBUG [org.hibernate.SQL] select top ? job0_.ID_ as ID1_30_, job0_.VERSION_ as VERSION3_30_, job0_.DUEDATE_ as DUEDATE4_30_, job0_.PROCESSINSTANCE_ as PROCESSI5_30_, job0_.TOKEN_ as TOKEN6_30_, job0_.TASKINSTANCE_ as TASKINST7_30_, job0_.ISSUSPENDED_ as ISSUSPEN8_30_, job0_.ISEXCLUSIVE_ as ISEXCLUS9_30_, job0_.LOCKOWNER_ as LOCKOWNER10_30_, job0_.LOCKTIME_ as LOCKTIME11_30_, job0_.EXCEPTION_ as EXCEPTION12_30_, job0_.RETRIES_ as RETRIES13_30_, job0_.NAME_ as NAME14_30_, job0_.REPEAT_ as REPEAT15_30_, job0_.TRANSITIONNAME_ as TRANSIT16_30_, job0_.ACTION_ as ACTION17_30_, job0_.GRAPHELEMENTTYPE_ as GRAPHEL18_30_, job0_.GRAPHELEMENT_ as GRAPHEL19_30_, job0_.NODE_ as NODE20_30_, job0_.CLASS_ as CLASS2_30_ from JBPM_JOB job0_ where (job0_.LOCKOWNER_ is null or job0_.LOCKOWNER_=?) and job0_.RETRIES_>0 and job0_.ISSUSPENDED_<>1 order by job0_.DUEDATE_ asc
2007-09-19 15:05:27,372 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to open ResultSet (open ResultSets: 0, globally: 0)
2007-09-19 15:05:27,372 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close ResultSet (open ResultSets: 1, globally: 1)
2007-09-19 15:05:27,372 DEBUG [org.hibernate.jdbc.AbstractBatcher] about to close PreparedStatement (open PreparedStatements: 1, globally: 1)
2007-09-19 15:05:27,372 DEBUG [org.hibernate.engine.StatefulPersistenceContext] initializing non-lazy collections
2007-09-19 15:05:27,372 DEBUG [org.jbpm.JbpmContext] closing JbpmContext
2007-09-19 15:05:27,372 DEBUG [org.jbpm.svc.Services] closing service 'persistence': org.jbpm.persistence.db.DbPersistenceService@586f14d6
2007-09-19 15:05:27,372 DEBUG [org.jbpm.persistence.db.DbPersistenceService] committing hibernate transaction org.hibernate.transaction.JDBCTransaction@2c11b4c2
2007-09-19 15:05:27,372 DEBUG [org.hibernate.transaction.JDBCTransaction] commit
2007-09-19 15:05:27,372 DEBUG [org.hibernate.transaction.JDBCTransaction] re-enabling autocommit
2007-09-19 15:05:27,372 DEBUG [org.hibernate.transaction.JDBCTransaction] committed JDBC Connection
2007-09-19 15:05:27,372 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
2007-09-19 15:05:27,372 DEBUG [org.hibernate.jdbc.ConnectionManager] releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
2007-09-19 15:05:27,373 DEBUG [org.jbpm.persistence.db.DbPersistenceService] closing hibernate session
2007-09-19 15:05:27,373 DEBUG [org.jbpm.svc.Services] closing service 'tx': org.jbpm.tx.TxService@64c11af5
------------------------------------------------------------------------------
--
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
17 years, 2 months