VIP Troubleshooting Guide

Transcription

1 VIP Troubleshooting Guide

2 EIP Trouble Shooting Guide Contents EIP Trouble Shooting Guide 2 Commercial In Confidence 3 Preface Information 4 Overview 5 Server Tuning and Troubleshooting 6 Memory Settings 6 64bit Architectures 6 Troubleshooting Common Issues 7 Error Handling for Messages 7 Ellipse Issues 7 All EWS Requests Failing 7 Symptom 7 Resolution 7 Unable to Contact the Ellipse Service 8 Unable to Construct the Ellipse Service 8 Ellipse Service Unable to Publish Event Message 8 SOAPFault core.e<number> 9 SOAPFault mims.e<number> 9 Web Service Client Mismatch 9 Tracing Adapter Processing 9 Tracing Ellipse SOAP Requests and Responses 10 Tracing Ellipse Web Services Processing 10 Database Errors 10 Connection Errors 11 Loading Properties Errors 11 Connection Pooling Cleanup 11 JMS Errors 11 IBM MQ Errors 12 Cannot Connect to MQ Queue Manager 12 Cannot Listen to the Inbound Message Queue 12 Cannot Send Outbound Message to Queue 12

3 Commercial In Confidence Copyright 2016 ABB All Rights Reserved Confidential and Proprietary Legal Disclaimer The product described in this documentation may be connected to, and/or communicate information and data via, a network interface, which should be connected to a secure network. It is your sole responsibility to ensure a secure connection to the network and to establish and maintain appropriate measures (such as but not limited to the installation of firewalls, application of authentication measures, encryption of data, installation of antivirus programs, etc.) to protect the product, the network, your systems, and the interface against any kind of security breach, unauthorised access, interference, intrusion, leakage, damage, or corruption or theft of data. We are not liable for damages or losses related to any such security breach, unauthorised access, interference, intrusion, leakage, damage, or corruption or theft of data.

4 Preface Information This document is intended for use by system administrators, professional services personal or other technical resources needing to solve common issues that may occur in the operation of the Ellipse Integration Platform (EIP).

5 Overview The Ellipse Integration Platform (EIP) is an open, standards-based platform that offers out-of-box integrations between the ABB suite of products as well as to leading ERP platforms. Leveraging industry standards such as Java, XML, Web Services and JMS, the platform provides a SOI (Service Oriented Infrastructure) that can quickly be leveraged to integrate existing customer solutions to the ABB suite of product services. Using this technology virtually eliminates the need to spend time and money developing custom point to point solutions, thereby reducing project implementation time and cost. The EIP solution includes a Console that caters for the monitoring and management of messages processed through EIP and the server along with related server components. For details of the Console refer to the EIP Console User Guide.

6 Server Tuning and Troubleshooting The default installation is set to provide the best performance and memory utilization for most customer deployments. In some cases it is necessary to tune these settings to provide optimal performance based on the customer's needs. Memory Settings Depending on your needs, it may be necessary to change the memory settings of the Java VM used to run the integration platform. These settings are changed by modifying the run.conf (run.conf.bat for Windows) file located in the <install-dir>/appserver/bin directory. If you experience OutOfMemory errors while running the platform, you may need to increate the available memory for the server. The default is 1024m. To increase, locate the JAVA_OPTS= line in the file and change the setting Xmx1024m to a larger value. You must restart the server for the changes to take effect. In larger deployments it may be required to increase the size of the PermGen space. To do this, again edit the run.conf file and change the JAVA_OPTS setting for -XX:MaxPermSize=. The default is 256m. If you experience OutOfMemory permgen errors, you should increase. You must restart the server for the changes to take effect. The max sizes for these values are dependent on your operating system, amount of available physical memory on the machine, and type of CPU architecture. Contact your system administrator and/or refer to the Java VM for more information. 64bit Architectures On some 64bit hardware like HP/UX, you may need to add a JAVA_OPTS setting to force the Java VM to use 64bit address space. Check with your Java VM vendor documentation for more information. For HP/UX I64 systems, see HP/UX IA64 located in this document.

