pub.jms:createConsumer , creates a volatile client on the broker which subscribes to the document only when the Consumer flow service which you have written is executing. After the execution of the flow service the corresponding client is deleted from the broker.
There can be two approaches to your problem . They are mentioned below :-
If you are aware that when the messages will be pushed on the topic then you can create one schedule task which will call the consumer service at that instance of time and also give some timeout value in the pub.jms:receive step whic will allow the volatile client to be active for that much time.
Second approach is the most widely used i.e. you need to use the durable subscriber which allows subscribers to receive all the messages published on a topic, including those published while the subscriber is inactive. So give the durable subscriber name in the pub.jms:createConsumer step of the flow service.
I have created a trigger and selected that JMS connection alias which has the external system details.
in Destination name : mentioned the TOPIC path from where we pick the data.
service name : the service name given where it has flow steps create consumer and receive services.
I can see in logs it’s polling onto the destination and trying to fetch the data , but in between it’s getting disconnected
with the exception “com.wm.app.b2b.server.jms.JMSCoderException: weblogic.jms.common.JMSException: [JMSClientExceptions:055115]Error deserializing an object [Linked Exception] java.lang.ClassNotFoundException: org.apache.openjpa.util.java$sql$Timestamp$proxy”
Trying to determine this exception is relevant to the application or some additional jars required in webM.
Please let me know if you have any idea on this exception