Any idea i need to fix this .......
the log is full of other errors, I think the one you see is just the tip of the iceberg. I assume that the "old" app you deploy contains a whole lot of JAR files. There seems to be an XML parser (Xerces?) included => remove all xml parser files, because they will "confuse" JBoss.
And check whether the app also bundles classes/jars with e.g. annotations of the JavaEE standard. Those should also be removed.
If you cannot resolve the problems yourself, please post a list of all JAR files of your app.
Really i tried my best but not able to resolve this problem now i get the new server for the clean installation.
First I install the jdk 1.6 and then jboss-5.1.0.GA.
When I run jboss without putting any war file then only get logging.xml and vfz type error.but when i put the war file of my application then got many error telling me deployment is failed.At the same time I put the jboss 4 and application start running.
Now it seems like there is something in the application which causing the issue. I am listing down the jars file i am using for this application
I really need to resolve this in this weekend saturday +sunday and i really need expert advise to resolve this.
Waiting for your quick reply
wolfgang any direction for me? can i share war file with you guys so that you can test your self
remove those files, because they conflict with JBoss bundled JARs:
Hope this helps
where should i place these files common\lib
You don't need to deploy them at all to the server.
The "j2ee" classes/interfaces are somewhere in JBoss jars. Log4J is also bundled with the server. And it contains also a XML parser. I don't know whether it is also Xerces, but at least there is working XML parser. And if your own app also contains Xerces or another XML parser, it will not work.
So maybe you need those libraries at compile time (depending on the way you compile your app), but don't deploy them to JBoss.
PS: No more replies for today - it is after midnight now ;-)
I really appreciate your help in resolving my issues removing these three jar files from deployment has resolved the issue.
Glad I could help ;-)