-
1. Re: Executing Session Bean methods very slow over internet
mnachev Mar 1, 2005 2:32 AM (in response to damencho)Try with commercial Application Servers like WebLogic, WebSphere and etc. Maybe this is a problem for JBoss.
-
2. Re: Executing Session Bean methods very slow over internet
damencho Mar 2, 2005 2:23 AM (in response to damencho)Obviusly a problem in JBoss. Nobody wants to answer me . Is this a common problem?
-
3. Re: Executing Session Bean methods very slow over internet
radl01 Mar 2, 2005 5:07 AM (in response to damencho)This is not problem of JBoss. !!!!!!! JBoss is fast as WebLogic or WebSphere.
It should be problem with resolving service. Do you use ip or host name to connect to your server ?
Dou you use rmi invoker or http invoker ?
Did you trace the request rout (ethereal etc.) ?
Your operation should be done within few ms (500ms).
Jan -
4. Re: Executing Session Bean methods very slow over internet
damencho Mar 2, 2005 9:54 AM (in response to damencho)Everything is using ip. even on the windows machine in hosts - the ip is described to desible some additional dns checking of InetAddress.
I'm using rmi invoker. I needed to open 1098,1099,4444 ports on my server firewall.
With ethereal I see 4 packets two from one side then two from the other to the 1099 port and then everything freezes. -
5. Re: Executing Session Bean methods very slow over internet
triathlon98 Mar 2, 2005 10:42 AM (in response to damencho)Have a look at the reply you get on the 1099 port. Does it contain a hostname and or ip adres?
Can you resolve both?
I assume it is enough to resolve the first occurence (which should be the hostname), but I am not sure.
If they cannot be resolved, try using the --host option when starting your jboss server.
Joachim -
6. Re: Executing Session Bean methods very slow over internet
damencho Mar 2, 2005 11:24 AM (in response to damencho)I tried with --host ipaddress. But now I got this exception :
non-JRMP server at remote endpoint
I noteced when I telnet to 1099 I see not the ip address but the dns name.
and something http://voipgw:8083 among the binary garbage.
where voipgw is the name of the PC in the local net.
Now the tcp packets between the two machines are 9 (8 pairs and one alone to the client). -
7. Re: Executing Session Bean methods very slow over internet
triathlon98 Mar 3, 2005 7:20 AM (in response to damencho)I think you should use host with the name as used for remote access (dns name).
In your servers configuration, you might need to make sure that this is known to be the local machine, but I am not sure about that part.
Joachim -
8. Re: Executing Session Bean methods very slow over internet
damencho Mar 7, 2005 5:28 AM (in response to damencho)For host and bind addresses I have put the ip-address .
I had this exception :
non-JRMP server at remote endpoint
I've changed
The param of the Context
from
environment.put(Context.PROVIDER_URL, "jnp://<server-ip-address>:1099");
to
environment.put(Context.PROVIDER_URL, "<server-ip-address>");
Now the exception is gone but everything again is slow.
Lookup,create,execute - for about 15-20 minutes.
I've made a summary with ethereal :
Between first and last packet : 1055.544 sec
Packets : 187
Bytes: 31714
Avg. bytes/sec : 30.045
Any ideas?
And why when I change The provider to the ip-address there is no that exception?
thanks for answering me