I always see this happening too, especially as the EAR gets larger, contains
WARs etc.
It starts to fill up your server.log with a bunch of junk. If you use JMX
to deploy your EAR from a directory not under JBoss, the next time you
restart JBoss it isn't deployed anymore!
We tried having our maven scripts copy the EAR into server/default,
undeploying and deploying, this helped a little.
Finally we just did this: open your server/default/conf/server.xml and save
it, or just touch it somehow. JBoss sees this and clears the server.log in
a few moments.
this is a real kludge, but it clears up the server.log
----- Original Message -----
From: "Stephane Nicoll" <[EMAIL PROTECTED]>
To: "Maven user list (E-mail)" <[EMAIL PROTECTED]>
Sent: Friday, January 09, 2004 2:00 AM
Subject: Jdom 0.7.jar with META-INF/info.xml displays a uncomplete
deployment when put in the deploy directory
Hello list,
I think the problem is related to JBoss deployers so I am gonna ask this
here.
BTW, we use JBoss 3.2.1 - Redhat Linux
We have an ear that contains some libraries we use only in our application
(ear). That way we have only file to deploy and we are sure everything is
there. We use jdom (version 0.7) wich contains a META-INF/info.xml file.
When we deploy our ear, everything is ok but this log entry at the end of
the
deployment:
2004-01-09 10:55:39,482 ERROR
[org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException:
Exception
in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[EMAIL PROTECTED] {
url=file:/var/jboss-3.2.1-kpserver2/server/default/tmp/deploy/server/default
/
deploy/kserver-mr-1.10.0-RC1.ear/38.kserver-mr-1.10.0-RC1.ear-contents/jdom-
0
.7.jar }
deployer: null
status: Starting
state: START_SUBDEPLOYMENTS
watch:
file:/var/jboss-3.2.1-kpserver2/server/default/tmp/deploy/server/default/depl
oy/kserver-mr-1.10.0-RC1.ear/38.kserver-mr-1.10.0-RC1.ear-contents/jdom-0.7.
j
ar
lastDeployed: 1073642108245
lastModified: 1073642106000
mbeans:
]Incompletely deployed packages:
<none>
MBeans waiting for classes:
<none>
MBeans waiting for other MBeans:
<none>
This is not really annoying because everything works ok but if you could
give
me a trick to avoid that message.
Regards,
Stephane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
