Hi List, We are experiencing problems with our Mid-Tier servers. The login page freezes after pressing the login button. After some time mid-tier returns to function. Sometimes it happens to one mid-tier server, sometimes to the other.
What we can see from the logs are RPC call ARERR 91 errors while trying to perform actions on login, like retrieving user preferences or saved searches, such as: "Dec 6, 2008 3:47:38 PM - WARNING (com.remedy.log.SESSION) : Error loading preference from server <ARserverIP> for the user DemoARERR [91] RPC call failed : ONC/RPC call timed out at com.remedy.arsys.goat.preferences.ARUserPreferences.clearAndLoadDefaultFields(Unknown Source) at com.remedy.arsys.goat.preferences.ARUserPreferences.loadFromServer(Unknown Source) at com.remedy.arsys.goat.preferences.ARUserPreferences.addConfiguredPreferences(Unknown Source) at com.remedy.arsys.goat.preferences.ARUserPreferences.<init>(Unknown Source) at com.remedy.arsys.goat.preferences.ARUserPreferences.getUserPreferences(Unknown Source) ... Dec 6, 2008 3:42:38 PM - FINE (com.remedy.log.INTERNAL) : Throw ARException - ERROR (91): RPC call failed; ONC/RPC call timed out ERROR (91): RPC call failed; ONC/RPC call timed out Dec 6, 2008 3:40:38 PM - FINE (com.remedy.log.INTERNAL) : Throw ARException - ERROR (91): RPC call failed; ONC/RPC call timed out ERROR (91): RPC call failed; ONC/RPC call timed out Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : Login: creating session Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : Login: establishing Session Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SERVLET) : GoatServlet: No SessionData Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SERVLET) : cookie=IP-Restriction-GUID=11d1def534ea1be0:-52afbacf:11e0872f9a3:-7fe4; JSESSIONID=BAC2EACFE02CCBF01F9D318B53933D99; PopBlock=0 Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SERVLET) : GoatServlet: url=http://<midtierIP>:8080/arsys/ Dec 6, 2008 3:38:45 PM - INFO (com.remedy.log.SESSION) : User Demo on IPAddress <ARserverIP> Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : LoginServlet: Authentication status: 16 Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : LoginServlet: Authenticating Demo against server <ARserverIP> Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : DefaultAuthenticator: Using credentials from login page - Demo Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : LoginServlet: Target URL attribute = /arsys/ Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : LoginServlet: locale=<locale> Dec 6, 2008 3:38:45 PM - FINE (com.remedy.log.SESSION) : LoginServlet: url=http://<midtierIP>:8080/arsys/servlet/LoginServlet?null" ... Dec 6, 2008 3:34:05 PM - WARNING (com.remedy.log.SERVLET) : Caught GoatException ARERR [91] RPC call failed : ONC/RPC call timed out at com.remedy.arsys.stubs.ServerLogin.<init>(Unknown Source) at com.remedy.arsys.stubs.ServerLogin.get(Unknown Source) at com.remedy.arsys.stubs.SessionData.getServerLogin(Unknown Source) " We also get this error: "Dec 5, 2008 6:25:42 PM - SEVERE (com.remedy.log.CACHE) : Globule: Error sending compressed data globule for formClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:352) at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392)" The ARS server group has the "Register with Port Mapper" flag on. I saw a post http://www.mail-archive.com/[email protected]/msg06018.html that could be related to this issue: from time to time mid-tier servers would try to connect to the ARS port mapper even though the TCP port is specified under the mid-tier ARS server configurations. However, the versions in that are ARS and Mid-Tier version 6.3 (we are using 7.1). Could this be the problem, since our firewall is configured to only accept connections on the TCP port and not in the UDP 111 port? We tested connection between the servers and everything seems ok both ways(by ping and telnet on the TCP port, the UDP port 111 is unreachable by the midtier servers, but we can see it's open and working in the ARS server). Has anyone experienced this issue or the errors above? Is there a know solution? I couldnt find any in the knowledge base. Our system is: AR System 7.1 patch 1 (Windows Server 2003 SP2) Mid Tier Version 7.1.00 Patch 003 200805260630 (Red Hat 4) Apache Tomcat 5.5.25 Thanks, Rudolf _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
