QMan on JBoss 
--------------

                 Key: QPID-1401
                 URL: https://issues.apache.org/jira/browse/QPID-1401
             Project: Qpid
          Issue Type: Improvement
          Components: Java Client
    Affects Versions: M4
         Environment: J2SE 1.5 or higher, JBoss 4.2.x or higher
            Reporter: Andrea Gazzarini
             Fix For: M4
         Attachments: 1_jboss-web-console-showing-qman-mbeans.JPG, 
2_jmx-console-showing-qman-mbeans.JPG, 
3_jboss-jmx-console-showing-qman-session-mbean.JPG

Hi all, 
what do you think about the attached screenshot? It's QMan deployed on JBoss 
Application Server!  :

- 1_jboss-web-console-showing-qman-mbeans.JPG : JBoss web console showing QMan 
MBeans (QMan connected to a remote broker)
- 2_jmx-console-showing-qman-mbeans.JPG : the same as above but this time is 
the JBoss jmx console;
- 3_jboss-jmx-console-showing-qman-session-mbean.JPG : jmx console showing the 
detail of a "session" object instance: there you can see properties, statistics 
& methods of the session object.
- 4_method_invocation_exception.JPG : invocation of a method through jmx 
console that is throwing an exception (this method is part of the session 
interface but it's not yet implemented) 
- 5_queue.purge_method_invocation_result.JPG : Invocation of the purge() method 
on a queue instance through jmx console. The method was invoked successfully.

So as I told you thery are showing QMan deployed inside JBoss. In order to 
achieve that there are only 2 little things to be done : 

1) Create a simple war with a preloaded servlet on startup (QMan initializer);
2) Starts your JBoss AS with the following option -Djboss.platform.mbeanserver 
(this is a standard jboss option included since 4.2.x version) 

And that's all...at free of charge you can interact with QMan using Html, RMI 
and all deployed / deployable connectors of the Application Server!

In addition 

- the integration strategy adopted is standard (no jboss proprietary 
descriptors) so I think should be easy to do the same for other Application 
Servers (tomorrow I will try with BEA Weblogic)
- each adaptor (included the html one) is local / resident to jboss you no 
longer have the issues described on Ted post (ClassNotFoundException) in 
QPID-1378;

As you understood, code and deployment descriptors for deploying QMan on JBoss 
are already completed...so please let me know what are you thinking about and 
after that if you think it's useful we can decide where to put that subproject 
on the build tree.

Best Regards,
Andrea

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to