-
30. Re: ejb access from one server to a second server
jaikiran Mar 2, 2012 11:12 AM (in response to jdabrowski)Jacek Dabrowski wrote:
ps. The same situation happens when I call second server from standalone application and comment user and password in jboss-client.properties
Important thing is that it works like that when second server is on another host then client - if on the same - it works without user and password (for standalone client)
For the standalone client on a different machine scenario, see this thread https://community.jboss.org/thread/196169?tstart=0. If you still have issues, feel free to ask for more help. I know we lack comprehensive documentation for this, at this point.
-
31. Re: ejb access from one server to a second server
jdabrowski Mar 3, 2012 10:48 AM (in response to jaikiran)I will give it a try on monday.
And what if I would need to set user and login for authentication? How to set it? In jboss-ejb-client.xml file?
btw. As markus78 said - it would be nice if there was a possibility to define conncetions dynamically like in client application.
-
32. Re: ejb access from one server to a second server
bessen Mar 29, 2012 2:30 PM (in response to jaikiran)Jaikiran,
I followed your documentation and it worked great. However, I have a question. If the destination server is restarted for some reason, the client server loses the outbound connection and can no longer process EJB requests to the destination server. I wonder is there a solution for this usecase?
-
33. Re: ejb access from one server to a second server
jaikiran Apr 15, 2012 2:34 AM (in response to bessen)brian essen wrote:
However, I have a question. If the destination server is restarted for some reason, the client server loses the outbound connection and can no longer process EJB requests to the destination server. I wonder is there a solution for this usecase?
Brian, I wish I had seen this message earlier. One other user noticed this issue this week and we have now fixed it in AS7 upstream https://issues.jboss.org/browse/AS7-4510. You can try out the latest nightly build https://community.jboss.org/thread/167590
-
34. Re: ejb access from one server to a second server
valefix May 14, 2012 4:15 AM (in response to jaikiran)Dear all,
I hope this thread is still opened, I read all the previuos posts and also the guide reported here:
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance
but I am still not able to make my example working. The main difference between my example and the one discussed in this thread is that the two JBoss instances are running on two different machines. If I start the 2 JBoss on the same machine my example works too.
I am using JBoss as 7.1.1 final in which I created two domains, after configuring the boss according to the guide if I start the 2 instances on the same machine I got the following message in the "JBoss client" and everything work well:
INFO [org.jboss.ejb.client.
remoting.RemotingConnectionEJBReceiver] (MSC service thread 1-8) Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@291972f8, receiver=Remoting connection EJB receiver [connection=Remoting connection <53dba43d>,channel=jboss.ejb,nodename=server_boss]} on channel Channel ID 8fb3eb90 (outbound) of Remoting connection 6ba00355 to localhost/127.0.0.1:4447
When I use 2 machines and I change the localhost address with the real IP where I start the "JBoss server", the above message doesn't show up and I got the following error:
ERROR [org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler] (EJB default - 1) Error invoking method public abstract void es.upm.lsd.cep.operators.Map.doMap(java.lang.String[]) on bean named map for appname modulename FirstService distinctname : java.util.concurrent.ExecutionException: javax.ejb.EJBException: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:SecondService,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@70e443f
at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.get(AsyncInvocationTask.java:132)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:300)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$200(MethodInvocationMessageHandler.java:64)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:196)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_26]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_26]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:SecondService,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@70e443f
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:80)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$2.runInvocation(MethodInvocationMessageHandler.java:294)
at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:73)
... 7 more
Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:SecondService,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@70e443f
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
at $Proxy18.setResults(Unknown Source) at es.upm.lsd.cep.operators.RemoteClient.callConsumer(RemoteClient.java:76)
at es.upm.lsd.cep.operators.MapBean.doMap(MapBean.java:47)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_26]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_26]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_26]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_26]
at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
... 26 more
any helps?
kind regards
Valerio
-
35. Re: ejb access from one server to a second server
jaikiran May 14, 2012 4:28 AM (in response to valefix)Have you configured the security configurations as explained in that article? What do they look like?
-
36. Re: ejb access from one server to a second server
valefix May 14, 2012 4:38 AM (in response to jaikiran)Hi Jaikiran,
Yes I did the configuration explained in the article. I first created an user in the "JBoss server" and then I did in the standalone-full.xml of the "Jboss client" the following modifications:
jboss_server_IP = 127.0.0.1 and the 2 JBoss running on the same machine, it works
jboss_server_IP = real_server_IP and 2 JBoss running on different machines, it doesn't work.
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
....
<outbound-socket-binding name="remote-lsd">
<remote-destination host="jboss_server_IP" port="4447"/>
</outbound-socket-binding>
</socket-binding-group>
<security-realms>
....
<security-realm name="lsd-security-realm">
<server-identities>
<secret value="dGVzdA=="/>
</server-identities>
</security-realm>
</security-realms>
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
<outbound-connections>
<remote-outbound-connection name="remote-lsd-connection" outbound-socket-binding-ref="remote-lsd" username="lsd" security-realm="lsd-security-realm">
<properties>
<property name="SASL_POLICY_NOANONYMOUS" value="false"/>
<property name="SSL_ENABLED" value="false"/>
</properties>
</remote-outbound-connection>
</outbound-connections>
</subsystem>
and this is the jboss-ejb-client.xml
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0">
<client-context>
<ejb-receivers>
<remoting-ejb-receiver outbound-connection-ref="remote-lsd-connection"/>
</ejb-receivers>
</client-context>
</jboss-ejb-client>
-
37. Re: ejb access from one server to a second server
jaikiran May 14, 2012 5:22 AM (in response to valefix)<secret value="dGVzdA=="/>
Are you sure this value is correct? The one I used in that article was a "test" password. What password did you use (you don't have to paste it here in case you are sure you generated the correct base64 value for it)?
-
38. Re: ejb access from one server to a second server
valefix May 14, 2012 5:44 AM (in response to jaikiran)Yes, I am using the same "test" password.
Anyhow it should't be a password problem because the "local" scenario works. I am able to successfully reproduce the article scenario on my machine, problems start when I move the "JBoss server" on a different machine.
Am I missing something?
-
39. Re: ejb access from one server to a second server
jaikiran May 14, 2012 5:47 AM (in response to valefix)Please enable TRACE level logs for org.jboss.ejb and org.jboss.as.ejb3 packages on the "client server" and attach those here.
-
40. Re: ejb access from one server to a second server
valefix May 14, 2012 6:17 AM (in response to jaikiran)This DEBUG message show up at the start up before starting the standalone client (the one which send the message to the "client server").
12:06:21,591 DEBUG [org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService] (MSC service thread 1-10) Creating remoting EJB receiver for connection remote-lsd-connection
12:06:26,668 DEBUG [org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService] (MSC service thread 1-10) Failed to create a connection for remote-lsd-connection. A reconnect handler will be added to the client context: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:140) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:101) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
12:06:26,673 DEBUG [org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService] (MSC service thread 1-10) Added 0 remoting EJB receivers to descriptor based EJB client context named service jboss.ejb3.dd-based-ejb-client-context."FirstService.war"
12:06:26,676 DEBUG [org.jboss.as.ejb3.deployment.processors.EjbClientContextSetupProcessor] (MSC service thread 1-6) Registering EJB client context org.jboss.ejb.client.EJBClientContext@6c23d1ab for classloader ModuleClassLoader for Module "deployment.FirstService.war:main" from Service Module Loader
12:06:26,703 DEBUG [org.jboss.as.ejb3] (MSC service thread 1-6) Security is *not* enabled on EJB: map, no security interceptors will apply
12:06:26,709 DEBUG [org.jboss.as.ejb3] (MSC service thread 1-6) Security is *not* enabled on EJB: map, no security interceptors will apply
12:06:26,800 DEBUG [org.jboss.as.ejb3] (MSC service thread 1-12) Using pool config StrictMaxPoolConfig{name=slsb-strict-max-pool, maxPoolSize=100, timeoutUnit=MINUTES, timeout=5} to create pool for Stateless EJB map
12:06:26,807 DEBUG [org.jboss.as.ejb3.timerservice.TimerServiceImpl] (MSC service thread 1-5) Starting timerservice for timedObjectId: FirstService.FirstService.map
12:06:26,824 DEBUG [org.jboss.as.ejb3] (MSC service thread 1-5) Found 0 active timers for timedObjectId: FirstService.FirstService.map
12:06:26,872 INFO [org.jboss.web] (MSC service thread 1-13) JBAS018210: Registering web context: /FirstService
12:06:26,876 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015951: Admin console listening on http://127.0.0.1:10090
12:06:26,877 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 7581ms - Started 234 of 318 services (83 services are passive or on-demand)
12:06:26,910 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "FirstService.war"
Then when I send the request I got the above, it seems that even if I have
<outbound-socket-binding name="remote-lsd">
<remote-destination host="xxx.xxx.xxx.xxx" port="4447"/>
</outbound-socket-binding>
it keeps searching for localhost:
12:12:28,123 TRACE [org.jboss.as.ejb3.remote.EJBRemoteConnectorService] (Remoting "client_boss" task-3) Welcome Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193 to the jboss.ejb channel
12:12:28,134 DEBUG [org.jboss.as.ejb3.remote.EJBRemoteConnectorService] (Remoting "client_boss" task-4) Client with protocol version 1 and marshalling strategy river trying to communicate on Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193
12:12:28,139 DEBUG [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "client_boss" task-4) Sending initial module availability message, containing 2 module(s) to channel Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193
12:12:28,140 DEBUG [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "client_boss" task-4) Writing out cluster formation message for 0 clusters, to channel Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193
12:12:28,173 TRACE [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "client_boss" task-1) Got message with header 0x3 on channel Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193
12:12:28,228 DEBUG [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "client_boss" read-1) Channel Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193 closed
12:12:28,229 TRACE [org.jboss.as.ejb3.remote.EJBRemoteConnectorService] (Remoting "client_boss" read-1) channel Channel ID 66a58b7d (inbound) of Remoting connection 0e478e18 to /127.0.0.1:47193 closed
12:12:28,250 INFO [org.jboss.ejb.client] (EJB default - 2) JBoss EJB Client version 1.0.5.Final
12:12:28,253 INFO [stdout] (EJB default - 2) valerio
12:12:28,254 INFO [stdout] (EJB default - 2) first invoke Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='SecondService', distinctName='', beanName='consumer', view='interface es.upm.lsd.consumer.ConsumerBeanRemote'}
12:12:33,259 DEBUG [org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService] (ejb-client-remote-connection-reconnect-3-thread-1) Reconnect attempt#1 failed for outbound connection service jboss.remoting.endpoint.subsystem.outbound-connection.remote-lsd-connection: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService$OutboundConnectionReconnectHandler.reconnect(DescriptorBasedEJBClientContextService.java:187) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.ejb.client.EJBClientContext$ReconnectAttempt.run(EJBClientContext.java:961) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_26]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_26]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
12:12:33,263 TRACE [org.jboss.as.ejb3] (EJB default - 2) Discard instance org.jboss.as.ejb3.pool.strictmax.StrictMaxPool@7fe3a7ec#org.jboss.as.ejb3.component.stateless.StatelessSessionComponentInstance@3b25b88c
12:12:33,266 ERROR [org.jboss.ejb3.invocation] (EJB default - 2) JBAS014134: EJB Invocation failed on component map for method public abstract void es.upm.lsd.cep.operators.Map.doMap(java.lang.String[]): javax.ejb.EJBException: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:SecondService,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@3b84411
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:80) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:43) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$2.runInvocation(MethodInvocationMessageHandler.java:294) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:73) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_26]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_26]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.IllegalStateException: No EJB receiver available for handling [appName:,modulename:SecondService,distinctname:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@3b84411
at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) [jboss-ejb-client-1.0.5.Final.jar:1.0.5.Final]
at $Proxy18.setResults(Unknown Source) at es.upm.lsd.cep.operators.RemoteClient.callConsumer(RemoteClient.java:76) [classes:]
-
41. Re: ejb access from one server to a second server
armandorv Sep 2, 2012 9:30 AM (in response to valefix)Hiii, do you get any solution? i 've got the same problem when i use differents machines. have you got any progress ?
-
42. Re: ejb access from one server to a second server
armandorv Sep 2, 2012 11:15 AM (in response to armandorv)It 's solved, i had made a mistake while installing my servers to separate machines. I've got running two machines with one AS7 for each of them, and security enabled.
Thanks,
-
43. Re: ejb access from one server to a second server
zeppelinux Dec 26, 2012 2:13 AM (in response to jaikiran)Jaikirian, any progress with this?
I'm extremely interested to see some documentation/examples for One to Many kind of scenario (one Client Server bean invokes Many EJB's deployed on different Destination Servers), can't find ANYTHING related.
-
44. Re: ejb access from one server to a second server
jaikiran Dec 27, 2012 8:08 AM (in response to zeppelinux)Dmitry Shultz wrote:
Jaikirian, any progress with this?
I'm extremely interested to see some documentation/examples for One to Many kind of scenario (one Client Server bean invokes Many EJB's deployed on different Destination Servers), can't find ANYTHING related.
Dmitry, would you mind opening a new thread for this one please, if it's related to this original thread? Since this one's a long thread involving multiple replies, I think it's better to start a new thread and explain what exactly you are looking for.