Eman Ali al-Maktari [IT Department] wrote:
> Dear Andrew,
I tried on both 4.0.5 and 4.2.1, both on Windows and Linux
For the Deployment I tried the two methods: deleting then copying, and overwriting.
I checked the temp folder it's clean.
Do you think it's normal?
err, no not really, I don't know how JBoss can do something like this.
What does the app in your war file do? It might be causing the problem.
Have you had the same problem with other war files? If you can compare
apps which work and others which fail then this might tell you something
about what is happening.
Also, might you still have a client process running when you do the
redeploy? This could cause the problem (although I would have expected
it merely to cause JBoss to delay the redeploy).
If it *is* JBoss code which is locking the port then look for server log
and console log warnings/errors before and after the deploy to see if
they shed any light on what is going on.
Actually look for these anyway [the log is your friend :-]. You might
need to configure trace in some of the code to get the information you
need but I suggest you start by looking for warnings/errors and progress
from there to identify what trace to enable.
If you cannot identify anything after checking these things you could
take it to the JBoss AS forum or, if you have a support contract, to the
support portal.
regards,
Andrew Dinn (JBoss Transactions)
--------------------------------
JBoss, a Division of Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire,
SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903
Directors: Michael Cunningham (USA), Charlie Peters (USA) and David
Owens (Ireland)
