[
https://issues.apache.org/jira/browse/QPID-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642598#action_12642598
]
Andrea Gazzarini commented on QPID-1378:
----------------------------------------
Another improvement I forgot to mention in the previous post:
Whenyou start QMan you can supply one optional argument that is the log4j.xml
configuration file. In that way the logging system load that file and watches
it every 10 seconds allowing you to change the logging options (category,
level, etc...) at runtime.
@Ted : As we spoke yesterday about that error this is an issue due to usage of
jconsole. I mean, due to usage of RMI remote client (and jconsole is an RMI
remote client).
Before patch was applied the method invocations simply returned "null" and so
there was no need to marshall / unmarshall null object. That's the reason why
before of that patch you could see the jconsole dialog saying "Method
successfully invoked".
With the current implementation return values are handled and when you invoke a
method you can have one of the following scenarios :
1) Status code != 0 : invocation throws MethodInvocationException;
2) Status code == 0 : invocation return a value object
"org.apache.qpid......InvocationResult"
Now, If you are calling QMan using a remote RMI client, those two classes are
not available to that client classpath and therefore it tries to load them
using RMI Class Loader. Since no security manager is installed that loader is
not able to work.
Anyway, this is not a big issue because
1) JConsole is just a facility to see what's happening on QMan;
2) QMan will be exposed as a WS (directly via WS or WS-DM) so at that time ,
remote client will have their local language-specifc implementations of those
mentioned classes.
Regards,
Andrea
> QMan : Multi-message handling
> ------------------------------
>
> Key: QPID-1378
> URL: https://issues.apache.org/jira/browse/QPID-1378
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M4
> Environment: J2SE 1.5 or higher, any OS that is supporting Java
> Reporter: Andrea Gazzarini
> Priority: Minor
> Fix For: M4
>
> Attachments: jconsole_showing_qman_remote_agent.JPG,
> qman_24102008_compound_message_handling.patch
>
>
> According to QPID-1360 management protocol has been changed in order to
> support "batching of QMF messages into AMQP bodies to further reduce the
> message load".
> So QMan needs to be updated in order to handle those changes.
> This issue will host all multi-message related patches.
> Regards,
> Andrea
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