7 org.jboss.soa.esb.listeners.message.overriddenactionpipelineprocessor.process(overriddenactionpipelineprocessor.java:73) at org.jboss.soa.esb.listeners.message.actionprocessingpipeline.processpipeline(actionprocessingpipeline.java:649) at org.jboss.soa.esb.listeners.message.actionprocessingpipeline.processpipeline(actionprocessingpipeline.java:603) at org.jboss.soa.esb.listeners.message.actionprocessingpipeline.process(actionprocessingpipeline.java:433) at org.jboss.soa.esb.listeners.message.messageawarelistener$transactionalrunner.run(messageawarelistener.java:550) at java.util.concurrent.threadpoolexecutor$worker.runtask(threadpoolexecutor.java:886) at java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:908) at java.lang.thread.run(thread.java:662) Caused by: org.apache.cxf.binding.soap.soapfault: org.springframework.transaction.unexpectedrollbackexception: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is javax.transaction.rollbackexception: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could not commit transaction. at org.apache.cxf.binding.soap.interceptor.soap11faultininterceptor.unmarshalfault(soap11faultininterceptor.java:75) at org.apache.cxf.binding.soap.interceptor.soap11faultininterceptor.handlemessage(soap11faultininterceptor.java:46) at org.apache.cxf.binding.soap.interceptor.soap11faultininterceptor.handlemessage(soap11faultininterceptor.java:35) at org.apache.cxf.phase.phaseinterceptorchain.dointercept(phaseinterceptorchain.java:255) at org.apache.cxf.interceptor.abstractfaultchaininitiatorobserver.onmessage(abstractfaultchaininitiatorobserver.java:99) at org.apache.cxf.binding.soap.interceptor.checkfaultinterceptor.handlemessage(checkfaultinterceptor.java:69) at org.apache.cxf.binding.soap.interceptor.checkfaultinterceptor.handlemessage(checkfaultinterceptor.java:34) at org.apache.cxf.phase.phaseinterceptorchain.dointercept(phaseinterceptorchain.java:255) at org.apache.cxf.endpoint.clientimpl.onmessage(clientimpl.java:785) at org.apache.cxf.transport.http.httpconduit$wrappedoutputstream.handleresponseinternal(httpconduit.java:2356) at org.apache.cxf.transport.http.httpconduit$wrappedoutputstream.handleresponse(httpconduit.java:2214) at org.apache.cxf.transport.http.httpconduit$wrappedoutputstream.close(httpconduit.java:2058) at org.apache.cxf.transport.abstractconduit.close(abstractconduit.java:56) at org.apache.cxf.transport.http.httpconduit.close(httpconduit.java:707) at org.apache.cxf.interceptor.messagesenderinterceptor$messagesenderendinginterceptor.handlemessage(messagesenderinterceptor.java:62) at org.apache.cxf.phase.phaseinterceptorchain.dointercept(phaseinterceptorchain.java:255) at org.apache.cxf.endpoint.clientimpl.invoke(clientimpl.java:546) at org.apache.cxf.endpoint.clientimpl.invoke(clientimpl.java:343) at org.apache.cxf.endpoint.clientimpl.invoke(clientimpl.java:295) at org.apache.cxf.frontend.clientproxy.invokesync(clientproxy.java:73) at org.apache.cxf.jaxws.jaxwsclientproxy.invoke(jaxwsclientproxy.java:124) more :03:12,335 INFO [com.mincom.mib.ellipse.finance.externalsysfinancialtransactionsaction] (pool-55-thread-1) Error detected in response:standarderror [additionalinformation=null, code=soapfault, details=org.springframework.transaction.unexpectedrollbackexception: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is javax.transaction.rollbackexception: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Could not commit transaction., operation=postexternalsysfinancialtransactions, requestindex=null] Troubleshooting Common Issues The following sections contain information on some of the more common issues you might encounter in the operation of EIP. Error Handling for Messages The table below outlines typical error scenarios that may be encountered and how messages are handled in each of those. Error Type Message Failure - Message is valid in structure but cannot be processed in Ellipse due to invalid data content e.g. invalid Supplier Id when doing Supplier sync. Routing Failure - message is valid in structure but no route has been defined to process the OAGIS BOD (Verb/Noun) that identifies the message type (e.g. GetCodeEntry). Message Error - Message contains invalid XML. Technical Error - Ellipse system is down and cannot be contacted. Therefore EIP message cannot be processed. Technical Error - unexpected. e.g. File system is full. Recommendation is to follow best practice of monitoring logs but no issues expected. Message will appear in EIP Console Y Y Y will be sent to EIP administrator Y - where configured. Y - where configured. Y - where configured. Response message on JMS endpoint Y - placed on mib.common.reply queue. Y - placed on mib.common.unrouted topic. Y - placed on mib.common.error queue. Y Y Y - placed on mib.common.error queue. Notes Appropriate action must be taken to address invalid data (in Ellipse or 3rd party system). The message may need to be resent from the source system to be reprocessed, or simply replayed through the EIP console where the data has been corrected in the target system. Appropriate action must be taken to address invalid message id (in 3rd party system) or define route for the message in EIP. The message may need to be resent from the source system to be reprocessed, or simply replayed through the EIP console where the route has been defined in EIP. Code changes may be required in the adapter/esb interfacing to EIP. Source system must resend valid message. Message needs to be manually replayed through the EIP console. N/A N/A N/A Daily log monitoring of server log recommended. Note All errors are logged. Ellipse Issues All EWS Requests Failing Symptom EIP server logs show all EWS requests failing with a stack trace as follows: Resolution Check the EWS server that the EIP requests are being sent to ensure that the /opt/vip directory is not full (via the unix df command). If the /opt/vip directory is at 100%, then this may be the cause of the problem. Disk space should be cleared in that directory and then the processing of EIP messages re-checked via the EIP server log file.

