Yeah I faced this problem as well. It was some time back but from what I can remember I believe the solution was to have two jars available.
1. spring-2.5.3.jar 2. spring-webmvc-2.5.3.jar The reason is that now, post 2.5, the DispatcherServlet is in the second jar. This would be preferable to moving back to spring 2.0.6. On Wed, Apr 9, 2008 at 7:49 AM, Hatta <[EMAIL PROTECTED]> wrote: > > hi Raj, > > Thanks for note and i ve did as what u ve advised. > > Result: No more exceptions such as reported being generated in the logs. > (Two thumbs up!) > > However, I would like to point out what was observed by other activemq users > have spotted as well. Its regarding the Spring DispatchServlet. > > ActiveMQ 5.1 Snapshot is unable to start the admin console cuz this file is > missing. Further investigation revealed that the library is Spring 2.5. > > Based on the thread discussions, the suggestion wuz to replace this Spring > 2.5 with Spring 2.0.6. That got the activemq broker started again without > any errors and I m able to see the results that you mentioned earlier. > > Please rectify this library issues as activemq has been selected for > production use from my side. > > Again, thanks for the help. > > Hatta > > > > > > > rajdavies wrote: > > > > I think this problem will go away if you use the latest 5.1 snapshot > > - please let us know if this is not the case > > > > On 8 Apr 2008, at 10:45, Hatta wrote: > > > >> > >> Hi Dil, > >> > >> Yes, I have received the same thing. I have browse thru all the > >> related > >> issue in AMQ 5.0.0 but non avail. > >> > >> Appreciate a response from the team about this matter. > >> > >> This log can be really disturbing when the solution goes to > >> production. > >> > >> Regards > >> Hatta > >> > >> > >> > >> Dil wrote: > >>> > >>> Did somebody see this Warning exception while using active MQ 5 when > >>> sending asynchronous messages? > >>> > >>> this is exception i am getting on producer class after some time of > >>> its > >>> running. > >>> > >>> the url for broker is : > >>> tcp://localhost:61616?trace=true&wireFormat.maxInactivityDuration=-1 > >>> > >>> 10:44:44,427 WARN ActiveMQConnection:1653 - Async exception with no > >>> exception listener: java.net.SocketException: socket closed > >>> java.net.SocketException: socket closed > >>> at java.net.SocketInputStream.socketRead0(Native Method) > >>> at java.net.SocketInputStream.read(Unknown Source) > >>> at > >>> org > >>> .apache > >>> .activemq > >>> .transport > >>> .tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:50) > >>> at > >>> org > >>> .apache > >>> .activemq > >>> .transport > >>> .tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:58) > >>> at java.io.DataInputStream.readInt(Unknown Source) > >>> at > >>> org > >>> .apache > >>> .activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:268) > >>> at > >>> org > >>> .apache > >>> .activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java: > >>> 192) > >>> at > >>> org > >>> .apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java: > >>> 184) > >>> at > >>> org > >>> .apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: > >>> 172) > >>> at java.lang.Thread.run(Unknown Source) > >>> > >> > >> -- > >> View this message in context: > >> > http://www.nabble.com/ActiveMQConnection%3A1653---Async-exception-with-no-exception-listener%3A-java.net.SocketException%3A-socket-closed-tp16323372s2354p16553555.html > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >> > > > > > > > > -- > View this message in context: > http://www.nabble.com/ActiveMQConnection%3A1653---Async-exception-with-no-exception-listener%3A-java.net.SocketException%3A-socket-closed-tp16323372s2354p16580643.html > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
