mtrottier
Well Known Member
Has anyone ever used RUNUBE/RUNUBEXML with a Windows Clustered Enterprise Server?
We can run it fine on our DEV/TEST Enterprise Server so I know we are using the proper format but it will not work on the production clustered environment.
I'm fairly certain that the problem is being caused because actual physical server names are ERP1 and ERP2 with a Windows cluster name of ERPCLUST but as when you define a cluster in JDE you give a third name like ERPSVR.
We we run the RUNUBE command a log is created for the UBE being submitted but after a while IPC errors appear in the log indicating that it cannot communicate with the METADATA kernel. (see errors below)The job also never appears in the WSJ table for the cluser name becuase I believe the RUNUBE command is not cluster aware.
I can try changeing the ipcstart value but I don't really think that will help.
10508/18764 MAIN_THREAD Mon Oct 20 12:43:59.908000 ipcmisc.c299
process 10508 <RUNUBE> registered in entry 49
10508/18764 MAIN_THREAD Mon Oct 20 12:43:59.923000 Runube.c724
Startup for User=BVRUNNER, Env=PD812, Role=*ALL, Report=ROOO6P, Version=XJDE0001
10508/18764 MAIN_THREAD Mon Oct 20 12:43:59.923001 Runube.c751
bAPListening=0
10508/18764 MAIN_THREAD Mon Oct 20 12:45:30.004000 SpecCnvrt.c2002
METADATA - Attempted to send Metadata Kernel a message 3 times and did not recieve a reply. Returning failure to the caller. The Metadata Kernel is Kernel #30 in the jde.ini and the message ID being sent to the kernel is 15751.
We can run it fine on our DEV/TEST Enterprise Server so I know we are using the proper format but it will not work on the production clustered environment.
I'm fairly certain that the problem is being caused because actual physical server names are ERP1 and ERP2 with a Windows cluster name of ERPCLUST but as when you define a cluster in JDE you give a third name like ERPSVR.
We we run the RUNUBE command a log is created for the UBE being submitted but after a while IPC errors appear in the log indicating that it cannot communicate with the METADATA kernel. (see errors below)The job also never appears in the WSJ table for the cluser name becuase I believe the RUNUBE command is not cluster aware.
I can try changeing the ipcstart value but I don't really think that will help.
10508/18764 MAIN_THREAD Mon Oct 20 12:43:59.908000 ipcmisc.c299
process 10508 <RUNUBE> registered in entry 49
10508/18764 MAIN_THREAD Mon Oct 20 12:43:59.923000 Runube.c724
Startup for User=BVRUNNER, Env=PD812, Role=*ALL, Report=ROOO6P, Version=XJDE0001
10508/18764 MAIN_THREAD Mon Oct 20 12:43:59.923001 Runube.c751
bAPListening=0
10508/18764 MAIN_THREAD Mon Oct 20 12:45:30.004000 SpecCnvrt.c2002
METADATA - Attempted to send Metadata Kernel a message 3 times and did not recieve a reply. Returning failure to the caller. The Metadata Kernel is Kernel #30 in the jde.ini and the message ID being sent to the kernel is 15751.