Client-acknowledge Mode

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Client-acknowledge Mode

TheQL
Hallo,

ein Partner ruft die SwiftMQ-Clientlibraries für die Verbindung zu einem SwiftMQ-Server aus einer Drittherstellerapplikation heraus auf und erhält dabei regelmäßig folgenden Fehler:

13:51:39 SYSTEM:MESSAGE:JMSLISTENER exception in handling jms message for Queuename:
javax.jms.IllegalStateException: acknowledge not possible, session was not created in mode CLIENT_ACKNOWLEDGE!
                at com.swiftmq.jms.v750.MessageConsumerImpl.acknowledgeMessage(Unknown Source)
                at com.swiftmq.jms.MessageImpl.acknowledge(Unknown Source)
                at com.ebd.hub.services.message.jms.JMSListener.handle(JMSListener.java:295)
                at com.ebd.hub.services.message.jms.JMSListener.handleQueue(JMSListener.java:182)
                at com.ebd.hub.services.message.jms.JMSListener.init(JMSListener.java:159)
                at com.ebd.hub.services.message.jms.JMSListener.run(JMSListener.java:78)

Ich bin nun unsicher, woher die Erwartung des Acknowledge stammt, kann man das am Server oder Client gezielt de- oder aktivieren oder ist hier der Hersteller der Dritthersteller-App gefragt?
Reply | Threaded
Open this post in threaded view
|

Re: Client-acknowledge Mode

IIT Software
Administrator
Your app calls message.acknowledge() although the session was not created with client-ack mode (connection.createSession(...)).
Reply | Threaded
Open this post in threaded view
|

Re: Client-acknowledge Mode

TheQL
Thanks, I will pass that on, they will need to get in touch with their product support. Which connection.createSession(...) parameters would be needed to create a connection with client-ack mode that would support calling message.acknowledge()?
Reply | Threaded
Open this post in threaded view
|

Re: Client-acknowledge Mode

IIT Software
Administrator
Exactly.