×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We don't have the authority to even *look* at the host table, or at the
domain information, BUT
The BIRT reports have the odaURL property set to (redacted for customer
privacy)
> jdbc:as400://wintouch.customername.com/redacted
and if, from a command line, we
> PING wintouch.customername.com
we get
Round-trip (in milliseconds) min/avg/max = 0/0/2.
which suggests that resolving the domain isn't the issue.
If we run a BIRT report in Tomcat on the customer box, it takes over six
seconds (timing it manually, with the stopwatch function on my Timex).
If we run the same BIRT report on our own Power 6, V6R1 box, ACCESSING
THE DATA ON THE CUSTOMER BOX, it takes about 2 seconds.
I did a "jar tvf" on the jt400 jar that appears to be in use; it appears
to be from September of 2012. But that driver JAR seems to work fine
everywhere else.
My colleague, from studying diagnostics he placed in a test webapp,
tells me that a call to driver.connect(url, connectionProperties) is
taking 6 seconds on the customer box.
--
JHHL
midrange.com
