#2 appserver4rpg problems

[davide]

we have a very strange issue on a new fresh ARDGATE installation of AppServer4RPG2014-04-16.ZIP on our IBM i is V7R1M0 with java version "1.6.0".
This is our first attempts to use Bender' Application and these are steps we done:

1) restore lib JVAGATE
2) create IFS /JVAGATE and put inside AppServer4RPG.jar, folders "conf" and "lib"
3) downloaded from Oracle's site ojdbc6.jar (because we need to talk to Oracle DB server) and put in \jvagate\lib
4) ADDRDBDIRE RDB(INTSTD) RMTLOCNAME(ARDPGM) ARDPGM(JVAGATE/JDBCGATE) for Oracle server at IP 192.168.10.140
5) ADDRDBDIRE RDB(ARD400LOC) RMTLOCNAME(ARDPGM) ARDPGM(JVAGATE/JDBCGATE) for testing purpose
6) modified conf\global.properties removing all entry for ard.url and ard.driver and adding only:

ard.url.INTSTD=jdbc:oracle:thin:@192.168.10.140:1521:xe
ard.driver.INTSTD=oracle.jdbc.driver.OracleDriver
ard.url.ARD400LOC=jdbc:as400://localhost;prompt=false
ard.driver.ARD400LOC=com.ibm.as400.access.AS400JDBCDriver

7) SBMJOB CMD(CALL PGM(JVAGATE/STRJVAGATE)) JOB(JVAGATE)

8) \jvagate\logs\ArdGateLog.log appears and content is

2014-06-09 16:37:22,010 INFO [main] de.bender_dv.jvagate.communication.Receiver: GlobalProps loaded

2014-06-09 16:37:22,037 INFO [main] de.bender_dv.jvagate.communication.Receiver: connected to DTAQ DataQueue (system: AS400 (system name: 'localhost' user ID: '*CURRENT'):com.ibm.as400.access.AS400@36783678 path: /QSYS.LIB/JVAGATE.LIB/JAVAQ.DTAQ):com.ibm.as400.access.DataQueue@3d423d42

2014-06-09 16:37:22,633 INFO [main] de.bender_dv.jvagate.communication.Receiver: getOrder

8) STRSQL executing command: connect to ARD400LOC user QSECOFR using 'xxxxxx'

9) command returns in joblog many errors the first is msgid RNX0100

From program . . . . . . . . : QRNXIE
From library . . . . . . . : QSYS
From module . . . . . . . . : QRNXMSG
From procedure . . . . . . : SignalException
From instructions . . . . . : 25

To program . . . . . . . . : PROPERTIES
To library . . . . . . . : JVAGATE
To module . . . . . . . . : PROPERTIES
To procedure . . . . . . : PROPERTIES_loadProperties
To instructions . . . . . : 196

9) every subsequent attemp to execute the command it returns in joblog many errors the first is MCH3402

From program . . . . . . . . : JDBCGATE
From library . . . . . . . : JVAGATE
From module . . . . . . . . : JDBCGATE
From procedure . . . . . . : WORK
From instructions . . . . . : 319

To program . . . . . . . . : JDBCGATE
To library . . . . . . . : JVAGATE
To module . . . . . . . . : JDBCGATE
To procedure . . . . . . : WORK
To instructions . . . . . : 319

after are:

JDBCGATE: SQLCODE: -913 SQLSTATE 57033 ARD400LOC ActivationGroup: 2
JDBCGATE: timeout ocurred - check Server

10) we close batch job JVAGATE and submit again. The same error sequenze RNX0100 at first executin SQl command and MCH3402 at any other attempts

The same happens for SQL command: connect to INTSTD user yyyyyy using 'xxxxxx'.
Moreover we made ADDRDBDIRE RDB(ARD400LOC1) RMTLOCNAME(*ARDPGM) ARDPGM(JVAGATE/JDBCGATE), and DONT put any reference in conf\global.properties.
Executing SQL command connect to ARD400LOC1 user QSECOFR using 'xxxxxx' we get the same errors first time RNX0100 and second MCH3402 even there is no refence in
global.properties for this Db.

ArdGateLog.log doesn't change because (we think) is not interested in the problem. May be some kind of Java bug on IBM i ? Or what else ?
Seems the first msgd RNX0100 caused by param error and successsive execution cant find program anymore in stack...maybe we are wrong.
After one week of tests me and my colleagues have no more ideas.

Sorry for my terrible english and gratefull for your help.

[Dieter Bender]

in all cases of error/problems I need:
- a description what you are trying
- a description of the error situation
- your global.properties
- the joblog
- the java log with level set to debug
to get the last:
change log4j.properties, uncomment (delete # in following line)

log4j.logger.de.bender_dv.ardgate=DEBUG

restart the server

In your case it might be a corrupted global.properties (missing CRLF or lots of following blanks) this might happen by your editor.

D*B

[Dieter Bender]

CCSID problem reading global.properties from RPG (# is not translated consistent for diffrent CCSIDs of Job). Fixed with Release 2014-06-12 (installing PROPERTIES.SRVPGM would be sufficient)

D*B