[JBoss JIRA] (WFLY-4336) Cannot run testsuite if an application holds port 8080 open
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-4336?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4336:
-----------------------------------
Issue Type: Enhancement (was: Bug)
> Cannot run testsuite if an application holds port 8080 open
> -----------------------------------------------------------
>
> Key: WFLY-4336
> URL: https://issues.jboss.org/browse/WFLY-4336
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Affects Versions: 9.0.0.Alpha1
> Reporter: Michael Musgrove
> Assignee: Fedor Gavrilov
> Priority: Optional
> Fix For: Awaiting Volunteers
>
>
> We run jobs on a Jenkins cluster where the master is also a slave. The master runs the web front end gui on port 8080. The default wildfly web profile uses the same port. I tried starting undertow on a different port but the testsuite has some hardcoded references to port 8080, for example:
> testsuite/integration/src/test/xslt/changeIPAddresses.xsl
> testsuite/integration/xts/src/test/java/org/jboss/as/test/xts/wsat/client/ATClient.java
> testsuite/integration/xts/src/test/java/org/jboss/as/test/xts/wsba/coordinatorcompletion/client/BACoordinatorCompletionClient.java
> testsuite/integration/xts/src/test/java/org/jboss/as/test/xts/wsba/participantcompletion/client/BAParticipantCompletionClient.java
> The particular command I tried was:
> {code}
> ./tools/maven/bin/mvn -s tools/maven/conf/settings.xml test '-f' './testsuite/integration/xts/pom.xml' '-Pxts.integration.tests.profile' -Djboss.http.port=xxx
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (LOGMGR-229) Upgrade parent pom and use the parent pom's MR jar profiles
by James Perkins (Jira)
James Perkins created LOGMGR-229:
------------------------------------
Summary: Upgrade parent pom and use the parent pom's MR jar profiles
Key: LOGMGR-229
URL: https://issues.jboss.org/browse/LOGMGR-229
Project: JBoss Log Manager
Issue Type: Component Upgrade
Components: core
Reporter: James Perkins
Assignee: James Perkins
In the latest parent pom, 31, there are profiles activated for creating MR JAR's. Upgrading the parent allows us to remove the MR specific stuff in the current pom's plus includes some plugin upgrades.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (JGRP-2288) S3_PING: Under certain conditions, subclusters fail to merge after network partition
by Nick Sawadsky (Jira)
[ https://issues.jboss.org/browse/JGRP-2288?page=com.atlassian.jira.plugin.... ]
Nick Sawadsky commented on JGRP-2288:
-------------------------------------
[~belaban] I've submitted a pull request to address this issue: https://github.com/belaban/JGroups/pull/410
> S3_PING: Under certain conditions, subclusters fail to merge after network partition
> ------------------------------------------------------------------------------------
>
> Key: JGRP-2288
> URL: https://issues.jboss.org/browse/JGRP-2288
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.15
> Reporter: Nick Sawadsky
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.17
>
>
> Repro steps:
> 1. Set up a cluster of four nodes, two on one machine (Host 1) and two on another (Host 2). Let's call the nodes A, B, C, and D.
> 2. Configure all 4 nodes with S3_PING as the discovery mechanism. Set remove_all_files_on_view_change to true.
> 3. Start up nodes in the order A, B, C, D.
> 4. In the S3 bucket, there should be a single file with all four nodes listed. Node A should be flagged as the coordinator. Ensure that the UUID for node B is larger than the UUID for node C, when compared as two's complement integers. If this is not the case, shut down all nodes and restart in order. Repeat until the desired relationship is achieved. Note that with two's complement, a UUID having a first hex digit of 8 or higher is treated as negative for comparison purposes. So, for example, a UUID starting with 'a' is less than a UUID starting with 'b' which is less than a UUID starting with '1'.
> 5. On Host 1, use iptables to block all traffic going to and coming from Host 2.
> sudo iptables -A INPUT -s <Host 2 IP addr> -j DROP
> sudo iptables -A OUTPUT -d <Host 2 IP addr> -j DROP
> 6. Allow a few minutes for the nodes to detect the network partition. Eventually you should see two files in the S3 bucket.
> 7. Using Ctrl-C, stop node A.
> 8. You should soon find only a single file in the bucket, containing a single entry for node B. This is a result of the remove_all_files_on_view_change setting on S3_PING, which we set to true to avoid accumulation of old files in the bucket.
> 9. Resolve the network partition:
> sudo iptables -F OUTPUT
> sudo iptables -F INPUT
> 10. You will find that, even after many minutes, the subclusters are not merged.
> I believe the reason why the subclusters are never merged is as follows:
> - MERGE3 on nodes B, C and D uses S3_PING to find members to send INFO messages to. Each one finds only node B in the discovery file. As a result, only node B's view consistency checker has anything to work with.
> - On node B, the consistency checker can see that there are two coordinators, B and C. However, node C has a lower UUID, so node B defers to it to perform the merge. Node C never performs the merge because, as mentioned above, it is not receiving any INFO messages.
> I this this problem would affect FILE_PING as well, and other protocols derived from FILE_PING. Looking at the latest 4.x code, it appears the problem still exists there.
> I think the crux of the issue is that the coordinator on Host 2 (node C) does not re-create its discovery file after it is deleted by node B. Would it be reasonable for FILE_PING.findMembers() to create the discovery file if the node is a coordinator and the file doesn't exist?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt edited comment on DROOLS-3412 at 12/7/18 11:19 AM:
-----------------------------------------------------------------------
The reason for this issue seems to be that the InternalProcessRuntime inside StatefulKnowledgeSessionImpl doesn't get disposed with session pools. It only gets set to null. For the default case where DummyInternalProcessRuntime is used that works fine. However in our case (real application, not the example sandbox linked to this ticket) org.jbpm.process.instance.ProcessRuntimeImpl is used. I did a quick debugging of the benchmark you linked at that could also explain why this hasn't shown in the benchmark so far. I will try to come up with an idea how to change the benchmark next week.
was (Author: christianl):
The reason for this issue seems to be that the InternalProcessRuntime inside StatefulKnowledgeSessionImpl doesn't get disposed with session pools. It only gets set to null. For the default case where DummyInternalProcessRuntime is used that works fine. However in our case (real application, not the reproducer linked to this ticket) org.jbpm.process.instance.ProcessRuntimeImpl is used. I did a quick debugging of the benchmark you linked at that could also explain why this hasn't shown in the benchmark so far. I will try to come up with an idea how to change the benchmark next week.
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Christian Liebhardt (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Christian Liebhardt commented on DROOLS-3412:
---------------------------------------------
The reason for this issue seems to be that the InternalProcessRuntime inside StatefulKnowledgeSessionImpl doesn't get disposed with session pools. It only gets set to null. For the default case where DummyInternalProcessRuntime is used that works fine. However in our case (real application, not the reproducer linked to this ticket) org.jbpm.process.instance.ProcessRuntimeImpl is used. I did a quick debugging of the benchmark you linked at that could also explain why this hasn't shown in the benchmark so far. I will try to come up with an idea how to change the benchmark next week.
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3410) Found duplicate declaration for type exception after generating drl from scorecards xls
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3410?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3410:
---------------------------------------
[~drwho] attachments removed.
> Found duplicate declaration for type exception after generating drl from scorecards xls
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-3410
> URL: https://issues.jboss.org/browse/DROOLS-3410
> Project: Drools
> Issue Type: Bug
> Components: PMML, XLS Score Card Editor
> Affects Versions: 6.5.0.Final
> Reporter: Gordon Hu
> Assignee: Lance Leverich
> Priority: Major
>
> After generating a drl from the attached scorecard model, attempt to load the drl file with the following code:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()), ResourceType.DRL);
> //kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()));
> for (KnowledgeBuilderError error : kbuilder.getErrors()) {
> System.out.println(error.getMessage());
> }
> Assert.assertFalse(kbuilder.hasErrors());
> StatelessKieSession session = kbuilder.newKnowledgeBase().newStatelessKieSession();
> Drools compiler gave the following exception:
> Found duplicate declaration for type com.xxxx.xxxx.xxxx, unable to reconcile
> Unable to process type BaselineScore
> Unable to process type ScoreRow
> Unable to process type PhoneScoreScoreCardData
> Unable to process type ScoreRank
> Unable to process type PhoneScoreOutput
> Unable to process type DataField
> Unable to process type PhoneMatch
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3410) Found duplicate declaration for type exception after generating drl from scorecards xls
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3410?page=com.atlassian.jira.plugi... ]
Edson Tirelli closed DROOLS-3410.
---------------------------------
Resolution: Out of Date
> Found duplicate declaration for type exception after generating drl from scorecards xls
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-3410
> URL: https://issues.jboss.org/browse/DROOLS-3410
> Project: Drools
> Issue Type: Bug
> Components: PMML, XLS Score Card Editor
> Affects Versions: 6.5.0.Final
> Reporter: Gordon Hu
> Assignee: Lance Leverich
> Priority: Major
>
> After generating a drl from the attached scorecard model, attempt to load the drl file with the following code:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()), ResourceType.DRL);
> //kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()));
> for (KnowledgeBuilderError error : kbuilder.getErrors()) {
> System.out.println(error.getMessage());
> }
> Assert.assertFalse(kbuilder.hasErrors());
> StatelessKieSession session = kbuilder.newKnowledgeBase().newStatelessKieSession();
> Drools compiler gave the following exception:
> Found duplicate declaration for type com.xxxx.xxxx.xxxx, unable to reconcile
> Unable to process type BaselineScore
> Unable to process type ScoreRow
> Unable to process type PhoneScoreScoreCardData
> Unable to process type ScoreRank
> Unable to process type PhoneScoreOutput
> Unable to process type DataField
> Unable to process type PhoneMatch
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3410) Found duplicate declaration for type exception after generating drl from scorecards xls
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3410?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-3410:
----------------------------------
Attachment: (was: gem_phone_scoremodel.xls)
> Found duplicate declaration for type exception after generating drl from scorecards xls
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-3410
> URL: https://issues.jboss.org/browse/DROOLS-3410
> Project: Drools
> Issue Type: Bug
> Components: PMML, XLS Score Card Editor
> Affects Versions: 6.5.0.Final
> Reporter: Gordon Hu
> Assignee: Lance Leverich
> Priority: Major
>
> After generating a drl from the attached scorecard model, attempt to load the drl file with the following code:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()), ResourceType.DRL);
> //kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()));
> for (KnowledgeBuilderError error : kbuilder.getErrors()) {
> System.out.println(error.getMessage());
> }
> Assert.assertFalse(kbuilder.hasErrors());
> StatelessKieSession session = kbuilder.newKnowledgeBase().newStatelessKieSession();
> Drools compiler gave the following exception:
> Found duplicate declaration for type com.xxxx.xxxx.xxxx, unable to reconcile
> Unable to process type BaselineScore
> Unable to process type ScoreRow
> Unable to process type PhoneScoreScoreCardData
> Unable to process type ScoreRank
> Unable to process type PhoneScoreOutput
> Unable to process type DataField
> Unable to process type PhoneMatch
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3410) Found duplicate declaration for type exception after generating drl from scorecards xls
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3410?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-3410:
----------------------------------
Attachment: (was: gem_phone_scoremodel.xls)
> Found duplicate declaration for type exception after generating drl from scorecards xls
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-3410
> URL: https://issues.jboss.org/browse/DROOLS-3410
> Project: Drools
> Issue Type: Bug
> Components: PMML, XLS Score Card Editor
> Affects Versions: 6.5.0.Final
> Reporter: Gordon Hu
> Assignee: Lance Leverich
> Priority: Major
>
> After generating a drl from the attached scorecard model, attempt to load the drl file with the following code:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()), ResourceType.DRL);
> //kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()));
> for (KnowledgeBuilderError error : kbuilder.getErrors()) {
> System.out.println(error.getMessage());
> }
> Assert.assertFalse(kbuilder.hasErrors());
> StatelessKieSession session = kbuilder.newKnowledgeBase().newStatelessKieSession();
> Drools compiler gave the following exception:
> Found duplicate declaration for type com.xxxx.xxxx.xxxx, unable to reconcile
> Unable to process type BaselineScore
> Unable to process type ScoreRow
> Unable to process type PhoneScoreScoreCardData
> Unable to process type ScoreRank
> Unable to process type PhoneScoreOutput
> Unable to process type DataField
> Unable to process type PhoneMatch
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3410) Found duplicate declaration for type exception after generating drl from scorecards xls
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3410?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-3410:
----------------------------------
Attachment: (was: phone_scorecard.drl)
> Found duplicate declaration for type exception after generating drl from scorecards xls
> ---------------------------------------------------------------------------------------
>
> Key: DROOLS-3410
> URL: https://issues.jboss.org/browse/DROOLS-3410
> Project: Drools
> Issue Type: Bug
> Components: PMML, XLS Score Card Editor
> Affects Versions: 6.5.0.Final
> Reporter: Gordon Hu
> Assignee: Lance Leverich
> Priority: Major
>
> After generating a drl from the attached scorecard model, attempt to load the drl file with the following code:
> KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
> kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()), ResourceType.DRL);
> //kbuilder.add(ResourceFactory.newByteArrayResource(drl2.getBytes()));
> for (KnowledgeBuilderError error : kbuilder.getErrors()) {
> System.out.println(error.getMessage());
> }
> Assert.assertFalse(kbuilder.hasErrors());
> StatelessKieSession session = kbuilder.newKnowledgeBase().newStatelessKieSession();
> Drools compiler gave the following exception:
> Found duplicate declaration for type com.xxxx.xxxx.xxxx, unable to reconcile
> Unable to process type BaselineScore
> Unable to process type ScoreRow
> Unable to process type PhoneScoreScoreCardData
> Unable to process type ScoreRank
> Unable to process type PhoneScoreOutput
> Unable to process type DataField
> Unable to process type PhoneMatch
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months