Is anyone else having trouble with ReportCaster Stability? We are migrating from a 7.1.7/7.1.8 install to 7.6.11. Our distribution server is on a HP-UX box with the repository in DB2 on the MF.

I am having trouble with ReportCaster staying up. It is like it forgets to go check schedules to see what it needs to run. After logging into ReportCaster and getting into the GUI all the next run time dates are in the past. Anyone else seen this kind of behavior? This has been happening in our new Dev and Qual area. We are juust now building or new Prod environment.

I already have a case open with IBI.

This message has been edited. Last edited by: Kerry,

Similar environment but not exactly the same. (DS also on an IBM P5/Linux server). EVERY issue we had (and there were several) when we migrated to 7.6.x from 7.1.x was related to the Java installation on the server. At one point, we found that the web app server was using a different version than the DS server. Frequently the DS server appeared to be working and the test utility showed successful, but the DS server was not actually functioning. Tried to consolidate Java installs as much as possible so everything was using the same installation of Java. Also moved from Websphere to Tomcat server. Have experienced very little problem with stability since.

Our app server is running WebSphere on Linux using

java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20100127 (SR11 FP1 ))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223ifx-20100125 (JIT enabled)
J9VM - 20100122_52103_lHdSMr
JIT - 20091016_1845ifx1_r8
GC - 20091026_AA)
JCL - 20100127

Our DS server on hpux is running..

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.15-_12_jan_2009_08_47)
Java HotSpot(TM) Server VM (build 1.5.0.15 jinteg:01.12.09-07:54 PA2.0 (aCC_AP), mixed mode)

Any ideas how I can bring these installs more inline version wise? Not sure I would be allowed to install IBM Java on a HP machine. lol

We are still having problems with this. One thing we have discovered is the PID that is assigned to JAVA is using 100% of the CPU when it hands up. We are at JAVA realease 1.5.0_15 for the distribution server does anyone think that updating to JAVA 1.5.0_22 would help?

IBI helped us figure out the problem. We had been using the wrong driver type. We should have been using a type 4 DB2 driver instead of the type 2 DB2 driver. This did not bite us until we started using Java 1.5 for ReportCaster.

The ticket has been closed.