[JBoss JIRA] Created: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
3:57 p.m.
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
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: http://www.atlassian.com/software/jira
7:03 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8313:
-----------------------------------------
I installed a vanilla jboss-as 6 on the new image we got today. deployed several times to
it and ran into the same problems. I therefore guess that this is not an issue of the
jboss installation that is preinstalled on the image. I did a diff which pretty much tells
me that the preinstalled as6 is a default jboss-as installation. (see the diff I
attached)
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
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: http://www.atlassian.com/software/jira
7:14 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8313:
------------------------------------
Attachment: diff.txt
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: diff.txt
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: http://www.atlassian.com/software/jira
8:10 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8313:
-----------------------------------------
I unfortunately still experience this.
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: diff.txt
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: http://www.atlassian.com/software/jira
8:51 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8313:
------------------------------------
Attachment: gwt-helloworld.war
this is the war I try to deploy
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: 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: http://www.atlassian.com/software/jira
12:01 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim updated JBIDE-8313:
------------------------------------
Attachment: 404.ogv
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: http://www.atlassian.com/software/jira
12:03 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8313:
-----------------------------------------
added a screencast that shows how it happens.
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: http://www.atlassian.com/software/jira
5:15 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8313:
-----------------------------------------
what is odd to me in the current behavior:
when deploying, I get a dialog that says the run-on-server job is waiting for blocking
jobs and list 2 jmx-connection jobs. The deploy-job is obviously not blocked by them since
it's started. You can spot it in the status-bar. It's not listed in the jobs
though.
Rob?
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: http://www.atlassian.com/software/jira
5:31 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8313:
-----------------------------------------
reported this isse in JBIDE-8342 as Max told me that this is a bug.
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: http://www.atlassian.com/software/jira
7:51 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim edited comment on JBIDE-8313 at 2/16/11 8:51 AM:
------------------------------------------------------------------
reported this isse in JBIDE-8432 as Max told me that this is a bug.
was (Author: adietish):
reported this isse in JBIDE-8342 as Max told me that this is a bug.
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: http://www.atlassian.com/software/jira
12:10 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim commented on JBIDE-8313:
-----------------------------------------
the current state of this bug is related to 3 different bugs:
- "Run on server" has issues, this is know and there's no way for "Run
on server" to know when deployment was successfully executed. -> no fix
- We experienced a very rare AS bug where AS would not pick any new deployment. We could
not reproduce it even with intense testing last week.
- JBAS-8864
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: http://www.atlassian.com/software/jira
3:14 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Andre Dietisheim edited comment on JBIDE-8313 at 2/23/11 4:13 AM:
------------------------------------------------------------------
the current state of this bug is related to 3 different bugs:
- You may get a 404 initially when doing "Run on server". Further browser
refreshes should deliver the app though. There's basically no way for "Run on
server" to know when deployment was successfully executed. -> no fix
- We experienced a very rare AS bug where AS would not pick any new deployment. We could
not reproduce it even with intense testing last week.
- JBAS-8864
was (Author: adietish):
the current state of this bug is related to 3 different bugs:
- "Run on server" has issues, this is know and there's no way for "Run
on server" to know when deployment was successfully executed. -> no fix
- We experienced a very rare AS bug where AS would not pick any new deployment. We could
not reproduce it even with intense testing last week.
- JBAS-8864
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: http://www.atlassian.com/software/jira
3:44 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8313:
------------------------------------
I am convinced other issues / patches have fully fixed this bug.
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: http://www.atlassian.com/software/jira
3:44 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
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: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-8313.
-------------------------------
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.M1
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: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8313) Launch instance wizard: cannot access webapp (404) if using ami-7ad22213
[
https://issues.jboss.org/browse/JBIDE-8313?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-8313:
-------------------------------------
verified on v0.0.1.v20110503-1752-H179-M1
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.M1
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: http://www.atlassian.com/software/jira
5456
days inactive
5549
days old
jbosstools-issues@lists.jboss.org
15 comments
3 participants
participants (3)
-
Andre Dietisheim (JIRA) -
Libor Zoubek (JIRA)
-
Rob Stryker (JIRA)