While creating connection to MDM repository using MDM JAVA API

I am getting the following error message:
Unexpected field type 28
I am able to debug that this error message is being displayed after executing the following line of code:
/** Get the Repository schema */
GetRepositorySchemaCommand repositroySchemaCommand =
new GetRepositorySchemaCommand(simpleConnection);
repositroySchemaCommand.setSession(repositorySession);
repositroySchemaCommand.execute();
Now can anyone please explain how to resolve this error?
Thanks in Advance.
Rajat

public void getRepositoryConnection(
          java.lang.String hostName,
          java.lang.String repositoryName,
          java.lang.String userId,
          java.lang.String passWord) {
          //@@begin getRepositoryConnection()
          try {
               if (simpleConnection == null) {
                    simpleConnection =
                         SimpleConnectionFactory.getInstance(hostName);
                    // Establish TCP Connection to the server
                    if (simpleConnection != null) {
                         //                              wdComponentAPI.getMessageManager().reportSuccess("Got Connected");
                         /** Establish a repository session with the respository */
                         //Set the region properties
                         RegionProperties dataRegion = new RegionProperties();
                         /** Set region code for the session */
                         dataRegion.setRegionCode("engUSA");
                         /** Set the locale on data region */
                         dataRegion.setLocale(new Locale("en", "US"));
                         /** Set the name of data region */
                         dataRegion.setName("US");
                         // Createa repository identifier
                         RepositoryIdentifier repositoryID =
                              new RepositoryIdentifier(
                                   repositoryName,
                                   hostName,
                                   DBMSType.MS_SQL);
                         /** Create the User Session */
                         CreateUserSessionCommand createUserSessionCommand =
                              new CreateUserSessionCommand(simpleConnection);
                         /** Set the repository identifier (mandatory)*/
                         createUserSessionCommand.setRepositoryIdentifier(
                              repositoryID);
                         /** Set the region properties for the session (mandatory) */
                         createUserSessionCommand.setDataRegion(dataRegion);
                         createUserSessionCommand.execute();
                         /** Get the session identifier */
                         this.userSession =
                              createUserSessionCommand.getUserSession();
                         AuthenticateUserSessionCommand authenticateUserSessionCommand =
                              new AuthenticateUserSessionCommand(simpleConnection);
                         /** Set session identifier (mandatory)*/
                         authenticateUserSessionCommand.setSession(userSession);
                         /** Set id of repository user(mandatory) */
                         authenticateUserSessionCommand.setUserName(userId);
                         /** Set password (mandatory)*/
                         authenticateUserSessionCommand.setUserPassword(passWord);
                         /** Establish the session */
                         authenticateUserSessionCommand.execute();
                         SetUnicodeNormalizationCommand unicodeNormalizationCommand =
                              new SetUnicodeNormalizationCommand(simpleConnection);
                         unicodeNormalizationCommand.setSession(userSession);
                         unicodeNormalizationCommand.setNormalizationType(
                              SetUnicodeNormalizationCommand.NORMALIZATION_COMPOSED);
                         unicodeNormalizationCommand.execute();
                         CreateRepositorySessionCommand repositorySessionCommand =
                              new CreateRepositorySessionCommand(simpleConnection);
                         /** Set the repository identifier */
                         repositorySessionCommand.setRepositoryIdentifier(
                              repositoryID);
                         /** Obtain repository session */
                         repositorySessionCommand.execute();
                         /** Store the session id into the variable repositorySession */
                         this.repositorySession =
                              repositorySessionCommand.getRepositorySession();
                         /** Authenticate the users session */
                         AuthenticateRepositorySessionCommand authenticatedRepositorySession =
                              new AuthenticateRepositorySessionCommand(simpleConnection);
                         /** set the session id */
                         authenticatedRepositorySession.setSession(
                              repositorySession);
                         /** set id of the repository user */
                         authenticatedRepositorySession.setUserName(userId);
                         /** set password */
                         authenticatedRepositorySession.setUserPassword(passWord);
                         authenticatedRepositorySession.execute();
                         /** Get the Repository schema */
                         GetRepositorySchemaCommand repositroySchemaCommand =
                              new GetRepositorySchemaCommand(simpleConnection);
                         repositroySchemaCommand.setSession(repositorySession);
                         repositroySchemaCommand.execute();
                         this.schema = repositroySchemaCommand.getRepositorySchema();
          } catch (Exception e) {
               wdComponentAPI.getMessageManager().reportException(
                    e.getMessage(),
                    true);
          //@@end

Similar Messages

  • Issue while creating connection pool in weblogic using SERVICE NAME

    Found two issues while creating connection pool in weblogic using SERVICE NAME
    1. While running apps from jdeveloper using xxx-jdbc.xml
    weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Io exception: The Network Adapter could not establish the connection
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
    2. Configuriing the jndi in Weblogic server
    weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
    ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
    The Connection descriptor used by the client was:
    localhost:1521:SERVICENAME
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
    Problem
    database url is generated based on SID
    eg: jdbc:oracle:thin:@localhost:1521:SID
    Solution
    (generate seperate url for SERVICE NAME)
    jdbc:oracle:thin:@localhost:1521/SERVICENAME
    ------------------------

    It is so clear: host not found error for network connection and the other SID servcie name not found means your oracle instance name is not up. check with srvctl status for given servcie name or node, else check CRS_Stat -t if you are using RAC.

  • Error while create or mount a repository in MDM

    Hi,
    after installing SAP MDM 5.5 SP06 and SAP MaxDB 7.6.00.35 on the same hardware (Laptop with Windows NT Client) I started MDM Console, mounted the MDM Server and then started the MDM Server (green arrow).
    When I try to add a repository (unarchiving an existing or creating a new one) I enter the data (DBMS eerver, User-ID and password) and then I always get the same error message:
    "Error Getting DBMS Settings" --> "Error initializing database engine".
    Any ideas where the problem is?
    thanks and regards
    Erich

    Hi Jochen ,
    Kindly refer the below thread on a similar issue:
    MDM 5.5 SP6 & MaxDB
    Also have a glance on the following SAP NOTE:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_mdm/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31323936313839%7d
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Uploading images whit thumbnail to MDM repository using Java API

    Hello,
    can someone tell me how to upload images whit thumbnail to MDM repository using Java API?
    i get following message using setHasThumbnail(true):
    com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: Ungültiger Wert für Parameter
    thanks

    You can upload images to MDM via the API, but the only way to create thumbnails is via the MDM Data Manager application which uses some embedded libraries to do the work.
    Walter

  • Using Ant task wlserver/wlconfig: Received exception while creating connection for pool.

    Hi,
    I am using ant tasks wlserver and wlconfig to configure my weblogic server. while creating a connection pool as shown below
    <target name="jdbcinfo">
    <wlconfig password="weblogic"
    username="weblogic"
    url="${url}"
    <query domain="mydomain" type="Server"
    name="myserver" property="serverbean"
    />
    <create type="JDBCConnectionPool"
    name="jdbcpoolA"
    property="jdbcPoolProp">
    <set value="false"
    attribute="ShrinkingEnabled"
    <set value
    attribute="
    <set value="${serverbean}"
    attribute="Targets"/>
    The JDBCConnectionPool is created as long as I don't specified the attribute "Targets"
    Once I add the target I get the following error
    <JDBC> <BEA-001129> <Received exception while creating connection for pool "poolname" invalid arguments in call>
    Please any help will be greatly appreciated.
    Thanks

    In your applicaion module configurations check if you are using 'JDBC URL' or 'JDBC DataSource'. You should use JDBC DataSource. Then make sure that your deployment descriptor (menu 'Application->Application Properties->Deployment) has the 'Auto Generate ...' checkbox set.
    Timo

  • How to create a taxonomy using MDM 5.5 SP05 JAVA API?

    Hi ALL,
    I have a requirement in which i have to create a taxonomy using MDM 5.5 SP05 JAVA API.
    Can anyone tell me how that functionality can be achieved?
    Thanks in Advance.
    Rajat.

    HI, Rajat.
    For exposing hierarchy in WD view you need to use node with recursive children in the context and Tree/TreeNodeType UI elements in view layout.
    For load hierarchy records you have to use RetrieveLimitedHierTreeCommand. You can load whole hierarchy (as I know, SP05 API have a bug - only first 1000 record can be loaded) or load hierarchy nodes on demand (using OnLoadChildren action of TreeNodeType element).
    Refer to this example of loading child records:
    // Context structure:
    // Tree (model node, model class built from com.sap.mdm.data.Record interface)
    //  |-- Children (recursive child node repeating Tree node)
    //  |-- DisplayValue (string value attribute, TreeNodeType's text property bound here)
    //  |-- HasChildren (boolean value attribute, TreeNodeType's hasChildren property bound here)
    // parentElem is element of node Tree or Children for which we must load child records, null for first level of hierarchy
    private void fillNodeWithChildren(IPrivateHierarchySelectView.ITreeElement parentElem) {
         // Determining RecordId of parent record and context node to which child records belong
         RecordId parentRecordId = null;
         if (parentElem != null) parentRecordId = parentElem.modelObject().getId();
         IPrivateHierarchySelectView.ITreeNode parentNode =
              parentElem == null
                   ? wdContext.nodeTree()
                   : parentElem.nodeChildren();
         // Loading children with RetrieveLimitedHierTreeCommand
         try {
              RetrieveLimitedHierTreeCommand retTreeCmd = new RetrieveLimitedHierTreeCommand(...); // use suitable constructor
              if (parentRecordId != null) retTreeCmd.setRootNode(parentRecordId);
              retTreeCmd.setResultDefinition(...); // don't forget set ResultDefinition
              retTreeCmd.execute();
              HierNode subRoot = retTreeCmd.getTree()
              parentNode.invalidate();
              // Processing loaded child records - add elements into parentNode
              if (subRoot == null) return;
              IPrivateHierarchySelectView.ITreeElement childElem;
              HierNode childRecord;
              HierNode[] children = subRoot.getChildren();
              int count = children == null ? 0 : children.length;
              for (int i = 0; i < count; i++) {
                   childRecord = children<i>;
                   childElem = parentNode.createTreeElement(childRecord);
                   childElem.setDisplayValue(childRecord.getDisplayValue());
                   childElem.setHasChildren(!childRecord.isLeaf());
                   parentNode.addElement(childElem);
              if (parentElem != null) parentElem.setHasChildren(count > 0);
         } catch (/* Some MDM Exceptions */) {}
    Don't forget call fillNodeWithChildren(null) in wdDoInit for load first level of hierarchy.

  • How to use SessionManager (MDM 5.5 SP06 JAVA API 2) with TrustedConnection

    Hello MDM 5.5 SP06 JAVA API Experts,
    Is it possible to Use the SessionManager in conjunction with TrustedConnections ? The trusted connection is setup properly (adding the client IP to the allow.ip file on MDM-Server).
    I tried a lot but I didn't succeed with the new JAVA API 2 SessionManager functionality.
    I'm initializing a UserSessionContext object and set the field for trusted connections to true.
    Later I request an instance of SessionManager and call the createSession() method.
    Although I've set the trustedConnection (=true) field of UserSessionContext, I get an exception, if the password is not set correctly. Due to my understanding, the password should be ignored if the UserSessionContext --> trustedConnection field is set to true. Is this a bug or am I missing any important step ?
    I have also used several constructors of UserSessionContext but no chance.
    Could anyone use the SessionManager with trusted Connections ?
    Any help would be greatly appriciated.
    Best regards.
          public static void main(String[] args)
            Settings settings = new Settings();
            RepositoryIdentifier repId = new RepositoryIdentifier(settings.repository,
                                                                  settings.dbServer,
                                                                  settings.dbmsType);
            //Create a UserSessionContext
            //UserSessionContext sessionContext = new UserSessionContext("<servername>", "<repositoryName>", "<userName>");
            UserSessionContext sessionContext = new UserSessionContext( "<servername>", repId, "English [US]", "<userName>");
            sessionContext.setConnectionType(ConnectionTypes.LOCAL_POOL_CONNECTION);
            sessionContext.setRegionLocale(Locale.US);
            sessionContext.setTrustedConnection(true);
            //Get an instance of SessionManager
            SessionManager sessionManager = SessionManager.getInstance();
            //Create user session
            String userSession =
            sessionManager.createSession(sessionContext, SessionTypes.USER_SESSION_TYPE, "<any pwd !!!>");
            System.out.println("Created user SessionID: " + userSession);

    Hello Jitesh Talreja,
    thanks for your reply and hint. The trusted connection configuration on MDM server is already setup correctly.
    My concrete problem is to establish a trusted connection using the SessionManager.
    If I use the TrustedUserSessionCommand, everything works.
            CreateUserSessionCommand createUserSessionCommand = new CreateUserSessionCommand(connection);
            createUserSessionCommand.setRepositoryIdentifier(repId);
            createUserSessionCommand.setDataRegion(dataRegion);
            createUserSessionCommand.execute();
            session = createUserSessionCommand.getUserSession();
            state = STATE_SESSION_ESTABLISHED;
            try
                TrustedUserSessionCommand tuscTrustedUser = new TrustedUserSessionCommand(connection);
                tuscTrustedUser.setUserName(userName);
                tuscTrustedUser.setSession(createUserSessionCommand.getUserSession());
                tuscTrustedUser.execute();
                session = tuscTrustedUser.getSession();
             catch (com.sap.mdm.commands.CommandException e)
                /* In Case the Connection is not Trusted */
                System.out.println("Could not established trusted connection!!!");
                e.printStackTrace();
    But I want to make use of the SessionManager advantages see [MDM Java API Guide|http://help.sap.com/saphelp_mdm550/helpdata/en/47/9f23e5cf9e3c5ce10000000a421937/frameset.htm] -> API Structure and Basic Concepts

  • Error Message while creating connection pool

    Hi all,
    I got the following error message while creating connection pool for the
    SQL Server thru the Application Server Admin Console.
    The message is,
    An error has occured.
    Operation 'create.Jdbc.ConnectionPool' failed in 'resources' Config Mbean. Target exception message :
    JdbcConnectionPool Already Exists: cannot add duplicate.
    But the connection pool for the SQL Server was not there in the list.
    What may be the possible reason for this error.
    i was trying to deploy a BMP entiy bean using the Sun Application Server.
    Prior deploying i just tried to create connection pool and test the connection using the Admin Console
    Please help me by providing a solution.

    Kriti Sundar Mazumder wrote:
    Hi
    I am getting an following error message, while creating database connection pool
    in weblogic 7.
    "<Jun 18, 2004 4:52:36 AM CDT> <Error> <JDBC> <001060> <Cannot startup connection
    pool "MyJDBCConnectionPool" java.sql.SQLException: [IBM][JDBC Driver] CLI0647E
    Error allocating DB2 environment handle, rc=-1.>"
    Can anyone help me out in this regard
    Regards
    KritiHi. I am no expert, but it sounds like a problem with the privileges the user
    has... The best thing is to step back to a simpler environment. Can you try
    connecting to DB2 with a simple program like utils.dbping? Please look at our
    driver docs for the DB2 driver, because there are several variations in connect
    properties depending on the type of DB2 you are connecting to...
    Joe

  • Why to use the Java API in MDM

    Hi Experts,
    I am new to the MDM.
    We are having the requirement of inetration between Portal and MDM.Can u please tell me when to use the following coponents like the scenorio's.
    Why to install the MDM Business packages in Portal?
    why to use the JAVA API.
    Please give me the complete information.
    Regards

    Hi Vijay,
    Standard Business Package is use to provide interaction between MDM Server and the Portal. It consists of MDM iViews like Item Detail iView (allows to create,edit and delete the records) , Resultset iView (Displays the records, allows to add the records in workflows etc), Search iViews (for searching)i.e. Data Manager functionality.
    Java API are used when you need some functionality that standard MDM iViews dont have.MDM Java API consists of set of classes and interfaces with the help of which customization can be done.
    Regards,
    Jitesh Talreja

  • Connecting to XML Repository Using HTTPS?

    Is it possible to use HTTPS to connect to the repository using WebDAV or secure FTP? I can't run a web server using HTTP.
    Thanks,
    Bill

    The following may help... However please note at the moment we have not certified XML DB HTTP with a HTTPS /SSL / TCPS connection. Nor have I tried this myself..
    Please follow the following steps to configure HTTPS:
    1.     Make sure Oracle Advance Security is installed
    a.     It installs by default for Enterprise Edition
    2.     Create and configure a Wallet
    a.     Refer to Oracle Advance Security Administrator�s Guide, Chapter 17 � Using Oracle Wallet Manager, for creating the Wallet
    i.     From $ORACLE_HOME/bin run owm
    b.     Import the trusted certificate in the Wallet
    3.     Configure SSL on the Server
    a.     Refer to Oracle Advance Security Administrator�s Guide, Chapter 7 � Configuring Secure Sockets Layer Authentication
    b.     Follow the steps in Task 3: Configure SSL on the Server, in the Enabling SSL section
    4.     Edit the xdbconfig.xml configuration file to specify http-protocol as tcps
    a.     Locate the <httpconfig> section
    b.     Change the value of <http-protocol> tag from tcp to tcps
    5.     Edit the Database initialization file to start a TCPS dispatcher
    6.     Restart the Database

  • Save Query - An error occurred while creating connection strings for the query

    A workbook trying to edit and reload I get the following error "Save Query - An error occurred while creating connection strings for the query" No Power Pivot data model or anything.

    I am getting the same error when editing a Power Query in an Excel spreadsheet. It happens when I change a Group By step to do a Sum instead of Count Rows.

  • HT2534 i am not getting "none" option while creating an apple id without using credit card.

    i am not getting "none" option while creating an apple id without using credit card.

    To get the none option, sign out of anything apple you're signed into. Go to the app store and try to download a free app, any free app. Instead of signing in, take the option to to make a new apple ID. Then go through the steps to make the ID and you'll see the 'none' option.

  • Connection to system REPOSITORY using application REPOSITORY lost.

    Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://<host>:<port>/rep/query/int?container=any" with user "USER01". Response code is 401, response message is "Unauthorized".
    USER01 is locked, but i want to change this conection user to PIDIRUSER.
    Do you know where this connection user can be changed?

    Hello there.
    Please check the note below according to your system:
    #999962 - PI 7.10: Change passwords of PI service users
    #936093 - XI 7.0: Changing the passwords of XI service users
    #721548 - XI 3.0: Changing the passwords of the XI service users
    Regards,
    Caio Cagnani

  • Connection to system REPOSITORY using application REPOSITORY lost. Detailed

    Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://ECC:50000/rep/query/int?container=any" with user "PIDIRUSER". Response code is 401, response message is "Unauthorized"

    This problem occurs when user is locked. Unlock yhe user in su01.
    unable to access repository / SLD
    See this guide may help you.
    https://www.dw.dhhs.state.nc.us/wi/OnlineGuides/EN/ErrorsEN.pdf
    Rewards if helpful.
    BR,
    Alok

  • Error while using LiveCycle java APIs with Http servlets:"Remote EJBObject lookup failed for ejb/Inv

    Hi all,
    When i try to run more than one servelt of the Quick Start samples that using Livecycle Java APIs and i get an error of "Remote EJBObject lookup failed for ejb/Invocation provider" from any servelt i run.
    I try some Quick samples which is not servelts (java class) and it works fine, which makes me sure that my connection properties is true.
    Environment:
    The LiveCycle is based on "Websphere v6.1", and i use "Eclipse Platform
    Version: 3.4.1".
    i install "tomcat 5.5.17" to test the servelts in developing time through Eclipse.(only for test in developing time not for deploy on )
    The Jars i added in the classpath:
    adobe-forms-client.jar
    adobe-livecycle-client.jar
    adobe-usermanager-client.jar
    adobe-utilities.jar
    ejb.jar
    j2ee.jar
    ecutlis.jar
    com.ibm.ws.admin.client_6.1.0.jar
    com.ibm.ws.webservices.thinclient_6.1.0.jar
    server.jar
    utlis.jar
    wsexception.jar
    My code is :
    Properties ConnectionProps = new Properties();
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "iiop://localhost:2809");
    ConnectionProps.setProperty ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_ EJB_PROTOCOL);
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE,ServiceClientFa ctoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "Administrator");
    ConnectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
    ConnectionProps.setProperty("java.naming.factory.initial", "com.ibm.ws.naming.util.WsnInitCtxFactory");
    //Create a ServiceClientFactory object
    ServiceClientFactory myFactory = ServiceClientFactory.createInstance(ConnectionProps);
    //Create a FormsServiceClient object
    FormsServiceClient formsClient = new FormsServiceClient(myFactory);
    //Get Form data to pass to the processFormSubmission method
    Document formData = new Document(req.getInputStream());
    //Set run-time options
    RenderOptionsSpec processSpec = new RenderOptionsSpec();
    processSpec.setLocale("en_US");
    //Invoke the processFormSubmission method
    FormsResult formOut = formsClient.processFormSubmission(formData,"CONTENT_TYPE=application/pdf&CONTENT_TYPE=app lication/vnd.adobe.xdp+xml&CONTENT_TYPE=text/xml", "",processSpec);
    List fileAttachments = formOut.getAttachments();
    Iterator iter = fileAttachments.iterator();
    int i = 0 ;
    while (iter.hasNext()) {
    Document file = (Document)iter.next();
    file.copyToFile(new File("C:\\Adobe\\tempFile"+i+".jp i++;
    short processState = formOut.getAction();
    ...... (To the end of the sample)
    My Error was:
    com.adobe.livecycle.formsservice.exception.ProcessFormSubmissionException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider
    at com.adobe.livecycle.formsservice.client.FormsServiceClient.processFormSubmission(FormsSer viceClient.java:416)
    at HandleData.doPost(HandleData.java:62)
    at HandleData.doGet(HandleData.java:31)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
    a

    I assume here that your application is deployed on a different physical machine of where LCES is deployed and running.
    Do the following test:
    - Say that LCES is deployed on machine1 and your application is deployed on machine2. Ping machine1 from machine2 and note the ip address.
    - Ping machine1 from machine1 and note the ip address.
    The two pings should match.
    - Ping machine2 from machine1 and note the ip address.
    - Ping machine2 from machine2 and note the ip address.
    The two pings should match.
    Usually this kind of error would happen if your servers have internal and external ip addresses.

Maybe you are looking for