Hello,
I'm facing a curious problem, trying to expose Hibernate's statistics through
JMX. I updated jboss-service.xml to add the following:
| mbean code=org.hibernate.jmx.StatisticsService
|
name=jboss.monitoring:service=StatisticsService,name=xxxStatisticsService
|
|
Well, my statement about a simple value working OK was just wrong.
The above error message appears with anything I take from the Global JNDI
Namespace (as displayed by JNDIView in the JMX Console). A value from any other
namespace gives the following error (here with a random
Hello all,
I have a simple question. How do you make an EAR app (EJB endpoints) work with
Jax-ws RI on JBoss AS 4.2.2, instead of (or in collaboration with) JBossWs?
I tried to remove 'jbossws.sar' from server/default/deploy, and ship Jax-ws RI
2.1.4's jars into my EAR's /lib directory. JBoss
I guess you found your answer one year ago, but posting it as it appears as one
of the first results when you google JAXB can't handle interfaces.
It can occur when you try to marshall/unmarshall with Java classes containing
members that are not declared static, and which (or one of their own
For all those who encounter this issue: try to know if you're deploying a
webapp that has its own log4j.jar
Since JBoss has already a log4j.jar, you can obtain this error if both versions
are not the same. Just remove log4j.jar from you webapp's WEB-INF/lib when
deploying (an exclude might be
