-
1. Re: Cannot redeploy MBean on JBoss3.0.0CR1
adrian.brock Apr 24, 2002 7:09 AM (in response to qwang)I saw something similar on the dev-list similar.
It related to the system clock. Where you develop on one
machine, copy to another, the timestamps can be different,
or it might have been something to do with time zones?
I believe the deployment code was changed so that the
timestamp comparison was consistent.
It always compares the timestamp of the original files, rather than comparing the timestamp
of the original file against the temporary copy.
If this is not your problem, all I can say is that it
works for me, including errors during deployment
(assuming the deployment doesn't loop/block during
startup).
Regards,
Adrian -
2. Re: Cannot redeploy MBean on JBoss3.0.0CR1
qwang Apr 24, 2002 9:43 AM (in response to qwang)Thanks for replying.
It seems to me that the problem is not caused by the differences between the timestamps of the files because I deployed the newly build SAR file on the same machine.
Are you using the latest version of JBoss3 checked out from CVS or the CDR1? I am using CR1.
Regards.
qwang -
3. Re: Cannot redeploy MBean on JBoss3.0.0CR1
adrian.brock Apr 24, 2002 10:50 AM (in response to qwang)Latest(ish) CVS both 3.0 and 3.1 branch.
Are you getting undeploy messages?
Are you getting any messages?
Perhaps you can show the bottom of the log?
Regards,
Adrian -
4. Re: Cannot redeploy MBean on JBoss3.0.0CR1
qwang Apr 29, 2002 5:46 AM (in response to qwang)Hi Adrian,
It seems to me that JBoss-3.0.0-RC1 has the following problems in deploying and redeploy a SAR file:
1. When a deploy a SAR file, it cannot find the classes included in a JAR file in the SAR file and cannot open the JAR files included in the SAR file, it has the following messages come out:
org.jboss.deployment.DeploymentException: could not create mbean; - nested throw
able is: RuntimeErrorException: com.systemsunion.framework.services.deployment.E
voDeployer constructor has thrown an error: java.lang.NoClassDefFoundError: com/
systemsunion/framework/errors/SSException
...............................
.................................
10:39:08,396 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/log4
j.jar which could not be opened, entry ignored
10:39:08,396 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/jdom
.jar which could not be opened, entry ignored
10:39:08,396 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/xerc
es.jar which could not be opened, entry ignored
10:39:08,396 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/cast
or-0.9.3.9+-xml.jar which could not be opened, entry ignored
10:39:08,396 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/fram
ework-errors.jar which could not be opened, entry ignored
10:39:08,396 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/fram
ework-errors-resources.jar which could not be opened, entry ignored
10:39:08,406 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/fram
ework-util.jar which could not be opened, entry ignored
10:39:08,406 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/fram
ework-util-resources.jar which could not be opened, entry ignored
10:39:08,406 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/fram
ework-repository.jar which could not be opened, entry ignored
10:39:08,406 WARN [MainDeployer] The manifest entry in file:/H:/evodev/Evolutio
n/framework/services/deployment/build/lib/framework-deployment.sar references UR
L file:/H:/evodev/Evolution/framework/services/deployment/build/lib/library/fram
ework-repository-resources.jar which could not be opened, entry ignored
And then, it prints out a message saying that the MBean is deployed:
10:39:12,291 INFO [MainDeployer] Successfully completed deployment of package:
file:/H:/evodev/Evolution/framework/services/deployment/build/lib/framework-depl
oyment.sar
2. When redeploy the SAR file, the EJB JAR file deployed previously is not replaced by the new EJB JAR file included in the SAR file and the old EJB JAR is deployed instead.
Any ideas on the problems. I am running JBoss-3.0.0-RC1 on a Windowns2000 platform.
Reards
Qingxian