December 2017 - jboss-jira - Jboss List Archives

[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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5005) jacorb migration does not work in standalone mode

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5005?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5005. ---------------------------- > jacorb migration does not work in standalone mode > ------------------------------------------------- > > Key: WFLY-5005 > URL: https://issues.jboss.org/browse/WFLY-5005 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 10.0.0.Alpha5 > Reporter: Jeff Mesnil > Assignee: Tomasz Adamski > Fix For: 10.0.0.Beta2 > > > I was checking the messaging migration (for WFLY-5004) and I was wondering whether the jacorb migration was also working in domain mode. > It fails with an error but it also happens in standalone mode. > Steps to reproduce: > 1. edit the wildfly standalone-full.xml and replace the iiop-openjdk configuration from the template in legacy/jacorb resources (with the socket-bindings too): > {noformat} > <subsystem xmlns="urn:jboss:domain:jacorb:2.0"> > <orb persistent-server-id="1" socket-binding="jacorb" ssl-socket-binding="jacorb-ssl"> > <initializers transactions="spec" security="identity"/> > </orb> > <naming root-context="JBoss/Naming/root" export-corbaloc="on"/> > </subsystem> > {noformat} > 2. start the server in admin-only > 3. perform the migration > {noformat} > /subsystem=jacorb:migrate > { > "outcome" => "success", > "result" => [("iiop-openjdk" => "1.0.0")] > } > {noformat} > 4. reload the server in normal mode. > => it fails with the error: > {noformat} > 12:09:24,138 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 63) WFLYIIOP0001: Activating IIOP Subsystem > 12:09:24,138 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.3.0.Beta4 starting > 12:09:24,144 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.NumberFormatException: For input string: "undefined" > at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:142) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NumberFormatException: For input string: "undefined" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:580) > at java.lang.Integer.<init>(Integer.java:867) > at com.sun.corba.se.spi.orb.OperationFactory$IntegerAction.operate(OperationFactory.java:224) > at com.sun.corba.se.spi.orb.OperationFactory$ListAction.operate(OperationFactory.java:397) > at com.sun.corba.se.spi.orb.OperationFactory$ComposeAction.operate(OperationFactory.java:475) > at com.sun.corba.se.impl.orb.NormalParserAction.apply(NormalParserAction.java:47) > at com.sun.corba.se.spi.orb.PropertyParser.parse(PropertyParser.java:70) > at com.sun.corba.se.spi.orb.ParserImplBase.init(ParserImplBase.java:74) > at com.sun.corba.se.impl.orb.ORBDataParserImpl.<init>(ORBDataParserImpl.java:408) > at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:456) > at com.sun.corba.se.impl.orb.ORBImpl.set_parameters(ORBImpl.java:543) > at org.omg.CORBA.ORB.init(ORB.java:353) > at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:126) > ... 5 more > {noformat} > The giop-version in XML configuration after migration looks indeed wrong: > {noformat} > <subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0"> > <orb ssl-socket-binding="jacorb-ssl" socket-binding="jacorb" giop-version="1.undefined"/> > <initializers transactions="spec" security="identity"/> > <security add-component-via-interceptor="false"/> > </subsystem> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5172) Drop RSVP from default protocol stacks

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5172?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5172. ---------------------------- > Drop RSVP from default protocol stacks > -------------------------------------- > > Key: WFLY-5172 > URL: https://issues.jboss.org/browse/WFLY-5172 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta2 > > > Infinispan no longer flags any messages using Flag.RSVP, and therefore no longer requires RSVP in its protocol stack. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 December 2017