Re: [jboss-user] [JBoss Remoting] - JMREM-821 Included in 2.2.3 SP1 ???
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"JMREM-821 Included in 2.2.3 SP1 ???"
To view the discussion, visit: http://community.jboss.org/message/551103#551103
--------------------------------------------------------------
Hi Mike,
Re-reading the JIRA issue, it looks like the code changes were in response to Tim Fox's concerns about Remoting's shutdown behavior, but the problem itself was solved by configuration: "After increasing the client pool size I'm not getting these exceptions any more."
As for whether the code changes are included in Remoting release 2.2.3.SP1, the answer is "no." Remoting 2 has two branches that contribute releases to currently supported versions of the Enterprise Application Platform (EAP). Branch 2.2 ( http://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.2 http://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.2) contributes releases 2.2.x to EAP 4.2/4.3, and branch 2.x ( https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x https://svn.jboss.org/repos/jbossremoting/remoting2/branches/2.x) contributes release 2.4/2.5 to EAP 5.x. These code bases diverged years ago, and, though I often apply a particular fix to both branches, they are distinct. In particular, the changes referred to in JBREM-821 were made to branch 2.x, but do not exist on branch 2.2.
By the way, if you look at the "Subversion Commits" tab on JBREM-821, you'll see that all of the commits were to branch 2.x.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551103#551103]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 5 months
Re: [jboss-user] [JBoss Remoting] - Need help invoking EJB 2.0 on JBoss 4.3.0 from JBoss 4.0.5 client
by Ron Sigal
Ron Sigal [http://community.jboss.org/people/ron.sigal%40jboss.com] replied to the discussion
"Need help invoking EJB 2.0 on JBoss 4.3.0 from JBoss 4.0.5 client"
To view the discussion, visit: http://community.jboss.org/message/551079#551079
--------------------------------------------------------------
Hi Clive,
Yeah, that's a problem. Setting the -Djboss.remoting.pre_2_0_compatible=true flag affects Remoting throughout the JVM, so you can't satisfy both EJB and JBossMessaging. I don't think there's a way around that in AS 4, which uses Remoting version 2.2.x.
On the other hand, AS 5 uses Remoting 2.4/2.5, which has an option for setting the "remotingVersion" parameter on each Remoting Connector. So, in $JBOSS_HOME/server/$CONFIG/deploy/remotng-jboss-beans.xml, you could update the "UnifiedInvokerConfiguration" bean with
<!-- Parameters visible to both client and server -->
<property name="invokerLocatorParameters">
<map keyClass="java.lang.String" valueClass="java.lang.String">
...
<entry>
<key>remotingVersion</key>
<value>1</value>
</entry>
...
</map>
</property>
That would configure EJB2 to use the old wire format, and JBossMessaging would default to the new wire format.
-Ron
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/551079#551079]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 6 months