December 2017 - jboss-jira - Jboss List Archives

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

7 years, 1 month

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)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4838) Add smoke test for cloning profiles in CLI

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4838?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4838. ---------------------------- > Add smoke test for cloning profiles in CLI > ------------------------------------------ > > Key: WFLY-4838 > URL: https://issues.jboss.org/browse/WFLY-4838 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > Fix For: 10.0.0.Alpha5 > > > https://issues.jboss.org/browse/EAP7-35 provides profile cloning ability (runtime (CLI)) to create new profiles based on existing JBoss profiles (web, full, web-ha, full-ha). > This test serves as basic smoke tests to be run within the testsuite. > This test should be in WildFly TS (not WildFly Core TS), because WildFly has more complex default profile in domain part of TS than WildFly Core. > CloneProfileTestCase: > * clone default profile via CLI > * check results -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4530) Port jboss-as-ejb3_1_5.xsd to WildFly

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4530?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4530. ---------------------------- > Port jboss-as-ejb3_1_5.xsd to WildFly > ------------------------------------- > > Key: WFLY-4530 > URL: https://issues.jboss.org/browse/WFLY-4530 > Project: WildFly > Issue Type: Sub-task > Components: EJB > Reporter: Darran Lofthouse > Assignee: Richard Opalka > Fix For: 9.0.0.Final, 10.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4340) use-try-lock exposed for <connection-definition>

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4340?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4340. ---------------------------- > use-try-lock exposed for <connection-definition> > ------------------------------------------------ > > Key: WFLY-4340 > URL: https://issues.jboss.org/browse/WFLY-4340 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.2.0.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 10.0.0.Beta1 > > > <connection-definition> DMR: > {noformat} > use-try-lock undefined LONG > {noformat} > which should be removed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4048) Make sure predicated handlers (like handler-info.conf) can be used at a server level

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4048?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4048. ---------------------------- > Make sure predicated handlers (like handler-info.conf) can be used at a server level > ------------------------------------------------------------------------------------ > > Key: WFLY-4048 > URL: https://issues.jboss.org/browse/WFLY-4048 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4869) Failed to start statistics service for datasources

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4869?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4869. ---------------------------- > Failed to start statistics service for datasources > -------------------------------------------------- > > Key: WFLY-4869 > URL: https://issues.jboss.org/browse/WFLY-4869 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.Alpha4 > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 10.0.0.Alpha5 > > Attachments: jaxws-samples-wsrm-store.war > > > 11:45:40,471 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:jboss/datasources/rmclientdb] > 11:45:40,472 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.data-source.java:jboss/datasources/rmclientdb.statistics: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/rmclientdb.statistics: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > 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.IllegalArgumentException: WFLYCTL0218: A node is already registered at '/deployment=*/subsystem=datasources/data-source=*/statistics=jdbc' > at org.jboss.as.controller.registry.NodeSubregistry.register(NodeSubregistry.java:86) > at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:176) > at org.jboss.as.connector.services.datasources.statistics.DataSourceStatisticsService.start(DataSourceStatisticsService.java:83) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > reproducible w/ attached deployment -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3872) Recurring failure of EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3872?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3872. ---------------------------- > Recurring failure of EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn > -------------------------------------------------------------------------------------------- > > Key: WFLY-3872 > URL: https://issues.jboss.org/browse/WFLY-3872 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Alessio Soldano > Fix For: 10.0.0.Beta2 > > > Since https://github.com/wildfly/wildfly/pull/6660 was submitted, EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn is failing regularly. Not every time but very often. > Alessio, you mentioned seeing some error logging from XAResourceRecoveryImpl, but that's in the logs on successful runs as well, and occurs prior to the test as well. That's a period background task from the transaction manager trying to perform recovery of some previous transaction. I don't see why it would have any impact on this test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4577) Missing dependency "ibm.jdk" in module org.jboss.security.negotiation

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4577?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4577. ---------------------------- > Missing dependency "ibm.jdk" in module org.jboss.security.negotiation > --------------------------------------------------------------------- > > Key: WFLY-4577 > URL: https://issues.jboss.org/browse/WFLY-4577 > Project: WildFly > Issue Type: Enhancement > Affects Versions: JBoss AS7 7.2.0.Final > Reporter: Juraj Duráni > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > The module org.jboss.security.negotiation is missing "ibm.jdk" dependency. This module is needed if the JDV is running on IBM jdk - contains com.ibm.security.auth.module.Krb5LoginModule class. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4586) Provide JMS backward compatibility

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4586?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4586. ---------------------------- > Provide JMS backward compatibility > ---------------------------------- > > Key: WFLY-4586 > URL: https://issues.jboss.org/browse/WFLY-4586 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > New JMS clients (from WildFly 10) must be able to communicate with older WildFly 9 with HornetQ. -- 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