Durable Subscribers not found

Hi all,
I am working on SAP PI 7.3. My scenario is to publish the incoming messages to topic and then those messages will be sent to the suitable subscribers.
When I try to configure subscribers for the topic, the following error is coming:
There are no durable subscribers registered for the selected JMS Topic.
Please help me on how to register subscribers in NWA.
Thanks,
Kartheek

Hi Kartheek,
Once we create a TOPIC in NWA.In durable subscribers tab subscription ID and Subscription name will be automatically created once you publish the message in to TOPIC.
check in NWA-->jms server configuration-->durable subscribers.
thanks
Purna

Similar Messages

Subsequent COBRAS Exports fail, subscribers not found

4.2(1)Unity Voicemail Only with Dedicated Offbox Exchange Message Store. Failover Monitor indicates this server VM01 is Running;Active.
First time I ran COBRAS it found the 985 subscribers and took 1 hr 30 minutes.
================================================================
Running COBRASExport, version 7.0.106
Running COBRAS Export logged in as: VM\svc_unitymsg
Local Unity version=4.2(1.0)
Local Unity server name=VM01
Local subscriber count=985
Local call handler count=31
Local distribution list count=11
Local interview handler count=2
Local routing rules count=8
Local time=5/17/2011 8:12:10 PM
Second and other times I run COBRAS it doesn't find the subsribers and takes 10 minutes
================================================================
Running COBRASExport, version 7.0.106
Running COBRAS Export logged in as: VM\svc_unitymsg
Local Unity version=4.2(1.0)
Local Unity server name=VM01
Local subscriber count=0
Local call handler count=0
Local distribution list count=0
Local interview handler count=0
Local routing rules count=0
Local time=5/21/2011 7:00:00 PM
Why is COBRAS no longer finding subscribers?

Cripes, I found the problem. Someone turned CSA back on….
Event Type:        Information
Event Source:    CSAgent
Event Category:                Kernel Rule
Event ID:              256
Date:                     5/22/2011
Time:                     7:13:57 PM
User:                     N/A
Computer:          VM01
Description:
The process 'D:\Program Files\Cisco Systems\COBRAS\COBRAS Export for Unity\COBRASExport.exe' (as user VM\svc_unitymsg) attempted to call the function OpenProcess("D:\Program Files\Cisco Systems\COBRAS\COBRAS Export for Unity\wavcat.exe") from a buffer (the return address was 0x503f7d). The code at this address is '088b0851 6aff6800 001000e8 4f41f1ff 8945d4ff 157c1040 008b55d4 8955dcc7' This either happens when a process uses self-modifying code or when a process has been subverted by a buffer overflow attack. The user was queried and a 'Terminate' response was received. The response was the default taken after a timeout.

CUCM 8.6 Corporate/Personal Directory "Host Not Found"

