December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4974) XAResource of ActiveMQ does not implements org.jboss.tm.XAResourceWrapper

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4974?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4974. ---------------------------- > XAResource of ActiveMQ does not implements org.jboss.tm.XAResourceWrapper > ------------------------------------------------------------------------- > > Key: WFLY-4974 > URL: https://issues.jboss.org/browse/WFLY-4974 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha6 > > > messaging-activemq subsystem does not load properly the service for ActiveMQXAResourceWrapperFactory. > The service file contains a typo: it is org.apache.activemq.service.extensions.xa.ActiveMQXAResourceWrapperFactory while it must be org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperFactory -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5242) Inconsistent format for IPv6 addresses in server log

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5242?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5242. ---------------------------- > Inconsistent format for IPv6 addresses in server log > ---------------------------------------------------- > > Key: WFLY-5242 > URL: https://issues.jboss.org/browse/WFLY-5242 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Lyle Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 10.0.0.CR1 > > > Description of problem: > When IPv6 is used, square brackets for IPv6 addresses are missed in some of log entries. Specifically, the address format from Undertow logs is different from those "WFLYSRV" logs. > How reproducible: > Always > Steps to Reproduce: > 1. Config IPv6 (example: https://docs.jboss.org/author/display/WFLY10/Interfaces+and+ports) > 2. Start WildFly and check the log > Actual results: > ---------------------------------------- > 2015-08-31 12:51:47,812 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /0:0:0:0:0:0:0:1:8080 > ...... > 2015-08-31 12:51:48,431 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9993/management > 2015-08-31 12:51:48,432 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9993 > ---------------------------------------- > In Undertow logs it's like "/0:0:0:0:0:0:0:1:8080" but in WildFly server logs "http://[::1]:9993/management" > Expected results: > Consistent format should be used for IPv6 address across different components and the address is enclosed in square brackets [ ]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4824) Build fails downloading licenses due to insufficient heap space

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4824?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4824. ---------------------------- > Build fails downloading licenses due to insufficient heap space > --------------------------------------------------------------- > > Key: WFLY-4824 > URL: https://issues.jboss.org/browse/WFLY-4824 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 10.0.0.Alpha3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 10.0.0.Alpha4 > > > In our CI cluster we regularly see failures building the feature-pack module due to lack of heap space. Increasing it to 1024 seems to be enough to avoid these intermittent failures. Example output: > {code} > [INFO] --- maven-assembly-plugin:2.5.3:single (assemble) @ wildfly-feature-pack --- > [INFO] Reading assembly descriptor: assembly.xml > [INFO] Building zip: /home/mmusgrov/source/forks/narayana/jboss-as/feature-pack/target/wildfly-10.0.0.Alpha3-SNAPSHOT.zip > [INFO] > [INFO] --- license-maven-plugin:1.8:download-licenses (default) @ wildfly-feature-pack --- > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 07:09 min > [INFO] Finished at: 2015-06-23T16:21:09+01:00 > [INFO] Final Memory: 60M/399M > [INFO] ------------------------------------------------------------------------ > [ERROR] Java heap space -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4816) Add new ContextService needs reload

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4816?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4816. ---------------------------- > Add new ContextService needs reload > ----------------------------------- > > Key: WFLY-4816 > URL: https://issues.jboss.org/browse/WFLY-4816 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Hynek Švábek > Assignee: Eduardo Martins > Fix For: 9.0.1.Final, 10.0.0.Alpha6 > > > Add new ContextService needs reload. Other Concurrency Utils don't need reload.... > Example is here: > https://github.com/hsvabek/wildfly/tree/test_context_service > EEConcurrentManagementTestCase.testContextServiceManagement() -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4559) Add support for development mode to Weld's management model

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4559?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4559. ---------------------------- > Add support for development mode to Weld's management model > ----------------------------------------------------------- > > Key: WFLY-4559 > URL: https://issues.jboss.org/browse/WFLY-4559 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 10.0.0.Alpha3 > > > http://docs.jboss.org/weld/reference/3.0.0.Alpha9/en-US/html/devmode.html > http://weld.cdi-spec.org/news/2015/02/05/weld-300Alpha4/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4906) Serialization failure for maps with null values

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4906?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4906. ---------------------------- > Serialization failure for maps with null values > ----------------------------------------------- > > Key: WFLY-4906 > URL: https://issues.jboss.org/browse/WFLY-4906 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 9.0.0.Final > Reporter: Aparna Chaudhary > Assignee: Stuart Douglas > Labels: jackson > Fix For: 10.0.0.Alpha6 > > > Serialization of generic map with null values results in _java.lang.UnsupportedOperationException: Type id handling not implemented for type java.lang.Object_. > The issue is fixed in jackson-databind 2.5.2 https://github.com/FasterXML/jackson-databind/issues/691 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5213) Injecting external context to Artemis fails

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5213?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5213. ---------------------------- > Injecting external context to Artemis fails > ------------------------------------------- > > Key: WFLY-5213 > URL: https://issues.jboss.org/browse/WFLY-5213 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Beta2 > Reporter: Ondřej Kalman > Assignee: Jeff Mesnil > Fix For: 10.0.0.CR1 > > > When external-context is defined in EAP and it's pointing to external Artemis broker, it can't be injected in to MDB via @Resource(lookup = "java:global/externalcontext"). Such injection results in null object. > Injecting destinations from external context results in javax.ejb.EJBTransactionRolledbackException. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4638) EntityBean instances are leaked from pool if exception is thrown during instance activation

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4638?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4638. ---------------------------- > EntityBean instances are leaked from pool if exception is thrown during instance activation > ------------------------------------------------------------------------------------------- > > Key: WFLY-4638 > URL: https://issues.jboss.org/browse/WFLY-4638 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.CR2, 10.0.0.Alpha1 > Reporter: Alexey Makhmutov > Assignee: Alexey Makhmutov > Fix For: 10.0.0.Alpha2 > > > This is addition to WFLY-4569. > One more case was discovered when bean is leaked from the pool after an exception is thrown in certain methods: > * If any exception is thrown during call to instance.activate() (which includes calls to ejbActivate and ejbLoad), then cache implementations (both optimistic and pessimistic) never notifies pool that instance should be discarded. > In addition, a little correction should be made for handling exceptions thrown from ejbCreate (handling was introduced as part of WFLY-4569) -- such instances should not be released to the pool, but discarded with pool notification in order to comply with EJB specification. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4452) Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4452?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4452. ---------------------------- > Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache > --------------------------------------------------------------- > > Key: WFLY-4452 > URL: https://issues.jboss.org/browse/WFLY-4452 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Alpha6 > > > Currently, the attributes for each child resource of a cache use RESTART_ALL_SERVICES, thus any change to one of these attributes requires all services to restart. This is overkill, since only the services of the parent resource (i.e. cache) actually require restarting. > Ideally, each child resource should create a runtime service for its corresponding sub-configuration. e.g. the transaction resource would create a Service<TransactionConfiguration>. Thus the cache resource's add handler becomes much less complex - and the corresponding Service<Configuration> need only depend on the sub-configuration services for each child resource. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4308) Proxies created via ContextService.createContextualProxy(...) are not Serializable

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4308?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4308. ---------------------------- > Proxies created via ContextService.createContextualProxy(...) are not Serializable > ---------------------------------------------------------------------------------- > > Key: WFLY-4308 > URL: https://issues.jboss.org/browse/WFLY-4308 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 10.0.0.CR1 > > > Setting priority to critical since, I believe, this is a matter of compliance with the concurrency utilities specification. > Section 3.3.4 of the specification states that: > "All invocation handlers for the contextual proxy implementation must implement java.io.Serializable." > While the invocation handler of the generated proxy does indeed implement Serializable, it contains a reference to org.jboss.as.server.moduleservice.ServiceModuleLoader (among others), which is not serializable, thus attempts to serialize the proxies generated via ContextService.createContextualProxy(...) via JBoss Marshalling throw a org.infinispan.commons.marshall.NotSerializableException: org.jboss.as.server.moduleservice.ServiceModuleLoader -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017