[JBoss JIRA] (WFLY-2401) org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-2401?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka edited comment on WFLY-2401 at 11/9/13 9:21 PM:
-------------------------------------------------------------
Confirmed on Linux on current master - fc5e1dc // Fri Nov 8 09:51:14 2013
Failed tests: testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation
testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase)
testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase): expected:<1> but was:<2>
testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase): expected:<1> but was:<2>
Java version: 1.7.0_25, vendor: Oracle Corporation
was (Author: ozizka):
Confirmed on Linux on current master - fc5e1dc // Fri Nov 8 09:51:14 2013
Failed tests: testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation
testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase)
testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase): expected:<1> but was:<2>
testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase): expected:<1> but was:<2>
> org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails
> --------------------------------------------------------------
>
> Key: WFLY-2401
> URL: https://issues.jboss.org/browse/WFLY-2401
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.0.0.Beta1
> Environment: Solaris SPARC 10, Oracle Java 1.7.0_45
> Reporter: Frank Langelage
> Assignee: Emanuel Muckenhuber
> Attachments: org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase.txt
>
>
> Running a build of current sources with complete testsuite this test is failing with
> testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase)
--
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, 2 months
[JBoss JIRA] (WFLY-2401) org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/WFLY-2401?page=com.atlassian.jira.plugin.... ]
Ondrej Zizka commented on WFLY-2401:
------------------------------------
Confirmed on Linux on current master - Failed tests: testValidateModel(org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase): The model failed validation
testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase)
testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase): expected:<1> but was:<2>
testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase): expected:<1> but was:<2>
> org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails
> --------------------------------------------------------------
>
> Key: WFLY-2401
> URL: https://issues.jboss.org/browse/WFLY-2401
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.0.0.Beta1
> Environment: Solaris SPARC 10, Oracle Java 1.7.0_45
> Reporter: Frank Langelage
> Assignee: Emanuel Muckenhuber
> Attachments: org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase.txt
>
>
> Running a build of current sources with complete testsuite this test is failing with
> testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase)
--
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, 2 months
[JBoss JIRA] (DROOLS-330) Rule Inheritance using Extends keyword fails when the Sub Rule Appears before the Super Rule
by Davide Sottara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-330?page=com.atlassian.jira.plugin... ]
Davide Sottara commented on DROOLS-330:
---------------------------------------
This bug and similar (DROOLS-100) have been fixed in 5.6.0.CR1 and above, can you please test that?
Thanks
Davide
> Rule Inheritance using Extends keyword fails when the Sub Rule Appears before the Super Rule
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-330
> URL: https://issues.jboss.org/browse/DROOLS-330
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final
> Environment: Ubuntu 12.04 LTS in VM
> Reporter: Mike Fauzy
> Assignee: Mark Proctor
> Priority: Minor
>
> In Drools 5.5.0.Final the extends keyword allows one rule (SubRule) to extend another rule (SuperRule). SubRule should only fire if all of the conditions for SubRule and SuperRule are met.
> If SubRule is listed after SuperRule after in the .drl file, then it works correctly. However, if SubRule is listed before SuperRule in the .drl file, then only the SubRule's conditions need to be met for the rule to fire.
> A temporary workaround is to list all SubRules after the SuperRules.
> This might be related to: https://issues.jboss.org/browse/DROOLS-100
> To reproduce:
> I have a junit test packaged for Maven and Eclipse, but I don't see any place to add the file.
> Create 2 .drl files where rule "sub" extends rule "super". Setup a boolean that is true for the sub, but false for the super.
> In the first file, place the sub before the super. In the second file, reverse the two.
> Observe that the sub fires when it is in the file before the super, but not after. It should not fire either time.
--
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, 2 months
[JBoss JIRA] (JBREM-1322) Cannot set up serverBindAddress for secondarySocket in bisocket transport
by Ron Sigal (JIRA)
[ https://issues.jboss.org/browse/JBREM-1322?page=com.atlassian.jira.plugin... ]
Ron Sigal updated JBREM-1322:
-----------------------------
Fix Version/s: (was: 2.5.4.SP5)
> Cannot set up serverBindAddress for secondarySocket in bisocket transport
> -------------------------------------------------------------------------
>
> Key: JBREM-1322
> URL: https://issues.jboss.org/browse/JBREM-1322
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: transport
> Affects Versions: 2.5.4.SP4
> Reporter: Igor Kostromin
> Assignee: Ron Sigal
>
> Using IS_CALLBACK_SERVER = true.
> In BisocketClientInvoker.java:355
> InvokerLocator getSecondaryLocator() throws Throwable {
> ...
> 355: Object o = invoke(r);
> ...
> }
> It retrieves host from server, but if you want to use original client invoker host, you cannot do this (it is necessary if server is behind translating firewall). If you want to do this, you have to patch this code manually to
> Object o = invoke(r);
> // DZ: patch to use original server address for creating secondary connection
> // instead of address retrieved from server (because server will return jboss bind address
> // that can be local address, inaccessible from client)
> InvokerLocator patchedLocator = new InvokerLocator( (( InvokerLocator ) o).getOriginalURI().replace(
> (( InvokerLocator ) o).getHost(), this.getLocator().getHost() )
> );
> log.debug("secondary locator: " + o);
> log.debug("patched secondary locator: " + patchedLocator);
> return patchedLocator;
> and rebuild jboss-remoting project.
> For ports there are settings SECONDARY_BIND_PORT, SECONDARY_CONNECT_PORT allowing to set up them as you want. For address there is no one to do this.
--
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, 2 months