Re: ROI credit card software upgrade problems

Hi Joe,

Yep, I'm not a java programmer; I hoped this list would provide some Java expertise, especially as it pertains to the AS400.

I didn't see the original logs, but I was told it's the same error. I think they're still in a position to recreate the original error (before the upgrade attempt).

ROI has been called in now that they're doing the upgrade and still having problems. In addition, IBM has also been called in and has someone looking at TCP/IP stuff.

Afaik, no changes were made to the AS400 or the network (to answer one of Neill's questions) during the time period in question, which is what makes it puzzling. Now they're making sure PTFs are up to date, etc. Nothing in any of the AS400 job logs (to answer your other question Neill). The only clues that we could find are in the log the java program produced.

Where do I find the JDBC properties?

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Joe Sam Shirah wrote:

Hi Peter,

I often use Squirrel to hit various databases, and ran into something similar to this:

java.net.SocketTimeoutException: connect timed out

with later JTOpen versions. The issue there was that, by default, Squirrel tries to open all schemas (read libraries or collections on the AS/400) in the database at first connect. When I turned off that behavior, the problem went away.

I checked the JDBC properties, but couldn't find anything regarding timeouts. Since my change worked, and I never saw the issue in my programs using the driver, I didn't pursue it further. My suspicion, however, is that JTOpen now does something different with socket connections that allows the timeout, and there may be a more or less undocumented (in JTOpen) socket setting it uses.

So I'm wondering if the upgrade attempts to check all schemas when it starts up. Was the initial problem the same or do they have the log for that?

I see your site doesn't claim any Java skills and Visual Basic probably won't help, so you may want to contact someone familar with Java if you need to dig deeper. I also would encourage your client to set some fires under ROI's support staff; doesn't sound like a good ROI here...

HTH,


Joe Sam

Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400

----- Original Message ----- From: "Peter Dow" <maillist@xxxxxxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Tuesday, May 19, 2009 12:53 PM
Subject: ROI credit card software upgrade problems

Hi Everyone,

A customer of mine who uses ROI's credit card authorization software
(mostly in Java) ran into a problem. On Thursday, 05/14/2009, they
restarted the server and it started up just fine. On Sunday,
05/17/2009, they tried to restart the server and it failed.

ROI couldn't determine anything immediately, and asked them to upgrade
to the latest version before continuing. So they upgraded. The upgrade
tries to run a couple of AS400 commands (from Java) and fails. Here's
the upgrade log:

2009-05-18 21:42:22,105
**********************************************************************
2009-05-18 21:42:22,146 JCharge upgrade to version
7.4.3.14
2009-05-18 21:42:22,146 JCUpgrade launched with no command line
arguments.
2009-05-18 21:42:22,152
Initializing...
2009-05-18 21:42:22,225
ok
2009-05-18 21:42:22,225 Connecting to
services...
2009-05-18 21:42:26,998
ok
2009-05-18 21:42:26,998 Checking for dependent logical files in other
libraries...
2009-05-18 21:42:26,998 DSPDBR FILE(ASCCOM1/*ALL) OUTPUT(*OUTFILE)
OUTFILE(ASCCOM1/DSPDBR)
2009-05-18 21:45:37,275 java.net.SocketTimeoutException: connect timed
out
2009-05-18 21:45:37,384 at
java.lang.Throwable.<init>(Throwable.java:195)
2009-05-18 21:45:37,384 at
java.lang.Exception.<init>(Exception.java:41)
2009-05-18 21:45:37,384 at
java.io.IOException.<init>(IOException.java:40)
2009-05-18 21:45:37,384 at
java.net.SocketTimeoutException.<init>(SocketTimeoutException.java:24)
2009-05-18 21:45:37,384 at
java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
2009-05-18 21:45:37,384 at
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
2009-05-18 21:45:37,385 at
java.net.Socket.connect(Socket.java:488)
2009-05-18 21:45:37,385 at
java.net.Socket.connect(Socket.java:438)
2009-05-18 21:45:37,385 at
java.net.Socket.<init>(Socket.java:148)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.PortMapper.getServerSocket(PortMapper.java:141)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.AS400ImplRemote.signonConnect(AS400ImplRemote.java:1855)
2009-05-18 21:45:37,385 at
com.ibm.as400.access.AS400ImplRemote.signon(AS400ImplRemote.java:1755)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.AS400.sendSignonRequest(AS400.java:2571)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.AS400.promptSignon(AS400.java:2157)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.AS400.signon(AS400.java:3412)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.CommandCall.chooseImpl(CommandCall.java:238)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.CommandCall.run(CommandCall.java:571)

2009-05-18 21:45:37,385 at
com.ibm.as400.access.CommandCall.run(CommandCall.java:610)

2009-05-18 21:45:37,386 at
JCUpgrade.runCommand400(JCUpgrade.java:549)

2009-05-18 21:45:37,386 at
JCUpgrade.checkLogicalFiles(JCUpgrade.java:107)

2009-05-18 21:45:37,386 at
JCUpgrade.execute(JCUpgrade.java:79)

2009-05-18 21:45:37,386 at
JCUpgrade.main(JCUpgrade.java:66)

2009-05-18 21:45:37,386 Error: see log file for details

It appears to be trying to do a remote signon and timing out. All the
host servers are started, so why is it timing out? Or is it some other
problem?

tia,
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /