GetNode login failure

During peak loads some requests for GetNode return with error Core.LoginFailed even though user has logged in 1 second prior and token was returned. It only happens randomly during peak hours 8 -5 Monday to Friday. We even turned off facets but error still occurs. We are on CS10 update 12 with les-services hosted on Tomcat 7 and recently on Tomcat 6 (same error).

The behaviour is:

1) login -- success

2) getNote 1 second later-- error

Nothing in tread logs.

From les-services.log (No information other than status code):

2014-11-14 11:51:07,582 WARN [http-apr-8090-exec-10] Livelink error occurred

2014-11-14 11:51:07,582 WARN [http-apr-8090-exec-10] Status: -2147482645

2014-11-14 11:51:07,582 WARN [http-apr-8090-exec-10] Error Code:

2014-11-14 11:51:07,583 WARN [http-apr-8090-exec-10] Error Message:

2014-11-14 11:51:07,583 WARN [http-apr-8090-exec-10] ApiError:

1 --- SOAP LOGIN REQUEST:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:Core.service.livelink.opentext.com">

<soapenv:Header/>

<soapenv:Body>

<urn:AuthenticateUser>

<urn:userName>ServiceAccount</urn:userName>

<urn:userPassword>*******</urn:userPassword>

</urn:AuthenticateUser>

</soapenv:Body>

</soapenv:Envelope>

2 -- LOGIN RESPONSE:

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">

<S:Body>

<AuthenticateUserResult>uPawWIIHYAOQp0oMBhJmsKL75Ulo%2BtAGSMZb3DsoYSFX9fU%2Fpb6j6tmn0RrTR3KX</AuthenticateUserResult>

</AuthenticateUserResponse>

</S:Body>

</S:Envelope>

3 -- GETNODE REQUEST

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:DocMan.service.livelink.opentext.com">

<soapenv:Header>

<urn:OTAuthentication>

<urn:AuthenticationToken>uPawWIIHYAOQp0oMBhJmsKL75Ulo%2BtAGSMZb3DsoYSFX9fU%2Fpb6j6tmn0RrTR3KX</urn:AuthenticationToken>

</urn:OTAuthentication>

</soapenv:Header>

<soapenv:Body>

<urn1:GetNode>

<urn1:ID>14300444</urn1:ID>

</urn1:GetNode>

</soapenv:Body>

</soapenv:Envelope>

4- GET NODE RESPONSE

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">

<S:Header>

<AuthenticationToken>uPawWIIHYAOQp0oMBhJmsKL75Ulo%2BtAGSMZb3DsoYSFX9fU%2Fpb6j6tmn0RrTR3KX</AuthenticationToken>

</OTAuthentication>

</S:Header>

<S:Body>

<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">

<faultcode xmlns:ns0="urn:Core.service.livelink.opentext.com">ns0:Core.LoginFailed</faultcode>

<faultstring>javax.xml.ws.soap.SOAPFaultException</faultstring>

<ns2:exception class="javax.xml.ws.soap.SOAPFaultException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">

<ns2:stackTrace>

<ns2:frame class="com.opentext.livelink.service.core.ExceptionUtil" file="ExceptionUtil.java" line="162" method="throwSOAPFaultException"/>

<ns2:frame class="com.opentext.livelink.service.docman.DocumentManagement_JAXWS" file="DocumentManagement_JAXWS.java" line="476" method="getNode"/>

<ns2:frame class="sun.reflect.GeneratedMethodAccessor55" line="unknown" method="invoke"/>

<ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" line="unknown" method="invoke"/>

<ns2:frame class="java.lang.reflect.Method" line="unknown" method="invoke"/>

<ns2:frame class="com.sun.xml.ws.api.server.InstanceResolver$1" file="InstanceResolver.java" line="246" method="invoke"/>

<ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="146" method="invoke"/>

<ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="257" method="invoke"/>

<ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>

<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun"/>

<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun"/>

<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun"/>

<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync"/>

<ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process"/>

Find more posts tagged with

Comments

eLink User

In where you indicate 4 you have a token that livelink does not like which could be basically because of how cookies are setup in different instances of livelink .

If the cookie was left at default then livelink will only trust the combination of the ip address of the client.It is all explained in the server setup.

If a load balancer was involved you could make for webservices sticky algorithm which would send all the requests to one box(instance) taking care of

hitting it and with some mechanism of thread saturation prevention.I would also make the webservices instances completely isolated from web traffic and try to

put its cookie mechanism not dependent on client ip(slightly insecure but worth a try).If OTDS was doing the redirect and setting the cookie you would
somehow have to appear to livelink as coming from the same client.Since livelink was returning the error that does mean oscript code worked and it did not like the cookie.

Have a look at the cookie settings its timeouts etc that could help you in this.

..Appu

I wonder how one could debug livelink if Fiddler, Wireshark and Softerra LDAP browser was not invented and not free

On Fri, Nov 14, 2014 at 9:23 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

