on 12-07-2012 3:58 PM
Hello,
We have downloaded the app CFFS, We are having some problems when We try to get the company codes which return large number of customers. Company code 1100 is one such example; in QA it returns a list of 8120 customers
The FINFACTSheetservice name is np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/CustomerCollection?$filter=CompanyCode eq'1100'.
in the CFFS the following error:
Message=[ERROR]SUPJsonException:expected string, found 124/Location:-[SUPRequest startSynchronous] + 1183
Message=[ERROR]500:Internal server Error/Location:-{SUPRequest startSynchronous]+1208
If the request is timing out can you try out the below code snippet and see if it helps.
The code is as follows:
id<SDMRequesting> request = [SDMRequestBuilder requestWithURL:[NSURL URLWithString:@"<URL>"]];
[request setRequestMethod:@"<Type of Request>"];
[request addRequestHeader:@"<Different Relevant Headers>" value:@"<Value>];
[request setTimeOutSeconds:100]; // Increase this as required
[request startSynchronous];
Hope this is what you were looking for.
Best Regards,
Sujith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fiston,
Please find my analysis below.
Overall Analysis:
The error you are getting is because the query for the service document is returning null. Hence when the parser tries to parse, it does not have anything to parse. Hence, it throws the error.
The error 500 means that the server is down.
Internal Working:
So my initial analysis on the error is that. The server is down hence your request does not return anything(Hence, the 500 error). This returns a nil value back. When the parser tries to parse the nil value it throws SUPJsonException:expected string exception.
Suggestion:
What i would suggest when you face a 500 error is, that you try the same url with the REST client to see if you are able to retrieve any data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kalanda,
Good news that you are getting 200 Ok in browser. I guess the script error is from browser and nothing to do with response recieved.
What I am suspecting is the URL which is constructed in the app when you fire the request from application. There is a possibility to get Erro 500 when your URL is not correct.
To check that same, you can enable the logs and fire a request from application. The URL fired gets recorded in the logs. You can compare that URL with the one you run in browser.
Follow the below steps to enable logs
1. Domain>>DomainName>>Log>>Settings>>New >> Enter a name
2.Select "Application Connection" and chose your User
3. Select "payload" and chose "request response"
4. Select "Enable after creation"
Save the settings.
Change the log level at Server>>Logs>>Unwired Server>>Settings>>Proxy>>Debug.
Fire a new request from application. Check the logs under Server>>Logs>>Unwired Server>>general.
Regards
Rohith
Hi Kalanda,
Good news that you are getting 200 Ok in browser. I guess the script error is from browser and nothing to do with response recieved.
What I am suspecting is the URL which is constructed in the app when you fire the request from application. There is a possibility to get Erro 500 when your URL is not correct.
To check that same, you can enable the logs and fire a request from application. The URL fired gets recorded in the logs. You can compare that URL with the one you run in browser.
Follow the below steps to enable logs
1. Domain>>DomainName>>Log>>Settings>>New >> Enter a name
2.Select "Application Connection" and chose your User
3. Select "payload" and chose "request response"
4. Select "Enable after creation"
Save the settings.
Change the log level at Server>>Logs>>Unwired Server>>Settings>>Proxy>>Debug.
Fire a new request from application. Check the logs under Server>>Logs>>Unwired Server>>general.
Regards
Rohith
Hello ROhith,
i have a question
We have no issues with company codes
which return smaller amount of data.
the issue is for larger company code
like (1100) which return more data.
if the URL construction in the APP is the
probable cause, then how do wen dont see the issue for the company codes which
return smaller
amount data?
Hi Kalanda,
Thats strange. Then we cannot suspect any issue with URL. However the only way I know to troubleshoot is thorugh server logs.
Can you please enable logs as I mentined in my previous post and try a fresh request. Also share the logs. I am hoping that logs might shread some light on whats happenning internally.
Regards
Rohith
Hello Rohith,
I will do that and share the logs with You. just FYI I noticed the following errors:
onsolidated database server or ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Invalid user ID or password (ODBC State = 28000, Native error code = -103)
E. 2012-09-29 02:00:00. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server connection
limit exceeded (ODBC State = 08004, Native error code = -102)E.
E. 2012-09-29
02:00:09. <Main> [-10002] Consolidated database server or ODBC error:
ODBC: [Sybase][ODBC Driver][SQL Anywhere]Connection was terminated (ODBC State =
HY000, Native error code = -308)
Caused by: com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -196: Index
'_BUSINESS_PK_INDEX_d2_timeentry_2_0_logrec_63809' for table
'd2_timeentry_2_0_logrec_63809' would not be unique
I dont know if this is useful information
Hello Rohith,
As You requested, Here is the LOG if You have trouble reading it, I also attached a txt copy of it.:
2012-12-14 13:58:49.649 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel
2012-12-14 13:58:49.646 DEBUG PROXY Thread-747 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp
2012-12-14 13:58:49.644 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished firing the request to GW-----------
2012-12-14 13:58:49.644 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream
2012-12-14 13:58:49.643 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----
2012-12-14 13:58:49.642 ERROR PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]IOException caught in fire request :while connecting to the URL sent:
at java.lang.Thread.run(Thread.java:662)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:310)
at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:798)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl_DJC.$invoke(InboundMoIIOPTransportImpl_DJC.java:100)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl.execute(InboundMoIIOPTransportImpl.java:67)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl.process(InboundMoIIOPTransportImpl.java:118)
at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:101)
at com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler.execute(GatewayConnectorHandler.java:118)
at com.sybase.suplite.gwc.req.handler.GWProxy.handle(GWProxy.java:286)
at com.sybase.suplite.gwc.req.handler.GWProxy.fireRequest(GWProxy.java:496)
at shaded.org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at shaded.org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at shaded.org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
at shaded.org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at shaded.org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at shaded.org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at shaded.org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at shaded.org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
at shaded.org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at shaded.org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at shaded.org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketTimeoutException: Read timed out
2012-12-14 13:57:49.140 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Before Execute-----------
2012-12-14 13:57:49.140 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP: Firing the request to the Gateway
2012-12-14 13:57:49.140 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----Host request header set is ----np2apps761v.corp.halliburton.com:8000
2012-12-14 13:57:49.140 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=MYSAPSSO2 value=Not printed for security reasons
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Language value=en
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Encoding value=gzip
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy fireRequest()----------
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------About to fire the request to the GW-----------
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Leaving getConnection() of GWCConnectionPoolManager-- Found in cache first time----
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (1)true
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/CustomerCollection?$...'
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------
2012-12-14 13:57:49.139 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.bsuite.erp.fin.custfactsheet
2012-12-14 13:57:49.138 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------
2012-12-14 13:57:49.138 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------
2012-12-14 13:57:49.138 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Json Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.fin.custfactsheet"},{"request":"GET"},{"url":"http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/CustomerCollection?$...'"},{"Accept-Encoding":"gzip"},{"Accept-Language":"en"}]
2012-12-14 13:57:49.137 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]context.getDeviceUserName() is bbrb472@SSO
2012-12-14 13:57:49.137 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.fin.custfactsheet"},{"request":"GET"},{"url":"http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/CustomerCollection?$...'"},{"Accept-Encoding":"gzip"},{"Accept-Language":"en"}]
2012-12-14 13:57:49.137 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request body Read :
2012-12-14 13:57:49.137 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]ODP: Read the Request information
2012-12-14 13:57:49.137 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]UsrName/Pwd is extracted from context:
2012-12-14 13:57:49.137 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Cookie is extracted from Context :
2012-12-14 13:57:49.137 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------In GWCRequestAdapter constructor()----------
2012-12-14 13:57:49.130 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP :Recieved a request to fire to Gateway
2012-12-14 13:57:47.862 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel
2012-12-14 13:57:47.856 DEBUG PROXY Thread-746 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp
2012-12-14 13:57:47.855 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Connection released
2012-12-14 13:57:47.855 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Inside releaseConnection() of GWCConnectionPoolManager------
2012-12-14 13:57:47.855 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------
2012-12-14 13:57:47.855 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream
2012-12-14 13:57:47.855 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----
2012-12-14 13:57:47.854 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response body is obtained from BackEnd
2012-12-14 13:57:47.854 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Read response body from Gateway
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content encoding is ZIP ----------gzip
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content type|encoding|length--------application/xml----gzip----4843----
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-type Response header valueapplication/xml
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-encoding Response header valuegzip
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-length Response header value4843
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keylast-modified Response header valueSat, 10 Nov 2012 18:45:44 GMT
2012-12-14 13:57:47.852 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyx-sap-odata-extension-version Response header value0.9
2012-12-14 13:57:47.850 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keydataserviceversion Response header value2.0
2012-12-14 13:57:47.850 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyserver Response header valueSAP NetWeaver Application Server / ABAP 702
2012-12-14 13:57:47.850 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response code is HTTP/1.1 200 OK
2012-12-14 13:57:47.850 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Recieved the response from the gateway
2012-12-14 13:57:47.850 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished firing the request to GW-----------
2012-12-14 13:57:47.850 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Leaving FireRequest Method-----------
2012-12-14 13:57:47.850 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished Execute-----------
2012-12-14 13:57:44.920 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Before Execute-----------
2012-12-14 13:57:44.920 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP: Firing the request to the Gateway
2012-12-14 13:57:44.920 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----Host request header set is ----np2apps761v.corp.halliburton.com:8000
2012-12-14 13:57:44.920 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=MYSAPSSO2 value=Not printed for security reasons
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Language value=en
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Encoding value=gzip
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy fireRequest()----------
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------About to fire the request to the GW-----------
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Leaving getConnection() of GWCConnectionPoolManager-- Found in cache first time----
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (1)true
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/$metadata
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null
2012-12-14 13:57:44.919 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------
2012-12-14 13:57:44.918 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.bsuite.erp.fin.custfactsheet
2012-12-14 13:57:44.917 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Json Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.fin.custfactsheet"},{"request":"GET"},{"url":"http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/$metadata"},{"Accept-Encoding":"gzip"},{"Accept-Language":"en"}]
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]context.getDeviceUserName() is bbrb472@SSO
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.fin.custfactsheet"},{"request":"GET"},{"url":"http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/$metadata"},{"Accept-Encoding":"gzip"},{"Accept-Language":"en"}]
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request body Read :
2012-12-14 13:57:44.916 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]ODP: Read the Request information
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]UsrName/Pwd is extracted from context:
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Cookie is extracted from Context :
2012-12-14 13:57:44.916 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------In GWCRequestAdapter constructor()----------
2012-12-14 13:57:44.911 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP :Recieved a request to fire to Gateway
2012-12-14 13:57:43.977 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel
2012-12-14 13:57:43.969 DEBUG PROXY Thread-745 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp
2012-12-14 13:57:43.967 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Connection released
2012-12-14 13:57:43.967 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Inside releaseConnection() of GWCConnectionPoolManager------
2012-12-14 13:57:43.967 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------
2012-12-14 13:57:43.967 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream
2012-12-14 13:57:43.967 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----
2012-12-14 13:57:43.967 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response body is obtained from BackEnd
2012-12-14 13:57:43.967 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Read response body from Gateway
2012-12-14 13:57:43.966 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content encoding is ZIP ----------gzip
2012-12-14 13:57:43.966 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content type|encoding|length--------application/atomsvc+xml----gzip----906----
2012-12-14 13:57:43.966 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-type Response header valueapplication/atomsvc+xml
2012-12-14 13:57:43.965 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-encoding Response header valuegzip
2012-12-14 13:57:43.965 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-length Response header value906
2012-12-14 13:57:43.964 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyx-sap-odata-extension-version Response header value0.9
2012-12-14 13:57:43.964 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keydataserviceversion Response header value2.0
2012-12-14 13:57:43.964 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyserver Response header valueSAP NetWeaver Application Server / ABAP 702
2012-12-14 13:57:43.964 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]Response code is HTTP/1.1 200 OK
2012-12-14 13:57:43.964 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Recieved the response from the gateway
2012-12-14 13:57:43.964 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished firing the request to GW-----------
2012-12-14 13:57:43.964 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Leaving FireRequest Method-----------
2012-12-14 13:57:43.964 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished Execute-----------
2012-12-14 13:57:40.533 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Before Execute-----------
2012-12-14 13:57:40.533 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP: Firing the request to the Gateway
2012-12-14 13:57:40.532 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----Host request header set is ----np2apps761v.corp.halliburton.com:8000
2012-12-14 13:57:40.532 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=MYSAPSSO2 value=Not printed for security reasons
2012-12-14 13:57:40.532 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Language value=en
2012-12-14 13:57:40.532 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Encoding value=gzip
2012-12-14 13:57:40.532 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy fireRequest()----------
2012-12-14 13:57:40.532 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------About to fire the request to the GW-----------
2012-12-14 13:57:40.527 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Leaving getConnection() of GWCConnectionPoolManager-- Found in cache first time----
2012-12-14 13:57:40.526 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (1)true
2012-12-14 13:57:40.526 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/
2012-12-14 13:57:40.525 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager
2012-12-14 13:57:40.525 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null
2012-12-14 13:57:40.524 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------
2012-12-14 13:57:40.524 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.bsuite.erp.fin.custfactsheet
2012-12-14 13:57:40.522 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Json Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.fin.custfactsheet"},{"request":"GET"},{"url":"http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/"},{"Accept-Encoding":"gzip"},{"Accept-Language":"en"}]
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]context.getDeviceUserName() is bbrb472@SSO
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request header : [{"X-SAP-applicationId":"com.sap.bsuite.erp.fin.custfactsheet"},{"request":"GET"},{"url":"http://np2apps761v.corp.halliburton.com:8000/sap/opu/sdata/sap/FINCUSTFACTSHEET/"},{"Accept-Encoding":"gzip"},{"Accept-Language":"en"}]
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request body Read :
2012-12-14 13:57:40.521 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]ODP: Read the Request information
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]UsrName/Pwd is extracted from context:
2012-12-14 13:57:40.521 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Cookie is extracted from Context :
2012-12-14 13:57:40.519 DEBUG PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------In GWCRequestAdapter constructor()----------
2012-12-14 13:57:40.511 INFO PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP :Recieved a request to fire to Gateway
2012-12-14 13:39:54.521 ERROR MMS ScheduledTask:SynchronizeNode [com.sybase.djc.util.ResourceMonitor]A negative condition was detected, resetting to 0
2012-12-14 10:24:38.930 ERROR PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]IOException caught in fire request :while connecting to the URL sent:
at java.lang.Thread.run(Thread.java:662)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:310)
at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:798)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl_DJC.$invoke(InboundMoIIOPTransportImpl_DJC.java:100)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl.execute(InboundMoIIOPTransportImpl.java:67)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl.process(InboundMoIIOPTransportImpl.java:118)
at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:101)
at com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler.execute(GatewayConnectorHandler.java:118)
at com.sybase.suplite.gwc.req.handler.GWProxy.handle(GWProxy.java:286)
at com.sybase.suplite.gwc.req.handler.GWProxy.fireRequest(GWProxy.java:496)
at shaded.org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at shaded.org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at shaded.org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
at shaded.org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at shaded.org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at shaded.org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at shaded.org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at shaded.org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
at shaded.org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at shaded.org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at shaded.org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketTimeoutException: Read timed out
2012-12-14 09:59:16.619 ERROR PROXY MessageChannel Thread-699 [com.sybase.suplite.gwc.req.handler.GWProxy]IOException caught in fire request :while connecting to the URL sent:
at java.lang.Thread.run(Thread.java:662)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:310)
at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:798)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl_DJC.$invoke(InboundMoIIOPTransportImpl_DJC.java:100)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl.execute(InboundMoIIOPTransportImpl.java:67)
at com.sybase.sup.server.msgchannel.internal.InboundMoIIOPTransportImpl.process(InboundMoIIOPTransportImpl.java:118)
at com.sybase.sup.server.msgchannel.internal.MessageChannelInternal.dispatch(MessageChannelInternal.java:101)
at com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler.execute(GatewayConnectorHandler.java:118)
at com.sybase.suplite.gwc.req.handler.GWProxy.handle(GWProxy.java:286)
at com.sybase.suplite.gwc.req.handler.GWProxy.fireRequest(GWProxy.java:496)
at shaded.org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
at shaded.org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)
at shaded.org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)
at shaded.org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)
at shaded.org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)
at shaded.org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)
at shaded.org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)
at shaded.org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)
at shaded.org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)
at shaded.org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at shaded.org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketTimeoutException: Read timed out
2012-12-14 02:00:01.838 ERROR MMS Thread-60 [com.sybase.djc.log.SystemExceptionLog]com.sybase.djc.SystemException was thrown by transaction com.sybase.djc.server.PartitionLock.updateLock(long, boolean)\ncom.sybase.djc.SystemException: Failed to rollback transaction: javax.transaction.SystemException:
... 3 more
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:907)
at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:829)
at com.sybase.djc.transaction.Transaction.check(Transaction.java:1705)
| ... 4 more
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:827)
| at com.sybase.djc.transaction.Transaction.jdbcRollback(Transaction.java:1284)
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:1211)
| at com.sybase.djc.sql.tie.TieConnection_DJC.rollback(TieConnection_DJC.java:996)
| at com.sybase.djc.sql.tie.TieConnection.rollback(TieConnection.java:289)
| at com.sybase.jdbc3.jdbc.SybConnection.rollback(Unknown Source)
| at com.sybase.jdbc3.jdbc.SybConnection.checkConnection(Unknown Source)
| at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
| Caused by: java.sql.SQLException: JZ0C0: Connection is already closed.
| at com.sybase.djc.server.PartitionLock$RetainThread.run(PartitionLock.java:82)
| at com.sybase.djc.server.PartitionLock_DJC.updateLock(PartitionLock_DJC.java:170)
| at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:747)
| at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:907)
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:829)
| at com.sybase.djc.transaction.Transaction.check(Transaction.java:1701)
| at com.sybase.djc.util.ExceptionUtil.checkExceptions(ExceptionUtil.java:46)
Caused by: com.sybase.djc.SystemException: JZ0C0: Connection is already closed.
Caused by: javax.transaction.SystemException:
at com.sybase.djc.server.PartitionLock$RetainThread.run(PartitionLock.java:82)
at com.sybase.djc.server.PartitionLock_DJC.updateLock(PartitionLock_DJC.java:170)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:747)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:913)
| ... 4 more
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:827)
| at com.sybase.djc.transaction.Transaction.jdbcRollback(Transaction.java:1284)
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:1211)
| at com.sybase.djc.sql.tie.TieConnection_DJC.rollback(TieConnection_DJC.java:996)
| at com.sybase.djc.sql.tie.TieConnection.rollback(TieConnection.java:289)
| at com.sybase.jdbc3.jdbc.SybConnection.rollback(Unknown Source)
| at com.sybase.jdbc3.jdbc.SybConnection.checkConnection(Unknown Source)
| at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
| Caused by: java.sql.SQLException: JZ0C0: Connection is already closed.
| at com.sybase.djc.server.PartitionLock$RetainThread.run(PartitionLock.java:82)
| at com.sybase.djc.server.PartitionLock_DJC.updateLock(PartitionLock_DJC.java:170)
| at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:747)
| at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:907)
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:829)
| at com.sybase.djc.transaction.Transaction.check(Transaction.java:1701)
| at com.sybase.djc.util.ExceptionUtil.checkExceptions(ExceptionUtil.java:46)
Caused by: com.sybase.djc.SystemException: JZ0C0: Connection is already closed.
2012-12-14 02:00:01.837 ERROR MMS Thread-60 [com.sybase.djc.transaction.TransactionManagerLog]Failed to rollback transaction: javax.transaction.SystemException:
| ... 4 more
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:827)
| at com.sybase.djc.transaction.Transaction.jdbcRollback(Transaction.java:1284)
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:1211)
| at com.sybase.djc.sql.tie.TieConnection_DJC.rollback(TieConnection_DJC.java:996)
| at com.sybase.djc.sql.tie.TieConnection.rollback(TieConnection.java:289)
| at com.sybase.jdbc3.jdbc.SybConnection.rollback(Unknown Source)
| at com.sybase.jdbc3.jdbc.SybConnection.checkConnection(Unknown Source)
| at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
| Caused by: java.sql.SQLException: JZ0C0: Connection is already closed.
| at com.sybase.djc.server.PartitionLock$RetainThread.run(PartitionLock.java:82)
| at com.sybase.djc.server.PartitionLock_DJC.updateLock(PartitionLock_DJC.java:170)
| at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:747)
| at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:907)
| at com.sybase.djc.transaction.Transaction.rollback(Transaction.java:829)
| at com.sybase.djc.transaction.Transaction.check(Transaction.java:1701)
| at com.sybase.djc.util.ExceptionUtil.checkExceptions(ExceptionUtil.java:46)
Caused by: com.sybase.djc.SystemException: JZ0C0: Connection is already closed.
2012-12-14 02:00:01.835 ERROR MMS Thread-60 [com.sybase.djc.log.SystemExceptionLog]com.sybase.djc.DataStoreException was thrown by transaction com.sybase.djc.server.PartitionLock.updateLock(long, boolean)\ncom.sybase.djc.DataStoreException: JZ006: Caught IOException: com.sybase.jdbc3.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed.
... 9 more
at com.sybase.djc.sql.PersistenceManager.executeQuery(PersistenceManager.java:3171)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseErrorCheckDead(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.createIOEKilledConnEx(Unknown Source)
Caused by: java.sql.SQLException: JZ006: Caught IOException: com.sybase.jdbc3.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed.
at com.sybase.djc.server.PartitionLock$RetainThread.run(PartitionLock.java:82)
at com.sybase.djc.server.PartitionLock_DJC.updateLock(PartitionLock_DJC.java:170)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:747)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:845)
at com.sybase.djc.server.PartitionLock_DJC$2.invoke(PartitionLock_DJC.java:156)
at com.sybase.djc.server.PartitionLock_DJC.access$101(PartitionLock_DJC.java:4)
at com.sybase.djc.server.PartitionLock.updateLock(PartitionLock.java:343)
at com.sybase.djc.server.PartitionCycle.findByPrimaryKey(PartitionCycle.java:67)
at com.sybase.djc.server.PartitionCycle$findByPrimaryKey.invoke(PartitionCycle$findByPrimaryKey.java:27)
at com.sybase.djc.sql.PersistenceManager.executeQuery(PersistenceManager.java:3175)
2012-12-14 02:00:01.829 ERROR MMS Thread-60 [com.sybase.djc.log.SystemExceptionLog]com.sybase.djc.DataStoreException was thrown by method com.sybase.djc.server.PartitionLock.updateLock(long, boolean)\ncom.sybase.djc.DataStoreException: JZ006: Caught IOException: com.sybase.jdbc3.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed.
... 9 more
at com.sybase.djc.sql.PersistenceManager.executeQuery(PersistenceManager.java:3171)
at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source)
at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source)
at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source)
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.a(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseErrorCheckDead(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.createIOEKilledConnEx(Unknown Source)
Caused by: java.sql.SQLException: JZ006: Caught IOException: com.sybase.jdbc3.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed.
at com.sybase.djc.server.PartitionLock$RetainThread.run(PartitionLock.java:82)
at com.sybase.djc.server.PartitionLock_DJC.updateLock(PartitionLock_DJC.java:170)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:747)
at com.sybase.djc.transaction.TransactionManager.invokeRequiresNew(TransactionManager.java:845)
at com.sybase.djc.server.PartitionLock_DJC$2.invoke(PartitionLock_DJC.java:156)
at com.sybase.djc.server.PartitionLock_DJC.access$101(PartitionLock_DJC.java:4)
at com.sybase.djc.server.PartitionLock.updateLock(PartitionLock.java:343)
at com.sybase.djc.server.PartitionCycle.findByPrimaryKey(PartitionCycle.java:67)
at com.sybase.djc.server.PartitionCycle$findByPrimaryKey.invoke(PartitionCycle$findByPrimaryKey.java:27)
at com.sybase.djc.sql.PersistenceManager.executeQuery(PersistenceManager.java:3175)
2012-12-14 02:00:01.076 ERROR MMS Thread-35 [com.sybase.sup.server.monitoring.StartMonitoringService]com.sybase.sup.server.monitoring.StartScheduledMonitoringThread.run()
... 9 more
at com.sybase.djc.sql.ConnectionPool.createConnection(ConnectionPool.java:755)
at com.sybase.djc.sql.ConnectionPool.newConnection(ConnectionPool.java:807)
at com.sybase.jdbc3.jdbc.SybDataSource.getConnection(Unknown Source)
at com.sybase.jdbc3.jdbc.SybDriver.connect(Unknown Source)
at com.sybase.jdbc3.jdbc.SybDriver.connect(Unknown Source)
at com.sybase.jdbc3.jdbc.SybDriver.createConnection(Unknown Source)
at com.sybase.jdbc3.jdbc.SybConnection.<init>(Unknown Source)
at com.sybase.jdbc3.jdbc.SybConnection.handleHAFailover(Unknown Source)
at com.sybase.jdbc3.jdbc.SybConnection.a(Unknown Source)
at com.sybase.jdbc3.tds.Tds.login(Unknown Source)
at com.sybase.jdbc3.tds.Tds.case(Unknown Source)
at com.sybase.jdbc3.tds.Tds.for(Unknown Source)
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
Caused by: java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
at com.sybase.sup.server.monitoring.StartMonitoringService$MonitoringScheduledThread.run(StartMonitoringService.java:207)
at com.sybase.sup.server.monitoring.MonitoringDBUtil.deleteMonitoringData(MonitoringDBUtil.java:500)
at com.sybase.sup.server.monitoring.MonitoringDBUtil.callProcedure(MonitoringDBUtil.java:177)
at com.sybase.djc.sql.ConnectionWrapper_DJC.prepareCall(ConnectionWrapper_DJC.java:109)
at com.sybase.djc.sql.ConnectionWrapper.getConnection(ConnectionWrapper.java:146)
at com.sybase.djc.sql.ConnectionWrapper.checkOpen(ConnectionWrapper.java:198)
at com.sybase.djc.sql.ConnectionPool.getConnection(ConnectionPool.java:198)
at com.sybase.djc.sql.ConnectionPool.getConnection(ConnectionPool.java:234)
at com.sybase.djc.sql.ConnectionPool.getConnectionHandle(ConnectionPool.java:268)
at com.sybase.djc.sql.ConnectionPool.createConnection(ConnectionPool.java:783)
com.sybase.djc.DataStoreException: Connection Failed: java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
2012-12-13 22:39:59.902 CONSOLE MMS Thread-5 [com.sybase.sup.server.Console]Server Started
2012-12-13 22:39:19.060 INFO MMS Thread-5 [com.sybase.djc.server.ServiceComponent]Starting
2012-12-13 22:39:19.059 INFO MMS Thread-5 [com.sybase.djc.server.ServiceComponent]Component com.sybase.djc.mobilink.StartHandler
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]user = adssys
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]serverName = np2appg714cFS.corp.halliburton.com
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]portNumber = 6262
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]maxPoolSize = 100
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]databaseType = AdvantageDB
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]databaseName = \\np2appg714cFS.corp.halliburton.com\Data\Messaging\OBR\OBR.add
2012-12-13 22:39:18.121 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]ant.project = default-jmsbridge
2012-12-13 22:39:18.120 INFO MMS Thread-5 [com.sybase.djc.sql.DataSource]driverClass = class com.extendedsystems.jdbc.advantage.ADSDriver
2012-12-13 22:39:18.118 INFO MMS Thread-5 [com.sybase.djc.util.ThreadMonitor]init: targetResponseTime = 0 (unchecked)
2012-12-13 22:39:18.118 INFO MMS Thread-5 [com.sybase.djc.util.ThreadMonitor]init: initialThreadLimit = 0 (unlimited)
Hi Kalanda,
the logs are helpful. The reason for the error is that SUP has a time limit to get back the complete response from server. (I gues default time is 60 seconds). If the request takes more time SUP will timeout.
One of the alternate option is to finetune the gateway service to get the response fast. Or you can enhance your filter to fetch less data.
Almost the sam issue is faced by one more user. Check thread http://scn.sap.com/thread/3245820.
The latest realeased version of SUP(2.2) has streaming option for data. However the app needs to be adapted accordingly to use streaming.
I hope this answers your query.
Regards
Rohith
Hi Kalanda,
The below piece of code should be added in the application while building the request. Do you have access to your application source code?
I guess you are using .ipa downloaded from SAP appstore. So changing the timeout may not be possible.
I suggest you to finetune the gateway service to get the response fast. Or you can enhance your filter to fetch less data.
Also for light weight online applications any response taking more than 60 seconds may not be ideal.
Regards
Rohith
Hello Rohith,
regarding the SUP 60 seconds timeout that You mentioned, can You give me more details on where it is and it can be changed and any details that You can on that. This is issue is still opened and We need to narrow the problem. and Please could You tell me whether you are SUP Developer or CFFS Developer, so that We will know more.
thank you,
Fiston Kalanda
Hi Fiston,
Little late reply. However I feel this info may be useful for many others.
You can change the SUP-ODP server timeout in the config file. Below is the details of location and property name.
Server may need a restart after chaing the config file.
Please try and revert back.
Location : \Sybase\UnwiredPlatform\Servers\UnwiredServer\config
File name : OnlineProxy.properties
Property name: SOCKET_TIMEOUT
Regards
Rohith
Hi Fiston,
From the URL that you have pasted i see no space between "eq" and '1100' in $filter expression. I hope you have maintained that space while making an OData request.
Thanks
Kind Regards
Chandan VA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fiston,
It seems the error is coming from gateway and no issues from SUP Or App. To do a quick check, you can run the same URL in the REST client (this is an addon to Mozilla browser). If you are getting same error, you can post the same query @
http://scn.sap.com/community/netweaver-gateway to get help from gateway experts.
Regards
Rohith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello Rohith,
I've followed your recommendation, used the following URL for RESTClient
testing;
%20eq%20'1100'
I do
not get the 500error rather I get 200 Ok status.
However I do get
unresponsive script message ( as shown in the screen
shot). and then the
Mozilla browser crashes in couple of minutes. Please see the attached doc.
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.