>> "and started the server in standalone mode. the server log shows started in 3657ms - Started 151 of 189 services."
That indicates your JBoss is up and running.
By deploying (and enabling) a war you should see some lines like this (tested with default configuration):
14:53:51,044 INFO [org.jboss.as.repository] (HttpManagementService-threads - 1) JBAS014900: Content added at location /path/jboss-eap-6.3/standalone/data/content/aaa/bbb/content
14:53:54,638 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "example.war" (runtime-name: "example.war")
14:53:55,605 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /example
14:53:55,889 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS018559: Deployed "example.war" (runtime-name : "example.war")
That means your war is deployed, do you have these lines ?
You won't see "started in xxx ms - Started aaa of bbb services." again, which only takes place at the end of EAP startup, not on the deployment operation.
I have checked the logs am able to find the JBAS014900, JBAS015876, JBAS018210 in the logs but unable to find the JBAS018559
These are appearing only when deploying only one application. but after deploying another application am unable to access the second deployed application.
It is throwing below error and even unable to see the above JBAS014900, JBAS015876, JBAS018210 in logs for the second application deployed.
JBWEB000236: Servlet.service() for servlet ComponentDispatcher threw exception: java.lang.NoClassDefFoundError: Could not initialize class org.owasp.esapi.reference.DefaultValidator
at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_21]
at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_21]
at org.owasp.esapi.util.ObjFactory.make(ObjFactory.java:74) [esapi-2.1.0.jar:2.1.0]
at org.owasp.esapi.ESAPI.validator(ESAPI.java:191) [esapi-2.1.0.jar:2.1.0]
How do you deploy your app. ? Suggest to use the web console at 9990 port or CLI command line to deploy the war or ear file, try to avoid using exploded depoyment folder.
"NoClassDefFoundError" means unable to find the class "org.owasp.esapi.reference.DefaultValidator", make sure you have this class packaged within your app. deployment file.
Am deploying the application by using web console running on port 9990
esapi.jar already present in WEB-INF/lib folder of the application war
Initially deployed the application using web console it got deployed and able to access then tried to deploy the copy of the application.
Tried like deploying the same application twice like application1.war and application1copy.war in this scenario also unable to access the second application being deployed. getting the same error as mentioned above.
If you're using web console, add the .war file first then "Enable" it, and seeing no "JBAS018559: Deployed "xxx.war" (runtime-name : "xxx.war")" messages from the log,
I'd guess the deployment was probably not finished yet. do you have any warning/error during the deployment ? do you see the deployment status changed in web console ?
Generally the ClassNotFoundException / NoClassDefFoundError is caused by missing the required class in classpath, or duplicated jar / class files
You can use a tools named Tattletale (Tattletale - JBoss Community) to troubleshoot this, details are introduced here if you have a RH subscription :
Do you have "NoClassDefFoundError" when accessing the first deployed "application1.war " ? (I mean, don't deploy the 2nd one application1copy.war)
using web-console i have deployed & enabled the application and can see the logs with the below messages
JBAS014900: Content added at location
JBAS015876: Starting deployment of "application.war" (runtime-name: "application.war")
JBAS018210: Register web context: /application
but the message is not appearing "JBAS018559: Deployed "xxx.war" (runtime-name : "xxx.war")"
Able to access firstly deployed application with out issues.
After a while deploying the secondary application and enabled (copy of the application) it is throwing the class not found error. but still able to access the firstly deployed app.
Sorry I failed to reply this earlier.
I have no idea why you could deploy it once successfully and 2nd time it got NoClassDefFoundError.
war deployments should be seen as separate modules so they shouldn't have impact on each other (unless they have conflict such as using same).
If you're able to upload the full logs on deployment, and a reproducer deployment war file, then I may have a further look ... ...
>> but the message is not appearing "JBAS018559: Deployed "xxx.war" (runtime-name : "xxx.war")"
It should be printed out, have you ever changed any logging configuration ?