[JBoss JIRA] (WFLY-2628) Update to web console 2.1.0.Final
by Harald Pehl (JIRA)
[ https://issues.jboss.org/browse/WFLY-2628?page=com.atlassian.jira.plugin.... ]
Harald Pehl updated WFLY-2628:
------------------------------
Description:
Contains the following fixes:
- HAL-72
- HAL-280
- HAL-289
- HAL-295
- HAL-296
- HAL-308
- HAL-321
- WFLY-1921
- BZ-1030266
- BZ-1032234
was:
Contains the following fixes:
- HAL-295
- HAL-308
- HAL-296
- HAL-280
- HAL-321
- HAL-289
- WFLY-1921
- BZ-1030266
- BZ-1032234
> Update to web console 2.1.0.Final
> ---------------------------------
>
> Key: WFLY-2628
> URL: https://issues.jboss.org/browse/WFLY-2628
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web Console
> Reporter: Harald Pehl
> Assignee: Harald Pehl
> Priority: Blocker
> Fix For: 8.0.0.Final
>
>
> Contains the following fixes:
> - HAL-72
> - HAL-280
> - HAL-289
> - HAL-295
> - HAL-296
> - HAL-308
> - HAL-321
> - WFLY-1921
> - BZ-1030266
> - BZ-1032234
--
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
10 years, 11 months
[JBoss JIRA] (WFLY-2628) Update to web console 2.1.0.Final
by Harald Pehl (JIRA)
[ https://issues.jboss.org/browse/WFLY-2628?page=com.atlassian.jira.plugin.... ]
Harald Pehl updated WFLY-2628:
------------------------------
Description:
Contains the following fixes:
- HAL-295
- HAL-308
- HAL-296
- HAL-280
- HAL-321
- HAL-289
- WFLY-1921
- BZ-1030266
- BZ-1032234
was:
Contains the following fixes:
- HAL-295
- HAL-308
- HAL-296
- HAL-280
- HAL-321
- WFLY-1921
- BZ-1030266
- BZ-1032234
> Update to web console 2.1.0.Final
> ---------------------------------
>
> Key: WFLY-2628
> URL: https://issues.jboss.org/browse/WFLY-2628
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web Console
> Reporter: Harald Pehl
> Assignee: Harald Pehl
> Priority: Blocker
> Fix For: 8.0.0.Final
>
>
> Contains the following fixes:
> - HAL-295
> - HAL-308
> - HAL-296
> - HAL-280
> - HAL-321
> - HAL-289
> - WFLY-1921
> - BZ-1030266
> - BZ-1032234
--
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
10 years, 11 months
[JBoss JIRA] (WFLY-2649) Upgrade to HornetQ 2.4.0.Final
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-2649:
---------------------------------
Summary: Upgrade to HornetQ 2.4.0.Final
Key: WFLY-2649
URL: https://issues.jboss.org/browse/WFLY-2649
Project: WildFly
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: JMS
Affects Versions: 8.0.0.Beta1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.CR1
also upgrade Netty to 4.0.13.Final
--
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
10 years, 11 months
[JBoss JIRA] (JGRP-1740) Byteman tests fail on Windows
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1740?page=com.atlassian.jira.plugin.... ]
Bela Ban reopened JGRP-1740:
----------------------------
Doesn't work for me. Also need to test on Windows box
> Byteman tests fail on Windows
> -----------------------------
>
> Key: JGRP-1740
> URL: https://issues.jboss.org/browse/JGRP-1740
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The Byteman tests in the Jgroups testsuite fail when running the testsuite on Windows. The error text is as follows:
> {noformat}
> byteman:
> [testng] -- onStart -- byteman
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.BecomeServerTest#testSendingOfMsgsOnUnconnectedChannel
> [testng] FAIL: [1] org.jgroups.tests.byteman.BecomeServerTest.bmngBeforeTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.BecomeServerTest#testSendingOfMsgsOnUnconnectedChannel
> [testng] FAIL: [1] org.jgroups.tests.byteman.BecomeServerTest.bmngAfterTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.ForwardToCoordFailoverTest.testSendingDuringViewChange()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.ForwardToCoordFailoverTest#testSendingDuringViewChange
> [testng] FAIL: [1] org.jgroups.tests.byteman.ForwardToCoordFailoverTest.bmngAfterTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.MessageBeforeConnectedTest.testSendingOfMsgsOnUnconnectedChannel()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.MessageBeforeConnectedTest#testSendingOfMsgsOnUnconnectedChannel
> [testng] FAIL: [1] org.jgroups.tests.byteman.MessageBeforeConnectedTest.bmngAfterTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testBroadcastSequenceSenderIsB()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testBroadcastSequenceSenderIsC()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testFailoverWithMultipleThreadsSendingMessages()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testResendingVersusNewMessages()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.SequencerFailoverTest#testResendingVersusNewMessages
> [testng] FAIL: [1] org.jgroups.tests.byteman.SequencerFailoverTest.bmngAfterTest-Method()
> [testng] The tests failed.
> {noformat}
--
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
10 years, 11 months
[JBoss JIRA] (JGRP-1740) Byteman tests fail on Windows
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1740?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1740:
--------------------------------
I'm having a lot of problems when {{scripts/}} was removed; I'm reverting this change. Looking into the byteman source code, {{dir="scripts/Dir", value="File"}} should result in a file name {{scripts\\Dir\\File}}.
I have to verify this on a Windows box though... If push comes to shove, I'll modify the byteman src code and submit a pull request to that project.
> Byteman tests fail on Windows
> -----------------------------
>
> Key: JGRP-1740
> URL: https://issues.jboss.org/browse/JGRP-1740
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The Byteman tests in the Jgroups testsuite fail when running the testsuite on Windows. The error text is as follows:
> {noformat}
> byteman:
> [testng] -- onStart -- byteman
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.BecomeServerTest#testSendingOfMsgsOnUnconnectedChannel
> [testng] FAIL: [1] org.jgroups.tests.byteman.BecomeServerTest.bmngBeforeTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.BecomeServerTest#testSendingOfMsgsOnUnconnectedChannel
> [testng] FAIL: [1] org.jgroups.tests.byteman.BecomeServerTest.bmngAfterTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.ForwardToCoordFailoverTest.testSendingDuringViewChange()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.ForwardToCoordFailoverTest#testSendingDuringViewChange
> [testng] FAIL: [1] org.jgroups.tests.byteman.ForwardToCoordFailoverTest.bmngAfterTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.MessageBeforeConnectedTest.testSendingOfMsgsOnUnconnectedChannel()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.MessageBeforeConnectedTest#testSendingOfMsgsOnUnconnectedChannel
> [testng] FAIL: [1] org.jgroups.tests.byteman.MessageBeforeConnectedTest.bmngAfterTest-Method()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testBroadcastSequenceSenderIsB()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testBroadcastSequenceSenderIsC()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testFailoverWithMultipleThreadsSendingMessages()
> [testng] SKIP: [1] org.jgroups.tests.byteman.SequencerFailoverTest.testResendingVersusNewMessages()
> [testng] failed config: java.io.FileNotFoundException: Rule file not found for Byteman test case org.jgroups.tests.byteman.SequencerFailoverTest#testResendingVersusNewMessages
> [testng] FAIL: [1] org.jgroups.tests.byteman.SequencerFailoverTest.bmngAfterTest-Method()
> [testng] The tests failed.
> {noformat}
--
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
10 years, 11 months
[JBoss JIRA] (DROOLS-296) Drools date coercion and conditional OR
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-296?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-296:
------------------------------------------------
Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1029908|https://bugzilla.redhat.com/show_bug.cgi?id=1029908] from ON_QA to VERIFIED
> Drools date coercion and conditional OR
> ---------------------------------------
>
> Key: DROOLS-296
> URL: https://issues.jboss.org/browse/DROOLS-296
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final
> Environment: Windows 7
> Reporter: Madhura Jayaratne
> Assignee: Mario Fusco
> Fix For: 6.0.1.Final
>
>
> If I try a simple Drools rule with conditions on date type and uses conditional OR (||) I get the following error. If I change || to && it works fine.
> Condition
> $container: DateContainer( date >= "15-Oct-2013" || date <= "01-Oct-2013" )
> Error
> Unable to Analyse Expression date >= "15-Oct-2013" || date <= "01-Oct-2013":
> [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String]
> [Near : {... date >= "15-Oct-2013" || date <= "01-Oct-2013" ....}]
> ^
> [Line: 9, Column: 1] : [Rule name='Test rule']
--
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
10 years, 11 months
[JBoss JIRA] (DROOLS-280) lock-on-active broken
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-280?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-280:
------------------------------------------------
Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1025824|https://bugzilla.redhat.com/show_bug.cgi?id=1025824] from ON_QA to VERIFIED
> lock-on-active broken
> ---------------------
>
> Key: DROOLS-280
> URL: https://issues.jboss.org/browse/DROOLS-280
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.CR4
> Reporter: Anthony Patricio
> Assignee: Mario Fusco
> Fix For: 6.0.0.Final
>
>
> Hi,
> lock-on-active is not working as expected.
> I seems to work as activation-group.
> Works fine with 5.x
> Fails with 6.0.0 CR3 and CR4
> Fact:
> {code:java}
> public class Poc implements Serializable {
> private static final long serialVersionUID = 1L;
> private long id = 1;
> private boolean test1 = false;
> private boolean test2 = false;
> private int foundTest = 0;
> ...
> }
> {code}
> Rule:
> {code:java}
> rule "test1"
> lock-on-active
> dialect "mvel"
> when
> $poc:Poc( isTest1() )
> then
> System.out.println("test1 found");
> modify($poc) { setFoundTest($poc.getFoundTest() + 1) }
> end
> rule "test2"
> lock-on-active
> dialect "mvel"
> when
> $poc:Poc( isTest2() )
> then
> System.out.println("test2 found");
> modify($poc) { setFoundTest($poc.getFoundTest() + 1) }
> end
> {code}
> Test:
> {code:java}
> @Test
> public void lockOnActiveTest() {
> // Get the Knowledge base from the DRL file
> KieSession kSession = getSF();
>
> Poc poc = new Poc();
> poc.setTest1(true);
> poc.setTest2(true);
>
> kSession.insert(poc);
>
> // Fire the rules
> kSession.fireAllRules();
>
> assertTrue("broken",poc.getFoundTest()==2);
>
> // Clean up
> kSession.dispose();
> }
> {code}
--
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
10 years, 11 months
[JBoss JIRA] (WFLY-2643) JBOSS_LOG_DIR is checked but not used to set jboss.server.log.dir
by Stian Lund (JIRA)
[ https://issues.jboss.org/browse/WFLY-2643?page=com.atlassian.jira.plugin.... ]
Stian Lund commented on WFLY-2643:
----------------------------------
Thanks - maybe I should change to an enhancement request? As it's not a bug.
I don't have much experience with Git (if that's what you mean by PR) i'm afraid but maybe it's time to learn ;)
> JBOSS_LOG_DIR is checked but not used to set jboss.server.log.dir
> -----------------------------------------------------------------
>
> Key: WFLY-2643
> URL: https://issues.jboss.org/browse/WFLY-2643
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Logging, Server
> Affects Versions: JBoss AS7 7.1.1.Final, 8.0.0.Beta1
> Environment: All
> Reporter: Stian Lund
> Priority: Optional
> Labels: jbossas, logging, wildfly
>
> In standalone/domain start scripts (standalone.sh/bat) the value of environment variable JBOSS_LOG_DIR is checked for:
> {code}
> # determine the default log dir, if not set
> if [ "x$JBOSS_LOG_DIR" = "x" ]; then
> JBOSS_LOG_DIR="$JBOSS_BASE_DIR/log"
> fi
> {code}
> However, this is not actually used to set the value of Java property jboss.server.log.dir.
> {code}
> -Djboss.home.dir="$JBOSS_HOME"
> -Djboss.server.base.dir="$JBOSS_BASE_DIR"
> "$SERVER_OPTS"
> {code}
> (It should be set at the same place)
> This leads Jboss/Wildfly/EAP to assume the default value of $JBOSS_BASE_DIR/log.
> This is a problem for those who want to override the location of the server.log files.
--
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
10 years, 11 months