something weird going on : cant read the read off delploy di

[wiggy]

what is going on. My eclipse deploy wont work at all now

restarted my server and repoplyed the ear and get this ...

i've looked in the server exploded dir directory and its all there - why does it think it has a problem???

16:21:54,800 WARN [HDScanner] Scan failed
org.jboss.deployers.spi.DeploymentException: Exception determining structure: AbstractVFSDeployment(temp-ear.ear)
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:85)
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1000)
at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)
at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:267)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.RuntimeException: Error determining structure: temp-ear.ear
at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:293)
at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:73)
at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:196)
at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:221)
at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77)
... 15 more
Caused by: java.lang.RuntimeException: temp.war module listed in application.xml does not exist within .ear vfsfile:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/
at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:272)
... 19 more

[wiggy]

tried to restart the server with the ear left in the deploy directory this time - and it restarted with it okay

what is going on in the server - why does it get confused

[rob.stryker]

Hi Wiggy:

What version of the AS are you using? If you're using 5.0.x then I regret to inform you that those versions of the AS removed the suspend ability of the Deployment scanner, and so the deployment scanner is reading the folder before the entire structure is deployed.

A workaround would be, after receiving this message, to go touch the descriptor file in the deploy folder of the related application, or to "touch" the descriptor inside eclipse and do an incremental publish.

[wiggy]

okay - i'm using jboss 5.0.1

is that a feature or a bug ?

i suspect the latter - havnt tried to touch on the deploy descriptor yet -

i presume its a bug - is this planned to be fixed or do we have to live with it ?

I presume this is an issue with the AS then and not jboss tools. If i go back to As 5.0.0 does not have the problem? I have no specific burning problem requiring 5.0.1, and if gets rid of the problem i think i'd rather revert than live with the workaround until a fix is declared

:)

[rob.stryker]

Hi Wiggy:

It's not a bug... its a removed feature in the entire 5.x stream. They rewrote the microkernal from a JMX kernal to the microcontainer kernal and never exposed the ability to suspend and resume the deployment scanner.

https://jira.jboss.org/jira/browse/JBAS-6330

It's been re-added in the 5.1.x branch, but not in the 5.0.x stream yet because it's uncertain whether there will be a 5.0.2. If there is indeed a 5.0.2, then this will be added to it, but if not, we'll have to wait for 5.1.

Sorry =/

[wiggy]

well thats a bother -

however thanks for digging that one out - i guess we'll just have to run with it until we get 5.1 up and out

however if the post helps other people with similar gripe then thats good

how long do we have to wait to get a 5.1?