Hi all,
Could anyone help me with the following issue?
Users with 7961 phones receive a “Host not found” message after pressing the Corporate or Personal Directory menu item.   For 7940, 7960 and 7962 it works fine.
Configuration: CUCM version 8.6.2.21900-5, 9 Nodes (1 Pub, 6 Subs, 2 TFTP). Firmware SCCP41.9-2-3S.
We tried the following to resolve the issue:
•-          we’ve deleted the ITL file
•-          performed a Factory reset
•-          changed the “Services Provisioning ” from Internal to External/Both
•-          we changed the “Secured Directory URL” in Enterprise parameters from https to http
None of those helped us. According the phone logs the issue appears when phone tries to set up a secure connection with the subscribers. We receive the following error message:
1521: NOT 15:21:29.728225 SECD: clpSetupSsl: Trying to connect to IPV4, IP: 10.128.127.10, Port : 2445
1522: NOT 15:21:29.735200 SECD: clpSetupSsl: TCP connect() waiting, <10.128.127.10> c:14 s:15 port: 2445
1523: NOT 15:21:29.736812 SECD: clpSetupSsl: TCP connected, <10.128.127.10> c:14 s:15
1524: WRN 15:21:29.739053 SECD: WARN:clpSetupSsl: failed to set TOS (96) on srvr sock, <10.128.127.10> c:14 s:15, errno 131
1525: NOT 15:21:29.740695 SECD: clpSetupSsl: start SSL/TLS handshake, <10.128.127.10> c:14 s:15
1526: ERR 15:21:29.745568 SECD: EROR:clpSetupSsl: syscall errno 32 in SSL, give up, <10.128.127.10>
1527: ERR 15:21:29.746954 SECD: EROR:clpSetupSsl: SSL/TLS handshake failed, <10.128.127.10> c:14 s:15
1528: ERR 15:21:29.748314 SECD: EROR:clpSetupSsl: SSL/TLS setup failed, <10.128.127.10> c:14 s:15
1529: ERR 15:21:29.749614 SECD: EROR:clpSndStatus: SSL CLNT ERR, srvr<10.128.127.10>
1530: ERR 15:21:29.763938 SECD: EROR:secErr_errStr: *** bad err table ***
1531: ERR 15:21:29.765667 SECD: EROR:secErr_errStr: ** SEC-ERR: code:2(N/A) subcode:32(Broken pipe)
1532: ERR 15:21:29.766974 SECD: EROR:clpSndStatus: ** SEC-ERR: desc <Broken pipe>
1533: NOT 15:21:29.768626 SECD: clpTvsInit: select returned the TVS proxy server socket, fd : 13
1534: ERR 15:21:29.770174 SECD: EROR:secSock_isConnected: ** failed to connect to target
1535: ERR 15:21:29.771572 SECD: EROR:secErr_errStr: *** bad err table ***
1536: ERR 15:21:29.772917 SECD: EROR:secErr_errStr: ** SEC-ERR: code:2(N/A) subcode:32(Broken pipe)
1537: ERR 15:21:29.774278 SECD: EROR:secSock_isConnected: ** SEC-ERR: desc <Broken pipe>
1538: ERR 15:21:29.775800 SECD: EROR:checkTvsSrvrConn: Failed to get TVS TLS session connected - setup failed
1539: NOT 15:21:29.777170 SECD: cleanupTvsSrvrSock: Clearing TVS proxy server socket, fd : 13
Does anyone know what the “broken pipe” means (code:2(N/A) subcode:32(Broken pipe)
)? I attached the logs from the phone.

UPDATE:
We performed the factory reset again and now we receive a different error:
2549: NOT 16:23:08.175874 SECD: clpSetupSsl: Trying to connect to IPV4, IP: 10.128.127.10, Port : 2445
2550: NOT 16:23:08.177366 SECD: clpSetupSsl: TCP connect() waiting, <10.128.127.10> c:14 s:15 port: 2445
2551: NOT 16:23:08.181784 SECD: clpSetupSsl: TCP connected, <10.128.127.10> c:14 s:15
2552: NOT 16:23:08.183024 SECD: clpSetupSsl: start SSL/TLS handshake, <10.128.127.10> c:14 s:15
2553: ERR 16:23:08.188600 SECD: EROR:clpSetupSsl: syscall errno 131 in SSL, give up, <10.128.127.10>
2554: ERR 16:23:08.189689 SECD: EROR:clpSetupSsl: SSL/TLS handshake failed, <10.128.127.10> c:14 s:15
2555: ERR 16:23:08.193811 SECD: EROR:clpSetupSsl: SSL/TLS setup failed, <10.128.127.10> c:14 s:15
2556: ERR 16:23:08.194872 SECD: EROR:clpSndStatus: SSL CLNT ERR, srvr<10.128.127.10>
2557: ERR 16:23:08.195889 SECD: EROR:secErr_errStr: *** bad err table ***
2558: ERR 16:23:08.196900 SECD: EROR:secErr_errStr: ** SEC-ERR: code:2(N/A) subcode:131(Connection reset by peer)
2559: ERR 16:23:08.197883 SECD: EROR:clpSndStatus: ** SEC-ERR: desc
2560: NOT 16:23:08.199175 SECD: clpTvsInit: select returned the TVS proxy server socket, fd : 13
2561: ERR 16:23:08.200449 SECD: EROR:secSock_isConnected: ** failed to connect to target
2562: ERR 16:23:08.201551 SECD: EROR:secErr_errStr: *** bad err table ***
2563: ERR 16:23:08.202560 SECD: EROR:secErr_errStr: ** SEC-ERR: code:2(N/A) subcode:131(Connection reset by peer)
2564: ERR 16:23:08.203552 SECD: EROR:secSock_isConnected: ** SEC-ERR: desc
2565: ERR 16:23:08.204524 SECD: EROR:checkTvsSrvrConn: Failed to get TVS TLS session connected - setup failed
Does anyone know in which cases the peer might terminate the connection?

