• brianb08
  • NEWBIE
  • 0 Points
  • Member since 2004

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 4
    Replies
I've seen a dramatic increase in session timeout issues over the past few days communicating with the API. I've tested accessing the API from two different networks, and they both seem to fail at the same time.

Immediately after these failures, a new login returns:

UNKNOWN_EXCEPTION: server temporarily unavailable

Has anyone else experienced these problems? Is there any solutions in the works?
Thanks,
-Brian
We are having a strange issue with an integration we are writing around socket level timeouts. This is happening usually within a minute of the application running and doesn't appear to be a session management issue. This is happening while doing a series (sometimes as few as 70) of small SOQL queries (each returns one row) that happens at the beginning of the application.

We are seeing this exception:

java.net.ConnectException: Connection timed out: connect
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)

This is using JDK1.5.0_01 and Axis 1.2.1. and going against a trial version account that was upgraded to EE

Has anyone seen this or have any ideas of what may be causing the issue? Since itis an Axis/Java exception we are going to try various combinations of JVM's and Axis levels to see if that resolves it.

Any ideas or thoughts would be appreciated!

Thanks,

John
I've seen a dramatic increase in session timeout issues over the past few days communicating with the API. I've tested accessing the API from two different networks, and they both seem to fail at the same time.

Immediately after these failures, a new login returns:

UNKNOWN_EXCEPTION: server temporarily unavailable

Has anyone else experienced these problems? Is there any solutions in the works?
Thanks,
-Brian