March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4472) Upgrade HornetQ to 2.4.6.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-4472: --------------------------------- Summary: Upgrade HornetQ to 2.4.6.Final Key: WFLY-4472 URL: https://issues.jboss.org/browse/WFLY-4472 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 9.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4471) Enabled automatic encryption of passwords stored in configuration

by Jason Shepherd (JIRA)

Jason Shepherd created WFLY-4471: ------------------------------------ Summary: Enabled automatic encryption of passwords stored in configuration Key: WFLY-4471 URL: https://issues.jboss.org/browse/WFLY-4471 Project: WildFly Issue Type: Feature Request Components: ConfigAdmin Environment: Wildfly 9 Reporter: Jason Shepherd Assignee: Thomas Diesler Currently encrypting passwords such as Datasource passwords can only be done 'after the fact'. You have to create the datasource first, then retrospectively store the password in the vault and dereference it in the configuration. It would be great if could turn on automatic storage of passwords in the vault so that when you create a Datasource password, or add a resource adapter which specifies a remote resource password, those passwords were automatically added to the vault, and deferenced in the configuration file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-753) org.drools.core.common.DefaultFactHandle cannot be cast to org.drools.core.common.EventFactHandle

by MR-C MR-C (JIRA)

MR-C MR-C created DROOLS-753: -------------------------------- Summary: org.drools.core.common.DefaultFactHandle cannot be cast to org.drools.core.common.EventFactHandle Key: DROOLS-753 URL: https://issues.jboss.org/browse/DROOLS-753 Project: Drools Issue Type: Feature Request Components: core engine Affects Versions: 6.2.0.Final Environment: win7 java Reporter: MR-C MR-C Assignee: Mario Fusco Hi,when I use drools do some cep rules.I accour an exception.for more infomation,look at Forum Reference. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4470?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4470: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1159572 > 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 > Fix For: 9.0.0.CR1 > > > 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)

9 years

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4470?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4470: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1159572|https://bugzilla.redhat.com/show_bug.cgi?id=1159572] from ASSIGNED to POST > 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 > Fix For: 9.0.0.CR1 > > > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4419) Dependency on a deployed CDI module - beans are not injected

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-4419?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-4419: -------------------------------------- I just tried this out by modifying a test from the test suite and it appeared to work fine. Can you attach a reproducer? > Dependency on a deployed CDI module - beans are not injected > ------------------------------------------------------------ > > Key: WFLY-4419 > URL: https://issues.jboss.org/browse/WFLY-4419 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld > Affects Versions: 8.2.0.Final > Reporter: Dirk Buchhorn > Assignee: Stuart Douglas > > I want to deploy two modules to wildfly 8.2.0 The module-a contains beans (and later CDI producer and other stuff) and module-b use this beans. Beans from module-a should be injected with CDI in module-b (There is a beans.xml in both modules.). All works fine if the module-a is direct referenced as dependency like this: > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <dependencies> > <module name="deployment.module-a-1.0.0.jar" meta-inf="import" /> > </dependencies> > </deployment> > </jboss-deployment-structure> > > But the dependency to module-a should be without to know the deployed version, so I tried to set a module alias and (or) to re-export module-a under a different name like this. > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <module-alias name="deployment.module-a-alias" /> > </deployment> > </jboss-deployment-structure> > > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <module name="deployment.module-a"> > <module-alias name="deployment.module-a-alias" /> > <dependencies> > <module name="deployment.module-a-1.0.0.jar" export="true" meta-inf="export" /> > </dependencies> > </module> > </jboss-deployment-structure> > > But either the module alias or a re-export under a new module name worked. The reported exception is always: > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type XYZ with qualifiers @Default > > The module alias fit my requirements and I guess is should work with CDI but it dosn't. > Two questions: > - Why CDI don't work with module alias and module re-export? > - How to deal with dependencies and module versions? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3157) Add support for serving static resources from an external location

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3157?page=com.atlassian.jira.plugin.... ] Stuart Douglas reopened WFLY-3157: ---------------------------------- > Add support for serving static resources from an external location > ------------------------------------------------------------------ > > Key: WFLY-3157 > URL: https://issues.jboss.org/browse/WFLY-3157 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

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

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4338?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-4338: ------------------------------------- The linked PR reverts the change for https://issues.jboss.org/browse/WFLY-3829. We should find a way to accommodate both issues. > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-461) TestSuiteEnvironment should use privileged access to properties

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-461?page=com.atlassian.jira.plugin... ] James Perkins resolved WFCORE-461. ---------------------------------- Resolution: Rejected This doesn't make much sense to do this. > TestSuiteEnvironment should use privileged access to properties > --------------------------------------------------------------- > > Key: WFCORE-461 > URL: https://issues.jboss.org/browse/WFCORE-461 > Project: WildFly Core > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > > The current TestSuiteEnvironment uses lots of {{System.getProperty()}} which fail under a security manager. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-461) TestSuiteEnvironment should use privileged access to properties

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-461?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-461: --------------------------------- Fix Version/s: (was: 1.0.0.Beta1) > TestSuiteEnvironment should use privileged access to properties > --------------------------------------------------------------- > > Key: WFCORE-461 > URL: https://issues.jboss.org/browse/WFCORE-461 > Project: WildFly Core > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > > The current TestSuiteEnvironment uses lots of {{System.getProperty()}} which fail under a security manager. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2015