Urgent Help needed..Strange behavior with java client access

[sursha]

Hi,
I'm using JBOSS 4.0.5GA with ejb3. I am running into weird behavior when running java client from remote machine. If I run it from the same machine where the jboss server is running, no problem. So here is the behavior I'm noticing.
FOr the jndi lookup of ejb, it is connecting the remote server and gets a reference to the ejb. But when I call a method on the ejb reference, it is trying to call a method on the local machine( I mean the same machine where the client is running).
Sounds very weird to me. Any help is appreciated from EJB3 experts.
I upgraded to EJB3 RC9 patch1, but same behavior.
Here is the client code ..

try
{
Properties p=new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
p.put(Context.PROVIDER_URL,"jnp://remote-host:1099");

InitialContext ctx = new InitialContext(p);
IReportService report = (IReportService) ctx.lookup(
"ejb3/xxx/ReportService");

System.out.println("Got the ejb remote reference = "+report);

System.out.println("report.resubmit.."+report.resubmit(null,0L));

ReportJob reportJob = new ReportJob();
System.out.println("B4 report.submitRequest..");

report.submitRequest(reportJob);
System.out.println("After report.submitRequest..");
}
catch (Exception e)
{
e.printStackTrace();
}


Thanks

[alexg79]

How did you determine that it's trying to call a method on the same machine?

[sursha]

If I shutdown the jboss server on local machine, it gives me a socket connection error. Otherwise, it gives an application error.

[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.

[sursha]

Any one from JBOSS EJB team here to help????

[alrubinger]

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

[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?

[dkane]

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.

[alrubinger]

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

[rkrylov]

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.

[rkrylov]

"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.

[alrubinger]

Maybe check /etc/hosts, run ifconfig, make sure the address you're passing is valid?

S,
ALR

[rkrylov]

"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.