Query regarding durable subscribers in JMS Adapter (11g)

Hi , I am facing some issue with using durable subscribers..
I am doing a POC in which I have two consumers (consumer 1 and consumer 2) listening to a topic.
On the server console, the monitor tab of the JMS topic shows number of consumers as 2 which is good.
Also, when any message is put on the topic , BPEL processes for both consumers get triggered as expected.
Now, I add durable subscriber ID as 123 to one of the consumers (consumer 1)
After deploying the code, the count for the number of current consumers listening becomes 1.
So I create a durable subscriber on the console with id as 123 after which the consumer count is back to 2.
The issue however is that, now when I put a message on topic , only consumer 2 is triggered.
The message for consumer 1 can be seen on the durable subscriber 123's page.
My question is that, since the consumer is listening to the topic then why is the message going to the subscriber instead of creating instance ?
I also tried following :
1. created a new outbound connection pool in the resource adapter
2. setting property FactoryProperties to value "ClientID=123"
3. pointing the adapter connection factory to this new location
but this is also not helping.
Could anyone please help me out in this ?
Thanks and Regards,
Ketan

did u have any luck? can u tell me steps

Durable subscribers questions

Hello,
          I am building an application that has two WebLogic servers
          communicating certain information between them using JMS. I am using
          WebLogics implementation of JMS including destinations and messaging
          bridges.
          I am experiencing some problems.
          Server 1 takes files and puts them in a Stream Message and publishes
          them to a topic as shown here:
          Context context = new InitialContext();
          TopicConnectionFactory topicFactory = (TopicConnectionFactory)
          context.lookup(sourceDescriptor.getConnectionFactory());
          connection = topicFactory.createTopicConnection();
          session = connection.createTopicSession(false,
          Session.CLIENT_ACKNOWLEDGE);
          Topic topic = (Topic)
          context.lookup(sourceDescriptor.getTopicJNDIName());
          TopicPublisher publisher = session.createPublisher(topic);
          publisher.setDeliveryMode(DeliveryMode.PERSISTENT);
          StreamMessage message = session.createStreamMessage();
          for (int i = 0; i < files.length; i++)
          Loop through reading a set of files into the StreamMessage publishing
          each.
          publisher.publish(message);
          Topic config.xml
          <JMSTopic JNDIName="topic/topicName"
          Name="Topic Name" StoreEnabled="default"/>
          Destination config.xml
          <JMSBridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDINoTX"
          ConnectionFactoryJNDIName="ConnectionFactory"
          ConnectionURL="t3://localhost:7001"
          DestinationJNDIName="queue/queueName" Name="Queue Destination
          Name"/>
          <JMSBridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDINoTX"
          ConnectionFactoryJNDIName="ConnectionFactory"
          ConnectionURL="t3://machinename:8001"
          DestinationJNDIName="topic/topicName"
          DestinationType="Topic" Name="Topic Source Name"/>
          Messaging Bridge config.xml
          <MessagingBridge
          Name="The Bridge"
          QOSDegradationAllowed="true" QualityOfService="Duplicate-okay"
          SourceDestination="Topic Source Name"
          TargetDestination="Queue Destination Name" Targets="server1"/>
          Connection Factory
          <JMSConnectionFactory JNDIName="ConnectionFactory"
          Name="Server1 Connection Factory" Targets="server1"/>
          All settings in WebLogic are default for the configuration of this as
          far as I know.
          The bridge is using Duplicate Ok QOS at this point.
          This works like a charm as long as server which has the destination
          queue is up and running and has received messages in the past.
          The first problem is the first set of messesages are sent to the Queue
          on Server 2 but the MDB does not pick them up. I have left it running
          for an hour and these messages sit in the pending state for the
          monitoring of the Queue. In order to get this first set of messages
          to be processed I have to restart Server 2 at which point the initial
          messages are processed. Any subsequent messages are processed by the
          MDB immediately upon delivery. What is the cause of this and is there
          any way around having to restart after the first messages are received
          creating the file in the message store? Does this have anything to do
          with the fact that there is no file in the message store until the
          first messages are received and thus the MDB is not looking since
          there was nothing there on start up? This seems very odd....
          The second problem has to do with durability. I start Server 1 and it
          waits for a finish file and when it sees it it takes the files and
          puts them on the topic as described. As long as Server 2 is up and
          running at that time everything is fine. If However Server 2 is not
          running at that moment and is started at a later time then the
          messages seem to be lost. What could cause this? Is there any way I
          can visually see that the message is being held on Server 1? The
          bridge from this topic on Server 1 to the queue on Server 2 is
          configured on Sever 1 and you can see that it is working when Server 2
          is not running due to the connection refused messages the bridge
          throws. Is the bridge accepting the messages from the topic enough
          for the topic to decide it is done with them and delete them? Could
          the acknowledgement from the queue on another bridge for the same
          topic be confusing the topic and deleteing the message before all
          subscribers get it? This is a big issue since it seems that durabilty
          is only guarenteed when both servers are running and a message is
          created.
          Any help on this would be appreciated...If you wouldn't mind cutting
          and pasting any responses to my email as well it would be appreciated
          as I use google for groups and it has a long turn around.
          TIA...


