You have a number of varaibles in play that's going to make it hard to pinpoint the cause of the slowness: - midtier local to arserver host in fast configuration - different tomcat versions - different operating systems - physical vs. virtual machines - different java versions
The fact that one is on the same box as the arserver and the other is on a separate physical host is the first thing I'd look at. - What is the route between the linux midtier and the solaris arserver (latency and hops) The physical vs. virtual is the next thing I'd look at: - What is the load on the physical server that the virtual server is running on (mem, cpu, disk)? I don't think the version differences with Java, Tomcat, and the mid-tier software will make a difference, but it could. Axton Grams On Mon, Nov 28, 2011 at 2:18 PM, L G Robinson <[email protected]> wrote: > ** Hi Jarl, > Preload Tables Configuration has the default setting of: > Reload Tables At Init Only: No > Number of Preload Threads: 20 > Number of Preload Segments: 300 > I didn't think this would be a factor since the Solaris Mid-tier works fine > and these settings are per-server. But thanks for thew suggestion. > Larry > > On Mon, Nov 28, 2011 at 2:29 PM, Jarl Grøneng <[email protected]> > wrote: >> >> Hi, >> >> Have you tried to enable the Pre-Load option? You enable this is the >> AR Server option. >> >> -- >> J > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
