Are you packaging any JBoss specific jar files in your application (like some jar containing org.jboss.system.* classes)? If yes, remove them from the application packaging.
Lance Goforth wrote:
But when I run the application pointing to the new 5.1 server, it doesn't connect. I don't see any errors, any messages, just an eventual timeout.
How exactly do you start the server? What command do you use? And how do you try to "connect"? Using a browser or some other means?
No, I'm not including any older classes, or jboss classes at all. I did check that. I also tried recompiling all the server and client code with the new jbossall-client.jar.
I'm starting the jboss server with just the run command, but as I said it seems to be running fine - no errors. My client application is a java application that connects to the application server via JNDI lookup. It has no web or browser component at all.
As mentioned previously, this is definitely a compatibility problem from jboss 4 to 5.1. Have you moved configuration directly from jboss 4 to jboss 5.1? This is just a guess, but maybe that unknown method is being invoked by reflection based on outdated configuration from jboss 4 ...
I moved over the connection resource xml, and the application jar. I tried recompiling with the new jboss jars. But couldn't complete that because I couldn't find org.jboss.resource.adapter.jdbc.WrappedConnection class in the new jars.
Got pulled off to other urgent projects so not sure when I can get back to this one.