[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575535#comment-17575535 ] Justin Bertram commented on ARTEMIS-3913: - The more you can avoid screen-shots the better. A well-formatted text comment is much easier to read and the content is also searchable for folks who may hit a similar issue in the future. Obviously screen-shots are preferable in some cases, but code and stack-traces are much better as straight text. > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575533#comment-17575533
]
Justin Bertram edited comment on ARTEMIS-3913 at 8/5/22 2:58 AM:
-
I'd need a way to reproduce what you're seeing. At the very least I need a
[protocol trace
log|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#debug-logging]
which captures the problem.
There are tests in the test-suite which verify an MQTT 5 client gets a
{{CONNACK}} packet with a reason code of {{134}} ({{0x86}}) when authentication
fails, and those tests are succeeding. See:
*
[{{o.a.a.a.t.i.m.s.c.ConnectTestsWithSecurity#testAuthenticationFailureWithBadCredentials}}|https://github.com/apache/activemq-artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt5/spec/controlpackets/ConnectTestsWithSecurity.java#L51]
*
[{{o.a.a.a.t.i.m.s.c.ConnectTestsWithSecurity#testAuthenticationFailureWithNoCredentials}}|https://github.com/apache/activemq-artemis/blob/382267bf6364dec890f27ca1927394499c83a85b/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt5/spec/controlpackets/ConnectTestsWithSecurity.java#L64]
For what it's worth, those tests are using the Paho 1.2.5 client as well.
was (Author: jbertram):
I'd need a way to reproduce what you're seeing. At the very least I need a
[protocol trace
log|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#debug-logging]
which captures the problem.
There are tests in the test-suite which verify an MQTT 5 client gets a
{{CONNACK}} packet with a reason code of {{134}} ({{0x86}}) when authentication
fails, and those tests are succeeding. See:
*
[{{org.apache.activemq.artemis.tests.integration.mqtt5.spec.controlpackets.ConnectTestsWithSecurity#testAuthenticationFailureWithBadCredentials}}|https://github.com/apache/activemq-artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt5/spec/controlpackets/ConnectTestsWithSecurity.java#L51]
*
[{{org.apache.activemq.artemis.tests.integration.mqtt5.spec.controlpackets.ConnectTestsWithSecurity#testAuthenticationFailureWithNoCredentials}}|https://github.com/apache/activemq-artemis/blob/382267bf6364dec890f27ca1927394499c83a85b/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt5/spec/controlpackets/ConnectTestsWithSecurity.java#L64]
For what it's worth, those tests are using the Paho 1.2.5 client as well.
> MQTTReasonCodes byte loss of precision，must int type
>
>
> Key: ARTEMIS-3913
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3913
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: gongping.zhu
>Priority: Major
> Attachments: image-2022-08-02-08-23-52-965.png,
> image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png,
> image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png,
> image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png,
> image-2022-08-05-08-32-12-492.png
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575533#comment-17575533
]
Justin Bertram commented on ARTEMIS-3913:
-
I'd need a way to reproduce what you're seeing. At the very least I need a
[protocol trace
log|https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#debug-logging]
which captures the problem.
There are tests in the test-suite which verify an MQTT 5 client gets a
{{CONNACK}} packet with a reason code of {{134}} ({{0x86}}) when authentication
fails, and those tests are succeeding. See:
*
[{{org.apache.activemq.artemis.tests.integration.mqtt5.spec.controlpackets.ConnectTestsWithSecurity#testAuthenticationFailureWithBadCredentials}}|https://github.com/apache/activemq-artemis/blob/main/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt5/spec/controlpackets/ConnectTestsWithSecurity.java#L51]
*
[{{org.apache.activemq.artemis.tests.integration.mqtt5.spec.controlpackets.ConnectTestsWithSecurity#testAuthenticationFailureWithNoCredentials}}|https://github.com/apache/activemq-artemis/blob/382267bf6364dec890f27ca1927394499c83a85b/tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/mqtt5/spec/controlpackets/ConnectTestsWithSecurity.java#L64]
For what it's worth, those tests are using the Paho 1.2.5 client as well.
> MQTTReasonCodes byte loss of precision，must int type
>
>
> Key: ARTEMIS-3913
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3913
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: gongping.zhu
>Priority: Major
> Attachments: image-2022-08-02-08-23-52-965.png,
> image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png,
> image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png,
> image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png,
> image-2022-08-05-08-32-12-492.png
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575497#comment-17575497 ] gongping.zhu edited comment on ARTEMIS-3913 at 8/5/22 12:37 AM: my android device has allready used MQTT 5, and client still received (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; implementation 'org.eclipse.paho:org.eclipse.paho.mqttv5.client:1.2.5' !image-2022-08-05-08-32-12-492.png! was (Author: JIRAUSER293605): my android device has allready used MQTT 5, and client still received (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; !image-2022-08-05-08-32-12-492.png! > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gongping.zhu updated ARTEMIS-3913: -- Attachment: image-2022-08-05-08-32-12-492.png > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[ https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575497#comment-17575497 ] gongping.zhu commented on ARTEMIS-3913: --- my android device has allready used MQTT 5, and client still received (REASON_CODE_NOT_AUTHORIZED = 0x05) to zhe client after clientId validate fail; !image-2022-08-05-08-32-12-492.png! > MQTTReasonCodes byte loss of precision，must int type > > > Key: ARTEMIS-3913 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3913 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: gongping.zhu >Priority: Major > Attachments: image-2022-08-02-08-23-52-965.png, > image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png, > image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png, > image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png, > image-2022-08-05-08-32-12-492.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9017) Support merging jasypt managed properties with runtimeConfigurationPlugin
[ https://issues.apache.org/jira/browse/AMQ-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9017: --- Assignee: Matt Pavlovich > Support merging jasypt managed properties with runtimeConfigurationPlugin > - > > Key: AMQ-9017 > URL: https://issues.apache.org/jira/browse/AMQ-9017 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Fix For: 5.17.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9017) Support merging jasypt managed properties with runtimeConfigurationPlugin
Matt Pavlovich created AMQ-9017: --- Summary: Support merging jasypt managed properties with runtimeConfigurationPlugin Key: AMQ-9017 URL: https://issues.apache.org/jira/browse/AMQ-9017 Project: ActiveMQ Issue Type: Improvement Reporter: Matt Pavlovich -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9017) Support merging jasypt managed properties with runtimeConfigurationPlugin
[ https://issues.apache.org/jira/browse/AMQ-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9017: Fix Version/s: 5.17.2 > Support merging jasypt managed properties with runtimeConfigurationPlugin > - > > Key: AMQ-9017 > URL: https://issues.apache.org/jira/browse/AMQ-9017 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Priority: Major > Fix For: 5.17.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3922) Reducing contention on java.lang.Throwable#getOurStackTrace
[
https://issues.apache.org/jira/browse/ARTEMIS-3922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575408#comment-17575408
]
Justin Bertram commented on ARTEMIS-3922:
-
I think this is reasonable. Please send a PR to
https://github.com/apache/activemq-artemis.
> Reducing contention on java.lang.Throwable#getOurStackTrace
> ---
>
> Key: ARTEMIS-3922
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3922
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Affects Versions: 2.24.0
>Reporter: Rico Neubauer
>Priority: Major
> Attachments: threads.txt
>
>
> This is a request for improvement rg. performance in a very specific case,
> but easy to accomplish.
> h2. Scenario
> On certain contaier'ed Windows machines we have identified that
> {{java.lang.Throwable#getOurStackTrace}} along with
> {{java.lang.StackTraceElement#initStackTraceElements}} show up as a very
> expensive operations. The reason behind this is still unclear, but since the
> {{#getOurStackTrace}} is synchronized, it suffers even more when the native
> method {{#initStackTraceElements}} takes an unexpected long time.
> This shows in thread-dumps in 2 locations for Artemis, where
> connection-creation is the more crucial one from my pov.
> See attached threads.txt
> h2. Remedy
> Fortunately the location where this gets used via
> {{Thread.currentThread().getStackTrace()}} is simple to replace, since the
> information needed could just get passed by caller.
> Please see attached patch for my proposal.
> Also available [here as
> commit|https://github.com/seeburger-ag/activemq-artemis/commit/7396b9356256706a886f35da3a27274084e5a973].
> Can create a pull request as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Deleted] (ARTEMIS-3921) PG SLOT
[ https://issues.apache.org/jira/browse/ARTEMIS-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram deleted ARTEMIS-3921: > PG SLOT > --- > > Key: ARTEMIS-3921 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3921 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: johnson pg >Priority: Major > > [pg slot|https://pgslot.link/] pg slot เว็บสล็อตอันดับ 1 > แหล่งรวมเกมสล็อตPGใหม่ล่าสุด มีให้เลือกเล่นมากกว่า 120 เกม เล่นง่ายบนมือถือ > ฝาก-ถอน ออโต้ ไม่มีขั้นต่ำ สมัครเข้าเล่นง่าย 1 นาที -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-3913) MQTTReasonCodes byte loss of precision，must int type
[
https://issues.apache.org/jira/browse/ARTEMIS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575289#comment-17575289
]
Justin Bertram commented on ARTEMIS-3913:
-
As noted previously, the broker will send a {{CONNACK}} with a reason code of
{{134}} _if and only if_ the client is using MQTT *5*. This is true of every
broker since support for MQTT 5 was implemented in 2.21.0. This, of course,
includes 2.23.1.
> MQTTReasonCodes byte loss of precision，must int type
>
>
> Key: ARTEMIS-3913
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3913
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: gongping.zhu
>Priority: Major
> Attachments: image-2022-08-02-08-23-52-965.png,
> image-2022-08-02-08-24-39-288.png, image-2022-08-02-08-31-01-074.png,
> image-2022-08-02-08-42-24-117.png, image-2022-08-02-08-43-39-442.png,
> image-2022-08-02-08-45-11-459.png, image-2022-08-02-08-54-34-267.png
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQ-8622) Fix CVE-2020-10663 | CVSS 7.5 | org.apache.zookeeper_zookeeper in AMQ version
[ https://issues.apache.org/jira/browse/AMQ-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575283#comment-17575283 ] Matt Pavlovich commented on AMQ-8622: - [~satmadeep] You should not be vulnerable. Zookeeper usage was removed in 5.17.0 along with replicated-leveldb. ActiveMQ still has some unit tests that use Zookeeper, but nothing running in the broker. > Fix CVE-2020-10663 | CVSS 7.5 | org.apache.zookeeper_zookeeper in AMQ version > - > > Key: AMQ-8622 > URL: https://issues.apache.org/jira/browse/AMQ-8622 > Project: ActiveMQ > Issue Type: Bug > Components: AMQP, Broker >Reporter: Atmadeep Sen >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 5.18.0, 5.17.2 > > Attachments: Screen Shot 2022-06-02 at 12.21.56 PM.png > > > Hi AMQ team, > Our team is using the latest version 5.17.1 released on April 29, 2022. We > still see the above CVE-2020-10663 | CVSS 7.5 | > org.apache.zookeeper_zookeeper in the latest version. This vulnerability is > an unsafe Object Creation Vulnerability. > This is quite similar to CVE-2013-0269, but does not rely on poor > garbage-collection behavior within Ruby. Specifically, use of JSON parsing > methods can lead to creation of a malicious object within the interpreter, > with adverse effects that are application-dependent. > fixed in 3.6.3, 3.5.9 > Please provide us with an ETA for the next release in which the vulnerability > is going to be fixed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9006) All Network Connectors removed from JMX when the number of connectors is reduced
[ https://issues.apache.org/jira/browse/AMQ-9006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9006: --- Assignee: Matt Pavlovich > All Network Connectors removed from JMX when the number of connectors is > reduced > > > Key: AMQ-9006 > URL: https://issues.apache.org/jira/browse/AMQ-9006 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 5.15.15 >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Fix For: 5.18.0, 5.17.2 > > > Using runtime configuration, reduce the number of network connectors and > observe that all network connectors have been removed from JMX -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Deleted] (ARTEMIS-3920) Kumpulan Daftar Link Situs Slot Gacor Terpopuler Terlengkap Mudah Menang
[ https://issues.apache.org/jira/browse/ARTEMIS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram deleted ARTEMIS-3920: > Kumpulan Daftar Link Situs Slot Gacor Terpopuler Terlengkap Mudah Menang > > > Key: ARTEMIS-3920 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3920 > Project: ActiveMQ Artemis > Issue Type: Task >Reporter: Kumpulan Daftar Link Situs Slot Gacor Terpopuler > Terlengkap Mudah Menang >Priority: Critical > > Di Topslot88 kalian dapat bermain permainan judi online kesayangan anda > secara online dimana saja dan kapan saja kalian ingin bermain. > http://journal.ussh.vnu.edu.vn/files/journals/2/articles/1110/submission/original/1110-1275-1-SM.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3922) Reducing contention on java.lang.Throwable#getOurStackTrace
Rico Neubauer created ARTEMIS-3922:
--
Summary: Reducing contention on
java.lang.Throwable#getOurStackTrace
Key: ARTEMIS-3922
URL: https://issues.apache.org/jira/browse/ARTEMIS-3922
Project: ActiveMQ Artemis
Issue Type: Improvement
Affects Versions: 2.24.0
Reporter: Rico Neubauer
Attachments: threads.txt
This is a request for improvement rg. performance in a very specific case, but
easy to accomplish.
h2. Scenario
On certain contaier'ed Windows machines we have identified that
{{java.lang.Throwable#getOurStackTrace}} along with
{{java.lang.StackTraceElement#initStackTraceElements}} show up as a very
expensive operations. The reason behind this is still unclear, but since the
{{#getOurStackTrace}} is synchronized, it suffers even more when the native
method {{#initStackTraceElements}} takes an unexpected long time.
This shows in thread-dumps in 2 locations for Artemis, where
connection-creation is the more crucial one from my pov.
See attached threads.txt
h2. Remedy
Fortunately the location where this gets used via
{{Thread.currentThread().getStackTrace()}} is simple to replace, since the
information needed could just get passed by caller.
Please see attached patch for my proposal.
Also available [here as
commit|https://github.com/seeburger-ag/activemq-artemis/commit/7396b9356256706a886f35da3a27274084e5a973].
Can create a pull request as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (AMQ-9016) Upgrade to geronimo-annotation_1.3_spec 1.3
Jean-Baptiste Onofré created AMQ-9016: - Summary: Upgrade to geronimo-annotation_1.3_spec 1.3 Key: AMQ-9016 URL: https://issues.apache.org/jira/browse/AMQ-9016 Project: ActiveMQ Issue Type: Dependency upgrade Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 5.18.0, 5.17.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9012) Extend javax.xml.bind package import version range in activemq-web-console bundle
[ https://issues.apache.org/jira/browse/AMQ-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575065#comment-17575065 ] ASF subversion and git services commented on AMQ-9012: -- Commit 64fa32e128927cd5b9060d77629f5b5046de618d in activemq's branch refs/heads/main from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=64fa32e12 ] Merge pull request #868 from jbonofre/AMQ-9012 [AMQ-9012] Extend javax.xml.bind package import version range in activemq-web-console bundle > Extend javax.xml.bind package import version range in activemq-web-console > bundle > - > > Key: AMQ-9012 > URL: https://issues.apache.org/jira/browse/AMQ-9012 > Project: ActiveMQ > Issue Type: Improvement > Components: OSGi/Karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.18.0, 5.17.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9012) Extend javax.xml.bind package import version range in activemq-web-console bundle
[ https://issues.apache.org/jira/browse/AMQ-9012?focusedWorklogId=797863=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-797863 ] ASF GitHub Bot logged work on AMQ-9012: --- Author: ASF GitHub Bot Created on: 04/Aug/22 06:51 Start Date: 04/Aug/22 06:51 Worklog Time Spent: 10m Work Description: jbonofre merged PR #868: URL: https://github.com/apache/activemq/pull/868 Issue Time Tracking --- Worklog Id: (was: 797863) Remaining Estimate: 0h Time Spent: 10m > Extend javax.xml.bind package import version range in activemq-web-console > bundle > - > > Key: AMQ-9012 > URL: https://issues.apache.org/jira/browse/AMQ-9012 > Project: ActiveMQ > Issue Type: Improvement > Components: OSGi/Karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.18.0, 5.17.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9012) Extend javax.xml.bind package import version range in activemq-web-console bundle
[ https://issues.apache.org/jira/browse/AMQ-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575066#comment-17575066 ] ASF subversion and git services commented on AMQ-9012: -- Commit d038725423631796d1465cb2a00c658db8832329 in activemq's branch refs/heads/activemq-5.17.x from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d03872542 ] [AMQ-9012] Extend javax.xml.bind package import version range in activemq-web-console bundle (cherry picked from commit 38d1c9653e31a62b9de159bd0f7e2ced9aecc28c) > Extend javax.xml.bind package import version range in activemq-web-console > bundle > - > > Key: AMQ-9012 > URL: https://issues.apache.org/jira/browse/AMQ-9012 > Project: ActiveMQ > Issue Type: Improvement > Components: OSGi/Karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.18.0, 5.17.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (AMQ-9012) Extend javax.xml.bind package import version range in activemq-web-console bundle
[ https://issues.apache.org/jira/browse/AMQ-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved AMQ-9012. --- Resolution: Fixed > Extend javax.xml.bind package import version range in activemq-web-console > bundle > - > > Key: AMQ-9012 > URL: https://issues.apache.org/jira/browse/AMQ-9012 > Project: ActiveMQ > Issue Type: Improvement > Components: OSGi/Karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.18.0, 5.17.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9012) Extend javax.xml.bind package import version range in activemq-web-console bundle
[ https://issues.apache.org/jira/browse/AMQ-9012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17575064#comment-17575064 ] ASF subversion and git services commented on AMQ-9012: -- Commit 38d1c9653e31a62b9de159bd0f7e2ced9aecc28c in activemq's branch refs/heads/main from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=38d1c9653 ] [AMQ-9012] Extend javax.xml.bind package import version range in activemq-web-console bundle > Extend javax.xml.bind package import version range in activemq-web-console > bundle > - > > Key: AMQ-9012 > URL: https://issues.apache.org/jira/browse/AMQ-9012 > Project: ActiveMQ > Issue Type: Improvement > Components: OSGi/Karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 5.18.0, 5.17.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-3921) PG SLOT
johnson pg created ARTEMIS-3921: --- Summary: PG SLOT Key: ARTEMIS-3921 URL: https://issues.apache.org/jira/browse/ARTEMIS-3921 Project: ActiveMQ Artemis Issue Type: Bug Reporter: johnson pg [pg slot|https://pgslot.link/] pg slot เว็บสล็อตอันดับ 1 แหล่งรวมเกมสล็อตPGใหม่ล่าสุด มีให้เลือกเล่นมากกว่า 120 เกม เล่นง่ายบนมือถือ ฝาก-ถอน ออโต้ ไม่มีขั้นต่ำ สมัครเข้าเล่นง่าย 1 นาที -- This message was sent by Atlassian Jira (v8.20.10#820010)
