[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:30 PM:
--
i have added the [^setup.tar] in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
before restart :
!image-2020-04-01-16-27-26-201.png!
After restart of frontend broker :
!image-2020-04-01-16-30-27-209.png!
was (Author: vaishno.avi):
i have added the [^setup.tar] in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!image-2020-04-01-16-14-32-534.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: image-2020-04-01-16-14-32-534.png,
> image-2020-04-01-16-27-26-201.png, image-2020-04-01-16-30-27-209.png,
> offline_topic_durable_subscriber.png, setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *dur
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:14 PM:
--
i have added the [^setup.tar] in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!image-2020-04-01-16-14-32-534.png!
was (Author: vaishno.avi):
i have added the [^setup.tar] in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!image-2020-04-01-16-09-13-805.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: image-2020-04-01-16-09-13-805.png,
> image-2020-04-01-16-14-32-534.png, offline_topic_durable_subscriber.png,
> screenshot-1.png, setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes t
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:12 PM:
--
i have added the [^setup.tar] in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!image-2020-04-01-16-09-13-805.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!image-2020-04-01-16-09-13-805.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: image-2020-04-01-16-09-13-805.png,
> offline_topic_durable_subscriber.png, screenshot-1.png, setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of dura
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:09 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!image-2020-04-01-16-09-13-805.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: image-2020-04-01-16-09-13-805.png,
> offline_topic_durable_subscriber.png, screenshot-1.png, setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happen
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:06 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and restart it to see an
offline durable subscriber. http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable subscriber.
http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describ
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:05 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable subscriber.
http://localhost:8161/admin/subscribers.jsp
credentials :
username : admin
password: admin
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable subscriber.
http://localhost:8161/admin/subscribers.jsp
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describe
> the issue.
> Config with kahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
>
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 2:03 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable subscriber.
http://localhost:8161/admin/subscribers.jsp
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describe
> the issue.
> Config with kahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-cor
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072748#comment-17072748
]
Ashish edited comment on AMQ-7350 at 4/1/20, 1:58 PM:
--
Dockerfile for the activemq image :
was (Author: vaishno.avi):
Dockerfile for the activemq image :
{code:java}
# vim:set ft=dockerfile:
FROM openjdk:8-jre-alpine
ARG COMPONENT_NAME="activemq"
ARG COMPONENT_HOME="/opt/integration/${COMPONENT_NAME}"
RUN apk add --no-cache procps curl tar gzip && \
wget
"http://www.apache.org/dyn/closer.cgi?filename=/activemq/5.15.12/apache-activemq-5.15.12-bin.tar.gz&action=download";
-O /tmp/apache-activemq.tar.gz && \
mkdir --parents "${COMPONENT_HOME}" && \
tar xzf /tmp/apache-activemq.tar.gz --strip-components=1 -C
"${COMPONENT_HOME}" && \
rm /tmp/apache-activemq.tar.gz && \
rm /opt/integration/activemq/bin/env && \
ln -s /opt/integration/activemq/activemq-env/env
/opt/integration/activemq/bin/env
VOLUME ["${COMPONENT_HOME}/data", \
"${COMPONENT_HOME}/logs", \
"${COMPONENT_HOME}/temp" ]
EXPOSE 8161 61616 61612 5672
CMD ["/opt/integration/activemq/bin/activemq", "console"]
{code}
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describe
> the issue.
> Config with kahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd";>
>class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
> file:${activemq.conf}/credentials.properties
>
>
> http://activemq.apache.org/schema/core";
> brokerName="MQ-MY-BROKER-NAME" dataDirectory="${activemq.data}"
> schedulerSupport="false" persistent="true">
>
>
>
>
>
>
>
>
>
>
>
>
>
>memoryLimit="20mb">
>
>useQueueForQueueMessages="true"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireformat.maxFrameSize=104857600"/>
>uri="stomp://0.0.0.0:61612?maximumConnections=1000&transport.closeAsync=false&connectionTimeout=12&wireformat.maxFrameSize=104857600"/>
>
>
>
> http://www.springframework.org/schema/beans";
> class="org.apache.activemq.hooks.SpringContextHook" />
>
>
>
>
>
> {code}
> Config with mkahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd";>
>class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
> file:${activemq.conf}/credentials.properties
>
>
> http://activemq.apache.org/schema/core";
> brokerName="MQ-MY-BROKER-NAME" dataDirectory="${activemq.data}"
> schedulerSupport="false" persistent="true">
>
>
>
>
>
>
>
>
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 1:58 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
docker network create --driver bridge test
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describe
> the issue.
> Config with kahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd";>
>class="org.springframework.beans.factory.config.PropertyPlaceholderConfigur
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 1:45 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
{code:java}
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml down
-v
sleep 10
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
!screenshot-1.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
* !screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describe
> the issue.
> Config with kahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd";>
>class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
> file:${activemq.conf}/credentials.properties
>
>
> http://activemq.apache.org/schema/core";
> brokerName="MQ-MY-BROKER-NAME" dataDirectory="${activemq.data}"
> schedulerSupport="false" persistent="true">
>
>
>
>
>
>
>
>
>
>
>
>
>
>memoryLimit="20mb">
>
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072753#comment-17072753
]
Ashish edited comment on AMQ-7350 at 4/1/20, 1:44 PM:
--
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* start all the containers using docker-compose command
{code:java}
export PATH_OF_EXTRACTION=
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
$PATH_OF_EXTRACTION/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f $PATH_OF_EXTRACTION/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
* !screenshot-1.png!
was (Author: vaishno.avi):
i have added the setup.tar in the ticket to re-produce the issue
Setups :
* Extract the tar
* build the docker image
{code:java}
docker build . -t activemq:latest
{code}
* edit the docker-compose file and replace *path_of_extraction* with your local
path
* start all the containers using docker-compose command
{code:java}
docker-compose -f
path_of_extraction/mq-com.backend.broker.abcd/conf/docker-compose.yml up -d
docker-compose -f
path_of_extraction/mq-com.backend.broker.defg/conf/docker-compose.yml up -d
docker-compose -f
path_of_extraction/mq-com.backend.broker.hikj/conf/docker-compose.yml up -d
docker-compose -f
path_of_extraction/mq-com.backend.broker.lmno/conf/docker-compose.yml up -d
docker-compose -f
path_of_extraction/mq-com.backend.broker.tuvw/conf/docker-compose.yml up -d
docker-compose -f
path_of_extraction/mq-com.backend.broker.xyz/conf/docker-compose.yml up -d
docker-compose -f path_of_extraction/mq-frontend/conf/docker-compose.yml up -d
{code}
* you will have to then just stop the frontend broker and repeat(atleast twice)
this till you see an offline durable susbcriber
* !screenshot-1.png!
> Inconsistency in Offline Durable Topic Subscribers
> --
>
> Key: AMQ-7350
> URL: https://issues.apache.org/jira/browse/AMQ-7350
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 5.15.10
>Reporter: Ashish
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Attachments: offline_topic_durable_subscriber.png, screenshot-1.png,
> setup.tar
>
>
> Hello All,
> * I have a issue with my activemq setup with *durable subscription*.
> * My setup includes a broker with topics and the backend that durably
> subscribes to these topics.
> * Random mapping of durable subscribers happens on each restart. In order to
> fix it, I always have to wipe the persistence
> * All the topics are created via activemq.xml
> * With the usage of kahadb/mkahadb, I want to enable persistence as well. In
> doing so, after the restart of my broker i get inconsistency in my offline
> durable topic susbcribers.
> I am also attaching the config used by me. As well as an image to describe
> the issue.
> Config with kahadb
> {code:java}
> xmlns="http://www.springframework.org/schema/beans";
> xmlns:amq="http://activemq.apache.org/schema/core";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://activemq.apache.org/schema/core
> http://activemq.apache.org/schema/core/activemq-core.xsd";>
>class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
> file:${activemq.conf}/credentials.properties
>
>
> http://activemq.apache.org/schema/core";
> brokerName="MQ-MY-BROKER-NAME" dataDirectory="${activemq.data}"
> schedulerSupport="false" persistent="true">
>
>
>
>
>
>
>
>
>
>
>
>
>
>memoryLimit="20mb">
>
>useQueueForQueueMessages="true"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
[jira] [Comment Edited] (AMQ-7350) Inconsistency in Offline Durable Topic Subscribers
[
https://issues.apache.org/jira/browse/AMQ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981616#comment-16981616
]
Robbie Gemmell edited comment on AMQ-7350 at 11/25/19 2:48 PM:
---
There is some additional log details and summary in the nabble thread which, at
least in my case, did not make it through to the mailing list:
http://activemq.2283324.n4.nabble.com/offline-Durable-Topic-Subscribers-issue-in-activemq-5-15-8-tp4753263p4753376.html
{noformat}
I also wiped out my persistence today. Started the broker and then restarted
the broker.
I again ended up in the same issue. Below are the actual debug logs wrt to the
diagram attached in the original ticket
2019-11-15 13:55:39,664 | DEBUG | Restoring durable subscription:
SubscriptionInfo {subscribedDestination = topic://Hello.V1, destination =
topic://Hello.V1, clientId = broker-name-2-world_world, subscriptionName =
hello, selector = null, noLocal = false} |
org.apache.activemq.broker.region.TopicRegion | main
2019-11-15 13:55:39,668 | DEBUG | Restoring durable subscription:
SubscriptionInfo {subscribedDestination = topic://World.V1, destination =
topic://World.V1, clientId = broker-name-2-world_world, subscriptionName =
world, selector = null, noLocal = false} |
org.apache.activemq.broker.region.TopicRegion | main
2019-11-15 13:55:40,194 | DEBUG | Setting up new connection id:
ID:MY_SERVER-40009-1573807342637-4:169, address: tcp://MY_IP:59706, info:
ConnectionInfo {commandId = 1, responseRequired = true, connectionId =
ID:MY_SERVER-40009-1573807342637-4:169, clientId = broker-name-2-world_world,
clientIp = null, userName = MY_USERNAME, password = *, brokerPath = null,
brokerMasterConnector = false, manageable = true, clientMaster = true,
faultTolerant = false, failoverReconnect = false} |
org.apache.activemq.broker.TransportConnection | ActiveMQ Transport:
tcp:///MY_IP:PORT@61616
2019-11-15 13:55:40,261 | DEBUG | Deactivating keepActive=true,
DurableTopicSubscription-broker-name-2-world:world,
id=ID:MY_SERVER-40009-1573807342637-4:169:1:1, active=false, destinations=1,
total=0, pending=0, dispatched=0, inflight=0, prefetchExtension=0 |
org.apache.activemq.broker.region.DurableTopicSubscription | ActiveMQ
Transport: tcp:///MY_IP:PORT@61616
2019-11-15 13:55:40,261 | DEBUG | Activating
DurableTopicSubscription-broker-name-2-world:world,
id=ID:MY_SERVER-40009-1573807342637-4:169:1:1, active=false, destinations=1,
total=0, pending=0, dispatched=0, inflight=0, prefetchExtension=0 |
org.apache.activemq.broker.region.DurableTopicSubscription | ActiveMQ
Transport: tcp:///MY_IP:PORT@61616
2019-11-15 13:55:40,262 | DEBUG | Unregistering MBean
org.apache.activemq:type=Broker,brokerName=MY_FRONTEND,destinationType=Topic,destinationName=World.V1,endpoint=Consumer,clientId=broker-name-2-world,consumerId=Durable(broker-name-2-world_world)
| org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ Transport:
tcp:///MY_IP:PORT@61616
Summary :
It restored 2 durable subscriber even though there is just one for that topic.
Sets up connection, deactivate correct subscriber,activate correct subscriber
No more information for the wrongly mapped offline subscriber
{noformat}
was (Author: gemmellr):
There is some additional log details and summary in the nabble thread which, at
least in my case, did not make it through to the mailing list:
http://activemq.2283324.n4.nabble.com/offline-Durable-Topic-Subscribers-issue-in-activemq-5-15-8-tp4753263p4753376.html
{quote}
I also wiped out my persistence today. Started the broker and then restarted
the broker.
I again ended up in the same issue. Below are the actual debug logs wrt to the
diagram attached in the original ticket
2019-11-15 13:55:39,664 | DEBUG | Restoring durable subscription:
SubscriptionInfo {subscribedDestination = topic://Hello.V1, destination =
topic://Hello.V1, clientId = broker-name-2-world_world, subscriptionName =
hello, selector = null, noLocal = false} |
org.apache.activemq.broker.region.TopicRegion | main
2019-11-15 13:55:39,668 | DEBUG | Restoring durable subscription:
SubscriptionInfo {subscribedDestination = topic://World.V1, destination =
topic://World.V1, clientId = broker-name-2-world_world, subscriptionName =
world, selector = null, noLocal = false} |
org.apache.activemq.broker.region.TopicRegion | main
2019-11-15 13:55:40,194 | DEBUG | Setting up new connection id:
ID:MY_SERVER-40009-1573807342637-4:169, address: tcp://MY_IP:59706, info:
ConnectionInfo {commandId = 1, responseRequired = true, connectionId =
ID:MY_SERVER-40009-1573807342637-4:169, clientId = broker-name-2-world_world,
clientIp = null, userName = MY_USERNAME, password = *, brokerPath = null,
brokerMasterConnector = false, manageable = true, clientMaster = true,
faultTolerant = false, failoverReconnect = false} |
org.apache.activemq.broker.TransportCo
