Problem definition
------------------------
We are deploying the same source code in various server instance on the same machine, we have configured each server port to
be different and the databse for each application instance is different, the datasource is configured at cell level and all
jndi/resource names in the source code, ejb-jar.xml,web.xml have been changed.
I have deployed an enterprise application into the WAS 5.0, this application is using the Business Process Engine and
scheduler for data workflow. The application is using a session EJB to interact with the scheduler which is
callNaosSGScheduler.java. While I try to access the application via url, the application calls this particular EJB to call
Scheduler service configured in the WAS which then hits the database. I am getting the following error at admin console
--------------------------
STACK TRACE
--------------------------
[9/27/07 14:04:44:414 CST] 37238865 ApplicationMg A WSVR0221I: Application started: NaosSG_BSL
[9/27/07 14:04:44:483 CST] 37238865 StaffServiceI I STFF0032I: The Staff Service started successfully.
[9/27/07 14:04:44:891 CST] 37238865 HttpTransport A SRVE0171I: Transport http is listening on port 9,083.
[9/27/07 14:04:45:432 CST] 37238865 HttpTransport A SRVE0171I: Transport https is listening on port 9,486.
[9/27/07 14:04:45:444 CST] 37238865 SchedulerServ I SCHD0031I: The Scheduler Service is starting.
[9/27/07 14:04:46:279 CST] 37238865 SchedulerImpl E SCHD0007E: Error while accessing the persistent store: jdbc/bsl/naos_bpe
[9/27/07 14:04:46:299 CST] 37238865 SchedulerImpl E SCHD0003E: An error occured while starting the scheduler service:
BPEScheduler.
[9/27/07 14:04:46:913 CST] 37238865 SchedulerServ I SCHD0032I: The Scheduler Instance BPEScheduler is starting.
[9/27/07 14:04:47:407 CST] 37238865 SchedulerDaem I SCHD0038I: The Scheduler Daemon for instance BPEScheduler has started.
[9/27/07 14:04:47:407 CST] 37238865 SchedulerServ I SCHD0033I: The Scheduler Instance BPEScheduler has started.
[9/27/07 14:04:47:548 CST] 37238865 InternalGener I DSRA8203I: Database product name : Oracle
[9/27/07 14:04:47:548 CST] 37238865 InternalGener I DSRA8204I: Database product version : Oracle9i Enterprise Edition Release
9.2.0.6.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
[9/27/07 14:04:47:548 CST] 37238865 InternalGener I DSRA8205I: JDBC driver name : Oracle JDBC driver
[9/27/07 14:04:47:559 CST] 37238865 InternalGener I DSRA8206I: JDBC driver version : 9.2.0.6.0
[9/27/07 14:04:47:727 CST] 2ba3c87b SchedulerDaem E SCHD0007E: Error while accessing the persistent store: jdbc/bsl/naos_bpe
[9/27/07 14:04:48:293 CST] 37238865 SchedulerServ I SCHD0032I: The Scheduler Instance scheduler/bsl/NAOS_Scheduler is
starting.
[9/27/07 14:04:48:315 CST] 37238865 SchedulerDaem I SCHD0038I: The Scheduler Daemon for instance scheduler/bsl/NAOS_Scheduler
has started.
[9/27/07 14:04:48:411 CST] 37238865 SchedulerServ I SCHD0033I: The Scheduler Instance scheduler/bsl/NAOS_Scheduler has
started.
[9/27/07 14:04:48:412 CST] 37238865 SchedulerServ I SCHD0001I: The Scheduler Service has started.
[9/27/07 14:04:48:839 CST] 37238865 RMIConnectorC A ADMC0026I: RMI Connector available at port 9813
[9/27/07 14:04:49:576 CST] 37238865 WsServer A WSVR0001I: Server NaosSGServerBSL open for e-business
[9/27/07 14:04:54:192 CST] afdc87b DiscoveryMBea I ADMD0023I: Process discovered (name: nodeagent, type: NodeAgent, pid:
1605834)
[9/27/07 14:05:28:055 CST] 18a54862 JavaCompServi E ASYN0030E: Cannot find meta data for j2eename
SG_Naos#NaosSGEJB.jar#CallNaosSGScheduler
[9/27/07 14:05:28:201 CST] 18a54862 ComponentMeta E WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL
ComponentMetaData.
[9/27/07 14:05:28:303 CST] 554d887a JavaCompServi E ASYN0030E: Cannot find meta data for j2eename
SG_Naos#NaosSGEJB.jar#CallNaosSGScheduler
[9/27/07 14:05:28:630 CST] 554d887a ComponentMeta E WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL
ComponentMetaData.
[9/27/07 14:05:32:753 CST] 554d887a XATransaction E J2CA0026E: Method addSync caught javax.transaction.RollbackException
at com.ibm.ejs.jts.jta.TransactionImpl.registerSynchronization(TransactionImpl.java:1007)
at com.ibm.ejs.jts.jta.JTSXA.registerSynchronization(JTSXA.java:1096)
at com.ibm.ejs.j2c.XATransactionWrapper.addSync(XATransactionWrapper.java:259)
at com.ibm.ejs.j2c.ConnectionManager.initializeForUOW(ConnectionManager.java:952)
at com.ibm.ejs.j2c.ConnectionManager.involveMCInTran(ConnectionManager.java:769)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:484)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:215)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:306)
at com.ibm.ws.extensionhelper.db.impl.DatabaseHelperImpl.getConnection(DatabaseHelperImpl.java(Compiled Code))
at com.ibm.ws.scheduler.AlarmListener$TaskWork.doWork(AlarmListener.java:239)
at com.ibm.ws.scheduler.Work.run(Work.java:46)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:449)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:106)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:227)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:472)
at com.ibm.ws.asynchbeans.ExecutionContextImpl.go(ExecutionContextImpl.java:67)
at com.ibm.ws.scheduler.AlarmListener.executeTaskBatch(AlarmListener.java:514)
at com.ibm.ws.scheduler.AlarmListener.fired(AlarmListener.java:431)
at com.ibm.ws.asynchbeans.AlarmImpl.run(AlarmImpl.java:255)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:174)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:449)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:106)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:227)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:472)
at com.ibm.ws.asynchbeans.AlarmImpl.alarm(AlarmImpl.java:148)
at com.ibm.ws.asynchbeans.am._Alarm.fireAlarm(_Alarm.java:195)
at com.ibm.ws.asynchbeans.am._Alarm.run(_Alarm.java:164)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:681)
while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a
ResourceException.
[9/27/07 14:05:36:444 CST] 554d887a JavaCompServi E ASYN0030E: Cannot find meta data for j2eename
SG_Naos#NaosSGEJB.jar#CallNaosSGScheduler
[9/27/07 14:05:37:046 CST] 18a54862 JavaCompServi E ASYN0030E: Cannot find meta data for j2eename
SG_Naos#NaosSGEJB.jar#CallNaosSGScheduler
[9/27/07 14:05:39:233 CST] 554d887a JavaCompServi E ASYN0030E: Cannot find meta data for j2eename
SG_Naos#NaosSGEJB.jar#CallNaosSGScheduler
[9/27/07 14:05:39:353 CST] 554d887a ComponentMeta E WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL
ComponentMetaData.
[9/27/07 14:05:39:375 CST] 18a54862 JavaCompServi E ASYN0030E: Cannot find meta data for j2eename
SG_Naos#NaosSGEJB.jar#CallNaosSGScheduler
[9/27/07 14:05:39:428 CST] 18a54862 ComponentMeta E WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL
ComponentMetaData.
------------------------Stack Trace Ends-------------------------------------------------------
I have searched the forum, in this regards but unable to find my problem, If the problem is already been answered then please provide the link for the same, and accept my apologies in advance.
Best regards,
Prabhat Atri
http://www.ibm.com/developerworks/websphere/techjournal/0404_johnson/0404_johnson.html
Brian