[jboss-jira] [JBoss JIRA] (WFLY-5060) Migrate management operation JacORB to IIOP JDK orb fails on reload with NumberFormatException

[Ondřej Chaloupka (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondřej Chaloupka updated WFLY-5060:
-----------------------------------
    Steps to Reproduce: 
Use attached standalone-full.jacorb.xml and run server as
{code}
$JBOSS_HOME/bin/standalone.sh -c standalone-full.jacorb.xml
$JBOSS_HOME/bin/jboss-cli.sh -c
:reload(admin-only=true)
/subsystem=jacorb:migrate()
:reload
{code}


> Migrate management operation JacORB to IIOP JDK orb fails on reload with NumberFormatException
> ----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5060
>                 URL: https://issues.jboss.org/browse/WFLY-5060
>             Project: WildFly
>          Issue Type: Bug
>          Components: IIOP
>            Reporter: Ondřej Chaloupka
>            Assignee: Tomasz Adamski
>         Attachments: standalone-full.jacorb.initial.xml
>
>
> When I tried a simple migration of JacORB subsystem to IIOP OpenJDK with operation {{/subsystem=jacorb:migrate()}} server started with errors of not having successfully migrated attribute because of [1].
> I've consulted the dev discussion here
> http://lists.jboss.org/pipermail/wildfly-dev/2015-April/003855.html
> and what I understand it's fine that {{migrate}} operation succeed but if the {{migrate}} is able to find out that there is some trouble it should be shown as error/warning to console for user could fix the issue before going to live with {{reload()}} operation after migration.
> In this particular case the JacORB subsystem worked with value {{undefined}} which IIOP OpenJDK orb doesn't. I expect that such difference is possible to be detected during {{migrate}} operation and inform user about it.
> I believe that run operation as success and then failed during server startup is not right. Plus if you check the exception [1] you can see there is no much information what parameter is wrongly set. That would be fine to add some more info there as well.
> [1]
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) 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
> ...
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.iiop-openjdk.orb-service" => "org.jboss.msc.service.StartException in service jboss.iiop-openjdk.orb-service: java.lang.NumberFormatException: For input string: \"undefined\"
>     Caused by: java.lang.NumberFormatException: For input string: \"undefined\""}}
> INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186:   Services which 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"
> ...
> ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: EAP 7.0.0.Alpha1 (WildFly Core 2.0.0.Alpha11) started (with errors) in 690ms - Started 231 of 478 services (5 services failed or missing dependencies, 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)