daniele.ulrich wrote : OK, I spent some time to reproduce the error with a
sample application.
|
| Steps to reproduce the error:
|
| jboss-5.1.0.GA on Windows or Solaris
| patch default configuration with jbossws-metro-3.2.1.GA
http://jboss.org/file-access/default/members/jbossws
jaikiran wrote : If it's possible, could you please attach the application
which reproduces this issue, to that JIRA?
Sorry, this is not possible because there are a) too many dependencies and b) I
am not allowed to post code of the enterprise I'm working for.
It is exactly the same behaviour
All of the sudden we were facing the same problem in our PROD environment while
on all other environments we don't have this issue. We are running a 4.2.3.GA
and have 3 wars in one ear. The only way we could solve the problem is to take
the wars outside the ear. As the wars depend on jars in
daniele.ulrich wrote : All of the sudden we were facing the same problem in
our PROD environment while on all other environments we don't have this issue.
We are running a 4.2.3.GA and have 3 wars in one ear. The only way we could
solve the problem is to take the wars outside the ear
Hi jaikiran
The ear with the content listed below was running for a year without problems
in all our environments. Now it does not run in PROD anymore; that's why I
doubt that it helps to analyze the content. But I appreciate your help!
mpu.ear:
META-INF/
META-INF/MANIFEST.MF
Hi jaikiran
You wanted it, now you get it:
12:35:11,995 INFO [TomcatDeployer] deploy, ctxPath=/ssimpu,
warUrl=file:/opt/sp/messaging/tmp/deploy/tmp63416mpu.ear-contents/ssimpu-war-18.1-exp.war/
12:35:12,102 WARN [ServiceController] Problem starting service
