qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Gazzarini (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-1284) QMan : Qpid JMX Management Bridge
Date Mon, 29 Sep 2008 12:28:44 GMT

    [ 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] <QMAN-100012>
: 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] <QMAN-100012>
: 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] <QMAN-100012>
: Error on closing connection. Reason is : , error code is 501
2008-09-26 14:00:34,054 ERROR [org.apache.qpid.management.configuration.QpidDatasource] <QMAN-100012>
: 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.


Mime
View raw message