CGJ,

> When you remove the file, isn�t there an undeployment message in the
> console?

### pasted from origional message

14:00:14,041 INFO  [org.jboss.deployment.MainDeployer] Undeployed
file:/D:/programs/jboss-src/jboss-all/build/output/jboss-3.1.0al
pha/server/default/deploy/ind-term.wsr

### end

> Do you really put the wsr into an auto-deploy directory?

/server/default/deploy

Should I put it somewhere else?

> Which jboss version and which OS are you running?

  w2k, jboss build from latest src last week, jdk 1.4.0.

> Is hot-deployment with ears working for you?

Is there an .ear that I can test this with?  I have tried a .war (vqwiki
1.8.1), and was unable to delete the version of the .war in the deploy
directory, due to a (windows) access restriction error.

I intend to get the latest source for JBoss at some point -- perhaps someone
already checked something in this week that fixes this...

  - Matt

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jung , Dr.
Christoph
Sent: Wednesday, July 24, 2002 10:12 AM
To: '[EMAIL PROTECTED]'
Subject: AW: [JBoss-user] Undeployment of .wsr incomplete due to access
restriction


Your first procedure (even without deleting the .wsr) should work.

When you remove the file, isn�t there an undeployment message in the
console? Do you really put the wsr into an auto-deploy directory? Which
jboss version and which OS are you running? Is hot-deployment with ears
working for you?

CGJ

-----Urspr�ngliche Nachricht-----
Von: Matt Munz [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 24. Juli 2002 15:11
An: [EMAIL PROTECTED]
Betreff: RE: [JBoss-user] Undeployment of .wsr incomplete due to access
restriction


CGJ (& anyone else familiar with JBoss deployment),

> This is IMHO true for all jars/sars/ears/etc deployed in jboss and
> therefore, the tmp directory is not deleted until the next startup of
Jboss.

O.K., I'll buy that.  Let me rephrase my question.  I'd like to be able to
deploy, undeploy, and re-deploy my web service without restarting JBoss.  Is
this even possible?  If so, how can I do this?  I have tried the following
procedure without success.

1) copy .wsr to deploy directory
2) remove .wsr from deploy directory
3) copy new version of .wsr to deploy directory

The only procedure I've found that works is

1) copy .wsr to deploy directory
2) remove .wsr from deploy directory
3) restart JBoss
4) copy new version of .wsr to deploy directory

Is there a better way?

- Matt Munz

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jung , Dr.
Christoph
Sent: Wednesday, July 24, 2002 7:24 AM
To: '[EMAIL PROTECTED]'
Subject: AW: [JBoss-user] Undeployment of .wsr incomplete due to access
restriction


Matt,

The tmp/deploy copy is made because of the Java 2 platform holding such ugly
references to the files opened with the (already garbage-collected?)
URLCLassLoader/JarHandler/etc such that you can manipulate the original file
(under server/deploy/wherever) and deploy it a second time in another
classloader.

This is IMHO true for all jars/sars/ears/etc deployed in jboss and
therefore, the tmp directory is not deleted until the next startup of Jboss.

CGJ


-----Urspr�ngliche Nachricht-----
Von: Matt Munz [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 22. Juli 2002 20:26
An: jboss-user
Cc: Jason Weis
Betreff: [JBoss-user] Undeployment of .wsr incomplete due to access
restriction



Hi all,

  w2k, jboss build from latest src last week, jdk 1.4.0.

  Hot deployment of a .wsr works well.  I am having a bit of difficulty with
undeployment, however, as is indicated in the log exerpt below. Essentially,
some sort of dangling reference to the .wsr file (an open stream?), is
preventing the deletion of the copy of the .wsr file located in the
/tmp/deploy directory.  I tried deleting this file through windows explorer
and recieved an access violation error, similar to the ones that I get when
trying to delete a file to which the JVM has a stream open.  The .wsr is
undeployed successfully, but the copy remains (unused) in the tmp directory.

  This means that I must restart the server before re-deploying the .wsr (or
I must rename the .wsr before re-deployment).  Overall, not a major issue
but a small annoyance that perhaps others on this list have encountered...
Any tips would be appreciated.

  - Matt


14:00:13,940 INFO  [org.jboss.net.axis.server.AxisService] About to undeploy
axis descriptor org.jboss.deployment.DeploymentInfo@7
2bd92ec {
url=file:/D:/programs/jboss-src/jboss-all/build/output/jboss-3.1.0alpha/serv
er/default/deploy/ind-term.wsr }
  deployer: org.jboss.net.axis.server.AxisService@408a92
  status: Deployed
  watch:
jar:file:/D:/programs/jboss-src/jboss-all/build/output/jboss-3.1.0alpha/serv
er/default/tmp/deploy/server/default/deploy/i
nd-term.wsr/62.ind-term.wsr!/META-INF/web-service.xml
  lastDeployed: 1027360788582
  lastModified: 1027360788562
  mbeans:
, stop step.
14:00:13,981 INFO  [org.jboss.net.axis.server.AxisService] About to undeploy
axis descriptor org.jboss.deployment.DeploymentInfo@7
2bd92ec {
url=file:/D:/programs/jboss-src/jboss-all/build/output/jboss-3.1.0alpha/serv
er/default/deploy/ind-term.wsr }
  deployer: org.jboss.net.axis.server.AxisService@408a92
  status: Deployed
  watch:
jar:file:/D:/programs/jboss-src/jboss-all/build/output/jboss-3.1.0alpha/serv
er/default/tmp/deploy/server/default/deploy/i
nd-term.wsr/62.ind-term.wsr!/META-INF/web-service.xml
  lastDeployed: 1027360788582
  lastModified: 1027360788562
  mbeans:
, destroy step.
14:00:14,031 WARN  [org.jboss.deployment.DeploymentInfo] Could not delete
directory file:/D:/programs/jboss-src/jboss-all/build/ou
tput/jboss-3.1.0alpha/server/default/tmp/deploy/server/default/deploy/ind-te
rm.wsr/62.ind-term.wsr restart will delete it
14:00:14,041 INFO  [org.jboss.deployment.MainDeployer] Undeployed
file:/D:/programs/jboss-src/jboss-all/build/output/jboss-3.1.0al
pha/server/default/deploy/ind-term.wsr



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to