I also have been getting these errors. I have been unable to figure out the exact reason. But I am guessing that the common factor here seems to be Windows XP SP2. The openejb build itself fails on my Lenovo T60p with Windows XP SP2 with the same error that you get. I also tried with many parallel requests and got the same error. However it runs in Linux in another machine and also in a windows xp single core machine without the problem occurring(need to check whether its SP1 or SP2 but i believe its SP1). However I have not load tested it in the linux machine. However as of now it looks to me like the problem is occurring in WinXP SP2 with dual core processors (common factor for everyone getting this error)
Regards Manu On Fri, Apr 18, 2008 at 3:03 PM, Trygve Hardersen <[EMAIL PROTECTED]> wrote: > > > > On 18/04/2008, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > > On Thu, Apr 17, 2008 at 10:42 PM, Trygve Hardersen <[EMAIL PROTECTED]> > wrote: > > > > > javax.naming.NamingException: Cannot lookup > '/BankManagerFacadeBeanRemote'. > > > [Root exception is java.rmi.RemoteException: Cannot read the response > from > > > the server (OEJP/3.0) : null; nested exception is: > > > java.io.EOFException] > > > > > > > > > Hi, > > > > Are you by any chance running the tests on t60p machine? > > > T60p as in Lenovo Thinkpad? No, but I have a T61p machine I can test on. > > Here's a description on my test setup: > > Machine: Gigabyte 965P DQ6 with Dual Core 2.4 Ghz, 8GB RAM > Host OS: Windows Vista SP1, VMWare Workstation 6 > Test OS: Windows XP SP2, 2GB RAM, Java 1.6 > > I also have Ubuntu Server 7.10 virtual machines I can test on, but I haven't > run the integration tests on these yet. Will try. > > Trygve