Hi Kartheek,
Once we create a TOPIC in NWA.In durable subscribers tab subscription ID and Subscription name will be automatically created once you publish the message in to TOPIC.
check in NWA-->jms server configuration-->durable subscribers.
thanks
Purna

Two durable subscribers with same ID in Weblogic 9.2 MP 2?

External JMS durable topic subsribers of a distributed topic destination are connected to a Weblogic cluster with 3 Nodes. The clients are started with shell scripts on different hosts. A watchdog is checking if the clients are still alive; if not, they are restarted automatically. Randomly a node of the cluster is chosen and the client is reconnected (Note: Weblogic does not support durable topic subscribers for distributed destinations, this means you cannot connect with a cluster URL)
          However, from time to time we see two durable topic subscribers with the SAME ID connected on two different destinations: one of them is active, the other is not.
          This should not be possible. Is this a Weblogic bug or a mis-configuration of our domain.
          Thanks,
          Peter

It turned out that our operating team stops the clients with "kill -9". I guess that this may be the reason that the durable subscribers remain registrated on the server? Of course, one should never use "kill -9", however sometimes this can not be avoided:
          - Weblogic 8.1 SP 4 could not startup if a durable "ghost" subscriber was registrated
          - Weblogic 8.1 SP 6 could handle this in a robust way!
          - Weblogic 9.2 MP1/2 seems to go to an unstable state. Once, for example, we registrated 1635 connections for one Weblogic instance with the state "CLOSE_WAIT" (Of course you may argue this may be the cause of our inconvinience. However, normally this value is less than 20)
          The fact that the durable subscribers are not correctly placed in the Weblogic console may not be correlated to the problem above, but just another bug. It is just annoying, as it is nearly impossible to unregister the durable "ghost" subscriber via the console. Sometimes even the subscriber id is not shown.
          Do my comments sound reasonable?
          Thanks, Peter

What happens if I don't set a client id for durable subscribers?

What happens if I don't set a client id for durable subscribers?

