| WID Knowledge Base/tech notes etc. The infocenter for WID is available online and also from the WID menu by clicking Help -> Help Contents. It is no longer available from IBM download site. 1.1.2 J2CA0030E when connecting to CTG (CICS Transaction Gateway) When process has a step that tries to connect to CTG the following error may be encountered:
J2CA0030E: Method enlist caught javax.transaction.SystemException: XAResource start association error:XAER_RMERR
1. The CICS server is not completing existing requests either due to a resource shortage on the CICS server or to some other problem that is affecting the performance. One thing that could cause this is too many concurrent connections. If you have many AppServers opening connections and each with large connection pools, this could negatively impact the performance of the CICS server to the point where it is unable to complete CICS requests. 2. Another possible cause is that you have too many requester threads (either WebContainer or EJB container) threads that are attempting to request a connection. One common cause of this is to click the isGrowable box on either the WebContainer or EJBContainer thread pool. This would allow a potentially infinite number of requests for a connection, most of which would time out. This can also significantly compromise the performance of the AppServer. 3. Another possible cause is if the EJB or servlet that holds the connection does not complete. This can occur if you have nested EJB or servlet calls and the nested EJB or servlet requires a connection to the same DB table and is not able to share the existing connection (this would be the case if they are in separate transactions). 4. This problem can occur if your application leaks connections, that is if it terminates without closing the connection so that the connection is returned to the connection pool. 5. It is possible that the CICS CTG is not configured as an XA resource and the lazyEnlistment is causing it to have to be XA capable. 1.1.3 DuplicateGlobalInstanceIdException When trying to create a process instance the following error is encountered: com.ibm.events.datastore.DuplicateGlobalInstanceIdException Caused by: com.ibm.events.emitter.SendFailureException: CEIEM0025E The emitter failed to send the events to the event server. The local event bus enterprise bean on the event server failed during event processing. Events: [org.eclipse.hyades.logging.events.cbe.impl.CommonBaseEventImpl@6b22b52e (creationTime: 2006-10-24T21:08:41.991Z, globalInstanceId: CE11DB63A3D3B00971C58B8C578F1268BE, elapsedTime: <unset>, extensionName: BPC.BFM.LINK.STATUS, localInstanceId Existing event: org.eclipse.hyades.logging.events.cbe.impl.CommonBaseEventImpl@7f30352f Caused by: com.ibm.events.datastore.DuplicateGlobalInstanceIdException: CEIDS0007E An event with the global instance identifier, CE11DB63A3D3B00971C58B8C578F1268BE , already exists in the database. The event was not stored in the database. Solution: The problem has something to do with the CommonEventInfrastructure Bus not having the CommonEventInfrastructureTopicDestination topic setup. The topic communicates with the Messaging Cluster and provides the CEI with a Global Instance Id which is used to persist event records for a BPEL process. You may want to turn on logging on all of the CEI Event to understand that the topic destination is missing. Follow the steps to create the topic destination: Go to Buses -> CommonEventInfrastructure_Bus -> Destinations Click New and create a topic space destination with the name CommonEventInfrastructureTopicDestination Click Finish and save with synchronization It may not be required to restart the cluster/bus/application server Try creating a process instance If the error still persists, then try restarting the messaging engine cluster |