Configure JBoss' default startup timeout through Arquillian?

[michaelschuetz]

Hi to all,

I need to configure JBoss' default startup timeout.

I did find following posts:
http://community.jboss.org/wiki/HowToRunTheTestsuite
http://community.jboss.org/thread/89112?tstart=0

It mainly says:
###
Increasing server startup timeout
By default jboss-test's <server:start> task waits for 120 secs for the server to start up.
If you're server config takes more than 120 sec to startup with additional services deployed or on a really slow system you can override the server startup timeout by setting the jbossas.startup.timeout property.

export ANT_OPTS="-Djbossas.startup.timeout=240"
###

Would expect to find such parameter in arquillian.xml, but there is none. Is there a reason for that?

Thanks for quick status on this.

Cheers
Michael

[aslak]

have you tried using the javaVMArguments option in arq.xml ?

There is no special handling of those arguments except string splitting, so as far as I can tell, so you should be able to passin both -X or -D type arguments.

I assume your talking about a Managed Container:  http://docs.jboss.org/arquillian/reference/latest/en-US/html_single/#container.jbossas-managed-6.configuration

[michaelschuetz]

Aslak, will try that.

cheers

Michael

[abendt]

Hi,

i think javaVMArguments in arquillian.xml is not the correct place to set that option. set there it would be only available in the JVM of the AS. However the JUnit JVM is the one waiting for the AS to come up. So If you are using Maven I think the correct place is the configuration of your maven-surefire-plugin:

{code:xml}
<plugin>
  <artifactId>maven-surefire-plugin</artifactId>
  <configuration>
    <systemPropertyVariables>
      <jbossas.startup.timeout>240</jbossas.startup.timeout>
    </systemPropertyVariables>
  </configuration>
</plugin>   
{code}

best regards,

   Alphonse Bendt

[aslak]

Yes, correct. I missed that one.

They will be passed on to the starting Server, but have no effect there. They are read directly from System.getProperty in ServerManager.