March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-543) Revisit how the model validation happens

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-543?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFCORE-543. ------------------------------- Resolution: Done > Revisit how the model validation happens > ---------------------------------------- > > Key: WFCORE-543 > URL: https://issues.jboss.org/browse/WFCORE-543 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 1.0.0.Beta1 > > > Currently the ValidateModelStepHandler is triggered by AbstractAddStepHandler. Not all add handlers extend AbstractAddStepHandler. Also, it does not seem to be triggered for writes. > Also if used in a composite along the lines of > {code} > [standalone@localhost:9990 /] batch > [standalone@localhost:9990 / #] /system-property=xxx:add(value=test) > [standalone@localhost:9990 / #] /system-property=xxx:remove > [standalone@localhost:9990 / #] run-batch > {code} > the handler will get triggered at the end for the add. It will fail for the add since there is no such resource. While that is easy to work around by checking for a NoSuchResourceException around the OC.readResource() it seems that what triggers the use of the ValidateModelStepHandler should be more an intrinsic part of the controller which knows what has and has not been added/removed/written to. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4338) JConsole script builds wrong path

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4338?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-4338: ---------------------------------- [~avlemos] Can you open a pull request at https://github.com/wildfly/wildfly? I believe the files are in https://github.com/wildfly/wildfly/tree/master/feature-pack/src/main/reso... > JConsole script builds wrong path > --------------------------------- > > Key: WFLY-4338 > URL: https://issues.jboss.org/browse/WFLY-4338 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 8.2.0.Final > Environment: Linux (Ubuntu 14.10) and Mac OS X Yosemite (10.10.2) > Reporter: André Lemos > Assignee: Kabir Khan > Priority: Trivial > Labels: bash, jconsole, wildfly > Attachments: jconsole.patch > > > The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://{insert server ip here}:9990}} is probably never recognized and the connection is never done. > The path, under mac is: > {{/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar}} > So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1922) FD_SOCK/FD: members are not unsuspected

by Bela Ban (JIRA)

Bela Ban created JGRP-1922: ------------------------------ Summary: FD_SOCK/FD: members are not unsuspected Key: JGRP-1922 URL: https://issues.jboss.org/browse/JGRP-1922 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.4 When we have members \{A,B,C,D,E\} and E suspects B, then it broadcasts a SUSPECT(B) event and adds B to its suspects list. E then continues braodascting the SUSPECT(B) event until a new view has been installed. Everybody adds B to its suspects list, except B which sends an I_AM_ALIVE message. When VERIFY_SUSPECT on A detects that B is *not* dead, it sends an UNSUSPECT(B) event up and down the stack, removing B from its suspects list. However, this event is *not broadcast*; E will continue sending its SUSPECT(B) message. SOLUTION: broadcast an UNSUSPECT event for som protocols. This is needed for FD_SOCK and FD, and not needed by FD_ALL and FD_ALL2. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3370) 'max-redelivery-delay' is missing from the messaging schema

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3370?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3370: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1156048|https://bugzilla.redhat.com/show_bug.cgi?id=1156048] from ASSIGNED to CLOSED > 'max-redelivery-delay' is missing from the messaging schema > ----------------------------------------------------------- > > Key: WFLY-3370 > URL: https://issues.jboss.org/browse/WFLY-3370 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.CR2 > Environment: All > Reporter: Ravi Bhardwaj > Assignee: Jeff Mesnil > Fix For: 9.0.0.Alpha1 > > > max-redelivery-delay is missing from address-setting in JBoss EAP 6.2.2 and also WFLY 8.1.0 CR2. I see it being part of HornetQ 2.3.x in [1] > [1] http://docs.jboss.org/hornetq/2.3.0.CR2/docs/user-manual/html/configurati... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1253) Multiple JDBC drivers versions - wrong driver is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1253?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1253: ------------------------------------------------ Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1157649|https://bugzilla.redhat.com/show_bug.cgi?id=1157649] from ASSIGNED to CLOSED > Multiple JDBC drivers versions - wrong driver is used > ----------------------------------------------------- > > Key: JBJCA-1253 > URL: https://issues.jboss.org/browse/JBJCA-1253 > Project: IronJacamar > Issue Type: Bug > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > When multiple verions of the driver are being used only one is being used. the class driver is cached with the same string, i.e: "jdbc:mysql". This cache is shared among every mcf (the field LocalManagedConnectionFactory::driverCache is static). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4365) jboss-ejb-container-interceptors_1_0.xsd is invalid

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-4365?page=com.atlassian.jira.plugin.... ] Carlo de Wolf reassigned WFLY-4365: ----------------------------------- Assignee: Weston M. Price > jboss-ejb-container-interceptors_1_0.xsd is invalid > --------------------------------------------------- > > Key: WFLY-4365 > URL: https://issues.jboss.org/browse/WFLY-4365 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Sande Gilda > Assignee: Weston M. Price > > Importing the ejb-security-interceptors [1] quickstart into JBoss Developer Studio results in the following jboss-ejb3.xml validation errors. > cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. > jboss-ejb3.xml > /jboss-ejb-security-interceptors/src/main/resources/META-INF line 31 > XML Problem > jboss-ejb-security-interceptor source is here: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel... > The quickstart bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=1178748 > The related bug for the invalid schema for JBoss EAP 6.4 is here: https://bugzilla.redhat.com/show_bug.cgi?id=1193948 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-617) Invalid 'started in' values for embedded CLI server

