I have found the AS/400 to be much more resilient towards incomplete or
incorrect TCP/IP configuration when talking about non-Java stuff, and then
when the Java Toolbox tries to talk to prestarted jobs over TCP/IP there is
no end of problems as networking in Java essentially expect TCP/IP to be
properly configured.
Could you elaborate on what "unable to access files" mean in your situation?
(Can you locate the host name? Can you connect? Can you "select 1 from
sysibm.sysdummy1"? Do you see a stack trace?)
/Thorbjørn
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of James Lampert
Sent: 9. december 2011 01:58
To: Java Programming on and around the IBM i
Subject: Can anybody suggest any reasons why BIRT would be unable to
establish a JDBC connection, when running on the same physical box?
Thanks again for all who had suggestions on the "Java not where Tomcat is
expecting to find it" issue; we've resolved it, using the QOpenSys
locations.
We have another situation at a customer.
BIRT, running in a webapp under Tomcat, is unable to access files on the
same box that it's running on (using the TCP Loopback address).
Any suggestions on places to look for the cause?
--
JHHL
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.
midrange.com
