[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643460#action_12643460 ] Rajika Kumarasiri commented on QPID-1284: - Is the latests patch available on the trunk ? > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini >Assignee: Arnaud Simon > Attachments: actors.jpg, class_definition_building.jpg, > commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, > estabilish_initial_connection.jpg, Invokes an operation.jpg, > management_message.jpg, message_processing.jpg, QMan.jar, > qman_14102008_latest.patch, qman_patch, qman_patch_08102008, > qman_patch_14102008, qman_predefined_handlers_patch, qman_test_cases_patch, > qman_test_cases_patch_08102008, qpid_patch_under_management_folder_12102008, > QpidClass.jpg, use_cases.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639414#action_12639414 ] Andrea Gazzarini commented on QPID-1284: Hi Aidan, that works for me. Regards, Andrea > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: actors.jpg, class_definition_building.jpg, > commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, > estabilish_initial_connection.jpg, Invokes an operation.jpg, > management_message.jpg, message_processing.jpg, QMan.jar, qman_patch, > qman_patch_08102008, qman_patch_14102008, qman_predefined_handlers_patch, > qman_test_cases_patch, qman_test_cases_patch_08102008, > qpid_patch_under_management_folder_12102008, QpidClass.jpg, use_cases.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639365#action_12639365 ] Aidan Skinner commented on QPID-1284: - Now that this has landed in tree, I think it would be good to start splitting further work into different Jiras, like we do for the rest of the code base. This would allow more clarity about what's going on and why. It might also be worth creating a 'management lib' component for this in jira, what do you think? > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: actors.jpg, class_definition_building.jpg, > commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, > estabilish_initial_connection.jpg, Invokes an operation.jpg, > management_message.jpg, message_processing.jpg, QMan.jar, qman_patch, > qman_patch_08102008, qman_patch_14102008, qman_predefined_handlers_patch, > qman_test_cases_patch, qman_test_cases_patch_08102008, > qpid_patch_under_management_folder_12102008, QpidClass.jpg, use_cases.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637935#action_12637935 ] Ted Ross commented on QPID-1284: Andrea, QMan can be made to prevent closing its own connection and session. You will need an enhancement to the API to do this however. I'm told this enhancement is imminent. With regard to exposing powerful methods to remote actors, the broker provides an ACL capability to selectively allow or deny access to methods for specific users. -Ted > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: actors.jpg, class_definition_building.jpg, > commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, > estabilish_initial_connection.jpg, message_processing.jpg, QMan.jar, > qman_patch, qman_patch_08102008, qman_predefined_handlers_patch, > qman_test_cases_patch, qman_test_cases_patch_08102008, QpidClass.jpg, > use_cases.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637920#action_12637920 ] Andrea Gazzarini commented on QPID-1284: Hi All, I have some doubts about remote management of Qpid Broker. Running QMan I'm able to see several types of objects (queue, connection, session and so on). Those objects have methods that I can invoke. Now, there are some methods that in my opinion shouldn't be exposed for management. I mean shouldn't be part of the management interface. What are those methods? In general methods that control lifecycle of a specific object and specifically methods that are destroying / closing / invalidating an object. Those operations should be controlled by the owning broker and in my opinion is not good to let an external client terminate those objects. First possible scenario : 1) QMan starts up. At least it needs one connection and one session 2) An external client connects to QMan using an XXX connector (where XXX could be RMI, WSDM, etc...) 3) The external client invoke the close() operation on the connection instance that is used by QMan 4) Result : QMan suicide Second possible scenario : 1) QMan starts up. At least it needs one connection and one session 2) An external client connects to QMan using an XXX connector (where XXX could be RMI, WSDM, etc...) 3) The external client invoke the close() / detach() operation on the session instance that is used by QMan 4) Result : QMan is no longer working... Third possible scenario : 1) QMan starts up. At least it needs one connection and one session 2) An external client connects to QMan using an XXX connector (where XXX could be RMI, WSDM, etc...) 3) The external client invoke the purge() operation on the management and / or queue instance that is used by QMan 4) Result : QMan is not receiving management & method-reply messages Fourth possible scenario : 1) QMan starts up and it connects to a broker already connected with other management clients. 2) An external client connects to QMan using an XXX connector (where XXX could be RMI, WSDM, etc...) 3) The external client invoke the close() operation on the connection instance that is used by another client 4) Result : the other external client is no longer able to work. ...and so on... What are you thinking about? Let me know Regards, Andrea > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: actors.jpg, class_definition_building.jpg, > commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, > estabilish_initial_connection.jpg, message_processing.jpg, QMan.jar, > qman_patch, qman_patch_08102008, qman_predefined_handlers_patch, > qman_test_cases_patch, qman_test_cases_patch_08102008, QpidClass.jpg, > use_cases.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635730#action_12635730 ] Andrea Gazzarini commented on QPID-1284: Hi Ted, so please correct me if I'm wrong : if I re-sync broker code from the trunk and rebuild all the method invocation is working isn't it? Let me know Regards, Andrea > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: actors.jpg, class_definition_building.jpg, > commons-pool-1.4.jar, configuration_domain_model.jpg, DomainModel.jpg, > estabilish_initial_connection.jpg, message_processing.jpg, QMan.jar, > qman_patch, qman_predefined_handlers_patch, qman_test_cases_patch, > QpidClass.jpg, use_cases.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635489#action_12635489 ] Ted Ross commented on QPID-1284: Andrea, I finally got to the bottom of the problem you're seeing... It turns out that you are using "str16" for long strings (which is correct according to the Wiki page). The broker was assuming vbin32 as the type. I've fixed this and the echo methods now work. -Ted > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: commons-pool-1.4.jar, DomainModel.jpg, QMan.jar, > qman_patch, QpidClass.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635365#action_12635365 ] Andrea Gazzarini commented on QPID-1284: Hi Ted, I have got some strange behaviours after invoking the echo(int,String) method of the broker class. Can you help me? This is the stacktrace : java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:110) 2008-09-26 14:47:19,843 ERROR [org.apache.qpid.management.configuration.QpidDatasource] : Error on closing connection. Reason is : , error code is 501 2008-09-26 14:47:19,858 ERROR [org.apache.qpid.transport.network.io.IoSender] error in write thread java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:271) 2008-09-26 14:47:19,858 ERROR [org.apache.qpid.management.configuration.QpidDatasource] : Error on closing connection. Reason is : connection was closed, error code is 3 java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:110) java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.qpid.transport.network.io.IoSender.run(IoSender.java:271) 2008-09-26 14:00:34,054 ERROR [org.apache.qpid.management.configuration.QpidDatasource] : Error on closing connection. Reason is : , error code is 501 2008-09-26 14:00:34,054 ERROR [org.apache.qpid.management.configuration.QpidDatasource] : Error on closing connection. Reason is : connection was closed, error code is 3 java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) It's strange because if I invoke another method (for example queue.purge(int), session.solicitAck() ) all it's working and of course the code is the same... Method invocation is done following exactly what you told me in the previous post so the question is : could it be a broker problem? Thanks in advance. Best Regards, Andrea > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: commons-pool-1.4.jar, DomainModel.jpg, QMan.jar, > qman_patch, QpidClass.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[
https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633926#action_12633926
]
Ted Ross commented on QPID-1284:
Andrea,
For method calls, use a routing key of "agent.0". Here's the list of items to
be encoded:
Header (opcode='M')
ObjectId of target object (128 bits)
Package name (str8)
Class name (str8)
Class hash (bin128)
Method name (str8) [as defined in the schema]
Now encode all input ("I") and i/o (IO) arguments in the order in which they
are defined in the schema. (i.e. make one pass over the argument list and
encode arguments that are either input or inptu/output).
The response will be encoded thus:
Header (opcode='m')
Status code (uint32)
Status text (str8)
all output (O) and i/o (IO) arguments in the order in which they appear in the
schema.
-Ted
> QMan : Qpid JMX Management Bridge
> -
>
> Key: QPID-1284
> URL: https://issues.apache.org/jira/browse/QPID-1284
> Project: Qpid
> Issue Type: New Feature
>Affects Versions: M3
> Environment: J2SE 5, any OS that is supporting Java
>Reporter: Andrea Gazzarini
> Attachments: DomainModel.jpg, QMan.jar, QpidClass.jpg
>
>
> QMan is an application used for exposing via JMX the management domain model
> of one or more remote brokers.
> Capabilities (the list is not complete) :
> - Operates from a formally defined management schema;
> - Uses the AMQP protocol and its type system for communicating with remote
> brokers;
> - Exposes via JMX the remote broker domain model: that means for each
> connected broker QMan lets you see its domain model entities according to
> their schema (attribute, methods, statistics and events). In addition, lets
> you invoke operations on those entities.
> - Multi broker management;
> - It doesn't have prior knowledge of the management model of the system under
> management. no definition is hard-coded and entity definitions (schema) are
> requested and built "on demand";
> - Namespace separation between brokers : each connected broker can have a
> different schema.
> - JMX interface : QMan is itself a Management Bean and using JMX it exposes
> its public interface (for example, to connect with a new broker). So at the
> end it should be exposed via WS-DM, SMTP, RMI, etc...
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633634#action_12633634 ] Andrea Gazzarini commented on QPID-1284: Hi Ted, thanks for reply...now It's clear. In a previous post you told me that "Other protocol updates have occurred in the method and event area but those don't yet affect you (yet). "..well I've implemented method invocation; I mean, QMan is able to see and invoke the broker exposed operations but the 'm' response messages contain an error status code. Here are some examples : 1) Invoking close() operation on a connection object instance. Status code : 4 Status text : InvalidParameter 2) Invoking solicitAck() on a session object instance. Status code : 1 Status text : UnknownObject 3) Invoking detach() on a session object instance. Status code : 4 Status text : InvalidParameter 4) purge(int request) on queue object instance with 0 as parameter value Status code : 4 Status text : InvalidParameter Where could I read those protocol updates? Let me know. Regards, Andrea > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: DomainModel.jpg, QMan.jar > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633223#action_12633223 ] Ted Ross commented on QPID-1284: Andrea, Bits in the presence mask are only assigned for optional properties. Since the broker table has only one optional property (dataDir), only one bit is allocated in the bitmask. -Ted > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: DomainModel.jpg, QMan.jar > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[
https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633206#action_12633206
]
Andrea Gazzarini commented on QPID-1284:
Hi all,
I have a problem with optional properties...this is the scenario:
- Package is org.apache.qpid.broker
- class is "broker".
"broker" has 9 properties and the 9th is "dataDir".
The problem is the following : when the content indication message ('c')
arrives there's a value for dataDir property and there's only one presence
bitmask octect equals to 1 (0001) but the dataDir property is in the 9th
position so there should be 2 octects like this 1000. Am I wrong?
Any help would be appreciated...
Regards,
Andrea
> QMan : Qpid JMX Management Bridge
> -
>
> Key: QPID-1284
> URL: https://issues.apache.org/jira/browse/QPID-1284
> Project: Qpid
> Issue Type: New Feature
>Affects Versions: M3
> Environment: J2SE 5, any OS that is supporting Java
>Reporter: Andrea Gazzarini
> Attachments: DomainModel.jpg, QMan.jar
>
>
> QMan is an application used for exposing via JMX the management domain model
> of one or more remote brokers.
> Capabilities (the list is not complete) :
> - Operates from a formally defined management schema;
> - Uses the AMQP protocol and its type system for communicating with remote
> brokers;
> - Exposes via JMX the remote broker domain model: that means for each
> connected broker QMan lets you see its domain model entities according to
> their schema (attribute, methods, statistics and events). In addition, lets
> you invoke operations on those entities.
> - Multi broker management;
> - It doesn't have prior knowledge of the management model of the system under
> management. no definition is hard-coded and entity definitions (schema) are
> requested and built "on demand";
> - Namespace separation between brokers : each connected broker can have a
> different schema.
> - JMX interface : QMan is itself a Management Bean and using JMX it exposes
> its public interface (for example, to connect with a new broker). So at the
> end it should be exposed via WS-DM, SMTP, RMI, etc...
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[
https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632108#action_12632108
]
Andrea Gazzarini commented on QPID-1284:
Hi Ted, thanks for help.
I read the document of QMF but it is linking to the same
http://cwiki.apache.org/confluence/display/qpid/Management+Design+notes where
the changes you told me (object id for example) are not described.
Anyway,I printed out the array content of a 'c' content indication message.
Note that the first 4 bytes (AM1c) have been deleted:
byte data [] = {
0, 0, 0, 0, 22, 111, 114, 103, 46, 97, 112, 97, 99, 104, 101,
46, 113, 112, 105, 100, 46, 98, 114, 111, 107,
101, 114, 8, 101, 120, 99, 104, 97, 110, 103, 101, 109, 44, 75,
73, 108, 40, 88, 92, 26, -98, 93, 24, 122, 7,
-55, -44, 16, -12, 36, 99, -112, -27, 114, -7, 16, -12, 35, 64,
-119, 40, 126, -24, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 16, 0, 0, 0, 32, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 0, 16, 0, 0,
0, 16, 0, 0, 0, 0, 0, 0, 3, 9, 97, 109, 113, 46, 109, 97,
116, 99, 104, 7, 104, 101, 97, 100, 101, 114, 115, 1};
ByteBuffer buffer = ByteBuffer.wrap(data);
BBDecoder decoder = new BBDecoder();
decoder.init(buffer);
assertEquals(0,decoder.readSequenceNo());
assertEquals("org.apache.qpid.broker",decoder.readStr8());
assertEquals("exchange",decoder.readStr8());
// CLASS-HASH
decoder.readUint64();
decoder.readUint64();
// TIMESTAMPS
assertEquals(1221641408975565561,decoder.readDatetime());
assertEquals(1221640159010258664,decoder.readDatetime());
assertEquals(0,decoder.readDatetime());
// OBJECT ID : you told me that now is 128 bit wide.
decoder.readUint64();
decoder.readUint64();
// !!!
// What is it? I need to read further 64 bits in order to get the
correct data.
*decoder.readUint64();
assertEquals(1152921504606846979,decoder.readUint64());
assertEquals("amq.match",decoder.readStr8());
assertEquals("headers",decoder.readStr8());
assertTrue(decoder.readUint8() == 1);
If I delete the * line I'm getting
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException
at org.apache.qpid.transport.Binary.(Binary.java:41)
at org.apache.qpid.transport.codec.BBDecoder.get(BBDecoder.java:61)
at
org.apache.qpid.transport.codec.AbstractDecoder.readStr8(AbstractDecoder.java:144)
at org.apache.qpid.management.A.main(A.java:68)
while reading the "type" property.
Let me know when you want, there's no rush, and again thanks for support.
Regards,
--Gazza--
I don't know if the format of the code will be retained after
> QMan : Qpid JMX Management Bridge
> -
>
> Key: QPID-1284
> URL: https://issues.apache.org/jira/browse/QPID-1284
> Project: Qpid
> Issue Type: New Feature
>Affects Versions: M3
> Environment: J2SE 5, any OS that is supporting Java
>Reporter: Andrea Gazzarini
> Attachments: DomainModel.jpg, QMan.jar
>
>
> QMan is an application used for exposing via JMX the management domain model
> of one or more remote brokers.
> Capabilities (the list is not complete) :
> - Operates from a formally defined management schema;
> - Uses the AMQP protocol and its type system for communicating with remote
> brokers;
> - Exposes via JMX the remote broker domain model: that means for each
> connected broker QMan lets you see its domain model entities according to
> their schema (attribute, methods, statistics and events). In addition, lets
> you invoke operations on those entities.
> - Multi broker management;
> - It doesn't have prior knowledge of the management model of the system under
> management. no definition is hard-coded and entity definitions (schema) are
> requested and built "on demand";
> - Namespace separation between brokers : each connected broker can have a
> different schema.
> - JMX interface : QMan is itself a Management Bean and using JMX it exposes
> its public interface (for example, to connect with a new broker). So at the
> end it should be exposed via WS-DM, SMTP, RMI, etc...
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631823#action_12631823 ] Ted Ross commented on QPID-1284: Gazza, A few quick notes... 1) The "management design notes" wiki page is no longer being updated. It represents the state of the code in the M3 release. 2) A new page has been created (http://cwiki.apache.org/confluence/display/qpid/Qpid+Management+Framework) for the ongoing effort. Lots of details need to be filled in. 3) After a quick look at the QMan code (which looks very neat by the way), I think the main issue you are having with the trunk is that the objectId has been expanded from 64-bits to 128-bits. Other protocol updates have occurred in the method and event area but those don't yet affect you (yet). 4) Another feature your code doesn't support is optional properties. Search for "optional properties" in the M3 management design notes for details. -Ted > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: DomainModel.jpg, QMan.jar > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631798#action_12631798 ] Ted Ross commented on QPID-1284: Gazza, Thanks for your work. This will be a very valuable contribution. A lot of work has gone into the management for the C++ broker in the last few months and the trunk has advanced well beyond the point where it was in the Fedora release. We're calling it the Qpid Management Framework (QMF). It is being used inside and outside of Apache to manage components beyond just the broker. I would be happy to help you migrate to the trunk version as there have been a few protocol changes that have occurred. We can use this Jira, or you can email me at [EMAIL PROTECTED], or find me on #qpid at freenode. -Ted > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > Attachments: DomainModel.jpg > > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
[ https://issues.apache.org/jira/browse/QPID-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631773#action_12631773 ] Andrea Gazzarini commented on QPID-1284: *** status of the work *** I developed a first prototype which is able to interface with a M2.1 C++ broker.(the version installed with yum install qpidd on Fedora) I'm going to preparetyhe code for submit . Now I built the qpid c++ broker from the trunk and it seems that it's not working because something has changed in the 'c' ContentIndication Message. I'm trying to investigate... I'm also preparing some UML diagrams to explain what I've done and what I should do on this component. - Gazza - > QMan : Qpid JMX Management Bridge > - > > Key: QPID-1284 > URL: https://issues.apache.org/jira/browse/QPID-1284 > Project: Qpid > Issue Type: New Feature >Affects Versions: M3 > Environment: J2SE 5, any OS that is supporting Java >Reporter: Andrea Gazzarini > > QMan is an application used for exposing via JMX the management domain model > of one or more remote brokers. > Capabilities (the list is not complete) : > - Operates from a formally defined management schema; > - Uses the AMQP protocol and its type system for communicating with remote > brokers; > - Exposes via JMX the remote broker domain model: that means for each > connected broker QMan lets you see its domain model entities according to > their schema (attribute, methods, statistics and events). In addition, lets > you invoke operations on those entities. > - Multi broker management; > - It doesn't have prior knowledge of the management model of the system under > management. no definition is hard-coded and entity definitions (schema) are > requested and built "on demand"; > - Namespace separation between brokers : each connected broker can have a > different schema. > - JMX interface : QMan is itself a Management Bean and using JMX it exposes > its public interface (for example, to connect with a new broker). So at the > end it should be exposed via WS-DM, SMTP, RMI, etc... > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
