November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2469) Upgrade to HornetQ 2.4.0.CR1

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2469?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-2469: ------------------------------ Comment: was deleted (was: Jeff Mesnil <jmesnil(a)redhat.com> made a comment on [bug 1029836|https://bugzilla.redhat.com/show_bug.cgi?id=1029836] Description of problem: If an error occurs and the JMS bridge tries to reconnect to the JMS provider to look up the JMS resources from its FailureHandler, it fails with the exception: 10:37:02,546 INFO [org.hornetq.jms.server] (pool-3-thread-3) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 1,000 ms 10:37:03,547 WARN [org.hornetq.jms.server] (pool-3-thread-3) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.apache.qpid.jndi.PropertiesFileInitialContextFactory from classloader ModuleClassLoader for Module "org.hornetq:main" from local module loader @ac44b88 (finder: local module finder @5d3ad33d (roots: /usr/share/jbossas/modules,/usr/share/jbossas/modules/system/layers/base)) at org.jboss.as.naming.InitialContextFactoryBuilder.createInitialContextFactory(InitialContextFactoryBuilder.java:64) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:681) [rt.jar:1.6.0_24] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:305) [rt.jar:1.6.0_24] at javax.naming.InitialContext.init(InitialContext.java:240) [rt.jar:1.6.0_24] at javax.naming.InitialContext.<init>(InitialContext.java:214) [rt.jar:1.6.0_24] at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55) [hornetq-jms-server.jar:] at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40) [hornetq-jms-server.jar:] at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1222) [hornetq-jms-server.jar:] at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1460) [hornetq-jms-server.jar:] at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2000(JMSBridgeImpl.java:83) [hornetq-jms-server.jar:] at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2049) [hornetq-jms-server.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] How reproducible: Always Steps to Reproduce: 1. run a jms-bridge with a JMS provider loaded from a module 2. disconnect the network to make the jms-bridge fails 3. reconnect the network. The jms-bridge will handle the failure and reconnects to the JMS provider Actual results: The jms-bridge FailureHandler is not able to load the JMS provider classes. Expected results: The jms-bridge FailureHandler must be able to load the JMS provider classes from the module specified when the jms-bridge is added.) > Upgrade to HornetQ 2.4.0.CR1 > ---------------------------- > > Key: WFLY-2469 > URL: https://issues.jboss.org/browse/WFLY-2469 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > > HornetQ 2.4.0.CR1 depends on Netty 4.0.x versions that broke compatibility with Netty 3.x -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2469) Upgrade to HornetQ 2.4.0.BETA3

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2469?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-2469: ------------------------------ Summary: Upgrade to HornetQ 2.4.0.BETA3 (was: Upgrade to HornetQ 2.4.0.CR1) > Upgrade to HornetQ 2.4.0.BETA3 > ------------------------------ > > Key: WFLY-2469 > URL: https://issues.jboss.org/browse/WFLY-2469 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > > HornetQ 2.4.0.CR1 depends on Netty 4.0.x versions that broke compatibility with Netty 3.x -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2469) Upgrade to HornetQ 2.4.0.BETA3

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2469?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-2469: ------------------------------ Description: HornetQ 2.4.0.BETA3 depends on Netty 4.0.x versions that broke compatibility with Netty 3.x (was: HornetQ 2.4.0.CR1 depends on Netty 4.0.x versions that broke compatibility with Netty 3.x) > Upgrade to HornetQ 2.4.0.BETA3 > ------------------------------ > > Key: WFLY-2469 > URL: https://issues.jboss.org/browse/WFLY-2469 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > > HornetQ 2.4.0.BETA3 depends on Netty 4.0.x versions that broke compatibility with Netty 3.x -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2590) Zero Timeout Stateful EJB Leak

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2590?page=com.atlassian.jira.plugin.... ] Eduardo Martins updated WFLY-2590: ---------------------------------- Issue Type: Bug (was: Feature Request) > Zero Timeout Stateful EJB Leak > ------------------------------ > > Key: WFLY-2590 > URL: https://issues.jboss.org/browse/WFLY-2590 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Stateful EJB instances are not removed from cache upon release, if the timeout is zero. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2590) Zero Timeout Stateful EJB Leak

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-2590: ------------------------------------- Summary: Zero Timeout Stateful EJB Leak Key: WFLY-2590 URL: https://issues.jboss.org/browse/WFLY-2590 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB Reporter: Eduardo Martins Assignee: Eduardo Martins Stateful EJB instances are not removed from cache upon release, if the timeout is zero. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Jeff Mesnil edited comment on WFLY-2589 at 11/29/13 2:35 AM: ------------------------------------------------------------- I remember mentioning that when I refactored the messaging subsystem transformers. The new attributes that I added were reaching the legacy version with the default value set. At first, I thought about setting include-defaults to false when :read-resource is called by ReadTransformedResourceOperation but changed my mind on further notice. The resources are resolving every attributes and uses the default value if they are not set. If we do not include the default values when transforming the resources, we let the legacy versions resolve the attribute based on its own default value, not the one from the current version. That could lead to issues if such a value change between versions. I preferred to handle that explicitly when transforming the resources. For example, for new attributes, I discard them if they are undefined or set to the default value and reject them if they have any other value. was (Author: jmesnil): I remember mentioning that when I refactored the messaging subsystem transformers. The new attributes that I added were reaching the legacy version with the default value set. At first, I thought about setting include-defaults to false when :read-resource is called by ReadTransformedResourceOperation but changed my mind on further notice. The resources are resolving every attributes and uses the default value if they are not set. If we do not include the default values when transforming the resources, we let the legacy versions resolve the attribute based on its own default value, not the one from the current version. That could lead to issues if such a value change between versions. I preferred to handle tha > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2589) ReadTransformedResourceOperation should set include-defaults=false when calling read-resource

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-2589: ----------------------------------- I remember mentioning that when I refactored the messaging subsystem transformers. The new attributes that I added were reaching the legacy version with the default value set. At first, I thought about setting include-defaults to false when :read-resource is called by ReadTransformedResourceOperation but changed my mind on further notice. The resources are resolving every attributes and uses the default value if they are not set. If we do not include the default values when transforming the resources, we let the legacy versions resolve the attribute based on its own default value, not the one from the current version. That could lead to issues if such a value change between versions. I preferred to handle tha > ReadTransformedResourceOperation should set include-defaults=false when calling read-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-2589 > URL: https://issues.jboss.org/browse/WFLY-2589 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > > This needs further investigation, but it seems to mean that we have a lot of ModelFixers used in the wrong situation. i.e. the when transforming resources, attributes that should be undefined reach the transformers as defined with the default value set instead. > This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well. I'd like to see if he remembers before fixing -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2571) Make wildfly-mod_cluster-undertow module a separate subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2571?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-2571: -------------------------------------- Closed https://github.com/wildfly/wildfly/pull/5164 to take this approach instead. > Make wildfly-mod_cluster-undertow module a separate subsystem > ------------------------------------------------------------- > > Key: WFLY-2571 > URL: https://issues.jboss.org/browse/WFLY-2571 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2579) Aesh has problems on JDK8

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-2579?page=com.atlassian.jira.plugin.... ] Ståle Pedersen commented on WFLY-2579: -------------------------------------- hi, sorry for the delay. ive pushed version 0.33.11 which should work with jdk8 > Aesh has problems on JDK8 > ------------------------- > > Key: WFLY-2579 > URL: https://issues.jboss.org/browse/WFLY-2579 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: CLI > Reporter: Tomaz Cerar > Assignee: Ståle Pedersen > Fix For: 8.0.0.CR1 > > > Fix is already available in snapshot but it requires relase. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1085) No audit feature for security-realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1085?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1085: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 912233|https://bugzilla.redhat.com/show_bug.cgi?id=912233] from NEW to ON_QA > No audit feature for security-realm > ----------------------------------- > > Key: WFLY-1085 > URL: https://issues.jboss.org/browse/WFLY-1085 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Logging > Environment: EAP 6.0.x > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > There is no auditing feature for security-realm. Need the feature like audit provider for security-domain. -- 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, 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 November 2013