Basic setup is JBoss 3.2.3, default server, no config changes (save a datasource).
Swing client makes Stateless Session EJB calls. On linux (RedHat 9.0), EJB calls behave normally; context is created, lookup occurs quickly, call proceeds normally. On both Windows 2000 and Windows XP, same subnet, same JRE version, same application, the call to InitialContext.lookup() used to get the EJB Home interface takes over 7 seconds. Yes, that's seconds. 7000+ milliseconds. Same machine, same code agains Weblogic 6 is sub-1 second and not noticeable. Both clients use jbossall-client.jar There's no log information related to this in any log. This happens for every EJB that is looked up, regardless of how many times it has been accessed in the past. Questions: 1. What's my next step in identifying the problem? 2. Is there a Windows-specific version of the jboss client jar, or an otherwise better client jar that may alleviate some of this? 3. Is there a way to configure the server (or client) to improve performance or even cache things? (I believe a cache is the wrong solution here as 7 seconds seems excessive and indicates a configuration problem on my end) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836724#3836724 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836724 ------------------------------------------------------- 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=3149&alloc_id=8166&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