by Petr Kremensky (JIRA)

Petr Kremensky created WFCORE-617: ------------------------------------- Summary: Invalid 'started in' values for embedded CLI server Key: WFCORE-617 URL: https://issues.jboss.org/browse/WFCORE-617 Project: WildFly Core Issue Type: Bug Reporter: Petr Kremensky Priority: Minor Embedded CLI server use {{StartTimeHolder.START_TIME;}} as startTime property - used for server 'started in' time calculation. {noformat} $ ./jboss-cli.sh # wait for 5-10s [disconnected /] embed-server --std-out=echo ... started in 12241ms ... [standalone@embedded /] stop-embedded-server # wait for 5-10s [disconnected /] embed-server --std-out=echo ... started in 26388ms ... {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4470) Duplicate message deliveries when start an MDB twice via CLI

by Chao Wang (JIRA)

Chao Wang created WFLY-4470: ------------------------------- Summary: Duplicate message deliveries when start an MDB twice via CLI Key: WFLY-4470 URL: https://issues.jboss.org/browse/WFLY-4470 Project: WildFly Issue Type: Bug Components: EJB, JMS Affects Versions: 9.0.0.Beta2 Reporter: Chao Wang Assignee: Chao Wang Description of problem: A singleton MDB delivers duplicate messages when start-delivery() is invoked twice while the message being delivered Steps to Reproduce: 1. Create a producer, which keeps sending messages for every second 2. Deploy a singleton consumer MDB 3. Invoke start-delivery() method on the MDB while the messages being delivered Actual results: MDB delivers duplicate messages Expected results: MDB needs to ignore start-delivery() call if the MDB has already been started. Additional info: -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3386) Nullpointer exception on AbstractSessionBeanStore.getLockStore from within Activiti CDI

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-3386?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-3386: ------------------------------------ bq. ...which seems to be ignored somewhere in the event call chain, and hence getSession(true) effectively returns null. [~marembo2008] Do you have a reproducer for this? I've briefly looked at undertow sources and I don't think that unchecked exceptions are swallowed. > Nullpointer exception on AbstractSessionBeanStore.getLockStore from within Activiti CDI > --------------------------------------------------------------------------------------- > > Key: WFLY-3386 > URL: https://issues.jboss.org/browse/WFLY-3386 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.0.0.Final > Environment: CentOS, Mac (Mountain Lion). > Reporter: Andries Ehlers > Assignee: Martin Kouba > > Background: > The actual exception seems to be very close the one in issue: WFLY-3001 but we are not using JSF at all, but Activiti CDI. > Not sure if this is a Wildfly or Activiti issue - it could very well be that there is a bug in Activiti with how it manages the CDI scopes. Unfortunately we're at a loss and seeing that the nullpointer is thrown from within a weld AbstractSessionBeanStore, I decided to post it here. Please advise. > Error: > We use Activiti CDI within Wildfly 8.0.0.Final. We randomly encounter an issue (sometimes immediately after a redeploy, other times after a few hours of inactivity on the server) the following issue. When Activiti attempts to retrieve the ContextBeanInstance from its ConversationScopedAssociationProxy, a NullPointer exception is thrown while attempting to retrieve the lock store within Weld (see below). > ----------------------------- > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) java.lang.NullPointerException: null > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:90) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.activiti.cdi.impl.context.DefaultContextAssociationManager$ConversationScopedAssociation$Proxy$_$$_WeldClientProxy.getTask(Unknown Source) ~[activiti-cdi-5.15.jar:na] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.activiti.cdi.impl.context.DefaultContextAssociationManager.getTask(DefaultContextAssociationManager.java:237) ~[activiti-cdi-5.15.jar:na] > 2014-05-21 10:05:34,432 INFO [stdout] (default task-12) at org.activiti.cdi.BusinessProcess.startTask(BusinessProcess.java:332) ~[activiti-cdi-5.15.jar:na] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3904) Unable to enable statistics via configuration for resource adapters

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3904?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3904: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1191848 > Unable to enable statistics via configuration for resource adapters > ------------------------------------------------------------------- > > Key: WFLY-3904 > URL: https://issues.jboss.org/browse/WFLY-3904 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Daniel Atallah > Assignee: Stefano Maestri > > The statistics for resource adapters are hard-coded to be disabled at startup: > https://github.com/wildfly/wildfly/blob/47830b44d1bd48c4fcdc2489cecaa3971... > It's not possible to enable the statistics in a persistent way - it needs to be done each time the servers starts e.g. via jmx. > Ideally there'd be a "statistics-enabled" attribute on the "<connection-definition>" element in the configuration file in the same way that there is on "<datasource>". -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015