Another way to isolate if thats the problem specific with admin console, you can try to deploy using the CLI deploy command.
%asadmin deploy
Usage: deploy [--terse=false] [--echo=false] [--interactive=true] [--host localhost] [--port 4848|4849] [--secure | -s] [--user admin_user] [--passwordfile file_name] [--virtualservers virtual_servers] [--contextroot context_root] [--force=true] [--precompilejsp=false] [--verify=false] [--name component_name] [--upload=true] [--retrieve local_dirpath] [--dbvendorname dbvendorname] [--createtables=true|false | --dropandcreatetables=true|false] [--uniquetablenames=true|false] [--deploymentplan deployment_plan] [--enabled=true] [--generatermistubs=false] [--availabilityenabled=false] [--libraries jar_file[(pathseparator)jar_file]*] [--target target(Default server)] [--property (name=value)[:name=value]*] filepath
asadmin deploy --help will give you the man page with more info.
Anissa.
[Message sent by forum member 'anilam' (anilam)]
http://forums.java.net/jive/thread.jspa?messageID=356601