Hey Ole,
you know what, in the weekend I was doing some test and experienced the same
problems. I thought it was W2K, but given your mail I think could be
something more serious. See below for details.
> Hi,
>
> As subject says, I have been experiencing problems
> with JNDI lookups from the client for the last month
> or so. (Now you all know why I haven't committed
> anything lately.)
>
> The problem has changed over time, but one thing is
> common:
> It always seems to happen when a JNDI lookup of a
> home interface is done. In particular it seems to
> always be in a call to MarshalledObject.get() in
> org/jnp/interfaces/NamingContext.java line 299.
>
> The problem seems to surface as one of the following:
> - An exception thrown on attempt to get the superclass
> of the home proxy. Ie. ClassNotFoundException on
> org.jboss.ejb.plugins.jrmp13.interfaces.HomeProxy.
> org/jnp/interfaces/NamingContext.java line 299 is
> in the stack trace.
Never happened to me
> - The client hangs.
> The call to MarshalledObject.get() in
> org/jnp/interfaces/NamingContext.java line 299 goes
> in, but control never comes back.
>
> For the last week or two, I have only seen client hangs
> and no exceptions.
Yeah, this is also what I get.
In particular, randomly, it happens that sometimes it takes 1-2 sec to
create the InitialContext then hangs for 10-20 seconds then I finally get
the home interface. Some other times (most of the times) though, I ctrl-C
the client, tired of waiting more than 1 minute and getting no home
interface.
Last time I tried it happened that I ctrl-C'ed some 15 times the client,
then I gave up and went out running for 45 minutes: the latter was a better
decision than going on with the dumb client.
> Changing conf/default/jboss.properties sometimes helps
> a little, but never makes the problem go completely
> away. In particular changing the java.rmi.codebase
> property seems to have an effect: If I set it to
> http://localhost:8083/ it sometimes helps a little.
> If I set it to http://myhost.mydomain.dk:8083/ it
> sometimes helps a little more.
> But no matter what I do I am unable to run all the
> jbosstest tests.
>
> When debugging, I am always stopped by some native
> method that I cannot step into to find out about the
> problem.
Did you try a profiler to see where is most of the time spent ? I think I
will download OptimizeIt evaluation and give it a try...
> I use Suns JDK1.3 for Linux on a RedHat 6.1 host.
I use Sun's jdk1.3 on W2K
> I have (without success) tried:
> - Two older JDK1.3 betas/prereleases from Sun.
> - Lots of CVS downloads. The problem seems to
> be changing a little from time to time, but
> for the last month it has been there constantly
> one way or another.
> - Taking a new machine, installing another (Suse)
> Linux distribution, downloading Suns JDK1.3 (again,
> to make sure no transmission error), downloading
> jBoss, setting it all up again on completely new
> machine. Same problem.
>
> With success I have tried an old CVS snapshot from
> the middle of last month. So whatever has happened
> probably happened during the last half of last month.
>
> I am basically at a dead end here. I really would
> like to use jBoss, but unless I get this fixed I am
> forced to use another product instead.
>
> Please help!!
> I have been spending a lot of time on this, and I do
> not mind spending a lot more time if needed to get
> this fixed.
> But I simply do not know what to do about it!
Did you already try to take jbosstest sources (client and bean+interfaces)
jarring them from scrap and add the needed jars one by one, trying to add
them in the manifest or leaving the manifest empty and adding them to normal
classpath ?
I'll try writing a plain bean and see if there are problems also, but it
seems to me something very tight coupled with jbosstest module...
Good luck (to both) !
Simon
