Turn on your søl/api log and look for long queries.
--
Jarl
On 5/29/07, Francois - BTT <[EMAIL PROTECTED]> wrote:
**
Hi All,
We are trying to consume a web service in Remedy but keep receiving the
following in the mid-tier logs…
May 29, 2007 10:16:04 AM - SEVERE (com.remedy.log.WEBSERVICES) : (Thread 10)
AxisFault :
MessageType: 2
MessageNum: 93
MessageText: Timeout during data retrieval due to busy server -- retry the
operation
AppendedText: rmdytest
at com.remedy.arsys.api.Proxy.ARXMLGetEntry(Native Method)
at com.remedy.arsys.api.Util.ARXMLGetEntry(Util.java:2850)
at com.remedy.arsys.ws.services.ARService.performOperation(Unknown Source)
at com.remedy.arsys.ws.services.ARService.processRequest(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.axis.providers.java.MsgProvider.processMessage(MsgProvider.java:141)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
at
com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
at
com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
at
com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1846)
at
com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)
at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1002)
What I tried…
Increase Remedy Process Time-out setting on server to 60
Environment
SQL Server 2005
Win 2003 Server
AR System 7.0.0 Patch 2
Anyone have any ideas what can cause this?
Regards
Francois Seegers
Blue Turtle Technologies
Senior Remedy Consultant
(
Mobile:
+27 (82) 729-5273
(
Telephone
+27 (11) 206-5600
(
Facsimile:
+27 (11) 206-5606
*
Email:
[EMAIL PROTECTED]
8
Website:
www.blueturtle.co.za
"What lies behind us and what lies before us are small matters compared to what lies
within us."
__20060125_______________________This posting was submitted with HTML
in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
