If you right-click on the Server you can bring up the admin console. Bring up the admin console and look for the Applications link and look at the various projects that have been deployed. Undeploy any projects that you have previously deployed. Don't get rid of the admin console! But if you see any of your old project, or current one, on the server, delete them.
Save the changes after the delete, and restart the server. Then, try to redeploy and see what happens.
Just an idea, but it's worked for me in the past. I would keep an eye out for those log files. There's got to be some type of information being logged when either it doesn't deploy, or undeploys.
Joined: Mar 18, 2009
This is the only project deployed on the server, for sure, plus, the 9090/admin is not an available option when righ-clicking the server.
The logs in the console are so poor and mediocre. It just tells me that some reference ResourceRef on the deployment descriptor is not found. I guess is talking about the ibm-web-bnd.xmi file but nothing seems off about that file.
Also, the option on right click is "Run administrative console" not 9090/admin and the port for admin console is not 9090 but 9060.
By the way the ResourceRef is referring to some resource on the server that you have not set up. Check the details of resource-ref in your web.xml file, and add the appropriate resource to the server using the "administrative console" as mention above.
“Everything should be as simple as it is, but not simpler.” Albert Einstein
Cameron Wallace McKenzie
author and cow tipper
There's a chance that the admin console is running on a different port.
Do a netstat -a on the command line, and look for any open ports in the 9060 or 9080 range. Just an idea.
Joined: Mar 18, 2009
I swear, is the only one.
Anyway, I got it. It's quite silly, actuallly. I'm kind of embarrased. It turns out I was trying to access to the app through a server which didn't have any libraries in it. By clicking on the server I finally figured out that it was pointing to another path, express5.1 on runtimes folder, and I was trying to access to the test 5.1.