]
Rob Stryker resolved JBIDE-8313.
--------------------------------
Resolution: Done
Launch instance wizard: cannot access webapp (404) if using
ami-7ad22213
------------------------------------------------------------------------
Key: JBIDE-8313
URL:
https://issues.jboss.org/browse/JBIDE-8313
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud, JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.2.1
Attachments: 404.ogv, diff.txt, gwt-helloworld.war
Despite the fixes in JBIDE-8261, multiple issues seem to persist with remote AS when
using this setup.
First, it seems RSE loses the connection at a certain point (10 minutes? not sure), and
all efforts to restore it are lost. This means that even efforts to upload new changes
fails.
Second, even if i manually scp files (some new Dyn Web proj) to the server and then mv it
into the deploy folder, they often are not recognized. In fact, it seems the entire
deployment scanner shuts down and all efforts to restart it fail.
Even efforts to craft, on the machine in VI, a new -ds.xml file, and move it in, fails.
Even restarting the deployment scanner with the following commands fails:
/opt/jboss-as6/bin/twiddle.sh -s
service:jmx:rmi:///jndi/rmi://EC2-184-72-200-3.COMPUTE-1.AMAZONAWS.COM:1090/jmxrmi -u
admin -p admin invoke jboss.deployment:flavor=URL,type=DeploymentScanner stop
/opt/jboss-as6/bin/twiddle.sh -s
service:jmx:rmi:///jndi/rmi://EC2-184-72-200-3.COMPUTE-1.AMAZONAWS.COM:1090/jmxrmi -u
admin -p admin invoke jboss.deployment:flavor=URL,type=DeploymentScanner start
They do not fail with exceptions, and the twiddle finishes as expected.
So all in all, this is just extremely baffling. It has elements of RSE errors (losing
connection), elements of AS6-errors (deployment scanner start / stop really not doing a
damn thing), and I'm sure my tools are also not exempt from errors.
Unfortunately, code freeze is here and the best I can do is log errors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: