IBM Support

Task failing due to invalid or missing J2EE context information

Troubleshooting


Problem

Reusing scheduler tables that contain tasks scheduled by previous releases of IBM WebSphere Application Server might cause problems.

Symptom

  • Enterprise Beans components running on unexpected application servers
  • Tasks failing to run due to invalid or missing security credentials
  • Tasks failing to run due to invalid or missing J2EE context information

For example, you might see the following exception in the SystemOut.log:

[7/24/07 11:11:25:053 EDT] 00000097 JavaCompServi E ASYN0030E: Cannot find meta data for j2eename DataServicesApp#DataServicesEJB.jar#component.ProcessSingleDataTransferCall.
[7/24/07 11:11:25:053 EDT] 00000097 ComponentMeta E WSVR0603E: ComponentMetaDataAccessor beginContext method received a NULL ComponentMetaData.
[7/24/07 11:11:25:069 EDT] 00000097 AlarmListener E SCHD0063E: A task with ID 5252 failed to run on Scheduler BPEScheduler (BPEScheduler) because of an exception: java.lang.NullPointerException.
[7/24/07 11:11:25:069 EDT] 00000097 LocalTranCoor E WLTC0017E: Resources rolled back due to setRollbackOnly() being called.
[7/24/07 11:11:25:069 EDT] 00000097 AlarmImpl E ASYN0012E: Alarm/Timer threw exception commonj.work.WorkCompletedException: com.ibm.ws.asynchbeans.WorkRolledBackException
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1127)
at com.ibm.ws.asynchbeans.AlarmImpl.runListenerAsCJWork(AlarmImpl.java:170)
at com.ibm.ws.asynchbeans.am._Alarm.fireAlarm(_Alarm.java:332)
at com.ibm.ws.asynchbeans.am._Alarm.run(_Alarm.java:229)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)
Caused by: com.ibm.ws.asynchbeans.WorkRolledBackException
at com.ibm.ws.asynchbeans.J2EEServiceManager.popContext(J2EEServiceManager.java:522)
at com.ibm.ws.asynchbeans.J2EEContext.pop(J2EEContext.java:440)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1114)
... 4 more

Troubleshooting such problems might be challenging and demands analyzing logs on all servers that have a scheduler installed or configured.

Environment

This problem can occur when using any database.

Resolving The Problem

The following is an example that illustrates how to resolve this problem using a Cloudscape database:

1. Examine SystemOut.log and note the tasks IDs that are listed in the SCHD0063E messages

2. Stop the Server. (This must be done -- the default Cloudscape database can only be accessed by one program at a time)



3. Start the Cloudscape command program:
    C:\ibm\wid602\runtimes\bi_v6\cloudscape\bin\embedded\ij

4. At the ij command prompt, type:
    - Connect to the database

    connect 'jdbc:db2j:C:\IBM\WID602\pf\server\databases\BPEDB';

    - Repeat the following command for each task ID noted above

    DELETE FROM APP.SCHED_TASK WHERE TASKID = '5252' ;

    - End the ij command prompt:

    exit;

5. Restart the server, and verify that the SCHD0063E errors do
not reappear.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Scheduler","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21272980

Page Feedback