APAR status
Closed as program error.
Error description
When using durable subscribers, the subscriber name is set to
the J2EE name for the deployed message-driven bean as determined
by the EJB container. The format of the J2EE name is as
follows:
<Enterprise application resource>#<JAR file>#<MDB Name>
For example, an enterprise application is called "TestMDBEAR".
The application contains a single MDB: "MDB1",
that is contained within the JAR file "TestMDBs.jar". The J2EE
name for the MDB is:
TestMDBEAR#TestMDBs.jar#MDB1
A third-party JMS publish/subscribe broker does not accept '#'
as a valid character in the durable subscriber name.
The Generic JMS Connection Factory will be modified to check for
the definition of a new custom property -
"durable.subscriber.name". This property will allow customers
to specify the name of any durable subscribers that are created.
If the custom property has not been specified, the subscriber
name will default to the J2EE Name for the deployed
message-driven bean as determined by the EJB container.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use *
* WebSphere Application Server Version 5.x *
* with SonicMQ as the JMS Provider. *
****************************************************************
* PROBLEM DESCRIPTION: When using message-driven beans with *
* WebSphere Application Server Version *
* 5.x and SonicMQ as the broker, attempts *
* to create durable subscribers fail *
* with a SonicMQ error indicating that *
* the subscriber name contains an *
* invalid character. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using durable subscribers within WebSphere Application
Server Version 5.x, the subscriber name is set to the J2EE
name for the deployed message-driven bean as determined by
the EJB container. The format of the J2EE name is as follows:
<Enterprise application resource>#<JAR file>#<MDB Name>
For example, an enterprise application is called
"TestMDBEAR". The application contains a single MDB: "MDB1",
that is contained within the JAR file "TestMDBs.jar". The
J2EE name for the MDB is:
TestMDBEAR#TestMDBs.jar#MDB1
The SonicMQS publish/subscribe broker does not accept '#' as
a valid character in the durable subscriber name. Therefore,
when a WAS durable subscriber attempts to connect to the
broker, the subscriber is rejected.
Problem conclusion
The Generic JMS Connection Factory has be modified to allow
users to define a custom property called
"durable.subscriber.name". This property allows customers to
specify the name of any durable subscribers that are created.
If the custom property has not been specified, the subscriber
name will default to the J2EE Name for the deployed
message-driven bean as determined by the EJB container.
Temporary fix Comments
APAR information |
APAR number |
PQ87533 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-04-14 |
Closed date |
2004-05-17 |
Last modified date |
2004-05-17 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
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 |
|