If you do not set a clientID in 2.0, it will automatically set a clientID for
you. This means that you MUST unsubscribe the durable subscriber on the same
host (since otherwise the clientID's will be different)
In general, its good practice to set a client ID anytime you are using durables
(so that you have some control).

Doubt about durable subscribers

I read this in the weblogic docs
          For durable subscriptions, WebLogic JMS stores a message in a persistent
          file or database until the message has been delivered to the subscribers
          or has expired, even if those subscribers are not active at the time
          that the message is delivered. A subscriber is considered active if the
          Java object that represents it exists. Durable subscriptions are
          supported for Pub/Sub messaging only.
          Now how does the weblogic server know how many subscribers are there? To
          describe more accurately
          1. One weblogic server, say version 7.0. One topic has been configured
          along with
          the other required stuff.
          2. Suppose 3 subcribers connect to the server
          3. A message is sent to the topic.
          4. Now if I kill one of the subscribers then is weblogic going to wait
          to deliver to the killed subscriber before marking the message as
          delivered?
          Shiva.


WebLogic does not do anything different than any other
          JMS vendor. The behavior of durable subscriptions is
          explicitly defined in the JMS standards.
          The durable subscriber client explicitly creates "subscription"
          when it first comes up. The JMS server stores a record of this
          subscription both in memory and on disk. The subscription
          does not go away until the client explicitly calls
          "unsubscribe" to delete it. The subscription,
          as per the JMS spec, is uniquely identified by a combination
          of: the topic specified by the client, the connection-id
          specified by the client, and the subscriber-id specified by
          the client. The subscription is not identified in any
          way by "JVM id". All messages sent after the subscription
          is created accumulate, even if the client is disconnected.
          The client reconnects by specifying by subscribing with the
          same identifiers it used to so subscribe previously.
          Tom
          Shiva P wrote:
          > Guess my question is not clear. Here it is again.
          >
          > How does weblogic know that it has to wait for the durable subscriber? I mean
          > is it the JVM id of the subscriber or some other unique thing that weblogic
          > uses to know about all the durable subscribers?
          >
          > shiva.
          >
          > Tom Barnes wrote:
          >
          >
          >>Shiva P wrote:
          >>
          >>>I read this in the weblogic docs
          >>>For durable subscriptions, WebLogic JMS stores a message in a persistent
          >>>file or database until the message has been delivered to the subscribers
          >>>or has expired, even if those subscribers are not active at the time
          >>>that the message is delivered. A subscriber is considered active if the
          >>>Java object that represents it exists. Durable subscriptions are
          >>>supported for Pub/Sub messaging only.
          >>>
          >>>Now how does the weblogic server know how many subscribers are there? To
          >>>describe more accurately
          >>>
          >>>1. One weblogic server, say version 7.0. One topic has been configured
          >>>along with
          >>>the other required stuff.
          >>>2. Suppose 3 subcribers connect to the server
          >>>3. A message is sent to the topic.
          >>>4. Now if I kill one of the subscribers then is weblogic going to wait
          >>>to deliver to the killed subscriber before marking the message as
          >>>delivered?
          >>
          >>Yes, if the subscription is durable.
          >>
          >>Durable subscription continue to exist even if the consumer
          >>is killed (or closed). Messages continue to accumulate in
          >>them. This is the whole purpose of durable subscriptions. If
          >>you want the messages to go away when the consumer goes away
          >>do not use a durable subscriptions.
          >>
          >>Tom
          >>
          >>
          >>>Shiva.
          >>>
          >>
          >

How many durable subscribers can a session have?

On the API doc for session.createDurableSubscriber(), it is documented that:
"Sessions with durable subscribers must always provide the same client identifier. In addition, each client must specify a name which uniquely identifies (within client identifier) each durable subscription it creates. Only one session at a time can have a TopicSubscriber for a particular durable subscription. An inactive durable subscriber is one that exists but does not currently have a message consumer associated with it."
If a "particular durable subscription" is uniquely identified by client id and subscriber name, does that mean a session cannot have multiple durable subscribers, even though they are for different topics?
Ed

Answer is yes: a session can have multiple durable subscriptions, but only one active subscriber (or message listener) for a particular durable subscription.

List durable subscribers

Hi,
I have a server which connects to MQSeries topics with a durable subscriber.
Now, if my program is terminated unexpectetly, the subscriber cannot be made inactive(closed). If I then want to restart my program (so trying to connect to the topic with the same durable subscriberID), I sometimes get the error that there is still an active subscriber (which is normal, since previous one did not end correctly). Is there somehow a way to list all durable subscribers for a topic and/or to remove them (make them inactive)??
I hope my question is clear.
Thanx in advance,
Ssteven

hi,
I have exactly the same problem with IBM's implementation of JMS and could not find any workaround. One of IBM redbooks claims that there is a Cleanup utility that can be used to cleanup these type of subscribers, however, the utility only supports Java 1.3. I can't seem to find a version that supports 1.2. Did you have the problem resolved? What is your solution?
Your help will be greatly appreciated!!
ckshen00

Non Durable subscribers

Hi,
I am currently developing an application in java that will use Oracle 8i's (8.1.7 to be more specific) Advanced Queuing Java API. Is there any way to mimic a non-durable subscriber in Oracle 8i? Both 8i and 9i don't support non durable subscribers.
Thanks,
Jeff
null

I'm not sure what exactly you mean by non-durable subscribers. If you are mean the subscriptions should be dropped after the session is deleted - you can create unique subscriber names for every session and unsubscribe when a session is closed. You'll have to record these subscriber names somewhere persistently and in case of abnormal session termination, you'll have to drop them later

Non-durable subscribers persists after the end of their JMS session

Hi all,
I'm using OAQ as my JMS Provider.
I have created code for publishing and recieving messages to/from topics. Messaging works fine, but I have one problem:
All my non-durable subscribers persists after the end of their JMS session. I always perform unsubscribe operation in code and then closing session and connection.
When I subscribe to topic, there's one more line in DB table ( etc. NAME: TSUB_1_24E6DB98A2EB7712E040A8C, TYPE: 65). I have expected that subscribers will be deleted after performing unsubscribe operation, but they don't...
Can you help me with this problem? Thanks for any answer.
Best Regards,
Juraj

Have you found a solution to this yet - because I face the same problem

Removing durable subscribers

Is it possible to "purge" durable subscriptions established by JMS clients ? Any APIs available for this ?
Here is the scenrio. My application has a unique ID. The application establishes durable subscribers to a few topics. The uniqe ID is used in the setClientID() of the topic connection. Based on the messages it receives, the application would create more durable subscribers . All the subscribers are
created off of the same topic connection object.
When I "uninstall" the application, I want to "unsubscribe" or "remove" all the subscriptions established by the application. All I know about the application is the Unique ID and I do not know the subscriber id of the individual durable subscribers.
So, my question is, is it possible to "remove" all the subscription created by the application given the client id used in the application ?
TopicSession.unsubscribe() wont work for me because I do not know the subscriber id.
Is there a "Management" API availabe to to this ?

There is no management API to do what you described.
The MQ administration utilities do have support for purging
and destroying durable subscribers though. See the
'Managing Durable Subscriptions' section of chapter 6 in
the MQ Administration Guide.
imqcmd list dur -d topicName
imqcmd purge dur -n durableName -c clientID
imqcmd destroy dur -n durableName -c clientID
hope this helps,
-isa

Durable subscribers loosing messages

Hi,
          This is wls 8.1.4
          We have a distributed topic (T) with durable subscribers (DS)connected to both the member topics.
          Looks like the DS's connected to Member Topic 1 (MT1) loose some of the messages posted to T.
          DS's connected to MT2 get all the messages.
          From the admin console I also see that one of the Weblogic durable subscribers to MT1 is inactive and has a backlog.
          Not sure if this is causing the problem.
          WeblogicJmsDistributedTopic@Remote@MT1@Local@MT2@Dist@T
          is inactive and has backlog
          WeblogicJmsDistributedTopic@Remote@MT2@Local@MT1@Dist@T
          is active
          Thanx,

Hi Kartheek,
Once we create a TOPIC in NWA.In durable subscribers tab subscription ID and Subscription name will be automatically created once you publish the message in to TOPIC.
check in NWA-->jms server configuration-->durable subscribers.
thanks
Purna

Item cost not found for one or more items - Inventory Posting

Good Day Mentors,
My user has encountered an error during Inventory Posting and its "Item cost not found for one or more items".
The specific Message ID from SAP's System Message Log is 10001287.
I found a similar post which addresses this error here.
But unfortunately it did not help me solve my user's problem.
I already checked if the items had a defined "Item Cost" in the Item Master Data Inventory Tab, and they all have "Item Cost" defined.
I'm not sure if this will help, but below is the Inventory Audit Report of one of the items that is throwing the "Item cost not found" error.
I am not a business consultant neither am I literate in accounting, so thanks for the patience.
SAP Version: 9.0 PL5
Valuation Method: Moving Average
Thanks in advance!
Sean

Hi Augusto and Raviraj,
I've already verified in our production database the points you made:
- Is the "Manage Item cost per warehouse" selected in the Basic Initialization Screen?
YES
- Is the "Manage Inventory by Warehouse" ticked/checked in the "Inventory Data" tab of the "Item Master Data" screen?
YES
* I apologize for not have been able to give this information upfront.
Anyway, the database only has one warehouse at the moment.
I've checked the items, like the item in the screen shot above, and it does have an item cost.
Below is the screenshot of the sample item from my original post,
Thanks in advance!
Sean

Durable Subscribers not found

Similar Messages

Maybe you are looking for