I've been working with the issue I mentioned in an answer posted Feb 22 in the thread
702666
Everything works fine when I'm running my application while logged in to the Windows server via MSTCS. When I'm not logged in and the application is running from Scheduled Tasks, the rwserver processes fail and die. The reason why they fail seems to be that they can't connect to the namingservice (I'm using the COS discovery mechanism).
More experiments have led me to conclude that the namingservice though actually running is not accessible (unless I'm logged in via MSTSC as it is) when the system has been restarted with the Windows utility shutdown.exe but things work fine when the system has been restarted "manually" using the Start menu/Shutdown and giving a "Planned" reason for the restart. It does not appear to be related to the NIC-count (with reference to the thread mentioned above).
I want to be able to reboot the machines in my environment programmatically as part of an autonomous error recovery scheme and I have been using the shutdown command otherwise successfully like so:
shutdown /r /f /t 0 /d p:4:1 /c "MDServer automatic reboot"
During my experiments it has made no difference to omit the /t 0 (thus giving the default 30 seconds timeout) and/or the /c (thus attaching no comment to the restart). Also I have tried various /d [p:]xx:yy choices without any luck.
Does anybody have any idea what it is that makes Windows (or perhaps some Oracle component) behave differently when the machine has been rebooted with shutdown.exe from when it has been rebootet "by hand"?
Here are some installation and configurations details:
Running Oracle IAS Reports And Forms 10.1.2.0.2 on Windows Server 2003 SP2
Previously ran namingservice.bat with a shell command in my application and logged this output repeatedly from the script when the problem occurred>
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
Navngivningsserver svarer ikke. Genstarter..
Navngivningsservice er startet
(The two last lines are Danish meaning something like:
Naming server does not respond. Restarting..
Naming service is started)
I'm now having opmn run the namingservice. To that end I added this to opmn.xml:
<ias-component id="namingservice" status="enabled">
<process-type id="namingservice" module-id="CUSTOM">
<environment>
<variable id="PATH" value="XXXXXX\jdk\bin"/>
</environment>
<process-set id="namingservice" numprocs="1">
<module-data>
<category id="start-parameters">
<data id="start-executable" value="XXXXXX\jdk\bin\orbd"/>
<data id="start-args" value="-ORBInitialPort 14021"/>
</category>
</module-data>
</process-set>
</process-type>
</ias-component>
In the reports rwnetwork.conf I indicated to use namingservice thus:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE discoveryService SYSTEM "file:XXXXXX/reports/dtd/rwnetworkconf.dtd">
<discoveryService>
<!--multicast channel="228.5.6.7" port="14021" timeout="1000" retry="3"/-->
<namingService name="Cos" host="XXXXXXXX" port="14021"/>
</discoveryService>
In the trace output from my rwserver processes I get when the problem occurs:
2009/2/22 3:49:51:968 Exception 56114 (): Bind to naming server failed :org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
oracle.reports.RWException: IDL:oracle/reports/RWException:1.0
at oracle.reports.utility.Utility.newRWException(Utility.java:756)
at oracle.reports.server.RWServer.startServer(RWServer.java:889)
at oracle.reports.server.RWServer.jniMain(RWServer.java:243)
Best regards
Jakob