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

Dear Chuck,

thank you very much for your answer.

At the moment we are suspecting that the new Windows "PowerShell" is =

used instead of the old "CMD" exe to execute the start script. This =

shell surrogate seems to handle parameters in a very strange way. =

Because the installation was done remote and the server is managed by =

the customer it is difficult to test this out.

Anyway best regards,
Susanne

Am 13.11.2013 21:48, schrieb Chuck Hill:
> At one time Windows had a command line length limit of 1024 characters.
>   I don't know if that is still true.  I have also seen things like this
> when a previous parameter was malformed.
>
>
> Chuck
>
> --
> Chuck Hill
> Executive Managing Partner, VP Development and Technical Services
>
> Practical WebObjects - for developers who want to increase their overall
> knowledge of WebObjects or who are trying to solve specific problems.
> http://www.global-village.net/gvc/practical_webobjects
>
> Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest
> Growing Companies in B.C!
>
> Global Village Consulting ranks 44th in 25th annual PROFIT 500 ranking
> of Canada=92s Fastest-Growing Companies by PROFIT Magazine!
>
> On 2013-11-13 12:25 PM, "Susanne Schneider" wrote:
>
>     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]
>     <mailto:[email protected]>
>     web http://www.secuTrial.de
>
>     ----------------------------------------------------
>     Gesch=E4ftsf=FChrer: Dr. Marko Reschke, Thomas Fritzsche
>     Sitz der Gesellschaft: Berlin
>     Amtsgericht Berlin Charlottenburg, HRB 106103B
>     ----------------------------------------------------
>     _______________________________________________
>     WebObjects-dev mailing list
>     [email protected] <mailto:[email protected]>
>     http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>

-- =

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
----------------------------------------------------