My Oracle Support Banner

JMS Durable Subscribers Are Not Deleted When Stopping A WebService Application (Doc ID 1951024.1)

Last updated on JULY 03, 2023

Applies to:

Oracle WebLogic Server - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms


A  J2EE applicaton is deployed into WLS 12.1.2 server.
This application has Webservice using JMS transport (with a Topic destination).
The JMS transport configuration used the JMSTransportService annotation as the following :

@JMSTransportService(
timeToLive = 180000,
destinationType = JMSDestinationType.TOPIC,
...
activationConfig=(WS_ACTIVATIONCONFIG_TOPICMOCKSERVICE04))

where:
WS_ACTIVATIONCONFIG_TOPICMOCKSERVICE04="jmsClientId=MockServiceTopic04ClientID;subscriptionDurability=Durable;"
+ "topicMessagesDistributionMode=One-Copy-Per-Application;"
+ "distributedDestinationConnection=EveryMember;"
+ "durableSubscriptionDeletion=true; ..

The JMSTransport annotation has durableSubscriptionDeletion set to true.

And, the Topic destination is configured on another WLS server.

When starting the application , a durable subscriber related to the Webservice is created.
However, the problem is that  when stopping the application, this durable subscriber is not deleted.
 


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.