[jbosstools-issues] [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