[JBoss JIRA] (JGRP-1559) FD: monitor task sometimes isn't running
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1559?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1559 at 12/27/12 12:06 PM:
-----------------------------------------------------------
This method is called every 2 seconds:
{code}
private void startFdMonitorIfNeeded(FD fd, JChannel channel) {
boolean moreThanTwoMembersInCluster = channel.isConnected() &&
channel.getView().getMembers().size() > 1;
if( moreThanTwoMembersInCluster ) {
if( !fd.isMonitorRunning() ) {
fd.startFailureDetection();
LOG.error("FD forcefully started for nodeId = " +
channel.getName() + ", cluster = " + channel.getClusterName());
}
}
}
{code}
After 65 min it reported that task was not running.
was (Author: belaban):
This method is called every 2 seconds:
private void startFdMonitorIfNeeded(FD fd, JChannel channel) {
boolean moreThanTwoMembersInCluster = channel.isConnected() &&
channel.getView().getMembers().size() > 1;
if( moreThanTwoMembersInCluster ) {
if( !fd.isMonitorRunning() ) {
fd.startFailureDetection();
LOG.error("FD forcefully started for nodeId = " +
channel.getName() + ", cluster = " + channel.getClusterName());
}
}
}
After 65 min it reported that task was not running.
> FD: monitor task sometimes isn't running
> ----------------------------------------
>
> Key: JGRP-1559
> URL: https://issues.jboss.org/browse/JGRP-1559
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.2.6, 3.3
>
>
> FD.isMonitorRunning() is sometimes false even when the membership is > 1. Probable cause is restartMonitor() will stops the running monitor, but doesn't start a new one if ping_dest == null.
> Need to investigate concurrent updates to pingable_mbrs and ping_dest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JGRP-1559) FD: monitor task sometimes isn't running
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1559?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1559:
--------------------------------
This method is called every 2 seconds:
private void startFdMonitorIfNeeded(FD fd, JChannel channel) {
boolean moreThanTwoMembersInCluster = channel.isConnected() &&
channel.getView().getMembers().size() > 1;
if( moreThanTwoMembersInCluster ) {
if( !fd.isMonitorRunning() ) {
fd.startFailureDetection();
LOG.error("FD forcefully started for nodeId = " +
channel.getName() + ", cluster = " + channel.getClusterName());
}
}
}
After 65 min it reported that task was not running.
> FD: monitor task sometimes isn't running
> ----------------------------------------
>
> Key: JGRP-1559
> URL: https://issues.jboss.org/browse/JGRP-1559
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.2.6, 3.3
>
>
> FD.isMonitorRunning() is sometimes false even when the membership is > 1. Probable cause is restartMonitor() will stops the running monitor, but doesn't start a new one if ping_dest == null.
> Need to investigate concurrent updates to pingable_mbrs and ping_dest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JGRP-1559) FD: monitor task sometimes isn't running
by Bela Ban (JIRA)
Bela Ban created JGRP-1559:
------------------------------
Summary: FD: monitor task sometimes isn't running
Key: JGRP-1559
URL: https://issues.jboss.org/browse/JGRP-1559
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.2.6, 3.3
FD.isMonitorRunning() is sometimes false even when the membership is > 1. Probable cause is restartMonitor() will stops the running monitor, but doesn't start a new one if ping_dest == null.
Need to investigate concurrent updates to pingable_mbrs and ping_dest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6104) jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()
by Raymond Naseef (JIRA)
[ https://issues.jboss.org/browse/AS7-6104?page=com.atlassian.jira.plugin.s... ]
Raymond Naseef edited comment on AS7-6104 at 12/27/12 10:59 AM:
----------------------------------------------------------------
This comment on 2012-12-07 made no sense. Keeping as this was referenced later in the timeline
was (Author: raymond.naseef):
Reinstalled JBoss 7.1.1 and repeated steps on the same computer. :remove succeeded, so there were no errors. I will look into this more, but expect it will be closed unless something comes up.
> jboss-cli failed to remove PostgreSQL datasource module NullPointerException OperationContextImpl.doRemove()
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6104
> URL: https://issues.jboss.org/browse/AS7-6104
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 7.1.1.Final
> Environment: Windows 7 Professional SP1
> Reporter: Raymond Naseef
> Assignee: Brian Stansberry
> Labels: jboss-as7, modules, postgresql
> Fix For: 7.2.0.Alpha1
>
>
> NullPointerException during jboss-cli remove with command:
> jboss-cli --connect command="/subsystem=datasources/jdbc-driver=bop:remove"
> Console and log below.
> This happens when standalone.xml has XML entry for driver that does not exist (see "Steps to Reproduce"). I have also seen this happen in a case where the driver does exist; not sure how the latter happened, or how important that is.
> MS-DOS Console:
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014749: Operation handler failed: null",
> "rolled-back" => true
> }
> Server Log:
> 23:17:42,627 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 19) JBAS014612: Operation ("remove") failed - address: ([
> ("subsystem" => "datasources"),
> ("jdbc-driver" => "postgresql-driver")
> ]): java.lang.NullPointerException
> at org.jboss.as.controller.OperationContextImpl.doRemove(OperationContextImpl.java:298) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.OperationContextImpl.removeService(OperationContextImpl.java:293) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.connector.subsystems.datasources.JdbcDriverRemove.performRuntime(JdbcDriverRemove.java:66)
> at org.jboss.as.controller.AbstractRemoveStepHandler$1.execute(AbstractRemoveStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (JGRP-1558) Discovery: don't suppress response when merging for non-merge triggered discovery requests
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1558?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1558:
--------------------------------
The functionality to only return the physical address / logical name for a specific (requested) member is redundant as return_entire_cache=true performs a similar task.
> Discovery: don't suppress response when merging for non-merge triggered discovery requests
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-1558
> URL: https://issues.jboss.org/browse/JGRP-1558
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> In Discovery, when receiving a discovery request, we discard it if a merge is running (isMergeRunning()). The condition should be moved into the if-clause above (hdr.view_id != null), as it only applies to merge-triggered discoveries. When handling a regular discovery, e.g. at startup or when a physical address is looked up, a discovery response should be sent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6141) JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6141?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy edited comment on AS7-6141 at 12/27/12 7:09 AM:
---------------------------------------------------------------------
If you have a properly configured settings.xml file in your ~/.m2 directory, you should not need to use the example-settings.xml file. This file is present to show you how to configure Maven to use the examples. Skip this step if you have maven installed and running or if you are running the examples in an IDE that has a properly configured Maven plugin. If after skipping this step, the examples still don't work, please place a comment on this thread and paste the exception or error that you are getting. In the mean time I will research where this file has been placed.
was (Author: mikevan):
If you have a properly configured settings.xml file in your ~/.m2 directory, you should not need to use the example-settings.xml file. This file is present to show you how to configure Maven to use the examples. Skip this step if you have maven installed and running or if you are running the examples in an IDE that has a properly configured Maven plugin. If after skipping this step, the example don't work, please place a comment on this thread and paste the exception or error that you are getting. In the mean time I will research where this file has been placed.
> JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
> -------------------------------------------------------------------------------------------
>
> Key: AS7-6141
> URL: https://issues.jboss.org/browse/AS7-6141
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 7.1.1.Final
> Environment: JBoss Developer Framework site. http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/#introduction
> Reporter: Rick Wagner
> Priority: Critical
>
> The README.md describes an 'example-settings.xml' file that should be 'in the root of your quickstarts folder'. There does not seem to be such a file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6141) JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6141?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy commented on AS7-6141:
-------------------------------------------
If you have a properly configured settings.xml file in your ~/.m2 directory, you should not need to use the example-settings.xml file. This file is present to show you how to configure Maven to use the examples. Skip this step if you have maven installed and running or if you are running the examples in an IDE that has a properly configured Maven plugin. If after skipping this step, the example don't work, please place a comment on this thread and paste the exception or error that you are getting. In the mean time I will research where this file has been placed.
> JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
> -------------------------------------------------------------------------------------------
>
> Key: AS7-6141
> URL: https://issues.jboss.org/browse/AS7-6141
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 7.1.1.Final
> Environment: JBoss Developer Framework site. http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/#introduction
> Reporter: Rick Wagner
> Priority: Critical
>
> The README.md describes an 'example-settings.xml' file that should be 'in the root of your quickstarts folder'. There does not seem to be such a file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (AS7-6248) Missing file from Nexus preventing build of Arquillian TestNG Integration
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6248?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy edited comment on AS7-6248 at 12/27/12 5:39 AM:
---------------------------------------------------------------------
Patch file "0001-Moved-testng-integration-to-the-base-directory-and-m.patch" implements option 2 of this ticket. Released under ASF2.0 license.
was (Author: mikevan):
Implements option 2 of this ticket. Released under ASF2.0 license.
> Missing file from Nexus preventing build of Arquillian TestNG Integration
> -------------------------------------------------------------------------
>
> Key: AS7-6248
> URL: https://issues.jboss.org/browse/AS7-6248
> Project: Application Server 7
> Issue Type: Bug
> Components: Build System
> Affects Versions: 7.2.0.Alpha1
> Environment: CentOS 6.3, Intel X86-64
> Reporter: Michael Van Geertruy
> Assignee: Paul Gier
> Labels: Arquillian
> Attachments: 0001-Moved-testng-integration-to-the-base-directory-and-m.patch, AS7-6248-patch.txt
>
>
> After downloading the most recent codebase from git for jbossAS 7.2.0.SNAPSHOT, I recieved the following error:
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Arquillian TestNG Integration 7.2.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> [WARNING] The POM for org.jboss.as:jboss-as-spec-api:pom:7.2.0.Alpha1-SNAPSHOT is missing, no dependency information available
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [3.091s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [7.331s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [7.461s]
> [INFO] JBoss Application Server: Arquillian Embedded Container SUCCESS [18.654s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.766s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [19.634s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [2.147s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration FAILURE [3.535s]
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:08.150s
> [INFO] Finished at: Sat Dec 22 23:43:21 PST 2012
> [INFO] Final Memory: 51M/317M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project jboss-as-arquillian-testng-integration: Could not resolve dependencies for project org.jboss.as:jboss-as-arquillian-testng-integration:jar:7.2.0.Alpha1-SNAPSHOT
> Indeed after looking at the jboss nexus repository I came across this link:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbo...
> There do not appear to be any entries for 7.2.0.Alpha1-SNAPSHOT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months