Bug 1087504

This issue is very similar to BZ#1087422 but for Windows there are some other information about input line being too long.

Note that windows command line is limited to 8191 characters, so this could be related to this limit, see [1]

[1] http://support.microsoft.com/kb/830473

Could not reproduce with EAP 5.3.ER3, JON 3.2GA on Windows 2008 server

EAP 6.3 is auto discovered and the stop and start operations work as expected.

I tried again to reproduce on my Windows 2008 with EAP installed in a directory similar to the directory used for test automation:
C:\workspace\eap5-jon-plugin-windows\a28e18c8\eap5unsecured\jboss-eap-5.3\jboss-as

The stop/start sequence works.

On the server resource "Connection Settings" tab, what is the value of your "Start script" property? Mine is empty so the "start" operation uses the default value.

The Start script is filled in my case by the discovery process

I tried again with the "Start script" property set to the script absolute path and it still works.

Can you please build an environment where I can reproduce this bug? The only environment where this problem shows up is a Jenkins slave and the project workspace is cleared after the suite is executed.

Before that happens, I can't see what else I can do.

Created attachment 891196 [details]
Test class to reproduce issue

I eventually managed to reproduce the issue on a Windows 2008R2 box with a test class (attachment 891196 [details]).

The problem is that EAP5.3 needs the "OS" environment variable to be set:
== line 9
@if "%OS%" == "Windows_NT" setlocal enableextensions enabledelayedexpansion
==

If it is not set, the script goes in infinite loop here:
== line 22
:LoopArgs
for /f "usebackq tokens=1,*" %%A in ('!params!') do (
==

After some time, the cmd process ends with error message "Input line is too long"

JON team needs to update the EAP5 server discovery class (add the "OS" environment variable to the list of discovered env properties).

I had a look at the EAP5 server discovery class, the environment variables discovery process relies on the ServerStartScriptDiscoveryUtility class. And ServerStartScriptDiscoveryUtility actually looks up for the "OS" variable.

That's why it worked for me on Windows 2008 (see comment 2).

So now we need to understand why on your QE box the variable is not discovered. How do you start the EAP5.3 server process before discovery? Via Cygwin? Do you by accident start run.sh instead of run.bat?

It is started using run.bat via CMD. [1] this is the precise command used, first part of the command is a way to start the process and assigning it an identifier useful for PID detection.

Note, both EAP 5.2 and 5.3 are started the same way.


[1] cmd /C start "1776016263" /min run.bat -c default -b localhost

I tried again this morning and could not reproduce (on a Windows 2008R2 machine).

The only thing I can imagine is that, for some reason, the process environment cannot be determined. This could be because the RHQ Agent is running as a user without the required privilege.

Which user are your running on:
* the RHQ agent?
* the EAP 5.3 instance?

Can you attach the agent log at DEBUG level?

As there is insufficient data on this and it is not clear if this is even a bug and was only reported against an unreleased product, I am marking this as WORKSFORME.