-
1. Re: Changing default InvokerLocator port (ejb3-deployer)
ipetros Jun 12, 2006 6:34 AM (in response to rthompson)We still hav the same problem - multiple jboss configurations on the same machine. How to say to jboss AS server that EJB3 InvokerLocator runs on the other port than the default one (3873)?
-
2. Re: Changing default InvokerLocator port (ejb3-deployer)
mtedone1 Jul 1, 2006 7:58 PM (in response to rthompson)Yeah, I got the same problem. Tried with 3873 and everything works fine, with another port it doesn't. Do you know if there is a task in JIRA for this?
-
3. Re: Changing default InvokerLocator port (ejb3-deployer)
drbarela Jul 19, 2006 4:34 PM (in response to rthompson)I also have this same problem. Is there any updates about how to get around this?
-
4. Re: Changing default InvokerLocator port (ejb3-deployer)
alrubinger Aug 2, 2006 7:10 PM (in response to rthompson)I'm also having the same problem.
I have 2 server instances. Server Instance A is using the default ports as specified by sample-bindings.xml. Server Instance B is using the "ports-01" configuration:<service-config name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3" delegateClass="org.jboss.services.binding.AttributeMappingDelegate"> <delegate-config> <attribute name="InvokerLocator">socket://${jboss.bind.address}:3973</attribute> </delegate-config> <binding port="3973"/> </service-config>
When running both server instances at the same time, I receive a NotFoundInDispatcherException when attempting to execute a method on my EJB3 stub (I obtain the stub just fine). When running only Server Instance B, I get the following connect exception:org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection. at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:267) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.service.ServiceRemoteProxy.invoke(ServiceRemoteProxy.java:92) at $Proxy0.encrypt(Unknown Source) at com.ninem.rx.api.encryption.EncryptionDelegate.encrypt(EncryptionDelegate.java:54) at com.ninem.rx.api.encryption.EncryptionDelegateTests.testRoundtripEncryption(EncryptionDelegateTests.java:33) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:228) at junit.framework.TestSuite.run(TestSuite.java:223) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.<init>(Unknown Source) at java.net.Socket.<init>(Unknown Source) at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:535) at org.jboss.remoting.transport.socket.SocketClientInvoker.getConnection(SocketClientInvoker.java:471) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:263) ... 30 more
Proving my client can obtain a stub from Server Instance B, but when executing...something's still referring to my default ports that run Server Instance A.
All insight appreciated.
S,
ALR -
5. Re: Changing default InvokerLocator port (ejb3-deployer)
alrubinger Aug 2, 2006 7:30 PM (in response to rthompson)Created JIRA:
http://jira.jboss.com/jira/browse/EJBTHREE-673
S,
ALR -
6. Re: Changing default InvokerLocator port (ejb3-deployer)
alrubinger Aug 31, 2006 1:37 AM (in response to rthompson)Should affect Service Beans only. Patch is in.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968518#3968518
S,
ALR