Error
com.ibm.ccl.soa.test.common.framework.ResolvingException: Unable to find interface {http://www.bskyb.com/domestic/ops/crm/osr/Manager}Sample in project _Worker_Process.
at com.ibm.ccl.soa.test.common.core.framework.resolver.SimpleWsdlResolver.resolvePortType(Unknown Source)
at com.ibm.wbit.comptest.ui.resolver.WIDWsdlResolver.resolvePortType(Unknown Source)
at com.ibm.ccl.soa.test.common.core.framework.resolver.SimpleWsdlResolver.resolveOperation(Unknown Source)
at com.ibm.ccl.soa.test.common.core.framework.operation.wsdl.WSDLOperationFactory.createOperationDescriptionFromURI(Unknown Source)
at com.ibm.ccl.soa.test.common.core.framework.operation.wsdl.WSDLOperationFactory.createOperationDescriptionFromURI(Unknown Source)
at com.ibm.wbit.comptest.ui.editor.section.InteractiveEmulatorEventDetailSection.populateOutputEditor(Unknown Source)
at com.ibm.wbit.comptest.ui.editor.section.InteractiveEmulatorEventDetailSection.setSectionInput(Unknown Source)
at com.ibm.ccl.soa.test.common.ui.editor.page.TestEditorDetailsPage.selectionChanged(Unknown Source)
at org.eclipse.ui.forms.DetailsPart$1.run(Unknown Source)
at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source)
at org.eclipse.ui.forms.DetailsPart.showPage(Unknown Source)
at org.eclipse.ui.forms.DetailsPart.update(Unknown Source)
at org.eclipse.ui.forms.DetailsPart.selectionChanged(Unknown Source)
at org.eclipse.ui.forms.ManagedForm.fireSelectionChanged(Unknown Source)
at com.ibm.wbit.comptest.common.ui.editor.page.AbstractEventEditorPage.selectionChanged(Unknown Source)
at org.eclipse.jface.viewers.Viewer$2.run(Unknown Source)
at org.eclipse.core.runtime.SafeRunner.run(Unknown Source)
at org.eclipse.core.runtime.Platform.run(Unknown Source)
at org.eclipse.ui.internal.JFaceUtil$1.run(Unknown Source)
at org.eclipse.jface.util.SafeRunnable.run(Unknown Source)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Unknown Source)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(Unknown Source)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(Unknown Source)
at com.ibm.wbit.comptest.common.ui.editor.section.AbstractEventSection.setCurrentEvent(Unknown Source)
at com.ibm.wbit.comptest.common.ui.editor.page.AbstractEventEditorPage.selectNextEvent(Unknown Source)
at com.ibm.wbit.comptest.common.ui.editor.page.AbstractEventEditorPage$1.run(Unknown Source)
at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
at org.eclipse.core.launcher.Main.run(Unknown Source)
at org.eclipse.core.launcher.Main.main(Unknown Source)
Caused by: org.eclipse.core.internal.resources.ResourceException: Resource /BOHelper does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Unknown Source)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Unknown Source)
at org.eclipse.core.internal.resources.Project.checkAccessible(Unknown Source)
at org.eclipse.core.internal.resources.Resource.accept(Unknown Source)
at org.eclipse.core.internal.resources.Resource.accept(Unknown Source)
at org.eclipse.core.internal.resources.Resource.accept(Unknown Source)
... 48 more
Session data
eclipse.buildId=3.2.2
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-20080303 (JIT enabled)
J9VM - 20080228_17641_lHdSMR
JIT - 20070820_1846ifx1_r8
GC - 200802_28
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Framework arguments: -showlocation -product com.ibm.wbit.feature.ide -product com.ibm.wbit.feature.ide
Command-line arguments: -data C:\WS\Clawback -os win32 -ws win32 -arch x86 -showlocation -product com.ibm.wbit.feature.ide -clean -product com.ibm.wbit.feature.ide
Root Cause
This type error may come up on modifying the WSDL or BOs.
It can't trace to to the correct WSDL.
Resolution
Remove the older WSDL reference, add freshly, synchronize the WSDLs
Remove the invoke activities, create new invokes for those changed WSDLs.
Rebuilt and redeploy
Tuesday, August 25, 2009
WMSG0019E: Unable to start MDB Listener WebServicesJMSRouter_ClawbackManagementPort, JMSDestination jms/Clawback.ClawbackManagement.RequestQ : com.ibm.ejs.jms.listener.MDBInvalidConfigException: Cannot deploy an MDB against a listener port specifying a default messaging JMS resource
Error
default_host[*:9086,*:80,*:9449,*:5073,*:5072,*:443].
[10/03/09 13:10:42:207 GMT] 0000004a MDBListenerIm E WMSG0063E: Unable to start message-driven bean (MDB) WebServicesJMSRouter_ClawbackManagementPort against listener port Clawback_ClawbackManagement_LP. It is not valid to specify a default messaging Java Message Service (JMS) resource for a listener port; either use a different JMS resource with a listener port or use a default messaging JMS resource with an activation specification.
[10/03/09 13:10:42:254 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_0.txt
[10/03/09 13:10:42:269 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_0.txt
[10/03/09 13:10:42:269 GMT] 0000004a MDBListenerIm W WMSG0019E: Unable to start MDB Listener WebServicesJMSRouter_ClawbackManagementPort, JMSDestination jms/Clawback.ClawbackManagement.RequestQ : com.ibm.ejs.jms.listener.MDBInvalidConfigException: Cannot deploy an MDB against a listener port specifying a default messaging JMS resource
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:263)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:728)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:651)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:634)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:227)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:872)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:830)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:188)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:1255)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:1121)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:235)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:230)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:829)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1486)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4076)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4173)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1491)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1092)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:973)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1082)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:975)
at com.ibm.ws.management.commands.AdminServiceCommands$InvokeCmd.execute(AdminServiceCommands.java:251)
at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:239)
at com.ibm.ws.console.appdeployment.ApplicationDeploymentCollectionAction.execute(ApplicationDeploymentCollectionAction.java:537)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1101)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1036)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:565)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1070)
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:273)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:319)
at com.ibm.isclite.container.controller.InformationController.processForwardConfig(InformationController.java:206)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1101)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1036)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence(WSCUrlFilter.java:792)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:363)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:229)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:565)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3440)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1461)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:118)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
[10/03/09 13:10:42:269 GMT] 0000004a MDBListenerIm I WMSG0043I: MDB Listener Clawback_ClawbackManagement_LP stopped for JMSDestination jms/Clawback.ClawbackManagement.RequestQ
[10/03/09 13:10:42:269 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_1.txt
[10/03/09 13:10:42:285 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_1.txt
[10/03/09 13:10:42:285 GMT] 0000004a MsgListenerPo W WMSG0049E: Failed to start MDB WebServicesJMSRouter_ClawbackManagementPort against listener port Clawback_ClawbackManagement_LP
[10/03/09 13:10:42:285 GMT] 0000004a ApplicationMg A WSVR0221I: Application started: Clawback_ManagementApp
[10/03/09 13:10:42:347 GMT] 0000004a ApplicationDe I ApplicationDeploymentController perform ApplicationDeploymentController: performing appcontexts refresh
[10/03/09 13:10:43:254 GMT] 00000048 ServletWrappe I SRVE0242I: [isclite] [/ibm/console] [/secure/javascriptToSession.jsp]: Initialization successful.
default_host[*:9086,*:80,*:9449,*:5073,*:5072,*:443].
[10/03/09 13:10:42:207 GMT] 0000004a MDBListenerIm E WMSG0063E: Unable to start message-driven bean (MDB) WebServicesJMSRouter_ClawbackManagementPort against listener port Clawback_ClawbackManagement_LP. It is not valid to specify a default messaging Java Message Service (JMS) resource for a listener port; either use a different JMS resource with a listener port or use a default messaging JMS resource with an activation specification.
[10/03/09 13:10:42:254 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_0.txt
[10/03/09 13:10:42:269 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_0.txt
[10/03/09 13:10:42:269 GMT] 0000004a MDBListenerIm W WMSG0019E: Unable to start MDB Listener WebServicesJMSRouter_ClawbackManagementPort, JMSDestination jms/Clawback.ClawbackManagement.RequestQ : com.ibm.ejs.jms.listener.MDBInvalidConfigException: Cannot deploy an MDB against a listener port specifying a default messaging JMS resource
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:263)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:728)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:651)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:634)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:227)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:872)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:830)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:188)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:1255)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:1121)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:235)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:230)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:829)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1486)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4076)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4173)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1491)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1092)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:973)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1082)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:975)
at com.ibm.ws.management.commands.AdminServiceCommands$InvokeCmd.execute(AdminServiceCommands.java:251)
at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:239)
at com.ibm.ws.console.appdeployment.ApplicationDeploymentCollectionAction.execute(ApplicationDeploymentCollectionAction.java:537)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1101)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1036)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:565)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1070)
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:273)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:319)
at com.ibm.isclite.container.controller.InformationController.processForwardConfig(InformationController.java:206)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1101)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1036)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence(WSCUrlFilter.java:792)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:363)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:229)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:565)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3440)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1461)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:118)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
[10/03/09 13:10:42:269 GMT] 0000004a MDBListenerIm I WMSG0043I: MDB Listener Clawback_ClawbackManagement_LP stopped for JMSDestination jms/Clawback.ClawbackManagement.RequestQ
[10/03/09 13:10:42:269 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_1.txt
[10/03/09 13:10:42:285 GMT] 0000004a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_0000004a_09.03.10_13.10.42_1.txt
[10/03/09 13:10:42:285 GMT] 0000004a MsgListenerPo W WMSG0049E: Failed to start MDB WebServicesJMSRouter_ClawbackManagementPort against listener port Clawback_ClawbackManagement_LP
[10/03/09 13:10:42:285 GMT] 0000004a ApplicationMg A WSVR0221I: Application started: Clawback_ManagementApp
[10/03/09 13:10:42:347 GMT] 0000004a ApplicationDe I ApplicationDeploymentController perform ApplicationDeploymentController: performing appcontexts refresh
[10/03/09 13:10:43:254 GMT] 00000048 ServletWrappe I SRVE0242I: [isclite] [/ibm/console] [/secure/javascriptToSession.jsp]: Initialization successful.
Root Cause
Incorrect setting for Queue, QCF and listener port JNDIs.
Resolution
- Check the QCF (Queue Connection factory) authentication should be none (unless otherwise specified)
- Map the correct LP (Listener port ) to the MDB.
- Queue JNDI Type should be 'JMS'
- QCF JNDI type should be 'Client'
WMSG0019E: Unable to start MDB Listener WebServicesJMSRouter_ManagementPort, JMSDestination jms/Management.RequestQ : javax.jms.InvalidDestinationException: MQJMS0003: Destination not understood or no longer valid
Error
[27/03/09 09:22:51:445 GMT] 00000011 MDBListenerIm W WMSG0019E: Unable to start MDB Listener WebServicesJMSRouter_ClawbackManagementPort, JMSDestination jms/Clawback.ClawbackManagement.RequestQ : javax.jms.InvalidDestinationException: MQJMS0003: Destination not understood or no longer valid
at com.ibm.mq.jms.MQConnection.createConnectionConsumer(MQConnection.java:3588)
at com.ibm.ejs.jms.JMSQueueConnectionHandle.createConnectionConsumer(JMSQueueConnectionHandle.java:139)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:557)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:728)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:701)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:1036)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
[27/03/09 09:22:51:445 GMT] 00000011 MDBListenerIm I WMSG0043I: MDB Listener Clawback_ClawbackManagement_LP stopped for JMSDestination jms/Clawback.ClawbackManagement.RequestQ
[27/03/09 09:22:51:445 GMT] 00000011 MDBListenerIm I WMSG0058I: Listener Port Clawback_ClawbackManagement_LP will attempt to restart in 60 seconds
[27/03/09 09:23:25:899 GMT] 00000061 CacheServiceI I DYNA1001I: WebSphere Dynamic Cache instance named ws/WSSecureMapNotShared initialized successfully.
[27/03/09 09:22:51:445 GMT] 00000011 MDBListenerIm W WMSG0019E: Unable to start MDB Listener WebServicesJMSRouter_ClawbackManagementPort, JMSDestination jms/Clawback.ClawbackManagement.RequestQ : javax.jms.InvalidDestinationException: MQJMS0003: Destination not understood or no longer valid
at com.ibm.mq.jms.MQConnection.createConnectionConsumer(MQConnection.java:3588)
at com.ibm.ejs.jms.JMSQueueConnectionHandle.createConnectionConsumer(JMSQueueConnectionHandle.java:139)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:557)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:728)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:701)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:1036)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
[27/03/09 09:22:51:445 GMT] 00000011 MDBListenerIm I WMSG0043I: MDB Listener Clawback_ClawbackManagement_LP stopped for JMSDestination jms/Clawback.ClawbackManagement.RequestQ
[27/03/09 09:22:51:445 GMT] 00000011 MDBListenerIm I WMSG0058I: Listener Port Clawback_ClawbackManagement_LP will attempt to restart in 60 seconds
[27/03/09 09:23:25:899 GMT] 00000061 CacheServiceI I DYNA1001I: WebSphere Dynamic Cache instance named ws/WSSecureMapNotShared initialized successfully.
Root Cause
This error comes when you have an SOAP/JMS export (webservice) export for your service. WPS server creates default resources like Queues and QCFs (Queue Connection Factory) mentioned in the export.
These default created resources are not compatible with your application.
Resolution
Go to Resources -> Q and QCF, delete unwanted resources (they usually reside in the last tab/last row), save the changes and restart the server.
This error comes when you have an SOAP/JMS export (webservice) export for your service. WPS server creates default resources like Queues and QCFs (Queue Connection Factory) mentioned in the export.
These default created resources are not compatible with your application.
Resolution
Go to Resources -> Q and QCF, delete unwanted resources (they usually reside in the last tab/last row), save the changes and restart the server.
CWWBE0085E: Incompatible types - org.apache.commons.jxpath.JXPathException: Exception trying to create xpath
Error
[25/02/09 14:22:20:824 GMT] 00000087 BpelEngine I CWWBE0085E: Incompatible types were encountered during the assignment to a variable or partner link 'determineClawbackEligibilityRequest' in activity 'Assign'.
org.apache.commons.jxpath.JXPathException: Exception trying to create xpath Customer/PortfolioAccount/CancelledSubscriptionList/Subscription[bpws:getVariableData('Index1')]/Id; JXPath can only create a path if it uses exclusively the child:: and attribute:: axes and has no context-dependent predicates
[25/02/09 14:22:20:824 GMT] 00000087 BpelEngine I CWWBE0163I: Business Process Choreographer is using navigation based on JMS in long-running business processes
[25/02/09 14:22:20:824 GMT] 00000087 BpelEngine I CWWBE0085E: Incompatible types were encountered during the assignment to a variable or partner link 'determineClawbackEligibilityRequest' in activity 'Assign'.
org.apache.commons.jxpath.JXPathException: Exception trying to create xpath Customer/PortfolioAccount/CancelledSubscriptionList/Subscription[bpws:getVariableData('Index1')]/Id; JXPath can only create a path if it uses exclusively the child:: and attribute:: axes and has no context-dependent predicates
[25/02/09 14:22:20:824 GMT] 00000087 BpelEngine I CWWBE0163I: Business Process Choreographer is using navigation based on JMS in long-running business processes
Root Cause
When you use for loop in BPEL, and try to assign from a Xpath to a Xpath expression using loop variable , you will see the above error.
Like
Requset/customers/customer[LoopVar]/id = Response/customers/customer[LoopVar]/id.
In the left hand side the expression is fine, but the predicate (right side) is not correct in BPEL. you cant use variable in case of BPEL for loop predicate.
Resolution
You have to assign the individual id to a temp variable and that temp variable you have to add to the final response.
Requset/customers/customer[LoopVar]/id = Temp_id.
each_Cust = createNewCustomer.setString("id",Temp_id)
Cust_List = response.getList("customers/customer")
Cust_List.add(each_Cust);
CWWBE0126E: The state 'Terminated' of the process instance 'Process_Template_Name' does not allow the requested action 'sendMessage()' to be performed.
Error
[25/03/09 12:10:30:952 GMT] 00000146 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_00000146_09.03.25_12.10.30_0.txt
[25/03/09 12:10:30:952 GMT] 00000146 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_00000146_09.03.25_12.10.30_0.txt
[25/03/09 12:10:30:952 GMT] 00000146 ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "processMessage" on bean "BeanId(Process_Template_NameApp#Process_Template_NameEJB.jar#component.Process_Template_Name, null)". Exception data: com.ibm.bpe.api.EngineProcessWrongStateException: CWWBE0126E: The state 'Terminated' of the process instance 'Process_Template_Name' does not allow the requested action 'sendMessage()' to be performed.
at com.ibm.bpe.engine.BpelRequestChecker.createProcessWrongStateException(BpelRequestChecker.java:629)
at com.ibm.bpe.engine.BpelEngineCore.receiveEvent(BpelEngineCore.java:2014)
at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:811)
at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:746)
at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:696)
at com.ibm.bpe.framework.sca.ProcessSessionBean.invokeEngineSync(ProcessSessionBean.java:1136)
at com.ibm.bpe.framework.sca.ProcessSessionBean.invokeEngineSync(ProcessSessionBean.java:1108)
at com.ibm.bpe.framework.sca.ProcessSessionBean.processMessage(ProcessSessionBean.java:360)
at com.ibm.bpe.framework.sca.EJSLocalStatelesscomponent_Clawback_Collection_Pr_dcfdf588.processMessage(EJSLocalStatelesscomponent_Clawback_Collection_Pr_dcfdf588.java:639)
at com.ibm.bpe.framework.sca.ProcessImplementationHandler.handleInboundCalls(ProcessImplementationHandler.java:267)
at com.ibm.bpe.framework.sca.ProcessImplementationHandler.processMessage(ProcessImplementationHandler.java:154)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1286)
Root Cause
Similar error occurs when you create one more long running process instance in the WPS server context with same correlation id. One correlation id should be unique for one instance, even if the instance runing-Terminated-Paused state.
Resolution
If you have to create one more instance with the same request, the existing instance must be deleted (may be from BPC explorer)
[25/03/09 12:10:30:952 GMT] 00000146 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_00000146_09.03.25_12.10.30_0.txt
[25/03/09 12:10:30:952 GMT] 00000146 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\IBM\WID61\pf\ProcSrv04\logs\ffdc\server1_00000146_09.03.25_12.10.30_0.txt
[25/03/09 12:10:30:952 GMT] 00000146 ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "processMessage" on bean "BeanId(Process_Template_NameApp#Process_Template_NameEJB.jar#component.Process_Template_Name, null)". Exception data: com.ibm.bpe.api.EngineProcessWrongStateException: CWWBE0126E: The state 'Terminated' of the process instance 'Process_Template_Name' does not allow the requested action 'sendMessage()' to be performed.
at com.ibm.bpe.engine.BpelRequestChecker.createProcessWrongStateException(BpelRequestChecker.java:629)
at com.ibm.bpe.engine.BpelEngineCore.receiveEvent(BpelEngineCore.java:2014)
at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:811)
at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:746)
at com.ibm.bpe.engine.BpelEngine.receiveEvent(BpelEngine.java:696)
at com.ibm.bpe.framework.sca.ProcessSessionBean.invokeEngineSync(ProcessSessionBean.java:1136)
at com.ibm.bpe.framework.sca.ProcessSessionBean.invokeEngineSync(ProcessSessionBean.java:1108)
at com.ibm.bpe.framework.sca.ProcessSessionBean.processMessage(ProcessSessionBean.java:360)
at com.ibm.bpe.framework.sca.EJSLocalStatelesscomponent_Clawback_Collection_Pr_dcfdf588.processMessage(EJSLocalStatelesscomponent_Clawback_Collection_Pr_dcfdf588.java:639)
at com.ibm.bpe.framework.sca.ProcessImplementationHandler.handleInboundCalls(ProcessImplementationHandler.java:267)
at com.ibm.bpe.framework.sca.ProcessImplementationHandler.processMessage(ProcessImplementationHandler.java:154)
at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1286)
Root Cause
Similar error occurs when you create one more long running process instance in the WPS server context with same correlation id. One correlation id should be unique for one instance, even if the instance runing-Terminated-Paused state.
Resolution
If you have to create one more instance with the same request, the existing instance must be deleted (may be from BPC explorer)
java.io.IOException: Error reading XML
Error
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O com.ibm.bpe.api.RuntimeFaultException: CWWBE0003E: An error occurred during the invocation of the activity implementation 'Invoke-getExemption'.
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O com.ibm.wsspi.sca.message.NativeDataParseException: java.io.IOException: Error reading XML
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O java.io.IOException: Error reading XML
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'Customer' not found. (file:///C:/IBM/WID61/pf/ProcSrv03/, 1, 579)
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'Customer' not found. (file:///C:/IBM/WID61/pf/ProcSrv03/, 1, 579)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeature(XMLHandler.java:1745)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeature(XMLHandler.java:1709)
at com.ibm.ws.bo.bomodel.util.BOXMLHandler.handleFeature(BOXMLHandler.java:581)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:887)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:866)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:633)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:179)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:179)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1094)
at com.ibm.ws.bo.bomodel.util.SerializerUtil$2.run(SerializerUtil.java:171)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.ibm.ws.bo.bomodel.util.SerializerUtil.privilegedLoad(SerializerUtil.java:162)
at com.ibm.ws.bo.service.BOXMLSerializerImpl.load(BOXMLSerializerImpl.java:248)
at com.ibm.ws.bo.service.BOXMLSerializerImpl.readXMLDocumentWithOptions(BOXMLSerializerImpl.java:463)
at com.ibm.ws.sca.internal.sdo.impl.BOXMLSerializerDelegatorImpl.load(BOXMLSerializerDelegatorImpl.java:93)
Root Cause
The above error shows when the response XML is not in correct format.
If you have a closer look, you can spot the missing element as well (here its the customer)
Resolution
Correct the response xml, from the replying application.
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O com.ibm.bpe.api.RuntimeFaultException: CWWBE0003E: An error occurred during the invocation of the activity implementation 'Invoke-getExemption'.
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O com.ibm.wsspi.sca.message.NativeDataParseException: java.io.IOException: Error reading XML
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O java.io.IOException: Error reading XML
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'Customer' not found. (file:///C:/IBM/WID61/pf/ProcSrv03/, 1, 579)
[20/02/09 10:11:01:153 GMT] 0000006a SystemOut O org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'Customer' not found. (file:///C:/IBM/WID61/pf/ProcSrv03/, 1, 579)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeature(XMLHandler.java:1745)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeature(XMLHandler.java:1709)
at com.ibm.ws.bo.bomodel.util.BOXMLHandler.handleFeature(BOXMLHandler.java:581)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:887)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:866)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:633)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:179)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:179)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1094)
at com.ibm.ws.bo.bomodel.util.SerializerUtil$2.run(SerializerUtil.java:171)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.ibm.ws.bo.bomodel.util.SerializerUtil.privilegedLoad(SerializerUtil.java:162)
at com.ibm.ws.bo.service.BOXMLSerializerImpl.load(BOXMLSerializerImpl.java:248)
at com.ibm.ws.bo.service.BOXMLSerializerImpl.readXMLDocumentWithOptions(BOXMLSerializerImpl.java:463)
at com.ibm.ws.sca.internal.sdo.impl.BOXMLSerializerDelegatorImpl.load(BOXMLSerializerDelegatorImpl.java:93)
Root Cause
The above error shows when the response XML is not in correct format.
If you have a closer look, you can spot the missing element as well (here its the customer)
Resolution
Correct the response xml, from the replying application.
javax.jms.JMSSecurityException: CWSIA0006E: The authorization for the supplied user name was not successful.
Error
[27/03/09 09:57:45:099 GMT] 0000003e SibMessage W [SCA.SYSTEM.LIVWS0095952Node03Cell.Bus:LIVWS0095952Node03.server1-SCA.SYSTEM.LIVWS0095952Node03Cell.Bus] CWSII0212W: The bus SCA.SYSTEM.LIVWS0095952Node03Cell.Bus denied an anonymous user access to the bus.
[27/03/09 09:57:45:099 GMT] 0000003e JMSListenerMD E WSWS3406E: Unexpected exception caught while sending reply message: javax.jms.JMSSecurityException: CWSIA0006E: The authorization for the supplied user name was not successful.
Root Cause
Authorization problems connecting to the bus The primary reason for an authorization failure when connecting to the bus is that the user, or a group that includes the user, does not have the bus connector role for that bus.
Resolution.
You can configure a user to have the bus connector role using the administrative console or the wsadmin scripting tool.
Best practice is to assign roles using groups rather than users directly.
Resolving the problem using the administrative console
From the administrative console:
1. Select Service Integration Buses.
2. Click on the bus name to which the client requires access.
3. Select Security.
4. Select Users and groups in the bus connector role.
This page lists the users and groups in the bus connector role. By default, this
list only contains a single group, the Server group. This convention gives
application servers authority to connect to the bus, but not the individual
applications .
You can modify this list by either deleting or adding users or groups.
5. To give a user the bus connector role, click New.
A new panel displays that lets you add users and groups (along with the
special Everyone, AllAuthenticated, and Server groups) to the bus connector
role.
6. Click OK to add the user to the bus connector role. The result is shown in
Figure 17-8.
7. Save and synchronize the configuration. You do not need to restart the server.
[27/03/09 09:57:45:099 GMT] 0000003e SibMessage W [SCA.SYSTEM.LIVWS0095952Node03Cell.Bus:LIVWS0095952Node03.server1-SCA.SYSTEM.LIVWS0095952Node03Cell.Bus] CWSII0212W: The bus SCA.SYSTEM.LIVWS0095952Node03Cell.Bus denied an anonymous user access to the bus.
[27/03/09 09:57:45:099 GMT] 0000003e JMSListenerMD E WSWS3406E: Unexpected exception caught while sending reply message: javax.jms.JMSSecurityException: CWSIA0006E: The authorization for the supplied user name was not successful.
Root Cause
Authorization problems connecting to the bus The primary reason for an authorization failure when connecting to the bus is that the user, or a group that includes the user, does not have the bus connector role for that bus.
Resolution.
You can configure a user to have the bus connector role using the administrative console or the wsadmin scripting tool.
Best practice is to assign roles using groups rather than users directly.
Resolving the problem using the administrative console
From the administrative console:
1. Select Service Integration Buses.
2. Click on the bus name to which the client requires access.
3. Select Security.
4. Select Users and groups in the bus connector role.
This page lists the users and groups in the bus connector role. By default, this
list only contains a single group, the Server group. This convention gives
application servers authority to connect to the bus, but not the individual
applications .
You can modify this list by either deleting or adding users or groups.
5. To give a user the bus connector role, click New.
A new panel displays that lets you add users and groups (along with the
special Everyone, AllAuthenticated, and Server groups) to the bus connector
role.
6. Click OK to add the user to the bus connector role. The result is shown in
Figure 17-8.
7. Save and synchronize the configuration. You do not need to restart the server.
Subscribe to:
Posts (Atom)
