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

(7.4.z) Wrong error code in EjbLogger.connectorNotConfiguredForEJBClientInvocations compared to upstream

    XMLWordPrintable

    Details

      Description

      In WildFly main branch, the error code was defined to 527:

          @LogMessage(level = ERROR)
          @Message(id = 527, value = "Remoting connector (address %s, port %s) is not correctly configured for EJB client invocations, the connector must be listed in <remote/> 'connectors' attribute to receive EJB client invocations")
          void connectorNotConfiguredForEJBClientInvocations(String address, int port);
      

      But in EAP 7.4 , it was defined to 526:

          @LogMessage(level = ERROR)
          @Message(id = 526, value = "Remoting connector (address %s, port %s) is not correctly configured for EJB client invocations, the connector must be listed in <remote/> 'connectors' attribute to receive EJB client invocations")
          void connectorNotConfiguredForEJBClientInvocations(String address, int port);
      

      which is confusing, and it blocks the PR: https://github.com/jbossas/jboss-eap7/pull/3896 from merging because it used error code: 526 as well.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              gaol Lin Gao
              Reporter:
              gaol Lin Gao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: