Claus Ibsen-2 wrote:
>
> Yes you need to pass in this header every time you want to session closed.
>
I'm pretty convinced that this isn't happening for me despite passing in the
header that I want the session closed when complete (which I presume is when
I get a reply). Here's my log file:
2010-01-21 15:57:59,406 [lCalendarEvents] DEBUG
lendarEventAttendeeSMSNotifier - Sending message to xxx: Reply to confirm
meeting closed Thu, 21 Jan '10 03:35PM Scen 7 # 7
2010-01-21 15:57:59,409 [IoProcessor-1.2] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] CREATED
2010-01-21 15:57:59,409 [IoProcessor-1.2] DEBUG ExecutorFilter
- Launching thread for /192.168.0.200:9500
2010-01-21 15:57:59,410 [ MinaThreadPool] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] OPENED
2010-01-21 15:57:59,410 [ MinaThreadPool] DEBUG ExecutorFilter
- Exiting since queue is empty for /192.168.0.200:9500
2010-01-21 15:57:59,410 [lCalendarEvents] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] WRITE:
au.com.blueglue.bluegluesmsprotocol.send...@8e1a0d01
2010-01-21 15:57:59,411 [IoProcessor-1.2] DEBUG ExecutorFilter
- Launching thread for /192.168.0.200:9500
2010-01-21 15:57:59,411 [ MinaThreadPool] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] SENT:
au.com.blueglue.bluegluesmsprotocol.send...@8e1a0d01
2010-01-21 15:57:59,411 [ MinaThreadPool] DEBUG ExecutorFilter
- Exiting since queue is empty for /192.168.0.200:9500
2010-01-21 15:58:10,979 [IoProcessor-1.2] DEBUG ExecutorFilter
- Launching thread for /192.168.0.200:9500
2010-01-21 15:58:10,979 [ MinaThreadPool] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] RECEIVED:
au.com.blueglue.bluegluesmsprotocol.transmitted...@8e1a0d01
2010-01-21 15:58:10,979 [ MinaThreadPool] DEBUG ExecutorFilter
- Exiting since queue is empty for /192.168.0.200:9500
2010-01-21 15:58:10,979 [lCalendarEvents] DEBUG
lendarEventAttendeeSMSNotifier - Message sent
2010-01-21 15:58:10,980 [lCalendarEvents] DEBUG
lendarEventAttendeeSMSNotifier - Sending message to yyy: Reply to confirm
meeting closed Thu, 21 Jan '10 03:35PM Scen 7 # 7
2010-01-21 15:58:10,980 [lCalendarEvents] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] WRITE:
au.com.blueglue.bluegluesmsprotocol.send...@808819c0
2010-01-21 15:58:10,981 [IoProcessor-1.2] DEBUG ExecutorFilter
- Launching thread for /192.168.0.200:9500
2010-01-21 15:58:10,981 [ MinaThreadPool] INFO MinaProducer$ResponseHandler
- [/192.168.0.200:9500] SENT:
au.com.blueglue.bluegluesmsprotocol.send...@808819c0
2010-01-21 15:58:10,981 [ MinaThreadPool] DEBUG ExecutorFilter
- Exiting since queue is empty for /192.168.0.200:9500
2010-01-21 15:58:10,983 [IoProcessor-1.2] DEBUG ExecutorFilter
- Launching thread for /192.168.0.200:9500
...
After the received event at 2010-01-21 15:58:10,979, I was hoping that the
socket would be closed. As you can see there is no trace in the log of the
socket being closed.
Is this a bug or am I not doing something quite right. Here's my code again:
Object replyMessage = producerTemplate
.requestBodyAndHeader(
smsSenderEndpoint,
requestMessage,
MinaConsumer.HEADER_CLOSE_SESSION_WHEN_COMPLETE,
true);
The above template instance is called twice in succession as shown by the
"Sending message to" entries.
Thanks for your help.
Kind regards,
Christopher
--
View this message in context:
http://old.nabble.com/requestBodyAndHeader-and-HEADER_CLOSE_SESSION_WHEN_COMPLETE-tp27175565p27255912.html
Sent from the Camel - Users mailing list archive at Nabble.com.
