RAC on iSeries [message #35849] |
Wed, 19 October 2005 09:38 |
Eclipse User |
|
|
|
Originally posted by: bruno.denys.dekamer.be
Dear reader,
"Hyades" doesn't seem to work on a V5R3 iSeries Server. I'd like to
perform more troubleshooting, but cannot proceed by lack of appropriate
log files. Anybody a clue?
Environment: HYADES data collection engine as shipped with IBM's WebSphere
Studio Site Developer v5.1.2. Installation instructions as explained in
the /opt/hyadesdc/getting_started.txt were executed. I am not able to
find the exact version number of this runtime code.
Starting the hyades data collection engine works fine and after modifying
the serviceconfig.xml I am able to retrieve a lot of debug, warning and
information messages in the logfile.
The main problem is that remotely launching my iSeries WAS Express
instance (v5.1.1.4) doesn't work (starting it localy is no pbm). The
Raserver succeeds in launching a process named Q5BVAJVM, but this fails
with an errormessage MCH74A0.
In more detail: According to the RASERVER's logfile, the process which
RASERVER should launch is
wteCommandQueryV51.exe -Dcom.ibm.ws.management.launcher.ignoreDebug=true
com.ibm.etools.websphere.tools.internal.query.launch.RemoteS erverLaunchCommandQueryServer
/QIBM/UserData/WebASE51/ASE/config 'I5TEST_wsddTest' 'I5TEST_wsddTest'
'wsddTest'
-Dcom.ibm.websphere.servlet.temp.dir=/QIBM/UserData/WebASE51 /ASE/temp
-Dworkspace.user.root=/QIBM/UserData/WebASE51/ASE/wstemp
-Dinstance.name=wsddTest
-Dcom.ibm.ws.messaging.JMSProvider=com.ibm.ws.messaging.JMSE mbeddedProviderImpl
in location /QIBM/ProdData/WebASE51/ASE
The corresponding process actualy being launched is (as can be seen in the
hyades logfile):
iSeries arg�0| to spawn is: '/QSYS.LIB/Q5BVAJVM.PGM'
iSeries arg�1| to spawn is:
'com.ibm.etools.websphere.tools.internal.query.launch.Remote ServerLaunchCommandQueryServer'
iSeries arg�2| to spawn is:
'008034/QIBM/UserData/WebASE51/ASE/config015I5TEST_wsddTest0 15I5TEST_wsddTest008wsddTest069-Dcom.ibm.websphere.servlet.t emp.dir=/QIBM/UserData/WebASE51/ASE/temp056-Dworkspace.user. root=/QIBM/UserData/WebASE51/ASE/wstemp024-Dinstance.name=ws ddTest079-Dcom.ibm.ws.messaging.JMSProvider=com.ibm.ws.messa ging.JMSEmbeddedProviderImpl'
iSeries arg�3| to spawn is:
'/opt/hyadesdc/lib/wasToolsCommonV5.jar:/opt/hyadesdc/lib/wt eServersV5.jar:/QIBM/ProdData/WebASE51/ASE/classes:/opt/hyad esdc/lib/logutil.jar:/QIBM/ProdData/WebASE51/ASE/properties: /QIBM/ProdData/WebASE51/ASE/lib/bootstrap.jar:/QIBM/ProdData /WebASE51/ASE/lib/lmproxy.jar:/QIBM/ProdData/WebASE51/ASE/li b/wasjmx.jar:/QIBM/ProdData/WebASE51/ASE/lib/wasproduct.jar: /QIBM/ProdData/WebASE51/ASE'
iSeries arg�4| to spawn is:
'002042com.ibm.ws.management.launcher.ignoreDebug004true019o s400.stdin.allowed0011'
iSeries arg�5| to spawn is: '10'
iSeries arg�6| to spawn is: '10'
iSeries arg�7| to spawn is: '*NO'
iSeries arg�8| to spawn is: ''
The MCH74A0 with which the Q5BVAJVM.PGM programm abends seems to be the
iSeries errormessage for some sort of a fatal Java Exception. However, no
further detail regarding this message can be found (do you now where to
look perhaps).
Any suggestions to obtain more elements to find a solution are greatly
appreciated.
|
|
|
|
Powered by
FUDForum. Page generated in 0.04134 seconds