8 Unable to Contact the Ellipse Service If you receive the following error in a response to a message, it means that the integration service could not contact the Ellipse services. <Error date=" t21:04: :00" operation="unknown" code="generalexception"> <Details>Unable to contact the Ellipse service</details> </Error> Alternatively (if you don t get a response message on the expected reply queue) check the server log or search for the message via the EIP Console. If these contain a stack trace as below that also means that the integration service could not contact the Ellipse services. java.lang.runtimeexception: Unable to contact the Ellipse service at com.mincom.mib.ellipse.startconversationaction.startconversation(startconversationaction.java:110) at com.mincom.mib.ellipse.startconversationaction.process(startconversationaction.java:71) 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.apache.camel.component.bean.methodinfo.invoke(methodinfo.java:407) at org.apache.camel.component.bean.methodinfo$1.doproceed(methodinfo.java:278) at org.apache.camel.component.bean.methodinfo$1.proceed(methodinfo.java:251) at org.apache.camel.component.bean.beanprocessor.process(beanprocessor.java:166) at org.apache.camel.management.instrumentationprocessor.process(instrumentationprocessor.java:72) at org.apache.camel.processor.redeliveryerrorhandler.process(redeliveryerrorhandler.java:398) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) at org.apache.camel.processor.pipeline.process(pipeline.java:118) at org.apache.camel.processor.pipeline.process(pipeline.java:80) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) at org.apache.camel.util.asyncprocessorhelper.process(asyncprocessorhelper.java:105) at org.apache.camel.processor.delegateasyncprocessor.process(delegateasyncprocessor.java:87) at org.apache.camel.component.jms.endpointmessagelistener.onmessage(endpointmessagelistener.java:103) at org.springframework.jms.listener.abstractmessagelistenercontainer.doinvokelistener(abstractmessagelistenercontainer.java:562) at org.springframework.jms.listener.abstractmessagelistenercontainer.invokelistener(abstractmessagelistenercontainer.java:500) at org.springframework.jms.listener.abstractmessagelistenercontainer.doexecutelistener(abstractmessagelistenercontainer.java:468) at org.springframework.jms.listener.abstractpollingmessagelistenercontainer.doreceiveandexecute(abstractpollingmessagelistenercontainer.java:325) at org.springframework.jms.listener.abstractpollingmessagelistenercontainer.receiveandexecute(abstractpollingmessagelistenercontainer.java:263) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.invokelistener(defaultmessagelistenercontainer.java:1102) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.executeongoingloop(defaultmessagelistenercontainer.java:1094) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.run(defaultmessagelistenercontainer.java:991) at java.util.concurrent.threadpoolexecutor$worker.runtask(threadpoolexecutor.java:895) at java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:918) at java.lang.thread.run(thread.java:662)caused by: java.lang.runtimeexception: unable to open connection using [ at com.mincom.ews.client.ewsclientconversation.start(ewsclientconversation.java:100) at com.mincom.ews.client.ewsclientconversation.start(ewsclientconversation.java:64) at com.mincom.mib.ellipse.startconversationaction.createconversation(startconversationaction.java:138) at com.mincom.mib.ellipse.startconversationaction.startconversation(startconversationaction.java:88) more To verify, first check that the services are running. The simplest way is to use a browser or wget to access the services URL. This URL is the value you entered when installing the integration platform. An example would be If you get a page listing all of the service, the services are up. If you get a blank page, the service app is running but no services are deployed. If you get a message that the browser or wget could not connect, the services are down or the WAS instance is down. Consult the Ellipse Web Services (EWS) guide for more information. If testing in a Unix shell, you can use wget or lwp-download to test if the service is there. An example would be lwp-download If it downloads the WSDL, the service is running. If you get a 404 error, the service is not available. Unable to Construct the Ellipse Service If the processing of a EIP message fails with the following stack trace in the server.log file, it means that there is a problem with the web service definition. 15:33:24,876 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) org.jboss.soa.esb.actions.actionprocessingfaultexception: ReadWorkOrder:retrieve 15:33:24,876 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.esb.action.baseaction.storeexceptioninresponse(baseaction.java:339) ~[mib-camel.jar:na] 15:33:24,876 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.ellipsebaseaction.storeexceptioninresponse(ellipsebaseaction.java:209) ~[mib-common.jar:na] 15:33:24,876 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.workorder.workorderaction.get(workorderaction.java:767) ~[mib-common.jar:na] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.nativemethodaccessorimpl.invoke0(native Method) ~[na:1.6.0_45] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:39) ~[na:1.6.0_45] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:25) ~[na:1.6.0_45] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.lang.reflect.method.invoke(method.java:597) ~[na:1.6.0_45] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.methodinfo.invoke(methodinfo.java:407) ~[camel-core.jar:2.13.2] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.methodinfo$1.doproceed(methodinfo.java:278) ~[camel-core.jar:2.13.2] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.methodinfo$1.proceed(methodinfo.java:251) ~[camel-core.jar:2.13.2] 15:33:24,886 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.beanprocessor.process(beanprocessor.java:166) ~[camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.management.instrumentationprocessor.process(instrumentationprocessor.java:72) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.redeliveryerrorhandler.process(redeliveryerrorhandler.java:398) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:118) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:80) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.choiceprocessor.process(choiceprocessor.java:111) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.management.instrumentationprocessor.process(instrumentationprocessor.java:72) [camel-core.jar:2.13.2] 15:33:24,896 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.redeliveryerrorhandler.process(redeliveryerrorhandler.java:398) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:118) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:80) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.util.asyncprocessorhelper.process(asyncprocessorhelper.java:105) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.delegateasyncprocessor.process(delegateasyncprocessor.java:87) [camel-core.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.jms.endpointmessagelistener.onmessage(endpointmessagelistener.java:103) [camel-jms.jar:2.13.2] 15:33:24,906 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractmessagelistenercontainer.doinvokelistener(abstractmessagelistenercontainer.java:562) [spring-jms.jar:4.0.6.release] 15:33:24,916 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractmessagelistenercontainer.invokelistener(abstractmessagelistenercontainer.java:500) [spring-jms.jar:4.0.6.release] 15:33:24,916 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractmessagelistenercontainer.doexecutelistener(abstractmessagelistenercontainer.java:468) [spring-jms.jar:4.0.6.release] 15:33:24,916 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractpollingmessagelistenercontainer.doreceiveandexecute(abstractpollingmessagelistenercontainer.java:325) [spring-jms.jar:4.0.6.release] 15:33:24,916 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractpollingmessagelistenercontainer.receiveandexecute(abstractpollingmessagelistenercontainer.java:263) [spring-jms.jar:4.0.6.release] 15:33:24,916 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.invokelistener(defaultmessagelistenercontainer.java:1102) [spring-jms.jar:4.0.6.release] 15:33:24,916 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.executeongoingloop(defaultmessagelistenercontainer.java:1094) [spring-jms.jar:4.0.6.release] 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.run(defaultmessagelistenercontainer.java:991) [spring-jms.jar:4.0.6.release] 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.util.concurrent.threadpoolexecutor$worker.runtask(threadpoolexecutor.java:895) [na:1.6.0_45] 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:918) [na:1.6.0_45] 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.lang.thread.run(thread.java:662) [na:1.6.0_45] 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) Caused by: javax.xml.ws.webserviceexception: org.apache.cxf.service.factory.serviceconstructionexception 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.serviceimpl.getport(serviceimpl.java:318) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 15:33:24,926 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.serviceimpl.getport(serviceimpl.java:303) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.ews.client.ewsclientconversation.createservice(ewsclientconversation.java:255) ~[EWSJavaClient.jar:na] 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.ellipsebaseaction.createservice(ellipsebaseaction.java:174) ~[mib-common.jar:na] 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.ellipsebaseaction.createservice(ellipsebaseaction.java:158) ~[mib-common.jar:na] 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.workorder.workorderaction.get(workorderaction.java:713) ~[mib-common.jar:na] 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) common frames omitted 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) Caused by: org.apache.cxf.service.factory.serviceconstructionexception: null 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxb.jaxbdatabinding.initialize(jaxbdatabinding.java:337) ~[cxf-rt-databinding-jaxb.jar:2.2.6] 15:33:24,936 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.service.factory.reflectionservicefactorybean.buildservicefromwsdl(reflectionservicefactorybean.java:432) ~[cxf-rt-frontend-simple.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.service.factory.reflectionservicefactorybean.initializeservicemodel(reflectionservicefactorybean.java:528) ~[cxf-rt-frontend-simple.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.service.factory.reflectionservicefactorybean.create(reflectionservicefactorybean.java:278) ~[cxf-rt-frontend-simple.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.support.jaxwsservicefactorybean.create(jaxwsservicefactorybean.java:178) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.frontend.abstractwsdlbasedendpointfactory.createendpoint(abstractwsdlbasedendpointfactory.java:100) ~[cxf-rt-frontend-simple.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.frontend.clientfactorybean.create(clientfactorybean.java:51) ~[cxf-rt-frontend-simple.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.frontend.clientproxyfactorybean.create(clientproxyfactorybean.java:102) ~[cxf-rt-frontend-simple.jar:2.2.6] 15:33:24,946 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.jaxwsproxyfactorybean.create(jaxwsproxyfactorybean.java:115) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.serviceimpl.createport(serviceimpl.java:437) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.serviceimpl.getport(serviceimpl.java:316) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) common frames omitted 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) Caused by: com.sun.xml.bind.v2.runtime.illegalannotationsexception: 1 counts of IllegalAnnotationExceptions 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.xml.bind.v2.runtime.illegalannotationsexception$builder.check(illegalannotationsexception.java:106) ~[na:na] 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.xml.bind.v2.runtime.jaxbcontextimpl.gettypeinfoset(jaxbcontextimpl.java:466) ~[na:na] 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.xml.bind.v2.runtime.jaxbcontextimpl.<init>(jaxbcontextimpl.java:298) ~[na:na] 15:33:24,956 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.xml.bind.v2.runtime.jaxbcontextimpl.<init>(jaxbcontextimpl.java:141) ~[na:na] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.xml.bind.v2.runtime.jaxbcontextimpl$jaxbcontextbuilder.build(jaxbcontextimpl.java:1157) ~[na:na] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.xml.bind.v2.contextfactory.createcontext(contextfactory.java:145) ~[na:na] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.generatedmethodaccessor73.invoke(unknown Source) ~[na:na] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:25) ~[na:1.6.0_45] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.lang.reflect.method.invoke(method.java:597) ~[na:1.6.0_45] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at javax.xml.bind.contextfinder.newinstance(contextfinder.java:211) ~[jboss-jaxb-api_2.2_spec final.jar!/:1.0.3.final] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at javax.xml.bind.contextfinder.find(contextfinder.java:392) ~[jboss-jaxb-api_2.2_spec final.jar!/:1.0.3.final] 15:33:24,966 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at javax.xml.bind.jaxbcontext.newinstance(jaxbcontext.java:618) ~[jboss-jaxb-api_2.2_spec final.jar!/:1.0.3.final] 15:33:24,976 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxb.jaxbdatabinding.createcontext(jaxbdatabinding.java:560) ~[cxf-rt-databinding-jaxb.jar:2.2.6] 15:33:24,976 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxb.jaxbdatabinding.createjaxbcontextandschemas(jaxbdatabinding.java:500) ~[cxf-rt-databinding-jaxb.jar:2.2.6] 15:33:24,976 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxb.jaxbdatabinding.initialize(jaxbdatabinding.java:320) ~[cxf-rt-databinding-jaxb.jar:2.2.6] 15:33:24,976 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) common frames omitted To remedy this the Ellipse web service definition will need to be changed, this will require a case to be raised and lodged with ABB Global Support Services. The Ellipse web service will need to be changed and a new version of Ellipse released. This will contain a new version of the EWSJavaClient.jar file, the EIP version will then also need to be updated with the same EWSJavaClient.jar file version. Ellipse Service Unable to Publish Event Message Where all Ellipse web service requests fail with the following error, it means that there is a problem with the configuration of Ellipse or EIP. 10:38:29,586 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) 10:38: [Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]] INFO c.m.mib.ellipse.transactionaction - Start transaction failed, reason:com.mincom.ews.service.connectivity.authenticatorexception: com.mincom.ellipse.lsi.exception.legacyservicesessioncreationexception: nacalib.exceptions.abortsessionexception: AbortSessionException Prg=Msk000 Reason=Unable to publish ellipse event, attempt:1

