NullPointerException with jbossws 2.0.1

[koganty]

I was trying to use jbossws 2.0.1 relased t'day 'cos it fixed some inheritance problems on JBoss 4.0.5 with jdk1.6.

I had a working web service with jbossws 2.0.0.

When I upgraded to 2.0.1 there is an exception at the very beginning.
The annotation on the SLSB look like :
@WebService
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT,
use = SOAPBinding.Use.LITERAL,
parameterStyle = SOAPBinding.ParameterStyle.WRAPPED)
@Stateless
@RemoteBinding(jndiBinding=LookupConstants.CLIENT_MANAGER)
@Depends({LookupConstants.CLIENT_SERVICE_OBJECT_NAME})
public class ClientManagerBean implements ClientManager


And here is the exception :

java.lang.NullPointerException
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:303)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:103)
at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss40.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy29.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:619)

[thomas.diesler]

Please scan the logfile for ServerConfigFactory

Is jbossws-framework.jar deployed?

[koganty]

jbossws-framework.jar is deployed under jboss/server//lib.

This is how the ServerConfigFactory shows up in the log :

2007-08-23 13:34:29,019 DEBUG [main][DeploymentAspectManagerImpl]: WebAppGeneratorDeploymentAspect:Create
2007-08-23 13:34:29,191 DEBUG [main][DefaultSPIProvider]: provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory'
2007-08-23 13:34:29,206 DEBUG [main][DefaultSPIProvider]: class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl@93727d
2007-08-23 13:34:29,222 ERROR [main][MainDeployer]: Could not start deployment: file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/epicenter.ear/epicenter.jar
java.lang.NullPointerException
at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.generatWebDeployment(WebAppGeneratorDeploymentAspect.java:105)
at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.create(WebAppGeneratorDeploymentAspect.java:84)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)



But the real problem is I think is the MANIFEST.MF in the jbossws.sar/META-INF directory.

I see quite a few DeploymentExceptions during startup regards to unreachable jar files 'cos the MANIFEST.MF points to the wrong location.

2007-08-23 13:33:17,948 DEBUG [main][ClassLoaderUtils]: Multiple class loaders found for pkg:
2007-08-23 13:33:17,948 DEBUG [main][MainDeployer]: resolveLibraries: jbossws-spi.jar jbossws-common.jar jbossws-framework.jar jboss-jaxrpc.jar jboss-jaxws.jar jboss-saaj.jar activation.jar commons-logging.jar concurrent.jar javassist.jar jaxb-api.jar jaxb-impl.jar mail.jar jboss-remoting.jar jboss-xml-binding.jar policy.jar stax-api.jar wsdl4j.jar
2007-08-23 13:33:17,948 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jbossws-spi.jar
2007-08-23 13:33:17,948 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-spi.jar which could not be opened, entry ignored
2007-08-23 13:33:17,948 DEBUG [main][NestedThrowable]: org.jboss.util.NestedThrowable.parentTraceEnabled=true
2007-08-23 13:33:17,948 DEBUG [main][NestedThrowable]: org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2007-08-23 13:33:17,948 DEBUG [main][NestedThrowable]: org.jboss.util.NestedThrowable.detectDuplicateNesting=true
org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-spi.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)

2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jbossws-common.jar
2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-common.jar which could not be opened, entry ignored
org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-common.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)


2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jbossws-framework.jar
2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-framework.jar which could not be opened, entry ignored
org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws-framework.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)

2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: new manifest entry for sdi at jbossws.sar entry is jboss-jaxrpc.jar
2007-08-23 13:33:17,964 DEBUG [main][MainDeployer]: The manifest entry in file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jbossws.sar/ references URL file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jboss-jaxrpc.jar which could not be opened, entry ignored
org.jboss.deployment.DeploymentException: url file:/C:/dev/sources/newport/jboss/server/epicenter/deploy/jboss-jaxrpc.jar could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)

There is more but I think this is the problem...

Thank You.
-Raju

[thomas.diesler]

