Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-23081

[GSS](7.4.z) 'connector-ref' configuration in ejb3 subsystem not accepted

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Rejected
    • 7.4.2.GA
    • None
    • EJB
    • None

    Description

      Extracting a WildFly 26.0.0.Final server and replacing:

                  <remote cluster="ejb" connectors="http-remoting-connector" thread-pool-name="default">
                      <channel-creation-options>
                          <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
                      </channel-creation-options>
                  </remote>
      

      with

                  <remote cluster="ejb" connector-ref="http-remoting-connector" thread-pool-name="default">
                      <channel-creation-options>
                          <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
                      </channel-creation-options>
                  </remote>
      

      is resulting in

      ERROR [org.jboss.as.controller] (Controller Boot Thread) 
      
      OPVDX001: Validation error in standalone.xml -----------------------------------
      |
      |  442: <subsystem xmlns="urn:jboss:domain:pojo:1.0"/>
      |  443: <subsystem xmlns="urn:jboss:domain:remoting:4.0">
      |  444:     <http-connector name="http-remoting-connector" connector-ref="default" sasl-authentication-factory="application-sasl-authentication"/>
      |                                                          ^^^^ 'connector-ref' isn't an allowed attribute for the 'remote' element
      |                                                               
      |                                                               Did you mean 'connectors'?
      |                                                               
      |                                                               Attributes allowed here are: cluster, connectors, execute-in-worker,
      |                                                                 thread-pool-name 
      |
      |  445: </subsystem>
      |  446: <subsystem xmlns="urn:jboss:domain:request-controller:1.0"/>
      |  447: <subsystem xmlns="urn:jboss:domain:resource-adapters:6.0"/>
      |
      | 'connector-ref' is allowed on elements: 
      | - server > profile > {urn:jboss:domain:remoting:4.0}subsystem > http-connector
      |
      |
      | The primary underlying error message was:
      | > ParseError at [row,col]:[201,102]
      | > Message: WFLYCTL0197: Unexpected attribute 'connector-ref' encountered
      |
      |-------------------------------------------------------------------------------
      
      ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
              at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:137)
              at org.jboss.as.server.ServerService.boot(ServerService.java:404)
              at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:424)
              at java.lang.Thread.run(Thread.java:748)
      
      FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
      

      but this configuration should be accepted for compatibility.

      Attachments

        Issue Links

          Activity

            People

              rhn-support-jbaesner Joerg Baesner
              rhn-support-jbaesner Joerg Baesner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: