Bug 92277 - Problem while working with JBoss with secured JMX invoker
Problem while working with JBoss with secured JMX invoker
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: JBoss
5.x
Other Windows XP
: P2 (vote)
: TBD
Assigned To: Libor Kotouc
issues@serverplugins
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-11 08:47 UTC by piokoch
Modified: 2008-10-28 23:09 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description piokoch 2007-01-11 08:47:20 UTC
If JBoss JMX invoker is secured, i.e. in jmx-invoker-service.xml the following
line is NOT commented:

<interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor"
                     securityDomain="java:/jaas/jmx-console"/>

then Netbeans does not know that the server is started, as a result, application
cannot be redeployed from Netbeans without manually stopping the server.

I think that Netbeans should ask for username and password, this would work in
most cases.

BTW, Eclipse WebTools have also problems with this...
Comment 1 Libor Kotouc 2007-01-11 13:53:15 UTC
Could you please provide the exact configuration of your JBoss server (the
version, how it was installed - archive/jar, your security settings, etc.)?
Comment 2 piokoch 2007-01-14 11:58:00 UTC
My JBoss version is 4.0.5, installed using JAR installer in EJB 3.0
configuration. JMX invoker was secured using standard method:
http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureTheInvokers.

When JMX invoker was secured, then Netbeans was unable to detect if server is
running and to shutdown the server, which is ok, because in order to do this
things while invoker is secured, you need to give username and password.

Netbeans should detect that JMX invoker is secured and if yes, should ask for
username and password - this could be also added to the server configuration in
Netbeans.
Comment 3 Libor Kotouc 2007-01-14 20:47:44 UTC
Thanks for the explanation and suggestions. It is more an enhacement than a bug
and hopefully we are able to implement it within the NB6.0 time frame.
Comment 4 Vince Kraemer 2007-12-07 16:22:18 UTC
please close this issue if you forgot to earlier.  If this issue is still open,
please change the target milestone to reflect the current commitment.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo