From owner-freebsd-java Sun Jun 23 22:38:57 2002 Delivered-To: freebsd-java@freebsd.org Received: from chen.org.nz (chen.org.nz [210.54.19.51]) by hub.freebsd.org (Postfix) with ESMTP id 8F1E937B404 for ; Sun, 23 Jun 2002 22:38:53 -0700 (PDT) Received: from grimoire.chen.org.nz (localhost [127.0.0.1]) by chen.org.nz (8.12.3/8.12.3) with ESMTP id g5O5bQAs093933; Mon, 24 Jun 2002 17:37:26 +1200 (NZST) (envelope-from jonc@grimoire.chen.org.nz) Received: (from jonc@localhost) by grimoire.chen.org.nz (8.12.3/8.12.3/Submit) id g5O5bQDa093932; Mon, 24 Jun 2002 17:37:26 +1200 (NZST) (envelope-from jonc) Date: Mon, 24 Jun 2002 17:37:25 +1200 From: Jonathan Chen To: j mckitrick Cc: freebsd-java@FreeBSD.ORG Subject: Re: Frustrating Java RMI problem, reprise Message-ID: <20020624053725.GA93880@grimoire.chen.org.nz> References: <20020624043621.A29670@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020624043621.A29670@dogma.freebsd-uk.eu.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jun 24, 2002 at 04:36:21AM +0100, j mckitrick wrote: > > This problem has me pulling my hair out. Here's a cut and paste of a > sample run. I started rmiregistry, then 'comp' which is an alias to run > the correct class. It threw the exception. I broke out of rmiregistry, > ran it again, and ran my class again, and it worked. Any idea why this > might happen? Could there be a huge delay in the code somewhere where a > port isn't getting bound quickly enough? > > local:~/myjava> comp > ComputeEngine exception: RemoteException occurred in server thread; > nested exception is: > java.rmi.UnmarshalException: error unmarshalling arguments; > nested exception is: > java.lang.ClassNotFoundException: > engine.ComputeEngine_Stub > local:~/myjava> > local:~/myjava> fg > [1] + running rmiregistry > (pwd : ~) > ^C > (pwd now: ~/myjava) > local:~/myjava> rmiregistry& > [1] 377 > local:~/myjava> comp > Ready. From the trace above, my guess is the rmiregistry needs to have it's classpath set properly as well. That's why when you ran it in ~/myjava, the code worked (classpath by default includes . in its environment). Cheers. -- Jonathan Chen Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message