January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2000) Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2000?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2000: --------------------------- Fix Version/s: 3.6.7 I'll look at this before releasing 3.6.7, but I can't guarantee I'll fix it, as I never envisaged the way you use it. > Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications > ---------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2000 > URL: https://issues.jboss.org/browse/JGRP-2000 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Reporter: Jim Thomas > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.7 > > > The output of printProtocolSpecAsXML does not contain the pbcast package prefix for NACKACK2, GMS, STATE, etc. so the load fails due to class load failure. > Suggest either add org.jgroups.protocols.pbcast to the protocol loading search or write protocol names with full classpath when printing the spec. > Might it also make sense to skip writing out deprecated parameters? > Reason: I'm generating my protocol stack programmatically because some of the parameter values are determined at run time. In order to facilitate some experimentation with timeouts/retries/etc. I decided to temporarily use an xml file which I first generate by writing out the stack to an xml file which we can tweak the settings for subsequent runs. Since every member has a unique protocol stack keeping the edits to a minimum is helpful. (Maybe using property variables would be a better approach for me?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-591) revertReloadRequired() throws a NPE is reloadRequired has not been called

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-591?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-591: ------------------------------------------------ Romain Pelisse <rpelisse(a)redhat.com> changed the Status of [bug 1294591|https://bugzilla.redhat.com/show_bug.cgi?id=1294591] from ASSIGNED to POST > revertReloadRequired() throws a NPE is reloadRequired has not been called > ------------------------------------------------------------------------- > > Key: WFCORE-591 > URL: https://issues.jboss.org/browse/WFCORE-591 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 1.0.0.Beta1 > > > If an operation step handler calls org.jboss.as.controller.OperationContext#revertReloadRequired() when org.jboss.as.controller.OperationContext#reloadRequired() has not been called, it throws a NPE: > {noformat} > java.lang.NullPointerException > at org.jboss.as.controller.ControlledProcessState.revertReloadRequired(ControlledProcessState.java:181) > at org.jboss.as.controller.AbstractOperationContext.revertReloadRequired(AbstractOperationContext.java:1037) > at org.jboss.as.controller.test.RevertReloadRequiredTestCase$TestResourceAddHandler.rollbackRuntime(RevertReloadRequiredTestCase.java:98) > at org.jboss.as.controller.AbstractAddStepHandler$1$1.handleRollback(AbstractAddStepHandler.java:133) > at org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1419) > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1385) > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1367) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1323) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1283) > at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1172) > at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:929) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:877) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1182) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:205) > {noformat} > The NPE is caused by this.activeStep.restartStamp field which is set only when reloadRequired() (or restartRequired()) is called. > My OSH may call reloadRequired() or not depending on some runtime state and I could add some logic to make sure I call > I can fix my handle to check that I call context.revertReloadRequired() only I had previously called reloadRequired () first. > However, in order to make the OperationContext more robust, I think that the revertReloadRequired() method should instead be a no-op if there is no reload required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1019: ------------------------------------- Description: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1019?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1019: ------------------------------------- Description: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) - The release procedure will include copying the xsd file during a community .0.Final release. was: Discussion Mario & Geoffrey: - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: -- http://www.drools.org/xsd/kmodule_6_0.xsd -- http://www.drools.org/xsd/kmodule_6_1.xsd -- http://www.drools.org/xsd/kmodule_6_2.xsd -- http://www.drools.org/xsd/kmodule_6_3.xsd - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd -- Users are recommended but not obligated to change their xsd when upgrading. -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's > ------------------------------------------------------------------------------------- > > Key: DROOLS-1019 > URL: https://issues.jboss.org/browse/DROOLS-1019 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > Discussion Mario & Geoffrey: > - The xsd file will be published on drools.org, with a version in the filename under the xsd directory: > -- http://www.drools.org/xsd/kmodule_6_0.xsd > -- http://www.drools.org/xsd/kmodule_6_1.xsd > -- http://www.drools.org/xsd/kmodule_6_2.xsd > -- http://www.drools.org/xsd/kmodule_6_3.xsd > - The version in the filename does not break backwards compatibility because drools 6.3 accepts an kmodule.xml that references kmodule_6_0.xsd > -- Users are recommended but not obligated to change their xsd when upgrading. > -- This is the same versioning strategy as used for web.xml, beans.xml, etc in JEE. > - The target namespace will adjusted to avoid containing a version number (as that does break backwards compatibility) > - The release procedure will include copying the xsd file during a community .0.Final release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1019) Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-1019: ---------------------------------------- Summary: Publish kmodule.xsd (with version in filename) to allow code completion in user IDE's Key: DROOLS-1019 URL: https://issues.jboss.org/browse/DROOLS-1019 Project: Drools Issue Type: Feature Request Components: core engine Affects Versions: 6.3.0.Final Reporter: Geoffrey De Smet Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2000) Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications

by Jim Thomas (JIRA)

Jim Thomas created JGRP-2000: -------------------------------- Summary: Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications Key: JGRP-2000 URL: https://issues.jboss.org/browse/JGRP-2000 Project: JGroups Issue Type: Bug Affects Versions: 3.6.4 Reporter: Jim Thomas Assignee: Bela Ban Priority: Minor The output of printProtocolSpecAsXML does not contain the pbcast package prefix for NACKACK2, GMS, STATE, etc. so the load fails due to class load failure. Suggest either add org.jgroups.protocols.pbcast to the protocol loading search or write protocol names with full classpath when printing the spec. Might it also make sense to skip writing out deprecated parameters? Reason: I'm generating my protocol stack programmatically because some of the parameter values are determined at run time. In order to facilitate some experimentation with timeouts/retries/etc. I decided to temporarily use an xml file which I first generate by writing out the stack to an xml file which we can tweak the settings for subsequent runs. Since every member has a unique protocol stack keeping the edits to a minimum is helpful. (Maybe using property variables would be a better approach for me?) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5795) HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern.

by Michal Sudra (JIRA)

[ https://issues.jboss.org/browse/WFLY-5795?page=com.atlassian.jira.plugin.... ] Michal Sudra updated WFLY-5795: ------------------------------- Attachment: host-slave.xml > HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5795 > URL: https://issues.jboss.org/browse/WFLY-5795 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Environment: 2 node symmetrical colocated life backup cluster (domain mode). Configuration (domain.xml, host.xml) provided as attachment. > Reporter: Michal Sudra > Assignee: Jeff Mesnil > Priority: Critical > Attachments: ClusteredTopicTest.java, domain.xml, host-slave.xml, host.xml > > > Test Client is producing 10 messages on topic on node 1 and 2 consumers connected to node 1 and the other to node 2 are then consuming the messages. > Expectation: Every consumer receives 10 Messages. > Result of test: Consumer connected to node 1 is only getting every second message. Consumer connected to node 2 is receiving all 10 messages: > Output of test program: > Sent message: This is text message 0 > Sent message: This is text message 1 > Sent message: This is text message 2 > Sent message: This is text message 3 > Sent message: This is text message 4 > Sent message: This is text message 5 > Sent message: This is text message 6 > Sent message: This is text message 7 > Sent message: This is text message 8 > Sent message: This is text message 9 > 0 Recieved message: This is text message 0 from node 0 from java:/jms/topic/ClusterStateTopic > 1 Recieved message: This is text message 2 from node 0 from java:/jms/topic/ClusterStateTopic > 2 Recieved message: This is text message 4 from node 0 from java:/jms/topic/ClusterStateTopic > 3 Recieved message: This is text message 6 from node 0 from java:/jms/topic/ClusterStateTopic > 4 Recieved message: This is text message 8 from node 0 from java:/jms/topic/ClusterStateTopic > 5 error receiving message from node 0 > 6 error receiving message from node 0 > 7 error receiving message from node 0 > 8 error receiving message from node 0 > 9 error receiving message from node 0 > 0 Recieved message: This is text message 0 from node 1 from java:/jms/topic/ClusterStateTopic > 1 Recieved message: This is text message 1 from node 1 from java:/jms/topic/ClusterStateTopic > 2 Recieved message: This is text message 2 from node 1 from java:/jms/topic/ClusterStateTopic > 3 Recieved message: This is text message 3 from node 1 from java:/jms/topic/ClusterStateTopic > 4 Recieved message: This is text message 4 from node 1 from java:/jms/topic/ClusterStateTopic > 5 Recieved message: This is text message 5 from node 1 from java:/jms/topic/ClusterStateTopic > 6 Recieved message: This is text message 6 from node 1 from java:/jms/topic/ClusterStateTopic > 7 Recieved message: This is text message 7 from node 1 from java:/jms/topic/ClusterStateTopic > 8 Recieved message: This is text message 8 from node 1 from java:/jms/topic/ClusterStateTopic > 9 Recieved message: This is text message 9 from node 1 from java:/jms/topic/ClusterStateTopic > The test program is added and the 2 node names are given as parameters for main. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5795) HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern.

by Michal Sudra (JIRA)

[ https://issues.jboss.org/browse/WFLY-5795?page=com.atlassian.jira.plugin.... ] Michal Sudra commented on WFLY-5795: ------------------------------------ I forgot to attach the other host.xml for the second (slave) host of the domain. I use a Docker infrastructure for setting up the cluster in virtualbox environment on local machine. Basically I run three virtual machines, first containing the docker registry and database and the other two constructing the domain (master and slave hosts both running WildFly 10.0.0.CR4 instances and master acting as domain controller). > HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5795 > URL: https://issues.jboss.org/browse/WFLY-5795 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Environment: 2 node symmetrical colocated life backup cluster (domain mode). Configuration (domain.xml, host.xml) provided as attachment. > Reporter: Michal Sudra > Assignee: Jeff Mesnil > Priority: Critical > Attachments: ClusteredTopicTest.java, domain.xml, host.xml > > > Test Client is producing 10 messages on topic on node 1 and 2 consumers connected to node 1 and the other to node 2 are then consuming the messages. > Expectation: Every consumer receives 10 Messages. > Result of test: Consumer connected to node 1 is only getting every second message. Consumer connected to node 2 is receiving all 10 messages: > Output of test program: > Sent message: This is text message 0 > Sent message: This is text message 1 > Sent message: This is text message 2 > Sent message: This is text message 3 > Sent message: This is text message 4 > Sent message: This is text message 5 > Sent message: This is text message 6 > Sent message: This is text message 7 > Sent message: This is text message 8 > Sent message: This is text message 9 > 0 Recieved message: This is text message 0 from node 0 from java:/jms/topic/ClusterStateTopic > 1 Recieved message: This is text message 2 from node 0 from java:/jms/topic/ClusterStateTopic > 2 Recieved message: This is text message 4 from node 0 from java:/jms/topic/ClusterStateTopic > 3 Recieved message: This is text message 6 from node 0 from java:/jms/topic/ClusterStateTopic > 4 Recieved message: This is text message 8 from node 0 from java:/jms/topic/ClusterStateTopic > 5 error receiving message from node 0 > 6 error receiving message from node 0 > 7 error receiving message from node 0 > 8 error receiving message from node 0 > 9 error receiving message from node 0 > 0 Recieved message: This is text message 0 from node 1 from java:/jms/topic/ClusterStateTopic > 1 Recieved message: This is text message 1 from node 1 from java:/jms/topic/ClusterStateTopic > 2 Recieved message: This is text message 2 from node 1 from java:/jms/topic/ClusterStateTopic > 3 Recieved message: This is text message 3 from node 1 from java:/jms/topic/ClusterStateTopic > 4 Recieved message: This is text message 4 from node 1 from java:/jms/topic/ClusterStateTopic > 5 Recieved message: This is text message 5 from node 1 from java:/jms/topic/ClusterStateTopic > 6 Recieved message: This is text message 6 from node 1 from java:/jms/topic/ClusterStateTopic > 7 Recieved message: This is text message 7 from node 1 from java:/jms/topic/ClusterStateTopic > 8 Recieved message: This is text message 8 from node 1 from java:/jms/topic/ClusterStateTopic > 9 Recieved message: This is text message 9 from node 1 from java:/jms/topic/ClusterStateTopic > The test program is added and the 2 node names are given as parameters for main. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5934) Make IP address of remote JMS client accessible from within a login module

by Derek Horton (JIRA)

Derek Horton created WFLY-5934: ---------------------------------- Summary: Make IP address of remote JMS client accessible from within a login module Key: WFLY-5934 URL: https://issues.jboss.org/browse/WFLY-5934 Project: WildFly Issue Type: Feature Request Components: Domain Management, Security Reporter: Derek Horton Assignee: Darran Lofthouse Make the IP address of remote EJB clients accessible from within a login module login module when the security-realm is configured to defer to JAAS. This is possible when the authentication is handled by the security-realm, but it is not possible when the security-realm defers to a security-domain (JAAS). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1018) bigdecimal field compare

by Sante Stanisci (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1018?page=com.atlassian.jira.plugi... ] Sante Stanisci commented on DROOLS-1018: ---------------------------------------- yes. Best Regards > bigdecimal field compare > ------------------------ > > Key: DROOLS-1018 > URL: https://issues.jboss.org/browse/DROOLS-1018 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Environment: windows 8, java 1.6 > Reporter: Sante Stanisci > Assignee: Mario Fusco > Labels: bigdecimal, compare, field > Attachments: check_cond.drl, CtbTitoli.java > > > Comparing two field of bigdecimal, rule not file -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016