[
https://issues.apache.org/jira/browse/CXF-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925067#comment-13925067
]
Reginald Reed commented on CXF-5587:
------------------------------------
I then tried adding the following lines into my
applicationContext-webService.xml file and restarted my server
<jaxws:endpoint id="server" address="http://localhost:9081/TestMessage";
wsdlURL="ship.wsdl"
endpointName="s:TestSoapEndpoint"
serviceName="s:TestService"
xmlns:s="http://test"; >
<jaxws:properties>
<entry key="exceptionMessageCauseEnabled" value="true" />
</jaxws:properties>
</jaxws:endpoint>
According to CXF:
https://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging-Showingthecauseexceptionmessage
Showing the cause exception message:
CXF doesn't show the cause exception message in the fault message due to
security consideration. However, this could potentially cause some trouble on
the client side, as the client will not be able to see what the real cause of
the exception is. You can let the CXF server return the fault message with the
embedded cause exception message by enabling the option of
'exceptionMessageCauseEnabled' like this:
I then got a different error after the server restarted, this error was issued
last.
[3/8/14 18:35:56:480 CST] FFDC Exception:javax.management.MBeanException
SourceId:com.ibm.ws.management.AdminServiceImpl.invoke ProbeId:679
Reporter:com.ibm.ws.management.AdminServiceImpl$1@47864786
javax.management.MBeanException: Exception thrown in RequiredModelMBean while
trying to invoke operation pullNotifications
at
javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1113)
at
javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:967)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at
com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1332)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at
com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1225)
at
com.ibm.ws.management.remote.AdminServiceForwarder.invoke(AdminServiceForwarder.java:334)
at
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
at
javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
at
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360)
at
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at
javax.management.remote.rmi._RMIConnectionImpl_Tie.invoke(_RMIConnectionImpl_Tie.java:750)
at
javax.management.remote.rmi._RMIConnectionImpl_Tie._invoke(_RMIConnectionImpl_Tie.java:158)
at
com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:622)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:475)
at com.ibm.rmi.iiop.ORB.process(ORB.java:513)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2841)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2714)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
Caused by: com.ibm.ws.management.exception.ReceiverNotFoundException
at
com.ibm.ws.management.event.NotificationService.pullNotifications(NotificationService.java:625)
at
com.ibm.ws.management.AdminServiceImpl.pullNotifications(AdminServiceImpl.java:1793)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:600)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:244)
at
javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1086)
... 23 more
==> Performing default dump from com.ibm.ws.management.dm.JmxDM :Sat Mar 08
18:35:56 CST 2014
IntrospectDepth set from:3 to: 5
Dump of callerThis BEGIN:com.ibm.ws.management.AdminServiceImpl$1@47864786
com.ibm.ws.management.AdminServiceImpl$1::val$origName
BEGIN:javax.management.ObjectName@1ea81ea8
javax.management.ObjectName::oldSerialVersionUID:-5467795090068647408
javax.management.ObjectName::newSerialVersionUID:1081892073854801359
javax.management.ObjectName::oldSerialPersistentFields
BEGIN:[Ljava.io.ObjectStreamField;@1c4b1c4b
> CXF version 2.2.9 is not recognising my url-pattern
> ---------------------------------------------------
>
> Key: CXF-5587
> URL: https://issues.apache.org/jira/browse/CXF-5587
> Project: CXF
> Issue Type: Bug
> Environment: Windows 7, 32bit, IBM RAD 7.5.5.3
> Reporter: Reginald Reed
>
> We are trying to run our server locally on our PC using IBM RAD 7.5.5.3 under
> Windows 7, 32Bit. When we use SoapUI to run our test, we get back the error:
> Error 404: SRVE0190E: File not found: /services/worker
> the SoapUI url used was: http://localhost:9080/airport/services/worker we
> verified that (A) the port was correct (B) the context-root: airport is
> correct (C) The Servlet mapping /services/* is correct. Is there a
> compatibility with issue CXF version 2.2.9 and WIndows 7?
> <!-- START CXF Config -->
> <servlet>
> <servlet-name>CXFServlet</servlet-name>
>
> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
> <init-param>
> <description>Hides the listing of available services
> when set to true.
> It is considered a security risk to set this to false
> (or leave it unset),
> because a container should never give more information
> to the client
> than is necessary to function properly.</description>
> <param-name>hide-service-list-page</param-name>
> <param-value>true</param-value>
> </init-param>
> </servlet>
> <servlet-mapping>
> <servlet-name>CXFServlet</servlet-name>
> <url-pattern>/services/*</url-pattern>
> </servlet-mapping>
> <!-- END CXF Config -->
--
This message was sent by Atlassian JIRA
(v6.2#6252)
