PI95215: MESSAGEENDPOINTS ARE NOT PROPERLY RELEASED

Fixes are available

APAR status

Closed as program error.

Error description

In WAS v9.0, the message endpoints are created, but after some
time the number of message endpoints has reached the limit and
no more endpoints can be created. The following error could be
found in
the log:
[2/8/18 16:24:53:160 GST] 000000eb EndpointAdapt E
MessageEndpoint is not available

javax.resource.spi.UnavailableException: limit for number of
MessageEndpoint proxies reached. Limit = 500
at
com.ibm.ws.ejbcontainer.mdb.BaseMessageEndpointFactory.createEnd
point(BaseMessageEndpointFactory.java:344)
at
com.ibm.ws.ejbcontainer.mdb.BaseMessageEndpointFactory.createEnd
point(BaseMessageEndpointFactory.java:238)

Even after increasing the maximum number of message endpoints,
this limit can be reached again when more messages are
processed.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server - Message Driven Beans (MDB)         *
****************************************************************
* PROBLEM DESCRIPTION: MessageEndpoint release method not      *
*                      releasing resources                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a custom message listener interface declares a method with
the same signature as the MessageEndpoint.release() method,
then the MessageEndpoint.release() method will not behave
properly. Resources will not be released.
After delivering a message, the resource adapter calls
the MessageEndpoint release method to release the resources
associated with the endpoint, including making the endpoint
available to be used again. When the MessageEndpoint
release method does not work properly, the endpoint will not be
released, eventually resulting in the following exception:
javax.resource.spi.UnavailableException: limit for number of
MessageEndpoint proxies reached. Limit = 500
Similarly, if a message-driven bean implementation declares a
method with the same signature as a method on the
MessageEndpoint interface, then the generated
MessageEndpointProxy may fail to load with a ClassFormatError
(below).
Caused by: java.lang.ClassFormatError: JVMCFRE106 duplicate
method; class=mdb/MDBProxyNoMethodIntOverrideBean_65ec0f85,
offset=2504
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:346)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.java:95)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at
com.ibm.ws.ejbcontainer.jitdeploy.ClassDefiner.defineClass(Class
Definer.java:125)
at
com.ibm.ws.ejbcontainer.jitdeploy.ClassDefiner.findLoadedOrDefin
eClass(ClassDefiner.java:168)
at
com.ibm.ws.ejbcontainer.jitdeploy.JITDeploy.generateMDBProxy(JIT
Deploy.java:505)

Problem conclusion

The EJB container has been updated to properly generate the
MessageEndpoint proxy classes so that they will load correctly
and always perform the required MessageEndpoint interface
functions. MessageEndpoints will be released, avoiding the
UnavailableException error.

The fix for this APAR is currently targeted for inclusion in
fix pack 9.0.0.8 for WebSphere Application Server and 18.0.0.2
for WebSphere Application Server Liberty.  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
PI95215
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-14
Closed date
2018-05-30
Last modified date
2018-05-30

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

R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI95215: MESSAGEENDPOINTS ARE NOT PROPERLY RELEASED

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R900 PSY

Document Information

Share your feedback

Need support?