The manifest classpath is not the problem becasue the unified classloader can see/load the ServerConfigFactory

The implementation of that factory however tries to load the ServerConfig from the microkernel with the bean name: WSServerConfig

Is that bean there?

 <!-- An abstraction of server configuration aspects. -->
 <bean name="WSServerConfig" class="org.jboss.wsf.stack.jbws.NativeServerConfig">
 <property name="mbeanServer"><inject bean="WSMBeanServerLocator" property="mbeanServer"/></property>

 <!--
 The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address>
 element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address.

 If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless 'modifySOAPAddress' is true.
 If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below.

 If 'webServiceHost' is not set, JBossWS uses requesters protocol host when rewriting the <soap:address>.
 -->
 <property name="webServiceHost">${jboss.bind.address}</property>
 <property name="modifySOAPAddress">true</property>

 <!--
 Set these properties to explicitly define the ports that will be used for rewriting the SOAP address.
 Otherwise the ports will be identified by querying the list of installed connectors.
 If multiple connectors are found the port of the first connector is used.
 <property name="webServiceSecurePort">8443</property>
 <property name="webServicePort">8080</property>
 -->
 </bean>

[mdaguete]

The manifest classpath is not the problem becasue the unified classloader can see/load the ServerConfigFactory

The implementation of that factory however tries to load the ServerConfig from the microkernel with the bean name: WSServerConfig

Is that bean there?

There are no WSServerConfig bean in the jmx-console.

[koganty]

Thomas,
Any updates on this?
How do you suggest we proceed?
Any other information we should be looking for?

Thanks

[gumnaam]

By any chance do you set the following property in your run.{sh/conf/bat} file ?
-Dcom.sun.management.jmxremote

I was having the exact same problem, when I had the above string, in my run.conf. I had put it there to enable jmx local agent, so that I can use jconsole against jboss.

But somehow , having this property, prevented, the NativeServerConfig MBean from being published.

Once I removed the string from my run.conf , the problem went away.

thanks

[koganty]

Yes that was the problem.
I think we'd need to file Bug for this.

Having -Dcom.sun.management.jmxremote in the startup args prevents the jbossws from coming up properly.

[koganty]

And here is the bug :

http://jira.jboss.com/jira/browse/JBWS-1800

[heiko.braun]

thanks for the thorough report guys.
i appreciate it ...

[richard_opalka]

Follow the following link guys to solve your problem with JMX options turned on:

http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#How_to_use_JDK_JMX_JConsole_with_JBossWS.3F

Richard

[lukeb]

I've checked out the jira bug 1800 and it appears that this problem is fixed in jbossws 202 onwards.

I've tried both 202 and 203 and they fail to deploy if I include the -Dcom.sun.management.jmxremote.

Admittedly I am using Java 6 Update4 which I understand is unsupported?

Does anyone have any suggestions?

11-03-08 15:19:19,908 ERROR main [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/test.ear/test.jar/
java.lang.NullPointerException
at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.generatWebDeployment(WebAppGeneratorDeploymentAspect.java:105)
at org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect.create(WebAppGeneratorDeploymentAspect.java:84)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy32.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)

[lukeb]

Have some more info about my experiments version 202.


If I add this in to my launch args there is no exception at startup.....

-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
-Djboss.platform.mbeanserver
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=13095 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

However, upon connecting with jboss - all of the jconsole tabs are disabled. ie Overview, Memory, Threads, Classes, VMSummary are all disabled. Only the MBeans tab is enabled.

If I launch JBoss with these args...

-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.port=13095 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false

...ie I remove the jboss mbean entries, then I get the exception I posted above.

[skajotde]

thanks guys for pointing solution. Exception is horrible unclear . Before Christmas vacation i had added jmx parameter to run.conf to monitor jboss. After vacation I did svn update and JBoss doesn't start. I forget about this parameter added 2 weeks ago. I thought it is from updating svn repo but it was my mistake.

Thanks.

[ropalka]

The documentation fix mentioned in JBWS-1800 doesn't work on AS 5.x series. Related issue is: JBAS-6185.