-
1. Re: Urgent Help needed..Strange behavior with java client ac
alexg79 Dec 28, 2006 6:29 AM (in response to sursha)How did you determine that it's trying to call a method on the same machine?
-
2. Re: Urgent Help needed..Strange behavior with java client ac
sursha Dec 28, 2006 7:54 AM (in response to sursha)If I shutdown the jboss server on local machine, it gives me a socket connection error. Otherwise, it gives an application error.
-
3. Re: Urgent Help needed..Strange behavior with java client ac
sursha Dec 28, 2006 8:00 AM (in response to sursha)Just following up..I mean when the jboss server is up on the same machine where the client is running, it works. When I shutdown the jboss server on the same machine, i get a socket connection error. Thing is it gets the ejb reference from the remote machine, but when it calls methods on the ejb reference, it calls on the local machine. That is when the socket error is thrown.
-
4. Re: Urgent Help needed..Strange behavior with java client ac
sursha Dec 29, 2006 9:44 AM (in response to sursha)Any one from JBOSS EJB team here to help????
-
5. Re: Urgent Help needed..Strange behavior with java client ac
alrubinger Dec 29, 2006 11:35 AM (in response to sursha)Have you overridden @RemoteBinding.clientBindUrl or its XML equivalent on your EJB? If so, it's possible you've hardcoded the lookup address in the proxy object.
S,
ALR -
6. Re: Urgent Help needed..Strange behavior with java client ac
sursha Dec 29, 2006 2:46 PM (in response to sursha)I dont have clientBndUrl defined or xml files. I'm using ejb 3.0.
Do I need to define clientBndUrl in RemoteBinding? I only have the jndi name defined in the RemoteBinding.
Is it working for you? -
7. Re: Urgent Help needed..Strange behavior with java client ac
dkane Jun 6, 2007 10:10 AM (in response to sursha)Looks like I have the same problem. Any solution ?
Small addition : I am getting this problem when remote JBoss is running on Linux PC. For remote JBoss on Windows PC everything works well. -
8. Re: Urgent Help needed..Strange behavior with java client ac
alrubinger Jun 10, 2007 9:26 AM (in response to sursha)JBoss, starting in 4.2, for security reasons will now bind to localhost (127.0.0.1) by default. In Linux especially, some changes might have to be made to open up the bindings to listen on other IPs (either internal or external).
This is done via the -b switch to run.bat/run.sh. Like:$JBOSS_HOME/bin/run.sh -b 192.168.10.14
...if your machine has an internal IP of 192.168.10.14 and only needs to be accessed from within the network. If you're accessing from outside the network on one IP alone, use the external IP. If you need to access from many IPs and want JBoss to bind to all available, use 0.0.0.0
S,
ALR -
9. Re: Urgent Help needed..Strange behavior with java client ac
rkrylov Jun 12, 2007 11:11 AM (in response to sursha)I have problems even with starting run.sh with '-b address':
the RMI client side hangs occasionally.
I am using jboss-4.2.0-GA with jdk-1.6.0_u1, x86_64 gentoo linux on amd64 x2.
I have also some strange exceptions from my network classloader, which could not find java.lang.ObjectBeanInfo. -
10. Re: Urgent Help needed..Strange behavior with java client ac
rkrylov Jun 12, 2007 11:13 AM (in response to sursha)"rkrylov" wrote:
I have problems even with starting <tt>run.sh</tt> with '-b address':
the RMI client side hangs occasionally.
I am using jboss-4.2.0-GA with jdk-1.6.0_u1, x86_64 gentoo linux on amd64 x2.
I have also some strange exceptions from my network classloader, which could not find <tt>java.lang.ObjectBeanInfo</tt>.
I had no problems with jboss-4.0.5 though. -
11. Re: Urgent Help needed..Strange behavior with java client ac
alrubinger Jun 12, 2007 11:53 AM (in response to sursha)Maybe check /etc/hosts, run ifconfig, make sure the address you're passing is valid?
S,
ALR -
12. Re: Urgent Help needed..Strange behavior with java client ac
rkrylov Jun 12, 2007 3:33 PM (in response to sursha)"ALRubinger" wrote:
Maybe check /etc/hosts, run ifconfig, make sure the address you're passing is valid?
The address is valid of course :)
and there is the record in /etc/hosts corresponding to that address.
I had no problems with the same config on jboss-4.0.5 they came with 4.2.0.