Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » Web Services » Error Login resources unavailable: CM Server Closed Connection   XML
 
Author Message
TarunJindal



Joined: 12/12/2013 12:09:10
Messages: 2
Offline

Hi,

I am using java client to connect to SMS service. I open a session and maintain it for a batch of change requests.
What I see is after 2 successful processing of requests for the session - I start seeing this in error log

--> SOAP message: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><S
OAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>Connection Failed: Login resources unavailable: CM Server Closed Co
nnection
</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
---> FAULT: Connection Failed: Login resources unavailable: CM Server Closed Connection

---> FAULT CODE: SOAP-ENV:Server
javax.xml.ws.WebServiceException: java.lang.RuntimeException: [SOAP-ENV:Fault: null]
at com.sun.xml.ws.handler.ClientSOAPHandlerTube.callHandlersOnResponse(ClientSOAPHandlerTube.java:173)
at com.sun.xml.ws.handler.HandlerTube.processResponse(HandlerTube.java:162)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:877)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
at com.sun.xml.ws.client.Stub.process(Stub.java:272)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.


After this none of the requests go through.

In my code I release the session using following if I see null result from previous request and wait for 10 seconds before attempting new session.

public void releaseSession() {

try {

responseSID = SIDHandler.getSID();
logger.warn(" ServiceRequest::releaseSession before close responseSID " + responseSID);
ReturnType returnType = port.release(null);
Result returnResult = returnType.getReturn();
logger.warn(" ServiceRequest::releaseSession returnResult " + returnResult);
logger.warn(" ServiceRequest::releaseSession returnResult.getMessageText(); " + returnResult.getMessageText());
logger.warn(" ServiceRequest::releaseSession returnResult.getResultCode(); " + returnResult.getResultCode());
responseSID = SIDHandler.getSID();
logger.warn(" ServiceRequest::releaseSession after close responseSID " + responseSID);

}


This very puzzling - I see it working end to end for 2 requests and then it starts failing - any idea where the issue may be ?


Thanks,
Tarun

TarunJindal



Joined: 12/12/2013 12:09:10
Messages: 2
Offline

I see that sessionId returned is not the same when I execute the requests over a single connection.
 
 
Go to: