APAR status
Closed as program error.
Error description
Errors are being logged in ffdc for each message sent -
the message is still received by the recipient successfully
OpenJMS is being used for JMS implementation which is an open
source project.
When a JMS message is constructed there are several properties
that can be set. One of them is JMSDeliveryCount (this is an
optional property). When this is set, no number format errors
is seen. This would suggest
that com.ibm.ejs.jms.listener.MDBWrapper.onMessageis perhaps
treating this optional property as a mandatory one. The error
logged is below:
Original error in ffdc:
35 604822 05.04.26 06:59:51:016 GMT
java.lang.NumberFormatException
com.ibm.ejs.jms.listener.MDBWrapper.onMessage 101
Exception = java.lang.NumberFormatException
Source = com.ibm.ejs.jms.listener.MDBWrapper.onMessage
probeid = 101
Stack Dump = java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:436)
at java.lang.Integer.valueOf(Integer.java:574)
at
org.exolab.jms.message.FormatConverter.getInt(FormatConverter.ja
va:207)
at
org.exolab.jms.message.MessageProperties.getIntProperty(MessageP
ropertie
s.java:175)
at
org.exolab.jms.message.MessageImpl.getIntProperty(MessageImpl.ja
va:405)
at
com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:15
5)
at org.exolab.jms.client.JmsSession.run(JmsSession.java:484)
at
com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:924)
at
com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessa
ge(Serve
rSession.java:740)
at
com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:37
5)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
LOCAL FIX:
Will be fixed in the next release.
Local fix
Fix in next release
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the *
* Java Message Service (JMS) functionality *
* provided with WebSphere Application Server *
* Version 5.x and Version 6.x *
****************************************************************
* PROBLEM DESCRIPTION: The error logged is as follows when a *
* JMS message is constructed. *
* *
* Original error in ffdc: *
* 35 604822 05.04.26 06:59:51:016 *
* GMT *
* java.lang.NumberFormatException *
* com.ibm.ejs.jms.listener.MDBWrapper. *
* onMessage 101 *
* Exception = java.lang.NumberFormat *
* Exception *
* Source = com.ibm.ejs.jms.listener. *
* MDBWrapper.onMessage *
* probeid = 101 *
* Stack Dump = java.lang.NumberFormat *
* Exception: null *
* at java.lang.Integer.parseInt(Integer. *
* java:436) *
* at java.lang.Integer.valueOf(Integer. *
* java:574) *
* at *
* org.exolab.jms.message.FormatConverter. *
* getInt(FormatConverter.java:207) *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When a JMS message is constructed there are several properties
that can be set. One of them is JMSDeliveryCount which is an
optional property. When this is set, no number format errors is
seen but when it is not set an FFDC error is seen.
The com.ibm.ejs.jms.listener.MDBWrapper.onMessage is treating
this optional property as a mandatory one and throwing an FFDC.
Problem conclusion
Since it is optional, an ffdc should not be thrown. The code
that generates the ffdc exception has been removed and the
standard Trace statement that shows the property was not set
when tracing is turned on has been left in for tracing purpose.
The fix for this APAR is currently targeted for inclusion in
Cumulative Fix 14 for WebSphere Application Server Version
5.0.2, Cumulative Fix 8 for version 5.1.1. and Cumulative Fix 3
for WebSphere Application Server Version 6.0.2. 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 |
PK09928 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-08-04 |
Closed date |
2005-10-06 |
Last modified date |
2005-10-06 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|