Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 843830, 1 year ago
JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154
via hivmr.com by Unknown author, 1 year ago
JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154
com.sun.jbi.jmsbc.MessageExchangeProcessingException: JMSBC-E0715: Message exchange pattern for binding operation docServiceOperation is inout; can not send back output reply if no JMSReplyTo field is specified in JMS message with JMSMessageID ID:41-137.172.75.188(be:11:b3:ba:36:f5)-4477-1211856855154	at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.processInboundRequest(InboundMessageProcessorListenerEndpoint.java:399)	at com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint.onMessage(InboundMessageProcessorListenerEndpoint.java:225)	at com.stc.jmsjca.core.Delivery.deliverToEndpoint(Delivery.java:1105)	at com.stc.jmsjca.core.SyncDelivery$SyncWorker.runOnceStdNoXA(SyncDelivery.java:700)	at com.stc.jmsjca.core.SyncDelivery$SyncWorker.run(SyncDelivery.java:757)