start parameters were not transfered from WOMonitor during application startup on Windows server 2012

Hi all,

recently we had a strange problem with an installation at a customer's =

site: some start parameter entered as "additional arguments" in the =

WOMonitor application configuration got lost when starting the =

application. For example, the "-Xmx512m" configuration for the Java heap =

size was not handed over to the application. It was a little unclear if =

none or only some of the parameters got lost because for most of the =

parameters there is a working default if unset. The siteConfig.xml =

looked ok, all parameters entered in the WOMonitor were there.

The installation was done on a Windows Server 2012. As a first =

workaround we added the necessary parameters in the start script =

itself(.cmd). Previous installations on either linux or other windows =

versions worked without issues.

So, did anybody here ever experienced a similar problem? As far as I =

understand the situation the applications are started from the =

TaskDaemon (working as a service on the windows server) by calling =

(how?) the "Application.cmd" script and handing over the WO and =

additional parameters.

I would be very thankfull if anybody has any hint on what might by going =

wrong!

Best regards
Susanne
-- =

Susanne Schneider
Coordinator secuTrial Development

iAS interActive Systems GmbH
Dieffenbachstra=DFe 33 c, 10967 Berlin

fon    +49 30 22 50 50 - 498
fax    +49 30 22 50 50 - 451
mail   [email protected]
web    http://www.secuTrial.de

----------------------------------------------------
Gesch=E4ftsf=FChrer: Dr. Marko Reschke, Thomas Fritzsche
Sitz der Gesellschaft: Berlin
Amtsgericht Berlin Charlottenburg, HRB 106103B
----------------------------------------------------