[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1876:
---------------------------
Fix Version/s: 3.5.1
> MERGE3 : Strange number and content of subgroups
> ------------------------------------------------
>
> Key: JGRP-1876
> URL: https://issues.jboss.org/browse/JGRP-1876
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.2
> Reporter: Karim AMMOUS
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
> Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log
>
>
> Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2).
> The final mergeView is correct and contains 210 members.
> Here is an extract of subviews:
> {code}
> INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172]
> 210 subgroups
> [....
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]]
> [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]]
> ....]
> {code}
> II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view.
> Example:
> {code}
> {A, B, C} => {A, B, C} and {C} => {A, B, C}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1876:
--------------------------------
h4. Simple solution
* I left the proven code for merging intact and only added the list of subgroups to Merger
* Before creating the MergeView, all views in subviews whose creators are not in the new view are removed from subviews
* Merger.subviews is then passed into the new MergeView
This is the least intrusive way to fix this problem and doesn't touch critical merging code
> MERGE3 : Strange number and content of subgroups
> ------------------------------------------------
>
> Key: JGRP-1876
> URL: https://issues.jboss.org/browse/JGRP-1876
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.2
> Reporter: Karim AMMOUS
> Assignee: Bela Ban
> Fix For: 3.6
>
> Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log
>
>
> Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2).
> The final mergeView is correct and contains 210 members.
> Here is an extract of subviews:
> {code}
> INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172]
> 210 subgroups
> [....
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]]
> [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]]
> [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]]
> ....]
> {code}
> II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view.
> Example:
> {code}
> {A, B, C} => {A, B, C} and {C} => {A, B, C}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (DROOLS-599) kjar archertype
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-599?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-599:
----------------------------------
Assignee: Mario Fusco (was: Mark Proctor)
> kjar archertype
> ---------------
>
> Key: DROOLS-599
> URL: https://issues.jboss.org/browse/DROOLS-599
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.1.0.Final
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Fix For: 6.2.0.CR1
>
>
> I'm opening this JIRA as I will later open PR related to https://groups.google.com/d/msg/drools-development/uO17-kC4mvc/aBRunEcZ_b4J
> The version of the archetype defaults for non-CEP, non-Eclipse plugin in pom. There are property which user can change default value to have CEP, and Eclipse plug-in.
> For reference,
> * Set-up the new project's pom:
> ** Change Java version to 1.6 or greater, by including the maven-compiler-plugin
> ** Add Drools dependencies
> ** Change JUnit dependencies to version 4
> ** Add kie-maven-plugin
> ** [option] Add plug-in org.eclipse.m2e/lifecycle-mapping settings, to avoid Eclipse ERROR at the pom.xml line defining the kie-maven-plugin
> ** Set packaging to 'kjar'
> * ( ALT + F5 in betweens )
> * Creation of an initial .drl file in src/main/resources
> * Creation of minimal kmodule.xml in src/main/resources/META-INF directory
> * Create a simple JUnit test for:
> ** Creation of KieBase [option ->] with STREAM option for CEP features
> ** Creation of KieSession [option ->] with pseudo-clock
> ** [option: Advance] / Insert / Fire template
> ** ... and other verification/output patterns
> * Include SLF4J and LOG4J binding for logging, including a log4j.properties file in src/test/resources
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFCORE-99) standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-99?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-99:
-----------------------------------------------
Jay SenSharma <jsenshar(a)redhat.com> changed the Status of [bug 1145185|https://bugzilla.redhat.com/show_bug.cgi?id=1145185] from NEW to ASSIGNED
> standalone.bat script does not parse JAVA_OPTS containing '|' symbol properly
> -----------------------------------------------------------------------------
>
> Key: WFCORE-99
> URL: https://issues.jboss.org/browse/WFCORE-99
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 1.0.0.Alpha6
> Environment: Windows OS
> Reporter: Jay Kumar SenSharma
> Assignee: Tomaz Cerar
>
> *Scenario -1*
> - With the following line of JAVA_OPTS in "standalone.bat.conf" file
> {code}
> set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost|127.0.0.1|10.10.10.*"
> {code}
> Error while starting WildFly
> {code}
> C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin>standalone.bat
> Calling "C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin\standalone.conf.bat"
> Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> {code}
> *Scenario -2*
> - In Windows "^" sign is the escape character so we tried altering the JAVA_OPTS as following in the "standalone.bat.conf" file:
> {code}
> set "JAVA_OPTS=%JAVA_OPTS% -Dhttp.nonProxyHosts=localhost^|127.0.0.1^|10.10.10.*"
> {code}
> Now WildFly server starts but still we see the following messages in windows console:
> {code}
> C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin>standalone.bat
> Calling "C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin\standalone.conf.bat"
> Setting JAVA property to "C:\JDKs\jdk1.7.0_67\bin\java"
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\wildfly-9.0.0.Alpha1-SNAPSHOT"
> JAVA: "C:\JDKs\jdk1.7.0_67\bin\java"
> JAVA_OPTS: "-client -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=
> org.jboss.byteman -Dhttp.nonProxyHosts=localhost^|127.0.0.1^|10.10.10.*"
> ===============================================================================
> 15:50:35,453 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.4.Final
> 15:50:35,781 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
> 15:50:35,953 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly 1.0.0.Alpha5 "Kenny" starting
> {code}
> *NOTE*: It is also not possible to pass such JAVA_OPTS via command line, because it causes the same error:
> {code}
> C:\wildfly-9.0.0.Alpha1-SNAPSHOT\bin>standalone.bat -Dhttp.nonProxyHosts=localhost|127.0.0.1|10.10.10.*
> '127.0.0.1' is not recognized as an internal or external command,
> operable program or batch file.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-998) run-as does not work for Servlet.init()
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-998?page=com.atlassian.jira.plugin.s... ]
Stuart Douglas commented on WFLY-998:
-------------------------------------
Why has this been reopened?
> run-as does not work for Servlet.init()
> ---------------------------------------
>
> Key: WFLY-998
> URL: https://issues.jboss.org/browse/WFLY-998
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Derek Horton
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Alpha1
>
>
> According to the servlet 2.4 spec, the run-as should be used for Servlet.init()
> page 285:
> " Clarification: run-as identity must apply to all calls from a servlet including init() and destroy() (12.7)"
> This isn't working.
> In JBoss 5.x, it looks like this functionality was implemented by a RunAsListener. However, that listener does not appear to exist in the EAP 6 code base.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-998) run-as does not work for Servlet.init()
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-998?page=com.atlassian.jira.plugin.s... ]
Chao Wang reopened WFLY-998:
----------------------------
> run-as does not work for Servlet.init()
> ---------------------------------------
>
> Key: WFLY-998
> URL: https://issues.jboss.org/browse/WFLY-998
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Derek Horton
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Alpha1
>
>
> According to the servlet 2.4 spec, the run-as should be used for Servlet.init()
> page 285:
> " Clarification: run-as identity must apply to all calls from a servlet including init() and destroy() (12.7)"
> This isn't working.
> In JBoss 5.x, it looks like this functionality was implemented by a RunAsListener. However, that listener does not appear to exist in the EAP 6 code base.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month