November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2471: ----------------------------------------------- Jitka Kozana <jkudrnac(a)redhat.com> changed the Status of [bug 1028474|https://bugzilla.redhat.com/show_bug.cgi?id=1028474] from ON_QA to VERIFIED > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] This issue was verified using the 6.2.0.CR1 preview bits. > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2412) Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2412?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2412: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1024930|https://bugzilla.redhat.com/show_bug.cgi?id=1024930] from ON_QA to VERIFIED > Security Realm and LDAP Connection incorrectly available as resourced under core-services=management in domain mode. > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2412 > URL: https://issues.jboss.org/browse/WFLY-2412 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > Security realms and LDAP connections should only be definable under specific hosts in domain mode - the resources for these are currently available in the domain wide code-services=management resource. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2352) Domain controller fails to restart due to an inconsistent rollback of a redeploy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2352?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2352: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1021763|https://bugzilla.redhat.com/show_bug.cgi?id=1021763] This issue was verified using the 6.2.0.CR1 preview bits. > Domain controller fails to restart due to an inconsistent rollback of a redeploy > -------------------------------------------------------------------------------- > > Key: WFLY-2352 > URL: https://issues.jboss.org/browse/WFLY-2352 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Osamu Nagano > Assignee: Brian Stansberry > > When you try to redeploy (or deploy with --force option) the same application which has the same contents hash, and a necessary dependency like a datasource beeing injected in the application is lost by some reason, the redeploy operation will delete the contents under $JBOSS_HOME/domain/data/content directory but won't delete entries in domain.xml. Then the domain controller fails to start up because no contents found in the directory. This likely happens when you frequently changes settings during other servers shutting down. > The domain controller fails to restart with the following log messages. > {code} > 12:04:10,623 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "exampleapp.war")]) - failure description: "JBAS010876: No deployment content with hash c1306bc4855f4ed9914c9616f2b999c5c62a79d3 is available in the deployment content repository for deployment 'exampleapp.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > 12:04:10,628 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > The domain controller should be independent from such a server specific issue and there should be a way to fix this via CLI or Console, not by a manual editing of domain.xml. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2352) Domain controller fails to restart due to an inconsistent rollback of a redeploy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2352?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2352: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1021763|https://bugzilla.redhat.com/show_bug.cgi?id=1021763] from ON_QA to VERIFIED > Domain controller fails to restart due to an inconsistent rollback of a redeploy > -------------------------------------------------------------------------------- > > Key: WFLY-2352 > URL: https://issues.jboss.org/browse/WFLY-2352 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Osamu Nagano > Assignee: Brian Stansberry > > When you try to redeploy (or deploy with --force option) the same application which has the same contents hash, and a necessary dependency like a datasource beeing injected in the application is lost by some reason, the redeploy operation will delete the contents under $JBOSS_HOME/domain/data/content directory but won't delete entries in domain.xml. Then the domain controller fails to start up because no contents found in the directory. This likely happens when you frequently changes settings during other servers shutting down. > The domain controller fails to restart with the following log messages. > {code} > 12:04:10,623 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "exampleapp.war")]) - failure description: "JBAS010876: No deployment content with hash c1306bc4855f4ed9914c9616f2b999c5c62a79d3 is available in the deployment content repository for deployment 'exampleapp.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > 12:04:10,628 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > The domain controller should be independent from such a server specific issue and there should be a way to fix this via CLI or Console, not by a manual editing of domain.xml. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1717) Bundling reduces performance in scenario mimicking Inifinispan

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1717?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1717: -------------------------------- Investigate idea by [~rvansa]: As a last thought for DefaultBundler2 principle (this is the one I find most appealing): It seems to me that the thread does not do much work in the lock, so the bundle does not grab much messages. The format of batch does not specify how many messages will there be in advance, so, instead of just adding the message to list (fast), couldn't we keep the DataOutputStream and write the message to the stream? Potential issues: * We don't know up front whether the batch has 1 or more messages; in case of 1 message we send a single message, otherwise we send a batch. However, the wire format is different * We'd have to associate one output stream per target destination > Bundling reduces performance in scenario mimicking Inifinispan > -------------------------------------------------------------- > > Key: JGRP-1717 > URL: https://issues.jboss.org/browse/JGRP-1717 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3 > Reporter: Radim Vansa > Assignee: Bela Ban > Fix For: 3.5 > > Attachments: benchmark-jgroups.xml, jgroups-udp.pdf, jgroups-udp.xml > > > In Radargun benchmark of JGroups mimicking the behaviour of Infinispan we can see that performance with bundling on actually reduces the performance. > See attached configurations and results. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-336) Property Reactivity fails on phreak

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-336: ---------------------------------- Summary: Property Reactivity fails on phreak Key: DROOLS-336 URL: https://issues.jboss.org/browse/DROOLS-336 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco In LeftInputAdapterNode a modifyByPass happens, for a sink that has not been reached before. So it thinks it's new, and thus propagates as an insert The real bug comes in doInsertObject method. It creates a child LT here, even though once it enters doInsertSegmentMemory the mask intersect fails. This leaves a child LT, that is not propagated. Next time update is called, as the LT is there it thinks it's a modify and propagates as a modify - but it never reached the beta node or the LeftMemory, and thus the memory corruption. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1458) Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1458?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1458: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1021487|https://bugzilla.redhat.com/show_bug.cgi?id=1021487] from ON_QA to VERIFIED > Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState() > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-1458 > URL: https://issues.jboss.org/browse/WFLY-1458 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Ladislav Thon > Fix For: 8.0.0.CR1 > > Attachments: thread.dump.txt > > > When deploying a container, Arquillian will use a management client to connect to the deployed container to see if it is in a running state. If the management address and management port are incorrect, the connection to the container hangs indefinitely. > Please allow configuration of a timeout so that if the connection paramaters are not correct, at least the container deployment will fail with a meaningful error. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1458) Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1458?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1458: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> made a comment on [bug 1021487|https://bugzilla.redhat.com/show_bug.cgi?id=1021487] This issue was not spotted in EAP 6.2.0.ER7. > Allow specifying timeout for org.jboss.as.arquillian.container.ManagementClient.isServerInRunningState() > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-1458 > URL: https://issues.jboss.org/browse/WFLY-1458 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management, Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Richard Achmatowicz > Assignee: Ladislav Thon > Fix For: 8.0.0.CR1 > > Attachments: thread.dump.txt > > > When deploying a container, Arquillian will use a management client to connect to the deployed container to see if it is in a running state. If the management address and management port are incorrect, the connection to the container hangs indefinitely. > Please allow configuration of a timeout so that if the connection paramaters are not correct, at least the container deployment will fail with a meaningful error. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-335) Inconsistency between ReteOO and PHREAK on test with temporal reasoning and dynamic salience.

by Duncan Doyle (JIRA)

Duncan Doyle created DROOLS-335: ----------------------------------- Summary: Inconsistency between ReteOO and PHREAK on test with temporal reasoning and dynamic salience. Key: DROOLS-335 URL: https://issues.jboss.org/browse/DROOLS-335 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR5 Environment: Mac OS-X 10.9, Oracle Hotspot 1.7.0_45 Reporter: Duncan Doyle Assignee: Mark Proctor Reproducer at: https://github.com/DuncanDoyle/DroolsInOrderTemporalReasoningPhreakIssue Clone the project in the given GitHub repository and run 'mvn -Preteoo clean test'. The test will pass. Next, run 'mvn -Pphreak clean test', both tests fail. -- 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, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013