[ http://jira.jboss.com/jira/browse/JBESB-1711?page=comments#action_12417814 ] Tom Cunningham commented on JBESB-1711: --------------------------------------- I see the freeze, and when I kill off the tests, I see an exception here : java.io.IOException at java.io.DataInputStream.readFully(DataInputStream.java:178) at java.io.DataInputStream.readLong(DataInputStream.java:380) at org.jboss.jms.wireformat.ClosingRequest.read(ClosingRequest.java:56) at org.jboss.jms.wireformat.JMSWireFormat.read(JMSWireFormat.java:298) at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:665) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:533) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) Try copying over the versions of jboss-messaging-client.jar and jboss-remoting.jar over from SOA-P into your product/lib/ext directory. That got me past the hangs, although I did see errors on FTP tests afterwards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1711?page=com.atlassian.jira.plu... ] Len DiMaggio commented on JBESB-1711: ------------------------------------- We should revisit this issue - when we start testing SOA-P "one-offs" we'll want to be able to run these tests as a regressison test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1711?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-1711: ------------------------------------- The issue is likely to be related to having the wrong version of JBossRemoting, going by past experience, and may have been addressed with the recent work to tidy up the jars. Do we know if this is still a problem with the recent IR5 cut? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1711?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-1711: ------------------------------------- Hmm, we did have a JIRA to address that at one point. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1711?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-1711: ------------------------------------- Yep, that looks like the one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1711?page=com.atlassian.jira.plu... ] Tom Cunningham updated JBESB-1711: ---------------------------------- Fix Version/s: 4.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira