[jira] [Work logged] (ARTEMIS-4258) delayBeforeDispatch not working with OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-4258?focusedWorklogId=861237=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861237 ] ASF GitHub Bot logged work on ARTEMIS-4258: --- Author: ASF GitHub Bot Created on: 09/May/23 16:57 Start Date: 09/May/23 16:57 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4471: URL: https://github.com/apache/activemq-artemis/pull/4471 Issue Time Tracking --- Worklog Id: (was: 861237) Time Spent: 0.5h (was: 20m) > delayBeforeDispatch not working with OpenWire > - > > Key: ARTEMIS-4258 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4258 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.29.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4258) delayBeforeDispatch not working with OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721009#comment-17721009 ] ASF subversion and git services commented on ARTEMIS-4258: -- Commit 5f476896e9997072c8c42b429a9b6acb44cbef16 in activemq-artemis's branch refs/heads/main from Justin Bertram [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=5f476896e9 ] ARTEMIS-4258 make tests faster & more robust > delayBeforeDispatch not working with OpenWire > - > > Key: ARTEMIS-4258 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4258 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.29.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4258) delayBeforeDispatch not working with OpenWire
[ https://issues.apache.org/jira/browse/ARTEMIS-4258?focusedWorklogId=861235=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861235 ] ASF GitHub Bot logged work on ARTEMIS-4258: --- Author: ASF GitHub Bot Created on: 09/May/23 16:42 Start Date: 09/May/23 16:42 Worklog Time Spent: 10m Work Description: jbertram opened a new pull request, #4471: URL: https://github.com/apache/activemq-artemis/pull/4471 (no comment) Issue Time Tracking --- Worklog Id: (was: 861235) Time Spent: 20m (was: 10m) > delayBeforeDispatch not working with OpenWire > - > > Key: ARTEMIS-4258 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4258 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Fix For: 2.29.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4251) Support CORE client failover to other live servers
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?focusedWorklogId=861234=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861234 ] ASF GitHub Bot logged work on ARTEMIS-4251: --- Author: ASF GitHub Bot Created on: 09/May/23 16:19 Start Date: 09/May/23 16:19 Worklog Time Spent: 10m Work Description: clebertsuconic commented on code in PR #4447: URL: https://github.com/apache/activemq-artemis/pull/4447#discussion_r1188845326 ## docs/user-manual/en/client-reconnection-failover.md: ## @@ -1,10 +1,32 @@ -# Client Reconnection and Session Reattachment +# Client Reconnection and Failover Review Comment: Can we simplify the doc here? I still haven't figured out how you would configure the client to failover to another server... I thought about just having two topics would make it simpler. - Failover to a backup Server (don't worry too much about mentioning Apache ActiveMQ bblablablabla all the time) just say, if you want to reconnect to a backup server, configure this, and that. - Failover to non backup servers Mention what you have to do if you want to failover to non backup servers... There are so many options here that's getting confusing to understand. that's my only concern here. Issue Time Tracking --- Worklog Id: (was: 861234) Time Spent: 2h 10m (was: 2h) > Support CORE client failover to other live servers > -- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover connecting to other live > servers when all reconnect attempts fails, i.e. in a cluster composed of 2 > live servers, when the server to which the CORE client is connected goes down > the CORE client should reconnect its sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[ https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720970#comment-17720970 ] Liviu Citu commented on ARTEMIS-2824: - Then perfect! Thank you very much! > _AMQ_Client_ID on SESSION_CLOSED notification is always null > > > Key: ARTEMIS-2824 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2824 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.11.0 >Reporter: Tim Daly >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When a JMS client with a clientId set closes the session a notification > (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID > is always set to null. The JMS Client Id has been verified as being set via > the web UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-3042) Official Docker Multistage Build as well as an official Docker image.
[ https://issues.apache.org/jira/browse/ARTEMIS-3042?focusedWorklogId=861226=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861226 ] ASF GitHub Bot logged work on ARTEMIS-3042: --- Author: ASF GitHub Bot Created on: 09/May/23 15:31 Start Date: 09/May/23 15:31 Worklog Time Spent: 10m Work Description: gtully commented on code in PR #4297: URL: https://github.com/apache/activemq-artemis/pull/4297#discussion_r1188786028 ## artemis-image/README.md: ## @@ -0,0 +1,97 @@ +###What is in the image + +An _empty_, _open_ broker with a default acceptor on port 61616 + + - by empty: has no addresses or queues but will auto create on demand + - by open: has no security; authentication or authorization, users or roles + +###How will the image behave + + 1) the image will use or create `/app/data` for persistence of data + + 2) the image will use any [.properties files](https://activemq.apache.org/components/artemis/documentation/latest/configuration-index.html#broker_properties) from `/app/etc` to augment configuration + + 3) the image will use `/app/etc/broker.xml` if present, to bootstrap configuration, the 'bring your own config' use case + +###Build and Use + +First build an OCI image tar file from this artemis project using mvn: + + `$> mvn install` + +An OCI image is created as a tar file. + +> *Note that any OCI compatible container runtime and registry can be used for the next steps, eg: docker, podman... I have used podman.* + +To load the image tar into a registry, use: + + `$> podman image load --input target/jib-image.tar` + +To run the image with host network access, localhost:61616 will be visible, use: + + `$> podman run --net=host localhost/target/activemq-artemis-image:<...>` + +Execute the artemis producer/consumer command line tools from a `local distribution` to validate: +Note: there is a `local distribution` in ../artemis-distribution/target/apache-artemis--bin/apache-artemis-/ Review Comment: agree, will remove the suggestion to use the local distro. ## artemis-image/README.md: ## @@ -0,0 +1,93 @@ +###What is in the image + +An _empty_, _open_ broker with a default acceptor on port 61616 + + - by empty: has no addresses or queues but will auto create on demand + - by open: has no security; authentication or authorization, users or roles + +###How will the image behave + + 1) the image will use or create `/app/data` for persistence of data + + 2) the image will use any [.properties files](https://activemq.apache.org/components/artemis/documentation/latest/configuration-index.html#broker_properties) from `/app/etc` to augment configuration + + 3) the image will use `/app/etc/broker.xml` if present, to bootstrap configuration, the 'bring your own config' use case + +###Build and Use + +First build an OCI image tar file from this artemis project using mvn: + + `$> mvn install` + +An OCI image is created as a tar file, that tar can be loaded into a registry, eg: + + `$> podman image load --input target/jib-image.tar` + +To run the image with host network access, localhost:61616 will be visible, use: + + `$> podman run --net=host localhost/target/activemq-artemis-image:<...>` + +Execute the artemis producer/consumer command line tools from a `local distribution` to validate: +Note: there is a `local distribution` in ../artemis-distribution/target/apache-artemis--bin/apache-artemis-/ + + `$> ./bin/artemis producer --url tcp://127.0.0.1:61616` + + `$> ./bin/artemis consumer --url tcp://127.0.0.1:61616` + +###Intent + +The intent is that this image is useful as is. If one can trust users, having no access control or limits can work fine. + +If not, then this image can be configured by mounting an `/app/etc` directory with property files that augment default configuration. +This image could also be the base for a derived jib image, by simply adding more property files to the `src/main/resources` directory. + +###Examples Review Comment: will sort. thanks Issue Time Tracking --- Worklog Id: (was: 861226) Time Spent: 8h 20m (was: 8h 10m) > Official Docker Multistage Build as well as an official Docker image. > - > > Key: ARTEMIS-3042 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3042 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: John Behm >Priority: Minor > Labels: docker,, dockerfile,, kubernetes > Time Spent: 8h 20m > Remaining Estimate: 0h > > It would be rather convenient to get people up and running with an easy to > build or to setup Docker image that automatically builds the project from > source, discards the build container and moves the necessary files over to > the final container
[jira] [Work logged] (ARTEMIS-3042) Official Docker Multistage Build as well as an official Docker image.
[ https://issues.apache.org/jira/browse/ARTEMIS-3042?focusedWorklogId=861225=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861225 ] ASF GitHub Bot logged work on ARTEMIS-3042: --- Author: ASF GitHub Bot Created on: 09/May/23 15:30 Start Date: 09/May/23 15:30 Worklog Time Spent: 10m Work Description: gtully commented on code in PR #4297: URL: https://github.com/apache/activemq-artemis/pull/4297#discussion_r1188784971 ## artemis-image/README.md: ## @@ -0,0 +1,97 @@ +###What is in the image + +An _empty_, _open_ broker with a default acceptor on port 61616 Review Comment: I think it is simpler to utilise the sniffer and a single port. Issue Time Tracking --- Worklog Id: (was: 861225) Time Spent: 8h 10m (was: 8h) > Official Docker Multistage Build as well as an official Docker image. > - > > Key: ARTEMIS-3042 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3042 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: John Behm >Priority: Minor > Labels: docker,, dockerfile,, kubernetes > Time Spent: 8h 10m > Remaining Estimate: 0h > > It would be rather convenient to get people up and running with an easy to > build or to setup Docker image that automatically builds the project from > source, discards the build container and moves the necessary files over to > the final container that can simply be started. > The current docker image build is not really user firendly or convenient at > all. > > https://github.com/apache/activemq-artemis/tree/master/artemis-docker > The whole setup process of artemis in a containerized environment is very > far from even good. > The hurdle of using this software is gigantic, as the configuration is so > complex, one will not be able to do this within one month without having gone > through the whole documentation multiple times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-3042) Official Docker Multistage Build as well as an official Docker image.
[ https://issues.apache.org/jira/browse/ARTEMIS-3042?focusedWorklogId=861224=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861224 ] ASF GitHub Bot logged work on ARTEMIS-3042: --- Author: ASF GitHub Bot Created on: 09/May/23 15:23 Start Date: 09/May/23 15:23 Worklog Time Spent: 10m Work Description: gtully commented on code in PR #4297: URL: https://github.com/apache/activemq-artemis/pull/4297#discussion_r1188775709 ## artemis-image/pom.xml: ## @@ -0,0 +1,127 @@ + + +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> + 4.0.0 + + + org.apache.activemq + artemis-pom + 2.28.0-SNAPSHOT + + + artemis-image + Apache ActiveMQ Artemis Image + + + Official Docker Multistage Build as well as an official Docker image. > - > > Key: ARTEMIS-3042 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3042 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: John Behm >Priority: Minor > Labels: docker,, dockerfile,, kubernetes > Time Spent: 8h > Remaining Estimate: 0h > > It would be rather convenient to get people up and running with an easy to > build or to setup Docker image that automatically builds the project from > source, discards the build container and moves the necessary files over to > the final container that can simply be started. > The current docker image build is not really user firendly or convenient at > all. > > https://github.com/apache/activemq-artemis/tree/master/artemis-docker > The whole setup process of artemis in a containerized environment is very > far from even good. > The hurdle of using this software is gigantic, as the configuration is so > complex, one will not be able to do this within one month without having gone > through the whole documentation multiple times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-3042) Official Docker Multistage Build as well as an official Docker image.
[ https://issues.apache.org/jira/browse/ARTEMIS-3042?focusedWorklogId=861223=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-861223 ] ASF GitHub Bot logged work on ARTEMIS-3042: --- Author: ASF GitHub Bot Created on: 09/May/23 15:22 Start Date: 09/May/23 15:22 Worklog Time Spent: 10m Work Description: gtully commented on code in PR #4297: URL: https://github.com/apache/activemq-artemis/pull/4297#discussion_r1188774969 ## artemis-image/pom.xml: ## @@ -0,0 +1,127 @@ + + +http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;> + 4.0.0 + + + org.apache.activemq + artemis-pom + 2.28.0-SNAPSHOT + + + artemis-image + Apache ActiveMQ Artemis Image + + + Official Docker Multistage Build as well as an official Docker image. > - > > Key: ARTEMIS-3042 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3042 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: John Behm >Priority: Minor > Labels: docker,, dockerfile,, kubernetes > Time Spent: 7h 50m > Remaining Estimate: 0h > > It would be rather convenient to get people up and running with an easy to > build or to setup Docker image that automatically builds the project from > source, discards the build container and moves the necessary files over to > the final container that can simply be started. > The current docker image build is not really user firendly or convenient at > all. > > https://github.com/apache/activemq-artemis/tree/master/artemis-docker > The whole setup process of artemis in a containerized environment is very > far from even good. > The hurdle of using this software is gigantic, as the configuration is so > complex, one will not be able to do this within one month without having gone > through the whole documentation multiple times. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-2824) _AMQ_Client_ID on SESSION_CLOSED notification is always null
[
https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720950#comment-17720950
]
Justin Bertram commented on ARTEMIS-2824:
-
[~livicitu], the PR has a test to ensure the client ID property is set for both
{{SESSION_CREATED}} and {{SESSION_CLOSED}} notifications. To be clear, it
appears that this was already working.
> _AMQ_Client_ID on SESSION_CLOSED notification is always null
>
>
> Key: ARTEMIS-2824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2824
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Affects Versions: 2.11.0
>Reporter: Tim Daly
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a JMS client with a clientId set closes the session a notification
> (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID
> is always set to null. The JMS Client Id has been verified as being set via
> the web UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
