Application hangs during class loading with no errors

Hi,

I'm developing a large application that is spread across many jar files.

At run time the application appears to hang immediately prior to the constructor of a class being called, with no errors or exceptions.

This was discovered using a combination of the debugger and good old println... (i.e. there is a println immediately before the constructor is called and another on the first line of the constructor)

Using the -verbose:class option on the java command I can see that it's loading a series of classes from different jars, as they're required during run time. However after loading one class it always stops with no further action anywhere, or any errors or exceptions.

I've tried tracking the class dependencies but these are too numerous to trawl through all of them. However, for those I have checked there doesn't appear to be any rogue statics.

So, there are two parts to this question:

a) Has anyone seen this problem before or has any suggestions at what might be causing this.

b) Where can I find reference to exactly what the output of -verbose:class option actually relates to.

Thanks in advance,

[1192 byte] By [nattress] at [2007-9-26 2:46:35]
# 1
Does any of the .jar files include classes with the same name?
MagDy at 2007-6-29 10:30:06 > top of Java-index,Desktop,Deploying...
# 2

Your application hangs without any print out or thrown exception :

- you might have for some reason an infinit loop.

- you might have a blocking call such as InputStream.readFully

- you might have a blocking call via ServerSocket.accept

- you might have an OutOfMemoryException... This could make the app to hang ( also means somehow you caught the exception and provided no print out )

As I have no clue of what your application is performing .. just have a look at what it might be.

Even though such problems already occured to my apps, I have yet to see some mystic behavior.

Hope this helps

fquinet at 2007-6-29 10:30:06 > top of Java-index,Desktop,Deploying...
# 3
BTW try launching your app increasing meaningfully the memory size of the JVM ...
fquinet at 2007-6-29 10:30:06 > top of Java-index,Desktop,Deploying...