Fixes are available
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
We can implement a WebSphere scheduler task that calls a session bean as EJB3.x. When WebSphere scheduler is configured on a cluster and one of the cluster members tries to handle the scheduled task, there is a possibility that the scheduler service sends ejb methods like create/process to remote cluster members. This remote ejb call results in the CORBA.MARSHAL Incompatibility error.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Scheduler API * **************************************************************** * PROBLEM DESCRIPTION: Incompatibility between Stub and Tie * * reported for Scheduler TaskHandler * * interface * **************************************************************** * RECOMMENDATION: * **************************************************************** When an implementation of the com.ibm.websphere.scheduler.TaskHandler interface is provided in an EJB 3.0 or later module, the following error may occur if the Scheduler attampts to make a remote call to the bean: org.omg.CORBA.MARSHAL: Incompatibility between Stub and Tie 0x7f at offset 0x4d8 vmcid: IBM minor code: 8F3 completed: No at com.ibm.rmi.iiop.CDRReader.read_abstract_interface(CDRReader.jav a:1628) at com.ibm.websphere.scheduler._EJSRemoteCSLModelRootTaskHandler_1e 041c44_Tie.process(_EJSRemoteCSLModelRootTaskHandler_1e041c44_Ti e.java:100) at com.ibm.websphere.scheduler._EJSRemoteCSLModelRootTaskHandler_1e 041c44_Tie._invoke(_EJSRemoteCSLModelRootTaskHandler_1e041c44_Ti e.java) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDe legate.java:631)
Problem conclusion
WebSphere Application Server provides an RMIC generated Stub class for the Scheduler TaskHandler iterface, which is not compatible with the EJB 3.x style generated Tie class. A change will be made to the EJB Container to generate a Tie for the TaskHandler implementation that is compatible with the RMIC generated Stub. The error will no longer occur. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.14 and 9.0.0.8. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI92731
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-01-22
Closed date
2018-03-12
Last modified date
2018-03-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022