Contributions
Re: Intermittent issue with commandline client hanging
I thought that error above was isolated to one user, but looking in the logs I see several instances of: 2012-12-12 13:24:49,313 WARN http-8080-1 com.smartbear.ccollab.AuthTicketFilter - Login failed for user: crosander 2012-12-12 13:24:50,534 WARN http-8080-13 com.smartbear.ccollab.rpc.RpcGwtServlet$GwtInvocationHandler - Could not find valid user via session or cookie1.9KViews0likes0CommentsRe: Intermittent issue with commandline client hanging
We are running a test with the latest software. It looks like it does resolve the problem. Or atleast minimizes it. We had one reported instance where someone could not log into the web interface. The log message was: 2012-12-10 21:20:23,113 WARN http-8080-11 com.smartbear.ccollab.rpc.RpcGwtServlet$GwtInvocationHandler - Could not find valid user via session or cookie I presume that this is the same problem with our AD server. Once he logs in successfully then it will use the cookie instead of the AD server. Is that correct? How long does the cookie last? I am curious as to how often we might see this message.1.9KViews0likes0CommentsIntermittent issue with commandline client hanging
The server is 5.0.5036 We are using AD user validation. The issue is that roughly once per hour for about 1-10 minutes the commandline client will hang and spit out the error whose first line is: com.smartbear.ccollab.datamodel.xmlrpc.XmlRpcClientEngineImplementation$1 invokeFINE: XML-RPC exception org.apache.xmlrpc.XmlRpcException: I/O error while communicating with HTTP server: Connection reset at org.apache.xmlrpc.client.XmlRpcCommonsTransport.writeRequest(XmlRpcCommonsTransport.java:252) For most cases web access is still available. If I run the commandline on the server and use localhost, it still hangs so it doesn't look to be a network problem. The problem arose after we moved the app to the cloud. Any detailed response is greatly appreciated.11KViews0likes5Comments