[JBoss JIRA] (JGRP-1795) OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1795?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-1795 at 2/23/14 12:22 PM:
---------------------------------------------------------------------
This test fails randomly but regularly on multiple platforms.
was (Author: rachmato):
This test fails randomly but regularly on multiple platforms.
The error message is a little wierd: messages 0-20 are 21 messages, not 20!
> OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
> -----------------------------------------------------------------------
>
> Key: JGRP-1795
> URL: https://issues.jboss.org/browse/JGRP-1795
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL(3/24), WIN (1/6), Solaris (6/24) where (x/y) means x failures over y test executions.
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following with two channels a and b:
> - adds a DISCARD layer to a to disccard 50% of down messages
> - sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
> - wait 10 seconds for 20 messages to be received by each of a and b
> - print out the messages received
> - remove the DISCARD layer from a
> - wait 2.5 seconds for further messages to arrive
> - assert that 20 messages have arrived for each channel a and b
> The test fails on the assertion, with results such as:
> {noformat}
> expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
> {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
12 years, 4 months
[JBoss JIRA] (JGRP-1795) OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1795?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-1795 at 2/23/14 12:11 PM:
---------------------------------------------------------------------
This test fails randomly but regularly on multiple platforms.
The error message is a little wierd: messages 0-20 are 21 messages, not 20!
was (Author: rachmato):
This test fails randomly but regularly on multiple platforms.
> OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
> -----------------------------------------------------------------------
>
> Key: JGRP-1795
> URL: https://issues.jboss.org/browse/JGRP-1795
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL(3/24), WIN (1/6), Solaris (6/24) where (x/y) means x failures over y test executions.
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following with two channels a and b:
> - adds a DISCARD layer to a to disccard 50% of down messages
> - sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
> - wait 10 seconds for 20 messages to be received by each of a and b
> - print out the messages received
> - remove the DISCARD layer from a
> - wait 2.5 seconds for further messages to arrive
> - assert that 20 messages have arrived for each channel a and b
> The test fails on the assertion, with results such as:
> {noformat}
> expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
> {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
12 years, 4 months
[JBoss JIRA] (JGRP-1795) OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1795?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated JGRP-1795:
--------------------------------------
Description:
This test does the following with two channels a and b:
- adds a DISCARD layer to a to disccard 50% of down messages
- sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
- wait 10 seconds for 20 messages to be received by each of a and b
- print out the messages received
- remove the DISCARD layer from a
- wait 2.5 seconds for further messages to arrive
- assert that 20 messages have arrived for each channel a and b
The test fails on the assertion, with results such as:
{noformat}
expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
{noformat}
was:
This test does the following with two channels a and b:
- adds a DISCARD layer to a to disccard 50% of down messages
- sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
- wait 10 seconds for 20 messages to be received by each of a and b
- print out the messages received
- remove the DISCARD layer from a
- wait 2.5 seconds for further messages to arrive
- assert that 20 messages have arrived for each channel a and b
The test fails on the assertion, with results such as:
{noformat}
expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
{noformat}
> OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
> -----------------------------------------------------------------------
>
> Key: JGRP-1795
> URL: https://issues.jboss.org/browse/JGRP-1795
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL(3/24), WIN (1/6), Solaris (6/24) where (x/y) means x failures over y test executions.
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following with two channels a and b:
> - adds a DISCARD layer to a to disccard 50% of down messages
> - sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
> - wait 10 seconds for 20 messages to be received by each of a and b
> - print out the messages received
> - remove the DISCARD layer from a
> - wait 2.5 seconds for further messages to arrive
> - assert that 20 messages have arrived for each channel a and b
> The test fails on the assertion, with results such as:
> {noformat}
> expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
> {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
12 years, 4 months
[JBoss JIRA] (JGRP-1795) OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1795?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on JGRP-1795:
-------------------------------------------
This test fails randomly but regularly on multiple platforms.
> OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
> -----------------------------------------------------------------------
>
> Key: JGRP-1795
> URL: https://issues.jboss.org/browse/JGRP-1795
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL(3/24), WIN (1/6), Solaris (6/24) where (x/y) means x failures over y test executions.
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following with two channels a and b:
> - adds a DISCARD layer to a to disccard 50% of down messages
> - sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
> - wait 10 seconds for 20 messages to be received by each of a and b
> - print out the messages received
> - remove the DISCARD layer from a
> - wait 2.5 seconds for further messages to arrive
> - assert that 20 messages have arrived for each channel a and b
> The test fails on the assertion, with results such as:
> {noformat}
> expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
> {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
12 years, 4 months
[JBoss JIRA] (JGRP-1795) OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1795?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated JGRP-1795:
--------------------------------------
Description:
This test does the following with two channels a and b:
- adds a DISCARD layer to a to disccard 50% of down messages
- sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
- wait 10 seconds for 20 messages to be received by each of a and b
- print out the messages received
- remove the DISCARD layer from a
- wait 2.5 seconds for further messages to arrive
- assert that 20 messages have arrived for each channel a and b
The test fails on the assertion, with results such as:
{noformat}
expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
{noformat}
was:
This test does the following with two channels a and b:
- adds a DISCARD layer to a to disccard 50% of down messages
- sends 20 messages to the group, randomly using a and b as senders
- wait 10 seconds for 20 messages to be received by each of a and b
- print out the messages received
- remove the DISCARD layer from a
- wait 2.5 seconds for further messages to arrive
- assert that 20 messages have arrived for each channel a and b
The test fails on the assertion, with results such as:
{noformat}
expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
{noformat}
> OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
> -----------------------------------------------------------------------
>
> Key: JGRP-1795
> URL: https://issues.jboss.org/browse/JGRP-1795
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL(3/24), WIN (1/6), Solaris (6/24) where (x/y) means x failures over y test executions.
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following with two channels a and b:
> - adds a DISCARD layer to a to disccard 50% of down messages
> - sends 20 messages to the group, randomly using a and b as senders, and randomly choosing OOB or non-OOB
> - wait 10 seconds for 20 messages to be received by each of a and b
> - print out the messages received
> - remove the DISCARD layer from a
> - wait 2.5 seconds for further messages to arrive
> - assert that 20 messages have arrived for each channel a and b
> The test fails on the assertion, with results such as:
> {noformat}
> expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
> {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
12 years, 4 months
[JBoss JIRA] (JGRP-1795) OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created JGRP-1795:
-----------------------------------------
Summary: OOBTest testRandomRegularAndOOBMulticasts fails to receive all messages
Key: JGRP-1795
URL: https://issues.jboss.org/browse/JGRP-1795
Project: JGroups
Issue Type: Bug
Affects Versions: 3.2.13
Environment: RHEL(3/24), WIN (1/6), Solaris (6/24) where (x/y) means x failures over y test executions.
Reporter: Richard Achmatowicz
Assignee: Bela Ban
Fix For: 3.2.13
This test does the following with two channels a and b:
- adds a DISCARD layer to a to disccard 50% of down messages
- sends 20 messages to the group, randomly using a and b as senders
- wait 10 seconds for 20 messages to be received by each of a and b
- print out the messages received
- remove the DISCARD layer from a
- wait 2.5 seconds for further messages to arrive
- assert that 20 messages have arrived for each channel a and b
The test fails on the assertion, with results such as:
{noformat}
expected 20 elements, but got 19 (list=[1, 4, 3, 8, 6, 7, 10, 13, 15, 20, 2, 5, 9, 12, 14, 16, 17, 18, 19]), missing=[0, 11]
{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
12 years, 4 months
[JBoss JIRA] (JGRP-1791) PropertyConvertersTest.testNetworkList fails when trying to access interface lo
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1791?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on JGRP-1791:
-------------------------------------------
Confirm that these test failures no longer appear in test executions of 3.2.13.Final.
> PropertyConvertersTest.testNetworkList fails when trying to access interface lo
> -------------------------------------------------------------------------------
>
> Key: JGRP-1791
> URL: https://issues.jboss.org/browse/JGRP-1791
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: HPUX, Solaris
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.2.13, 3.5
>
>
> The interface lo does not exist on certain OSs, so the test fails with this exception on HPUX:
> {noformat}
> Error Message
> lo
> Stacktrace
> java.net.UnknownHostException
> at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
> at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:883)
> at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1236)
> at java.net.InetAddress.getAllByName0(InetAddress.java:1187)
> at java.net.InetAddress.getAllByName(InetAddress.java:1117)
> at java.net.InetAddress.getAllByName(InetAddress.java:1053)
> at java.net.InetAddress.getByName(InetAddress.java:1003)
> at org.jgroups.util.Util.parseInterfaceList(Util.java:3225)
> at org.jgroups.conf.PropertyConverters$NetworkInterfaceList.convert(PropertyConverters.java:34)
> at org.jgroups.tests.PropertyConvertersTest.testNetworkList(PropertyConvertersTest.java:41)
> {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
12 years, 4 months
[JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL
by Emeric Vernat (JIRA)
[ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.... ]
Emeric Vernat commented on WFLY-2898:
-------------------------------------
The jdbc datasource is now supported for WildFly like JBoss, since:
https://code.google.com/p/javamelody/source/detail?r=3686
You can download a snapshot build at:
https://javamelody.ci.cloudbees.com/job/javamelody/net.bull.javamelody$ja...
Note that you may check your config, because the debugging logs given are not coherent with your command line "-Djavamelody.datasources=java:jboss/datasources/ExampleDS" (or is it GOLDDatasource?).
> JNDI Name lookup of the DataSource returns NULL
> -----------------------------------------------
>
> Key: WFLY-2898
> URL: https://issues.jboss.org/browse/WFLY-2898
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Naming, Web (Undertow)
> Affects Versions: 8.0.0.CR1, 8.0.0.Final
> Reporter: Igor Shulika
> Assignee: Eduardo Martins
> Attachments: 1.PNG, 2.PNG, 3.PNG, jaffa-oracle-driver-6.0.0.Alpha2-SNAPSHOT.jar, server.log, standalone.conf.bat, standalone.xml, test.zip, test.zip
>
>
> Hi,
> I'm having a problem to obtain DataSource using JNDI Name lookup.
> Please see my code below:
> Connection connection = null;
> DataSource dataSource = null;
> try {
> final Context initContext = new InitialContext();
> dataSource = (DataSource) initContext.lookup("java:/MyDataSource"); connection = dataSource.getConnection();
> } catch (Exception e) {
> LOGGER.error(e);
> }
> I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14).
> Also I can find and test connection of my “java:/MyDataSource” under the “Datasources” section of the WildFly Administration Console just fine(anoter word the datasource is there).
--
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
12 years, 4 months
[JBoss JIRA] (DROOLS-439) Package builder unable to find declared array class
by Mark Sullivan (JIRA)
Mark Sullivan created DROOLS-439:
------------------------------------
Summary: Package builder unable to find declared array class
Key: DROOLS-439
URL: https://issues.jboss.org/browse/DROOLS-439
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.1.Final
Reporter: Mark Sullivan
Assignee: Mark Proctor
When declaring a fact type with an array field, where the array type is declared in the same package, for example:
{code}
declare Owner
name : String
end
declare Pet
owners : Owner[]
end
{code}
The following build error occurs:
{code}
[Message [id=1, level=ERROR, path=pets.drl, line=5, column=0
text=Unable to find class 'Owner']]
{code}
This error doesn't always occur when an array field is declared. It's dependent on the order in which each fact type is processed.
PackageBuilder attempts to order fact types for processing based on the declared super type and attribute types.
The following loop in *PackageBuilder.sortByHierarchy()* processes each field looking for field type dependencies:
{code}
for (TypeFieldDescr field : tdescr.getFields().values()) {
QualifiedName typeName = new QualifiedName(field.getPattern().getObjectType());
if (!hasCircularDependency(name, typeName, taxonomy)) {
supers.add(typeName);
}
}
{code}
However I don't think it correctly spots the dependency when the field type is an array.
This issue can be worked around by declaring an unused field of the same type as the array:
{code}
declare Owner
name : String
end
declare Pet
owners : Owner[]
_unused: Owner
end
{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
12 years, 4 months