]
Bill Burke commented on EJBTHREE-629:
-------------------------------------
i cannot reproduce this in HEAD
need to get remote binding uri from Connector for default
---------------------------------------------------------
Key: EJBTHREE-629
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-629
Project: EJB 3.0
Issue Type: Task
Affects Versions: EJB 3.0 RC8 - FD
Reporter: Andrea Luciano
Assigned To: Bill Burke
Fix For: EJB 3.0 RC2, EJB 3.0 RC9 - FD
The issue
http://jira.jboss.com/jira/browse/EJBTHREE-204 reopen.
I downloaded jboss 4.0.4 GA and jboss-EJB-3.0_RC8-FD.
I installed jboss and ejb3 support than I tryed to modify the standard port 3873 so I
changed the file deploy/ejb3.deployer/META-INF/jboss-service.xml:
<mbean code="org.jboss.remoting.transport.Connector"
xmbean-dd="org/jboss/remoting/transport/Connector.xml"
name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
<depends>jboss.aop:service=AspectDeployer</depends>
<attribute
name="InvokerLocator">socket://${jboss.bind.address}:10009</attribute>
<attribute name="Configuration">
<handlers>
<handler
subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
</handlers>
</attribute>
</mbean>
While the server listens correctly on new port the client has no way to contact the bean
I deployed.
Using strace I figured out that the client ignores the new port and tries to contact port
3873 as before RC3 of ejb3 support (while another installation with ejb3 rc3 works without
problems).
Is this a regression?
Regards.
Andrea
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: