[ http://jira.jboss.com/jira/browse/JBAS-4359?page=all ] Dimitris Andreadis updated JBAS-4359: ------------------------------------- Attachment: apr212007.zip Attach JBoss Profiler report. -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=comments#action_12360300 ] Clebert Suconic commented on JBAS-4359: --------------------------------------- The issue is that remoting now will aways keep the last invocation objects on the memory, until the next invocation or until the invoker is down. This was changed on the protocol.. .Remoting used to aways clear its object through a object.clear/object.writeDumbObject. This was changed on remoting marshallers now: public void sendObject(ObjectOutputStream oos, Object dataObject) throws IOException { oos.reset(); oos.writeObject(dataObject); // oos.reset(); // to make sure stream gets reset // Stupid ObjectInputStream holds object graph // can only be set by the client/server sending a TC_RESET // oos.writeObject(Boolean.TRUE); oos.flush(); // oos.reset(); } So... a fix would be either to change the testcase to send another message dumb message after the ejb test. Or to hack remoting code to clear ObjectInputStream without changing binary format. Dimitris.. I would like to talk to you about this. If you could call me over e-mail, telephone, smoke sign, telepathy, IM or any other way you like :-) -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=all ] Clebert Suconic updated JBAS-4359: ---------------------------------- Attachment: ObjectInputStreamWithClassLoader.java Proposed fix on remoting -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=all ] Clebert Suconic updated JBAS-4359: ---------------------------------- Comment: was deleted -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=comments#action_12360314 ] Ron Sigal commented on JBAS-4359: --------------------------------- Thank you for catching this, Clebert. I'm running the Remoting test suite with your changes, and as soon as it's done. I wll put a 2.2.0.SP2 jboss-remoting.jar in the repository. Clebert, can you think of a unit test? FYI: - Remoting HEAD is basically Remoting 3 - Remoting_2_x is "HEAD" for Remoting 2.x - Remoting_2_2_0_GA is for patches to Remoting 2.2.0 -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=all ] Ron Sigal updated JBAS-4359: ---------------------------- Attachment: RawTestCase.output -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=comments#action_12360320 ] Ron Sigal commented on JBAS-4359: --------------------------------- The Remoting test suite has finished, and the RawTestCase is the only problem. The only difference between the "fake" Remoting client invoker and the real one (using the JavaSerializationManager) is that the latter writes a TC_RESET byte before writing each object. When I updated RawTestCase to write a TC_RESET byte, it works. So, I'll put a new jboss-remoting.jar in the repository. -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=comments#action_12360323 ] Ron Sigal commented on JBAS-4359: --------------------------------- I don't think things would work otherwise. The socket transport writes the whole invocation at once, so the loop goes (unrolling things a little): ObjectOutputStream oos = ...; ObjectInputStream ois = ...; int version; while (...) { oos.write(version); oos.reset(); oos.writeObject(invocation); oos.flush(); version = ois.read(); Object result = ois.readObject(); } -- 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

[ http://jira.jboss.com/jira/browse/JBAS-4359?page=comments#action_12360327 ] Dimitris Andreadis commented on JBAS-4359: ------------------------------------------ The version in the component-info.xml should be SP2, not SP1. I've corrected it. <component id="jboss/remoting" licenseType="lgpl" version="2.2.0.SP2" -- 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