3:12 p.m.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://jira.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:46 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://jira.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin.s...
]
Dominik Pospisil commented on JBIDE-7814:
-----------------------------------------
When there was an auth error during JMX call, JBT used to display authentication window.
Now, nothing happens.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://jira.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:22 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Max Andersen updated JBIDE-7814:
--------------------------------
Fix Version/s: 3.2.0.CR1
Priority: Blocker (was: Major)
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:48 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-7814.
--------------------------------
Resolution: Won't Fix
These errors are logged to the server log view. Right click on the server and select
"Shown In -> Server Log View". I've just tested and that view shows both
"Error adding deployment folder to deployment scanner" and a full stacktrace.
We do not overload the user with errors popups and errors here. We silently log it in the
server log view where users can always go have a look if they suspect something is wrong.
This is working as designed.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:14 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Dominik Pospisil updated JBIDE-7814:
------------------------------------
Attachment: serverlog.jpg
Server log view after startup and unsuccessful shutdown on a server with disabled JMX. No
indication here.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:36 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Max Andersen commented on JBIDE-7814:
-------------------------------------
...and I will add that making all errors silent is not what we want and I believe we
actually did show critical errors like this one before (i.e. not able to authenticate).
This does look like a rather big regression to what we had before (which also wasn't
perfect either - but at least you knew as a user something went wrong)
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:51 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-7814:
-------------------------------
Attachment: JBIDE-7814.jpg
screenshot of it logging properly
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:51 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-7814:
------------------------------------
In the past we only showed the error message and jmx box when JMX poller was used, never
for publishing. Publishing never got a front-and-center error message and was alwyas
silently logged. Always. So this is not a regression at all.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:25 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-7814:
------------------------------------
- Add ability for server log view to select which server you want to look at
- add option to also log errors to the Error Log view
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-7814.
--------------------------------
Resolution: Done
updates to server log view committed. I've added a preference action which can also
re-log errors to the Error Log. Also, now simply selecting a server anywhere in the
workbench (most likely in server view) will update the server log view.
Finally the annoying progress monitor dialog was replaced with background jobs so as not
to annoy the user every time they select a new server.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:53 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Dominik Pospisil closed JBIDE-7814.
-----------------------------------
Thanks Rob, missed that. Verified
(jbdevstudio-product-eap-linux-gtk-x86_64-4.0.0.v201101192139R-H84-CR1.jar
).
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Dominik Pospisil commented on JBIDE-7814:
-----------------------------------------
Please ignore previous comment, wrong JIRA. Sorry.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:19 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-7814:
--------------------------------------------
just to be clear things *looks* fine and dandy but deployment didnt work.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR2 (tentative)
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:19 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-7814:
---------------------------------------
Assignee: Rob Stryker (was: Max Rydahl Andersen)
Fix Version/s: 3.2.0.CR2 (tentative)
(was: 3.2.0.CR1)
Rob - im seeing the same - no logs and things looks fine and dandy.
Are the defaults bad or something ?
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR2 (tentative)
Attachments: JBIDE-7814.jpg, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-7814:
-------------------------------
Attachment: JBIDE-7814_b.patch
seems i just forgot the else statement in the publisher code. oops. Patch attached. Logs
the error and also adds a new status code for transition failed.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR2 (tentative)
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:15 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-7814:
------------------------------------
Interesting to note, but, if JMX isn't unsecured, you can't even *stop* such a
server. The stop script for the server requires the use of JMX. Yes, you heard me
correctly. Even when you use the command line stop script,
[rob@localhost bin]$ ./shutdown.sh -S
Exception in thread "main" java.lang.SecurityException: Failed to authenticate
principal=null, securityDomain=jmx-console
at
org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
So a secured soa-p cannot even be shut down properly. Kinda baffling, eh?
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR2 (tentative)
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:29 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-7814:
---------------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.0.CR2 (tentative))
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:54 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-7814:
-------------------------------------
yes, I can't stop it. 1st attempt=exception. How it works if you do 2nd attempt to
stop server? 'cause it looks like it is stopped then.
thanks
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call 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] Resolved: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-7814.
--------------------------------
Resolution: Done
committed to trunk and branch
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-7814:
-------------------------------------
verified on as.core (2.2.0.v20110123-0154-H22-CR1)
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-7814.
-------------------------------
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails
[
https://issues.jboss.org/browse/JBIDE-7814?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-7814:
------------------------------------
The second attempt tries to cancel the process directly rather than execute a shutdown
script of any sort.
User is not notified when deployment fails
------------------------------------------
Key: JBIDE-7814
URL: https://issues.jboss.org/browse/JBIDE-7814
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: JBIDE-7814.jpg, JBIDE-7814_b.patch, serverlog.jpg
AFAIK when deploying we are calling server via JMX. What happens when JMX call is not
successful? Nothing good. Studio shows project as deployed, but app server in worse case
does not know about deployment (when target dir is set to workspace), in better case
notices it after a few seconds.
User than can only guess what and why is his project not deployed.
This confusing behavior can be simply reproduced on any soa-p server, since you have to
uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to
make JMX working. If you do not do that, you'll reproduce.
AS Adapter should warn user on JMX call errors.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5557
days inactive
5607
days old
jbosstools-issues@lists.jboss.org
21 comments
5 participants
participants (5)
-
Dominik Pospisil (JIRA) -
Libor Zoubek (JIRA)
-
Max Andersen (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)