[
https://issues.apache.org/jira/browse/JAMES-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938276#comment-16938276
]
Benoit Tellier commented on JAMES-2739:
---------------------------------------
Hi [~marin_cenusa]
JMX is a low level protocol that actually make quite strong assertions on the
underlying JAVA beans. Here I bet you are trying to pass a long as an argument
of what had been refactored into an Optional<Duration>.
It turns out JMX usage for 'management purposes' like the mailQueue in
completly untested. In the last year, the community developed alternatives to
the JMX protcol for mailQueue management. See [1] [2].
For your information the community is trying to get rid of JMX for the newest
Guice products.
As such I doubt the community can provide much help on this topic.
Of course contributions and fixes for this issue are welcome.
[1] WebAdmin MailQueue routes:
http://james.apache.org/server/manage-webadmin.html#Administrating_mail_queues
[2] Grafana metrics: http://james.apache.org/server/metrics.html
> Can not browse message queue via jmx connection
> -----------------------------------------------
>
> Key: JAMES-2739
> URL: https://issues.apache.org/jira/browse/JAMES-2739
> Project: James Server
> Issue Type: Bug
> Components: JMX
> Reporter: Hans müller
> Priority: Major
> Attachments: image-2019-04-19-16-58-30-066.png,
> image-2019-04-19-16-59-46-136.png
>
>
> Connect to james via jmx client, e.g. jconsole
> !image-2019-04-19-16-59-46-136.png!
> browse the outgoing queue (if it has content).
> it shows something like
> !image-2019-04-19-16-58-30-066.png!
> Same with other clients
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
