First thing I would do is check to make sure I have the latest IBM JDK filesets... looks like 184.108.40.206 (32 and 64-bit) is the latest available now for JDK-1.4.2.
Next, I would try to build Jboss with the IBM JDK.
Over the years, I've occasionally seen cases where the IBM JVM chokes on classes compiled using Sun's JDK. (strange but true)
If all else fails, it looks like you have no choice but to open up an IBM support issue. After all, if their JVM is core-dumping, it's their problem and not Jboss'. (i.e. there's nothing Jboss folks can do to help)
FYI, we've run jboss-3.2.3 and jboss-3.2.7 on AIX 5.x in production, but only on JDK-1.3.1 (32 and 64-bit).
We're planning to eventually (in the next few months) move to jboss-4.0.2 on AIX w/JDK-1.4.2, so I'd be curious to know if you manage to resolve this issue.
Yeah done that.
Thanks anyway, will let you know how I get on.
It would appear the issues was one of classloading. We have managed to resolve our issues by going to JBoss4.0 and using isolated class loaders for our separate archives.
I have to say I am not impressed with the IBM jdk if anything untorward happens it just core dumps, really helpful.