[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:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> made a comment on [bug 1025824|https://bugzilla.redhat.com/show_bug.cgi?id=1025824]
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:
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;
...
}
Rule:
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
Test:
@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();
}
> 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
>
> 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
11 years, 1 month
[JBoss JIRA] (DROOLS-280) lock-on-active broken
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-280?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-280.
--------------------------------
Fix Version/s: 6.0.0.Final
Resolution: Done
> 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
11 years, 1 month
[JBoss JIRA] (DROOLS-280) lock-on-active broken
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-280?page=com.atlassian.jira.plugin... ]
Mario Fusco reassigned DROOLS-280:
----------------------------------
Assignee: Mario Fusco
> 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
>
> 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
11 years, 1 month
[JBoss JIRA] (JGRP-1727) McastReceiverTest output does not display correctly on Windows
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1727?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz resolved JGRP-1727.
---------------------------------------
Resolution: Done
> McastReceiverTest output does not display correctly on Windows
> --------------------------------------------------------------
>
> Key: JGRP-1727
> URL: https://issues.jboss.org/browse/JGRP-1727
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows XP, Windows 7
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Minor
> Fix For: 3.5
>
>
> When using McastSenderTest and McastReceiverTest on Windows to check multicast connectivity, the output displayed by McastReceiverTest not presented in the same was as when running the utilities on Linux; part of the output is either completely lost (Windows 7) or the output has extra blank characters inserted (Windows XP).
>
--
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, 1 month
[JBoss JIRA] (JGRP-1727) McastReceiverTest output does not display correctly on Windows
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1727?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz reassigned JGRP-1727:
-----------------------------------------
Assignee: Richard Achmatowicz (was: Bela Ban)
> McastReceiverTest output does not display correctly on Windows
> --------------------------------------------------------------
>
> Key: JGRP-1727
> URL: https://issues.jboss.org/browse/JGRP-1727
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows XP, Windows 7
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Minor
> Fix For: 3.5
>
>
> When using McastSenderTest and McastReceiverTest on Windows to check multicast connectivity, the output displayed by McastReceiverTest not presented in the same was as when running the utilities on Linux; part of the output is either completely lost (Windows 7) or the output has extra blank characters inserted (Windows XP).
>
--
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, 1 month
[JBoss JIRA] (JGRP-1727) McastReceiverTest output does not display correctly on Windows
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1727?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on JGRP-1727:
-------------------------------------------
The problem is is the following: when a DatagramPacket is received by McastReceiverTest, a String used for display of the payload is created as follows:
{noformat}
new String(packet.getData())
{noformat}
where the size of the array returned by DatagramPacket.getData() is fixed at 256. Any data in the buffer is followed by zeros.
On Linux, this seems to work fine to create the right String; on Windows, the String created contains the trailing zeros and the display gets messed up.
This can be fixed as follows:
{noformat}
new String(packet.getData(), 0, packet.getLength())
{noformat}
> McastReceiverTest output does not display correctly on Windows
> --------------------------------------------------------------
>
> Key: JGRP-1727
> URL: https://issues.jboss.org/browse/JGRP-1727
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows XP, Windows 7
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> When using McastSenderTest and McastReceiverTest on Windows to check multicast connectivity, the output displayed by McastReceiverTest not presented in the same was as when running the utilities on Linux; part of the output is either completely lost (Windows 7) or the output has extra blank characters inserted (Windows XP).
>
--
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, 1 month
[JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.... ]
David Lloyd reassigned WFLY-2422:
---------------------------------
Assignee: Cheng Fang (was: David Lloyd)
Cheng, I was wondering if you might be interested in looking at this one.
> Simplify the remote-outbound connections
> ----------------------------------------
>
> Key: WFLY-2422
> URL: https://issues.jboss.org/browse/WFLY-2422
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: EJB, Remoting
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: Cheng Fang
>
> At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml.
> But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster.
> It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration.
> In this case it is possible to keep the application deployment independent from the server environment.
--
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, 1 month
[JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-2422:
-----------------------------------
*Requirements* (edit as needed)
Essentially this implies that the EJB subsystem will have to become aware of the deployment EJB client context. We should have a sort of "client context profile" notion in the EJB subsystem configuration. Then jboss-ejb-client.xml can simply select a profile (and possibly supplement it with more direct connection information).
The EJB client context profile should contain a listing of discovery methods, though to start we'd only support one: static connection listing.
Deployments with a given selected profile will have those EJB receivers registered with the deployment EJB client context.
> Simplify the remote-outbound connections
> ----------------------------------------
>
> Key: WFLY-2422
> URL: https://issues.jboss.org/browse/WFLY-2422
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: EJB, Remoting
> Affects Versions: 8.0.0.Beta1
> Reporter: Wolf-Dieter Fink
> Assignee: David Lloyd
>
> At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml.
> But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster.
> It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration.
> In this case it is possible to keep the application deployment independent from the server environment.
--
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, 1 month
[JBoss JIRA] (JGRP-1727) McastReceiverTest output does not display correctly on Windows
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created JGRP-1727:
-----------------------------------------
Summary: McastReceiverTest output does not display correctly on Windows
Key: JGRP-1727
URL: https://issues.jboss.org/browse/JGRP-1727
Project: JGroups
Issue Type: Bug
Affects Versions: 3.5
Environment: Windows XP, Windows 7
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Priority: Minor
Fix For: 3.5
When using McastSenderTest and McastReceiverTest on Windows to check multicast connectivity, the output displayed by McastReceiverTest not presented in the same was as when running the utilities on Linux; part of the output is either completely lost (Windows 7) or the output has extra blank characters inserted (Windows XP).
--
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, 1 month