-
15. Re: nightly builds
peter craddock wrote:
We managed to get the application deployed by first starting the server then adding the war and ears to the deployments directory. Starting the server with the apps in the deploy directory fails with a duplicate resource error.
Now we have started the application we have been able to test the ejb lookup this still fails with a null pointer.
Let's take a step back. Get a clean nightly build. Place your deployments in the deployments folder and start the server. If you run into problems with that then post the relevant details including exception stacktrace(s).
-
16. Re: nightly builds
Ok
If the application server is started with an app in the deployments dir we get the following
14:24:48,608 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jquery.war"
14:24:48,608 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "cp.ear"
14:24:48,629 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("add") failed - address: ([("deployment" => "cp.ear")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"cp.ear\")]"
14:24:48,639 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"cp.ear\")]"}}
14:24:48,648 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) undefined
This is fine if we start the server then copy in the applications
-
17. Re: nightly builds
Are you sure this is a clean installation? I suspect you are using some changed standalone*.xml files which probably have a deployments element in there. Can you quickly check that?
-
18. Re: nightly builds
I am taking the nightly build then running a script to copy the shipped standalone-full.xml file to abs.xml then altering this to set certain values I need.
I tried to start the server using the standalone-full.xml and still get the same errors as I get when running using abs.xml
-
19. Re: nightly builds
Hi
Did you manage to find out what was causing the duplicate resource exception ?
We are experiencing this intermittently against 7.2.0.Alpha1 build from cb72a7cd1669131b28a552f1dbf3c2582ad19813 with a standalone server.
-
20. Re: nightly builds
we did not we worked round the problem by dropping the ear and war files in after the server had started
-
21. Re: nightly builds
If this is reproducible, please create a JIRA with the details and if possible attach an application which reproduces this issue.
-
22. Re: nightly builds
Ahhh, ok.
I am wondering in our case if it might be due to the frequency of the deployment scanner and the latency of the operating system's IO operations during the initial deployment.
Did you try altering the scan-interval attribute on the deployment-scanner in the standalone.xml from what appears to be the shipped default of 5 seconds to something higher ?
-
23. Re: nightly builds
I have been using a standard script to configure each build and the scanner has been setup like this
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="300000" auto-deploy-zipped="true" auto-deploy-exploded="true"/>
I also tried to use the shipped standalone.xml and that caused the same problem
-
24. Re: nightly builds
Hmm,
Well... I just tried lots of different scan-interval setting from 25 to your figure of 300000, but I cannot reproduce the error with my build. If you can reproduce it every time, as jaikiran suggests, it would definitely be worth submitting a jira.
-
25. Re: nightly builds
I have not tried it for some time I will get the latest nightly build down and have a go tomorrow