George, This appears to be more of a resolution problem than a problem with your Mid-Tier itself.
Would it be possible for you to ask your network team to add hostname.com to the DNS as an alias to hostname?? That way it will resolve the same server irrespective. I can't really explain how and why your application randomly tries hostname.come instead of hostname but having a DNS entry for hostname.com would resolve your connection problem in my opinion. Hope this helps.. Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Payne, George Sent: Wednesday, September 19, 2007 4:44 PM To: arslist@ARSLIST.ORG Subject: Need Help with 7.0.01 P02 Mid-Tier installation ** Please help if you can! Server: AIX 5.3 ARS Version: 7.0.01 P02 Web Server: Apache 2.0.47 Java Server: Tomcat 5.5.17 Jakarta Connector: 1.2.6 This is our Development box and is _supposed_ to be configured just like our Production box, which IS working properly. Obviously SOMETHING is different, but I’ve exhausted all of the things that I can think of. I suspect that this is a relatively simple configuration issue, just not sure where else to look. I’ve compared the Jakarta modules, the httpd.conf files, the workers.properties files What we’re running into is that the user can login to the Mid-Tier and navigate through “a few” pages (sometimes more / sometimes fewer), there doesn’t appear to be any rhyme or reason as to how far they get (maybe it’s further into the application for the first few users, but that’s very subjective). We observe the same problem when logging in to the Mid-Tier Configuration Utility. Sometimes you can maneuver through 3 to 5 of the screens, sometimes you can’t even get past the LOGIN screen. The error message indicates that the server is having trouble contacting http://www.hostname.com which is NOT the URL that we’re typing when we enter either the Remedy Application or Mid-Tier Configuration: http://hostname/arsys/home and http://hostname/arsys/shared/config/config.jsp respectively When it DOES work, it provides the pages accurately and relatively quickly. The HEAP SIZES on the DEV box were not set, so I set those to match our production server (1024M for both the starting and maximum), stopped and re-started Tomcat and the increased HEAP SIZES didn’t seem to help with this issue at all. I see that folks were experiencing “Out of Memory” errors when their Heap sizes weren’t set, but that’s not the error that we’re experiencing anyway. I have sent this to our level one support who asked for a screen shot of the error. I sent that to them this morning and haven’t heard anything else. George George Payne Corporate Applications Developer Electric Reliability Council of Texas (512) 248-3940 [EMAIL PROTECTED] No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.487 / Virus Database: 269.13.22/1015 - Release Date: 9/18/2007 11:53 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
