]
Eduardo Martins commented on WFLY-10837:
----------------------------------------
[~tomekadamski] the migrate op of the jacorb subsystem must be updated to handle this
migration on its own, otherwise it has no purpose
IIOP subsystem requires port binding to be defined which was not
necessary in prior WFLY versions
-------------------------------------------------------------------------------------------------
Key: WFLY-10837
URL:
https://issues.jboss.org/browse/WFLY-10837
Project: WildFly
Issue Type: Bug
Components: IIOP
Reporter: Ondra Chaloupka
Assignee: Tomasz Adamski
If the {{standalone-*.xml}} configuration defines to use IIOP subsystem but it does not
defines the port binding element
{code}
<orb socket-binding="iiop"/>
{code}
The server starts with error
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start
service jboss.iiop-openjdk.orb-service: org.jboss.msc.service.StartException in service
jboss.iiop-openjdk.orb-service: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP
socket bindings have been configured
at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:150)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at
org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at
org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at
org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: WFLYIIOP0115: No IIOP socket bindings have
been configured
at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:109)
... 8 more
{code}
The attribute of the {{socket-binding}} in the model is not defined as {{required}}.
{code}
"socket-binding" => {
"type" => STRING,
"description" => "The name of the socket binding
configuration that specifies the ORB port.",
"attribute-group" => "orb",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min-length" => 1L,
"max-length" => 2147483647L,
"access-constraints" => {"sensitive" =>
{"socket-binding-ref" => {"type" => "core"}}},
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
}
{code}
Up to that declaring the iiop socket binding was not necessary in WildFly 13.0.0.Final.
Could that be a backward compatibility problem too?
Up to that