GetNode login failure Posted bykevin.cartwright@icbc.com (Cartwright, Kevin)On 11/14/2014 10:19 PM

During peak loads some requests for GetNode return with error Core.LoginFailed even though user has logged in 1 second prior and token was returned. It only happens randomly during peak hours 8 -5 Monday to Friday. We even turned off facets but error still occurs. We are on CS10 update 12 with les-services hosted on Tomcat 7 and recently on Tomcat 6 (same error).The behaviour is:1) login -- success2) getNote 1 second later-- errorNothing in tread logs.From les-services.log (No information other than status code):2014-11-14 11:51:07,582 WARN [http-apr-8090-exec-10] Livelink error occurred2014-11-14 11:51:07,582 WARN [http-apr-8090-exec-10] Status: -21474826452014-11-14 11:51:07,582 WARN [http-apr-8090-exec-10] Error Code:2014-11-14 11:51:07,583 WARN [http-apr-8090-exec-10] Error Message:2014-11-14 11:51:07,583 WARN [http-apr-8090-exec-10] ApiError: 1 --- SOAP LOGIN REQUEST:<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:Core.service.livelink.opentext.com"> <soapenv:Header/> <soapenv:Body> <urn:AuthenticateUser> <urn:userName>ServiceAccount</urn:userName> <urn:userPassword>*******</urn:userPassword> </urn:AuthenticateUser> </soapenv:Body></soapenv:Envelope> 2 -- LOGIN RESPONSE:<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Body> <AuthenticateUserResponse xmlns="urn:Core.service.livelink.opentext.com"> <AuthenticateUserResult>uPawWIIHYAOQp0oMBhJmsKL75Ulo%2BtAGSMZb3DsoYSFX9fU%2Fpb6j6tmn0RrTR3KX</AuthenticateUserResult> </AuthenticateUserResponse> </S:Body></S:Envelope>3 -- GETNODE REQUEST<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:api.ecm.opentext.com" xmlns:urn1="urn:DocMan.service.livelink.opentext.com"> <soapenv:Header> <urn:OTAuthentication> <urn:AuthenticationToken>uPawWIIHYAOQp0oMBhJmsKL75Ulo%2BtAGSMZb3DsoYSFX9fU%2Fpb6j6tmn0RrTR3KX</urn:AuthenticationToken> </urn:OTAuthentication> </soapenv:Header> <soapenv:Body> <urn1:GetNode> <urn1:ID>14300444</urn1:ID> </urn1:GetNode> </soapenv:Body></soapenv:Envelope>4- GET NODE RESPONSE<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Header> <OTAuthentication xmlns="urn:api.ecm.opentext.com"> <AuthenticationToken>uPawWIIHYAOQp0oMBhJmsKL75Ulo%2BtAGSMZb3DsoYSFX9fU%2Fpb6j6tmn0RrTR3KX</AuthenticationToken> </OTAuthentication> </S:Header> <S:Body> <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"> <faultcode xmlns:ns0="urn:Core.service.livelink.opentext.com">ns0:Core.LoginFailed</faultcode> <faultstring>javax.xml.ws.soap.SOAPFaultException</faultstring> <detail> <ns2:exception class="javax.xml.ws.soap.SOAPFaultException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/"> <ns2:stackTrace> <ns2:frame class="com.opentext.livelink.service.core.ExceptionUtil" file="ExceptionUtil.java" line="162" method="throwSOAPFaultException"/> <ns2:frame class="com.opentext.livelink.service.docman.DocumentManagement_JAXWS" file="DocumentManagement_JAXWS.java" line="476" method="getNode"/> <ns2:frame class="sun.reflect.GeneratedMethodAccessor55" line="unknown" method="invoke"/> <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" line="unknown" method="invoke"/> <ns2:frame class="java.lang.reflect.Method" line="unknown" method="invoke"/> <ns2:frame class="com.sun.xml.ws.api.server.InstanceResolver$1" file="InstanceResolver.java" line="246" method="invoke"/> <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="146" method="invoke"/> <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="257" method="invoke"/> <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/> <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun"/> <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun"/> <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun"/> <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync"/> <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process"/>
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center

Kevin_Cartwright

We had a produciton incident where our second front end server was down for 1 hour and all load balanced traffic was directed to one server. We still saw the WARN messages during that time.

When we install Tomcat (6 or 7) we use the out of the box settings, and then install the les-services.war web services.

I will open a support ticket.

Kevin_Cartwright

Solved. Under Admin pages "Configure Security Parameters" ?func=admin.securityvars

Set Cookie Authentication Information: Client IP Address TO (255.255.255.0) FROM (255.255.255.255) Compare Entire IP Address)

Reason: The leading application is load balanced hosted on multiple servers. Requests for authentication can come from server #1 and the getNode request 1 second later can come from server #2 resulting in the authentication token passed in being "invalid" . Changing the IP to ignore the last group of IP numbers solved our issue.

We are going to test changing the load balancer to "sticky" put the IP setting back and test. Currently all traffic is internal.

Kevin