Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-18 Thread Johan Haleby
t of dynamic endpoints which are different? >>>>>>>> >>>>>>>> >>>>>>>>> /Johan >>>>>>>>> >>>>>>>>> >>>>>>>>> Claus Ibsen-2 wrote: >&

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-18 Thread Claus Ibsen
gt;>>>>> >>>>>>>>> And you see this DEBUG logging when you send to that remote >>>>>>>>> endpoint? >>>>>>>>> >>>>>>>>>             if (LOG.isDebugEnabled()) { >&g

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-18 Thread Johan Haleby
(LOG.isDebugEnabled()) { >>>>>>>>                 LOG.debug("Closing session when complete at >>>>>>>> address: " >>>>>>>> + endpoint.getAddress()); >>>>>

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Johan Haleby
gt; endpoints >>>>>>>> configured to disconnect the session after each received message. >>>>>>>> When >>>>>>>> lots >>>>>>>> of messages are sent over a longer period of time I eventually run >>>

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Claus Ibsen
gt;>> memory and the system either throws OutOfMemoryError or spends long >>>>>>> intervals in GC. When analyzing the heap dump in Eclipse MAT it finds >>>>>>> this >>>>>>> leak suspect: >>>>>>> >>>>>

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Johan Haleby
figured to disconnect the session after each received message. >>>>>> When >>>>>> lots >>>>>> of messages are sent over a longer period of time I eventually run >>>>>> out >>>>>> of >>>>>> m

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Claus Ibsen
d like: >>>>> mina:tcp://localhost:6200?sync=false&textline=false and the message is >>>>> sent >>>>> to the endpoint using a  http://camel.apache.org/recipient-list.html >>>>> recipient list . >>>>> >>>>> What cou

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Johan Haleby
62,464 >>>> (20.42%) >>>> bytes >>>> >>>> The endpoint is configured like: >>>> mina:tcp://localhost:6200?sync=false&textline=false and the message is >>>> sent >>>> to the endpoint using a  http://camel.apache.org/recip

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Claus Ibsen
gt;> >>> The endpoint is configured like: >>> mina:tcp://localhost:6200?sync=false&textline=false and the message is >>> sent >>> to the endpoint using a  http://camel.apache.org/recipient-list.html >>> recipient list . >>> >>&g

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Johan Haleby
-retained-in-memory-indefinitely-tp27624487p27624487.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > -- View this message in context: http://old.nabble.com/SocketSessionImpl-in-Mina-component-retained-in-memory-indefinitely-tp27624487p27625230.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Claus Ibsen
pache.org/recipient-list.html > recipient list . > > What could be the cause of this? E.g. do I need to stop the producer > template after each sent message? Right now the ProducerTemplate is a > singleton used concurrently by multiple threads. > > /Johan > -- > Vi

SocketSessionImpl in Mina component retained in memory indefinitely

2010-02-17 Thread Johan Haleby
now the ProducerTemplate is a singleton used concurrently by multiple threads. /Johan -- View this message in context: http://old.nabble.com/SocketSessionImpl-in-Mina-component-retained-in-memory-indefinitely-tp27624487p27624487.html Sent from the Camel - Users mailing list archive at Nabble.com.