[JNDI/Naming/Network] - Re: Best practices for inter-server JNDI lookup
by sgrenholm
Sorry - I have no experience with that exception. At first, I was surprised that any stub errors would appear in a JMS context, but to be truthful I'm less than familiar with all the handshaking that JBoss does using JNDI.
Although in the general case I'd starting looking at the network traffic (is it busy) and your initial marshaling of data, if applicable, I believe that in your situation something possibly JBoss-specific is going on.
Some of the Jboss forums mention this sort of error happening when a non-clustered JBoss instance is contacting a clustered instance - so the first question is how have you setup your instances - are they clustered, which configuration are they using ("default", "all", your own config...)
I'd suggest verifying your configuration, and post the relevant information. Maybe someone (...) will have an answer, or maybe I'll have time to look at the source and experiment [uh, don't hold your breath!]
But whatever it is, it seems interesting! Stephen
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074951#4074951
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074951
18Â years, 11Â months
[JNDI/Naming/Network] - Why does jbossall-client.jar cause
by leo_ni
Hi,
Recently I am doing migration from jboss4.0.4GA to jboss4.2.1.GA, but when I included jbossall-client.jar in the web-inf/lib folder of war file, and deployed the war file to jboss, where all the enclosed jars coming from jboss4.2.1.GA/client folder. It failed with "java.lang.IncompatibleClassChangeError" when "sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener"
I am guessing the new jbossall-client.jar is created based on some dependency classes of diferent version other than server-side jars, and jboss runtime just picked up the classes from the client jar instead of from server-side jars. therefore the above exception came out.
Does anybody have the same issue and get a solution for that, 'coz I need jbossall-client.jar for calling ejb from tomat web container which is embedded in jboss4.2.1.GA.
Thanks,
Leo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074942#4074942
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074942
18Â years, 11Â months