9 10:38:29,586 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) 10:38: [Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]] INFO c.m.mib.ellipse.transactionaction - Transaction start failed! com.mincom.ews.service.connectivity.authenticatorexception: com.mincom.ellipse.lsi.exception.legacyservicesessioncreationexception: nacalib.exceptions.abortsessionexception: AbortSessionException Prg=Msk000 Reason=Unable to publish ellipse event 10:38:29,586 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) 10:38: [Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]] INFO c.m.mib.ellipse.transactionaction - Error detected in response:standarderror [additionalinformation=null, code=soapfault, details=com.mincom.ews.service.connectivity.authenticatorexception: com.mincom.ellipse.lsi.exception.legacyservicesessioncreationexception: nacalib.exceptions.abortsessionexception: AbortSessionException Prg=Msk000 Reason=Unable to publish ellipse event, operation=starttransaction, requestindex=null] 10:38:29,597 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) 10:38: [Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]] WARN c.m.m.e.a.esbmessagethrewexceptionaction - message processing threw exception for message id [8a001abe4a3bee51014a3bee ] 10:38:29,647 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) 10:38: [Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]] WARN c.m.m.e.a.esbmessagethrewexceptionaction - exception thrown was: 10:38:29,647 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) org.jboss.soa.esb.actions.actionprocessingfaultexception: starttransaction 10:38:29,647 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.esb.action.baseaction.storeexceptioninresponse(baseaction.java:314) ~[mib-camel.jar:na] 10:38:29,647 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.ellipsebaseaction.storeexceptioninresponse(ellipsebaseaction.java:209) ~[mib-common.jar:na] 10:38:29,647 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.transactionaction.start(transactionaction.java:142) ~[mib-common.jar:na] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.nativemethodaccessorimpl.invoke0(native Method) ~[na:1.6.0_45] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:39) ~[na:1.6.0_45] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:25) ~[na:1.6.0_45] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.lang.reflect.method.invoke(method.java:597) ~[na:1.6.0_45] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.methodinfo.invoke(methodinfo.java:407) ~[camel-core.jar:2.13.2] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.methodinfo$1.doproceed(methodinfo.java:278) ~[camel-core.jar:2.13.2] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.methodinfo$1.proceed(methodinfo.java:251) ~[camel-core.jar:2.13.2] 10:38:29,657 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.bean.beanprocessor.process(beanprocessor.java:166) ~[camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.management.instrumentationprocessor.process(instrumentationprocessor.java:72) [camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.redeliveryerrorhandler.process(redeliveryerrorhandler.java:398) [camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) ~[camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:118) ~[camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:80) ~[camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.choiceprocessor.process(choiceprocessor.java:111) ~[camel-core.jar:2.13.2] 10:38:29,667 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.management.instrumentationprocessor.process(instrumentationprocessor.java:72) [camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.redeliveryerrorhandler.process(redeliveryerrorhandler.java:398) [camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) ~[camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:118) ~[camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.pipeline.process(pipeline.java:80) ~[camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.camelinternalprocessor.process(camelinternalprocessor.java:191) ~[camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.util.asyncprocessorhelper.process(asyncprocessorhelper.java:105) [camel-core.jar:2.13.2] 10:38:29,677 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.processor.delegateasyncprocessor.process(delegateasyncprocessor.java:87) [camel-core.jar:2.13.2] 10:38:29,687 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.camel.component.jms.endpointmessagelistener.onmessage(endpointmessagelistener.java:103) [camel-jms.jar:2.13.2] 10:38:29,687 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractmessagelistenercontainer.doinvokelistener(abstractmessagelistenercontainer.java:562) [spring-jms.jar:4.0.6.release] 10:38:29,687 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractmessagelistenercontainer.invokelistener(abstractmessagelistenercontainer.java:500) [spring-jms.jar:4.0.6.release] 10:38:29,687 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractmessagelistenercontainer.doexecutelistener(abstractmessagelistenercontainer.java:468) [spring-jms.jar:4.0.6.release] 10:38:29,687 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractpollingmessagelistenercontainer.doreceiveandexecute(abstractpollingmessagelistenercontainer.java:325) [spring-jms.jar:4.0.6.release] 10:38:29,687 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.abstractpollingmessagelistenercontainer.receiveandexecute(abstractpollingmessagelistenercontainer.java:263) [spring-jms.jar:4.0.6.release] 10:38:29,697 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.invokelistener(defaultmessagelistenercontainer.java:1102) [spring-jms.jar:4.0.6.release] 10:38:29,697 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.executeongoingloop(defaultmessagelistenercontainer.java:1094) [spring-jms.jar:4.0.6.release] 10:38:29,697 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.springframework.jms.listener.defaultmessagelistenercontainer$asyncmessagelistenerinvoker.run(defaultmessagelistenercontainer.java:991) [spring-jms.jar:4.0.6.release] 10:38:29,697 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.util.concurrent.threadpoolexecutor$worker.runtask(threadpoolexecutor.java:895) [na:1.6.0_45] 10:38:29,697 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:918) [na:1.6.0_45] 10:38:29,707 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at java.lang.thread.run(thread.java:662) [na:1.6.0_45] 10:38:29,707 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) Caused by: javax.xml.ws.soap.soapfaultexception: com.mincom.ews.service.connectivity.authenticatorexception: com.mincom.ellipse.lsi.exception.legacyservicesessioncreationexception: nacalib.exceptions.abortsessionexception: AbortSessionException Prg=Msk000 Reason=Unable to publish ellipse event 10:38:29,707 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at org.apache.cxf.jaxws.jaxwsclientproxy.invoke(jaxwsclientproxy.java:146) ~[cxf-rt-frontend-jaxws.jar:2.2.6] 10:38:29,707 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.sun.proxy.$proxy97.begin(unknown Source) ~[na:na] 10:38:29,707 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) at com.mincom.mib.ellipse.transactionaction.start(transactionaction.java:94) ~[mib-common.jar:na] 10:38:29,707 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) common frames omitted In this case Ellipse has been configured with Event processing enabled. Where that is the case, Ellipse will publish event messages (where changes occur to data in Ellipse) to allow 3rd party systems that are interested in those changes to consume those messages. In order for that to be processed successfully, Ellipse must be configured to communicate with a JMS topic (EllipseServices) that is hosted in EIP. Check that: a. EIP has a JMS topic indentified as EllipseServices. b. Check that Ellipse is configured to be able to connect to the EllipseServices JMS topic. SOAPFault core.e<number> When integrating with Ellipse via Ellipse Web Services (EWS), there are times when the service returns a general error. These come in different formats but most will have an error code of SOAPFault and a details element with core.e<some number>. The error code is the value starting with value core and is the standard Ellipse codes. An example of this is as below: <Error date=" t14:33: :00" operation="updatestatus" code="soapfault"><details>core.e10001</details></error> To find out more details about this error, check the server log for the EWS server where EWS is deployed. This will possibly contain additional information about the error. Once you have located the log, search for the error code. In the example above, you might see the following in the log, which explains that the record could not be found to delete. [9/28/10 14:30:01:776 GMT-05:00] e SystemOut O :30:01,776 [] ERROR c.m.e.e.c.l.e.exception.trace - EDOI MSF877 delete Operation Failed.Object with identifier : authsdstatus=n positionid= tran_877type=pr dstrctcode=gcb transactionkey= reasoncode=xx does not exist[9/28/10 14:30:01:850 GMT-05:00] e info E : :user:core.e10001:edoi infrastructure error. See logs for details. com.mincom.ellipse.edoi.common.exception.edoiobjectnotfoundexception: EDOI MSF877 delete Operation Failed: Object with identifier : authsdstatus=n positionid= tran_877type=pr dstrctcode=gcb transactionkey= reasoncode=xx does not exist SOAPFault mims.e<number> When integrating with Ellipse via Ellipse Web Services (EWS), there are times when the service returns a data validation error. These come in different formats but most will have an error type of SOAPFault or EnterpriseServiceOperationException and a Code element with mims.e<some number>. The error code is the value starting with value mims.e and is a standard Ellipse code. The Message element contains a short description of the error. In addition the FieldName element contains the field with the value that is in error. An example of this is as below: Caused by: Caused by: javax.xml.ws.soap.soapfaultexception: Error 0: Code: mims.e.0669 Message: DATE MUST BE GREATER THAN OR EQUAL TO TODAY FieldName: DeferDate FieldIndex: 0 DtoIndex: 0 To find out more details about this error, check the server log for the EWS server where EWS is deployed. This will possibly contain additional information about the error. Once you have located the log, search for the error code. Web Service Client Mismatch EIP is shipped with the EWSJavaClient from Ellipse, the build of both Ellipse and EIP are normally synced so that where EIP and Ellipse are installed under the appliance model, the version of the EWSJavaClient on EIP should match that in Ellipse. Where EIP and Ellipse are installed under the DIY model it s possible the versions of the EWSJavaClient do not match. In that case, when EIP performs EWS request and response processing the following error could occur: 16:49:03,310 INFO [stdout] (Camel (camel-1) thread #11 - JmsConsumer[MIB.COMMON.GW]) Caused by: javax.xml.bind.unmarshalexception: unexpected element (uri:" local:"protectpostype"). Expected elements are <{ This indicates that the EIP version of the EWSJavaClient jar does not match the Ellipse version of the EWSJavaClient jar. In this case a new attribute (protectpostype) has been added to the emppositions web service in Ellipse, the web service response processing in EIP fails as the version of the EWSJavaClient in EIP does not have the up to date definition of the web service response. A new version of EIP will be required with an EWSJavaClient that matches that of the Ellipse version (for the Ellipse instance that EIP is configured to use). Tracing Adapter Processing There may be times when you will need to trace adapter processing for diagnosing an issue. This can be done by changing the logging value for the following to DEBUG in the JBoss configuration file standalone.xml. This will be found here: <JBoss server root>/standalone/configuration <profile> <subsystem xmlns="urn:jboss:domain:logging:1.1"> <root-logger> <level name="info"/> <handlers> <handler name="console"/> <handler name="file"/> </handlers> </root-logger> </subsystem> By default, they are set to INFO, which means minimal tracing is emitted to the logs. By setting to DEBUG, each calls inbound OAGIS message and outbound OAGIS response is logged to the JBoss server.log.

10 Tracing Ellipse SOAP Requests and Responses There may be times when you will need to obtain the EWS SOAP requests and responses in order to diagnose an issue. This can be done by changing the logging values for the following to DEBUG in the JBoss configuration file standalone.xml. This will be found here: <JBoss server root>/standalone/configuration <profile> <subsystem xmlns="urn:jboss:domain:logging:1.1"> <logger category="org.apache.cxf"> <level name="warn"/> </logger> <logger category="com.mincom.ews.client.ewsclientconversation"> <level name="warn"/> </logger> By default, they are set to WARN, which means no tracing is emitted to the logs. By setting to DEBUG, each calls outbound SOAP message and inbound SOAP response is logged to the system.log. Tracing Ellipse Web Services Processing There may be times when you will need to trace the Ellipse web service processing for diagnosing an issue. This can be done by changing the information in the OAGIS message sent to an Ellipse adapter from which the Ellipse web services are then called. The following Operation Context settings can be passed to the Ellipse web service request: 1. eventdisable 2. maxinstances 3. returnwarnings 4. trace The setting of these values for the web service request can be made in the OperationContext group under the ApplicationArea group. An example of this is as follows: <oa:applicationarea> <oa:sender> <oa:logicalid>testing</oa:logicalid> <oa:taskid>getengineeringworkdocument</oa:taskid> <oa:referenceid>work Request</oa:ReferenceID> </oa:sender> <oa:receiver/> <oa:creationdatetime> </oa:creationdatetime> <oa:bodid>junit Test</oa:BODID> <oa:extension> <oa:anyextension> <ip1:servicecontext xmlns:ip1=" <ip1:servicename>getengineeringworkdocument</ip1:servicename> <ip1:serviceversion>1.0</ip1:serviceversion> <ip1:messagetype>engineeringworkdocument</ip1:messagetype> <ip1:documentname>work Request</ip1:DocumentName> </ip1:servicecontext> <ip1:authorizationcontext xmlns:ip1=" <ip1:proxy> <ip1:userid>integrat</ip1:userid> <ip1:orgid>r100</ip1:orgid> <ip1:role>integrat</ip1:role> </ip1:proxy> </ip1:authorizationcontext> <ip1:operationcontext xmlns:ip1=" <ip1:eventdisable>true</ip1:eventdisable> <ip1:maxinstances>20</ip1:maxinstances> <ip1:returnwarnings>false</ip1:returnwarnings> <ip1:trace>false</ip1:trace> </ip1:operationcontext> </oa:anyextension> </oa:extension> </oa:applicationarea> To obtain tracing set the Trace element value to 'true'. Once the adapter has completed processing login to the Ellipse UI using the same Ellipse credentials used to the process the message and download the trace. Database Errors Depending on the database you are using, you may encounter issues with connections to the DB. The most common issue is that communications to the DB have been lost. This can occur if a network connection is lost, if the DB is shutdown, or the DBA has restricted access. EIP under an appliance model uses uses the Oracle database used by Ellipse, so if Ellipse is shutdown then the Oracle database may be shutdown as well.