Fixes are available
APAR status
Closed as fixed if next.
Error description
With PM94096, EJB container generates stubs that recognizes mangled and unmangled exception names, which allows it to receive exceptions thrown by ties generated by either EJB container or rmic. However, by default, EJB container will NOT generate ties that send mangled exception names because that would be incompatible with stubs that do not recognize mangled exception names (servers that do not have the PM94096 fix, or stubs generated by createEJBStubs prior to the PM94096 fix), which means that by default, EJB container will generate ties that are incompatible with rmic stubs, and there are no plans to change this in any release. So EJBBinding which follow IDL spec have to recoganize unmangled exception.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM BPM Advanced, Standard, and Express * **************************************************************** * PROBLEM DESCRIPTION: When an EJB container does not follow * * Java2idl specification, an unmangled * * exception is thrown. Although this * * behavior does not affect product * * usage, the EJB container does not * * generate ties that send mangled * * exception names so the EJB bindings * * do not receive unmangled exceptions * * even though the EJB binding that * * follows the specification can * * recognize the mangled exception name * * only. * **************************************************************** * RECOMMENDATION: * **************************************************************** EJB bindings do not recognize unmangled exceptions that are thrown by EJB containers that do not follow the Java2idl specification.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR47759
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-12
Closed date
2013-12-01
Last modified date
2013-12-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022