[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-04-18 Thread Catalin Alexandru Zamfir (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16442198#comment-16442198
 ] 

Catalin Alexandru Zamfir commented on ARTEMIS-1737:
---

Hello,

We have a live/backup1/backup2 set-up. When doing failovers (we're testing the 
different scenarios), the Hawtio console does not start back-up with the live 
server. We have a healtheck in Docker on 8161 and when our current "live" has 
come back the console is not active.

 
{code:java}
db21d0feaebb        
artifactory.d.g.org/external/default/production/artemis:2.5.0                
"/var/lib/artemis/..."   2 hours ago         Up 32 minutes (unhealthy)          
             i1-shared-artemis-r1-p
{code}
The live server for us is i1-shared-artemis-r1-p. We' know this from logs:
{code:java}
2018-04-18 09:07:52.595 dlk-p-mqs001 dockerc: i1-shared-artemis-r1-p: 
2018-04-18 09:07:49,118 INFO [org.apache.activemq.artemis.core.server] 
AMQ221020: Started EPOLL Acceptor at 10.117.28.32:61616 for protocols 
[CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
2018-04-18 09:07:52.595 dlk-p-mqs001 dockerc: i1-shared-artemis-r1-p: 
2018-04-18 09:07:49,063 INFO [org.apache.activemq.artemis.core.server] 
AMQ221007: Server is now live
2018-04-18 09:07:52.595 dlk-p-mqs001 dockerc: i1-shared-artemis-r1-p: 
2018-04-18 09:07:48,448 INFO [org.apache.activemq.artemis.core.server] 
AMQ221071: Failing over based on quorum vote results.
{code}
But trying to contact the port (command line or browser) we cannot connect:
{code:java}
root@dlk-p-mqs001:/ # nc -zv i1-shared-artemis-r1-p.d.g.org 8161
nc: connect to i1-shared-artemis-r1-p.d.g.org port 8161 (tcp) failed: 
Connection refused
root@dlk-p-mqs001:/ # date
Wed Apr 18 09:44:04 UTC 2018{code}
Healthcheck (in Compose format):
{code:java}
healthcheck:
  test: [CMD, nc, -zv, i1-shared-artemis-r1-p.d.g.org, '8161']
  interval: 90s
  timeout: 10s
  retries: 3
  start_period: 60s

{code}
 

> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
> Fix For: 2.5.0
>
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392964#comment-16392964
 ] 

ASF subversion and git services commented on ARTEMIS-1737:
--

Commit dc096f950d24e47f48883fdd49b27f51914d5783 in activemq-artemis's branch 
refs/heads/master from [~sknot]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=dc096f9 ]

ARTEMIS-1737 fix for inaccessible slave console after failover


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-09 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392970#comment-16392970
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/1945


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-09 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392965#comment-16392965
 ] 

ASF subversion and git services commented on ARTEMIS-1737:
--

Commit 91c0452d601729585cd75e4d74c473b92f3bd1af in activemq-artemis's branch 
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=91c0452 ]

ARTEMIS-1737 Fixing semantic of ServerControl.forceFailover

This closes #1940


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-09 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392871#comment-16392871
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1945
  
@michaelandrepearce when isExit=true, it means the VM is going away. The 
previous task was to shutdown the server upon a forceCall, on that case isExit 
must be true.

I changed it to the previous method and I am using @stanlyDoge's test to 
validate it.


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392398#comment-16392398
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1945
  
@michaelandrepearce ^^


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392397#comment-16392397
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

GitHub user clebertsuconic opened a pull request:

https://github.com/apache/activemq-artemis/pull/1945

ARTEMIS-1737 Fixing WebServer stopped

This is replacing #1940 

#1940 will be closed when this one is merged.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-1737

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/1945.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1945


commit dc096f950d24e47f48883fdd49b27f51914d5783
Author: Stanislav Knot 
Date:   2018-03-08T10:03:37Z

ARTEMIS-1737 fix for inaccessible slave console after failover

commit 6a0f3232c7921e6e67cd8211e4b05d065cffcceb
Author: Clebert Suconic 
Date:   2018-03-08T21:24:38Z

ARTEMIS-1737 Fixing semantic of ServerControl.forceFailover

This closes #1940




> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392069#comment-16392069
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
@michaelandrepearce will do.. I thought I would be able to do it tonight... 
I'm hitting another issue.. so it will be tomorrow.


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392062#comment-16392062
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
@clebertsuconic i assume you will PR your modifications before merge.


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391935#comment-16391935
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user clebertsuconic commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
I'm running the testsuite... I will merge a modified patch.. thanks a lot 
@stanlyDoge 


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391844#comment-16391844
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
@stanlyDoge nice test though!! What ever the fix worth making sure it gets 
added in :)


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391264#comment-16391264
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user stanlyDoge commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
Ah, I see. Yeah, it seem to be changed in 
[ARTEMIS-1440](https://issues.apache.org/jira/browse/ARTEMIS-1440). 
@clebertsuconic can you take a look?


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391254#comment-16391254
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
@stanlyDoge its not just the console affected. the root cause of the issue 
you are seeing was that actually fail() method called prior to your change used 
to have the isExit flag to false, there are actually a few places that can be 
invoked as well, as such whilst the negative effect of this change that ive 
called out, is most visible with the console, there are more serious bits seen 
that also look like they're affected such as Network Pinger. 

This really needs to have @clebertsuconic look over his original change, as 
it seems that it is what caused this, also others in my opinion. And any fix 
needs to not just care about the console.


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391251#comment-16391251
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user stanlyDoge commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
Yes, it is. I used this conf: https://pastebin.com/2G0c341X
If I am not wrong, restaring logic is implemented as 
[this](https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/SharedNothingLiveActivation.java#L194).
I am not sure if it would be ok to iterate all ExternalComponents here and 
if it is web one, just start it again. What do you think?


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARTEMIS-1737) When live-slave fails-back to master, it turns off everything down, even its console

2018-03-08 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391237#comment-16391237
 ] 

ASF GitHub Bot commented on ARTEMIS-1737:
-

Github user michaelandrepearce commented on the issue:

https://github.com/apache/activemq-artemis/pull/1940
  
Is this on fail back to master? With restart enabled?

If so shouldn’t the console be in the restarting logic with the other 
components?


> When live-slave fails-back to master, it turns off everything down, even its 
> console
> 
>
> Key: ARTEMIS-1737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1737
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Stanislav Knot
>Assignee: Stanislav Knot
>Priority: Major
>
> 1) Set up HA pair with slave {{true}}
> 2) Kill master
> 3) Make sure slave becomes live
> 4) Start master again, slave gives control to master and becomes a slave
> 5) Console of slave (backup now) becomes inaccessible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)