[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
I had a similar problem - Swing app accessing Session bean worked fine on local network but performance degraded quite a bit when deployed using JNLP over a VPN. I was using IP addresses as the provider URL back to the server, but a sniffer showed a bunch of UDP traffic based on the host name and unsuccessful host name lookups. Implemented above solution and works great over the VPN - thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3839442#3839442 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3839442 --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
Thank you Adrian, now I have some arguments for Why need we one DNS for our network? field expierience question. anymore anywhere? bax View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837172#3837172 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837172 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
I forgot to specify that I'm not using DNS. We're using the IP address. Furthermore, this behavior occurs on every Windows box on our LAN (at least all those where we've tried it), and on none of the Linux boxes on our LAN. Is there something else I can check? What happens during the lookup that could cause a bottleneck? Am I using the appropriate client jar for what I'm doing? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837089#3837089 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837089 --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
Try adding TRACE logging for org.jnp (this is the naming category), it might show something useful. You should also look at installing some packet sniffers/network monitoring so you can see which network requests are taking time. I still think a host lookup timeout is the most likely cause. Try doing the initial stage of the lookup yourself: telnet server-ip 1099 Have you been through the FAQs? e.g. /etc/hosts Like I've said many times before, these forums are NOT network support forums. Your network adminstrator is responsible for your network problems. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837091#3837091 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837091 --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
OK, part of my problem seems to be that JBoss sends, to the client, a URL like http://hostname:8083/ and in the log, this appears as: Using RMI Server codebase: http://hostname:8083 It seems to be happening during the JNDI handshaking process (presumably JBoss is telling the client where to go for RMI calls) Why this is a problem is that hostname is not in DNS (and, for my case, cannot ever be). Furthermore, the machine in question must be named hostname (don't ask). I am not sure where it gets this from, so I created a SystemPropertiesService MBean in jboss-service.xml (xml below) to set the property jboss.bind.address to be my ip address. This did not have any effect on the RMI Server codebase, nor my problem. The change DID have an effect, as anywhere in the logfile that '0.0.0.0' showed up, my ip address now shows up; just not for the RMI Server codebase (or what is getting sent to the client). I figure as long as JBoss is sending over an invalid hostname (invalid to the client that is), then all bets are off regarding my problem. The linux vs. windows things is coincidental, because our linux boxes have the servername in question in their /etc/hosts, whereas windows boxes do not. So, how can I control the hostname that the RMI server codebase uses without modifying the network configuration of my machine? XML: | mbean code=org.jboss.varia.property.SystemPropertiesService |name=jboss.util:type=Service,name=SystemProperties |attribute name=Properties |jboss.bind.address=156.9.155.141 |/attribute | /mbean | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837106#3837106 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837106 --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
BTW, it seems that the WebService MBean controls the RMI Codebase, and it's Host
attribute controls the 'name of the public interface'. This is set to
${jboss.bind.address} and as such I would expect it to get my IP address as its value,
based on my system properties MBean setup. Appears that is not the case, or I'm
missing some other location where it's set?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837107#3837107
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837107
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
OK, so sorry to be posting 8000 messages, but I solved my problem, and I believe that
it was the result of a bug in JBoss that I was thankfully able to workaroud.
In org.jboss.web.WebService there is a method:
| protected void startService() throws Exception
|{
| // Host must be set to continue (either by user or detection)
| String address = getHost();
| if (address == null)
| throw new MissingAttributeException(Host);
|
| // Start the WebServer running
| server.start();
| log.info(Started WebServer with address: + server.getBindAddress() + :
+ getPort());
|
| // Set the rmi codebase if it is not already set
| String codebase = System.getProperty(java.rmi.server.codebase);
| if (codebase == null)
| {
| address = ServerConfigUtil.fixRemoteAddress(address);
|
| codebase = http://; + address + : + getPort() + /;
| System.setProperty(java.rmi.server.codebase, codebase);
| }
| log.info(Using RMI server codebase: + codebase);
|}
|
What happens is that if you do not set the system property in question, it uses your
configured host (which, by default is jboss.bind.hostname system property). That is
reasonable and correct.
THEN, it puts the address through ServerConfigUtil.fixRemoteAddress, which turns your
host address into a servername. This, IMHO, is incorrect behavior. At least, it
seems incorrect when you've specified the jboss.bind.address to be something other
than the default. Names are for humans. Numbers are for machines. The number is
always correct, wheras the name is dependant on the DNS server and client
configuration, and introducing this dependancy by default seems wrong. Maybe this is
addressed in a later version, but FYI, the solution was to set
java.rmi.server.codebase=http://my_ip_address:8083/
in my SystemPropertiesService MBean.
If there's a bug tracker for JBoss, I'll submit this if anyone agrees with me.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837112#3837112
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837112
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
While I generally agree with you about names and numbers, it is too naive for more complicated network configurations. e.g. 1) If you are using a firewall, although the firewall will rewrite the packet headers to translate ip addresses, it will not rewrite ip addresses embedded in the packet bodies (like the RMI codebase) 2) If your machine is multi-homed with NICs accessing networks that cannot see each other, you cannot send the ip address to the client, because it will be wrong on one of the networks. 3) The default configuration binds to all ip addresses 0.0.0.0 (which is useless to a client) Where I will agree with you is that if you do specify an ip address, it shouldn't then change over to using the host name. Bug reports (as mentioned in the faq): www.sf.net/projects/jboss View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837117#3837117 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837117 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: context.lookup takes 7+ _seconds_ to return over LAN on
Sounds like a dns/host config issue to me. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3836808#3836808 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3836808 --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
