[
http://jira.jboss.com/jira/browse/JBWS-1943?page=comments#action_12393800 ]
Chris Laprun commented on JBWS-1943:
------------------------------------
This is actually more than just changing the port. Just activating the VM JMX agent for
monitoring (-Dcom.sun.management.jmxremote) is enough for JBoss WS to not be able to find
the WS port anymore.
NPE when com.sun.management.jmxremote.port is changed, preventing
correct publication of WSDL
---------------------------------------------------------------------------------------------
Key: JBWS-1943
URL:
http://jira.jboss.com/jira/browse/JBWS-1943
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jbossws-2.0.1.SP2
Reporter: Chris Laprun
Assigned To: Richard Opalka
Changing the com.sun.management.jmxremote.port value results in WSDLFilePublisher not
being to publish the WSDL file:
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.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 $Proxy158.start(Unknown Source)
Looks like the root of the error is an issue with AbstractServerConfig.getConnectorPort
failing from called from getWebServicePort. A warning is issued on the console:
"Unable to calculate 'WebServicePort', using default '8080'".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira