2020年4月8日 21:21:15未分类评论55阅读模式

英文:

How to configure messaging activemq - thorntail or swarm using project-defaults yaml

问题

以下是翻译好的内容：

如何使用 project-defaults.yaml 配置 messaging activemq - thorntail 或 swarm

我目前遇到以下异常：

要求资源 '/subsystem=messaging-activemq/connection-factory=RemoteConnectionFactory' 具备的功能不可用：
org.wildfly.messaging.activemq.connector.external.http-connector；此功能的可能注册点：

messaging-activemq:
  connection-factories:
    InVmConnectionFactory:
      entries:
        - 'java:/ConnectionFactory'
      connectors:
        - 'in-vm'
    RemoteConnectionFactory:
      ha: true
      entries:
        - 'java:jboss/exported/jms/RemoteConnectionFactory'
      connectors:
        - 'http-connector'
  pooled-connection-factories:
    activemq-ra:
      entries:
        - 'java:/JmsXA'
        - 'java:jboss/DefaultJMSConnectionFactory'
      transaction: xa
  in-vm-connectors:
    in-vm:
      server-id: 0
  http-connectors:
    http-connector-throughput:
      params:
        batch-delay: 50
      socket-binding: http
      endpoint: http-acceptor-throughput
  servers:
    default:
      jms-queues:
        ExpiryQueue:
          entries:
            - 'java:/jms/queue/ExpiryQueue'
        DLQ:
          entries:
            - 'java:/jms/queue/DLQ'
        CsiDLQ:
          entries:
            - 'java:/jms/queue/CsiDLQ'
        CCDLQ:
          entries:
            - 'java:/jms/queue/CCDLQ'
        CCRequestQueue:
          entries:
            - 'java:/jms/queue/CCRequestQueue'
      address-settings:
        default:
          message-counter-history-day-limit: 10
          page-size-bytes: 2097152
          max-size-bytes: 10485760
          expiry-address: jms.queue.ExpiryQueue
          dead-letter-address: jms.queue.DLQ
          redistribution-delay: 1000
        CCRequestQueue:
          message-counter-history-day-limit: 10
          page-size-bytes: 2097152
          max-size-bytes: 10485760
          expiry-address: jms.queue.ExpiryQueue
          dead-letter-address: CCDLQ
          redistribution-delay: 1000
      security-settings:
        default:
          roles:
            guest:
              send: true
              delete-durable-queue: true
              create-non-durable-queue: true
              consume: true
      http-acceptors:
        http-acceptor-mq:
          http-listener: default
      http-connectors:
        http-connector-mq:
          socket-binding: http
          endpoint: http-acceptor
      cluster-password: ${jboss.messaging.cluster.password:CHANGEME}
      discovery-groups:
        activemq-discovery:
          jgroups-cluster: activemq-cluster
      broadcast-groups:
        activemq-broadcast:
          jgroups-cluster: activemq-cluster
          connectors:
            - 'http-connector'
      cluster-connections:
        activemq-cluster:
          cluster-connection-address: jms
          connector-name: http-connector
          discovery-group: activemq-discovery

启动时的完整异常：

2020-04-08 14:55:27.032 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: 资源 '/subsystem=messaging-activemq/connection-factory=RemoteConnectionFactory' 所需的功能不可用：
org.wildfly.messaging.activemq.connector.external.http-connector；此功能的可能注册点：
		/subsystem=messaging-activemq/connector=*
		/subsystem=messaging-activemq/in-vm-connector=*
		/subsystem=messaging-activemq/remote-connector=*
		/subsystem=messaging-activemq/http-connector=*
		/subsystem=messaging-activemq/server=*/connector=*
		/subsystem=messaging-activemq/server=*/in-vm-connector=*
		/subsystem=messaging-activemq/server=*/remote-connector=*
		/subsystem=messaging-activemq/server=*/http-connector=*
		/subsystem=messaging-activemq/server=*/http-acceptor=*
2020-04-08 14:55:27.036 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: 服务器引导失败，无法恢复；退出。有关详细信息，请参见前面的消息。

英文:

How to configure messaging activemq - thorntail or swarm using project-defaults yaml

I am currently getting the below exception

Capabilities required by resource '/subsystem=messaging-activemq/connection-factory=RemoteConnectionFactory' are not available:
org.wildfly.messaging.activemq.connector.external.http-connector; Possible registration points for this capability:

 messaging-activemq:
    connection-factories:
      InVmConnectionFactory:
        entries:
          - &#39;java:/ConnectionFactory&#39;
        connectors:
          - &#39;in-vm&#39;
      RemoteConnectionFactory:
        ha: true
        entries:
          - &#39;java:jboss/exported/jms/RemoteConnectionFactory&#39;
        connectors:
          - &#39;http-connector&#39;
    pooled-connection-factories:
      activemq-ra:
        entries:
          - &#39;java:/JmsXA&#39;
          - &#39;java:jboss/DefaultJMSConnectionFactory&#39;
        transaction: xa
    in-vm-connectors:
      in-vm:
        server-id: 0
    http-connectors:
      http-connector-throughput:
        params:
          batch-delay: 50

        socket-binding: http
        endpoint: http-acceptor-throughput
    servers:
      default:
        jms-queues:
          ExpiryQueue:
            entries:
              - &#39;java:/jms/queue/ExpiryQueue&#39;
          DLQ:
            entries:
              - &#39;java:/jms/queue/DLQ&#39;
          CsiDLQ:
            entries:
              - &#39;java:/jms/queue/CsiDLQ&#39;
          CCDLQ:
            entries:
              - &#39;java:/jms/queue/CCDLQ&#39;
          CCRequestQueue:
            entries:
              - &#39;java:/jms/queue/CCRequestQueue&#39;
        address-settings:
          default:
            message-counter-history-day-limit: 10
            page-size-bytes: 2097152
            max-size-bytes: 10485760
            expiry-address: jms.queue.ExpiryQueue
            dead-letter-address: jms.queue.DLQ
            redistribution-delay: 1000
          CCRequestQueue:
            message-counter-history-day-limit: 10
            page-size-bytes: 2097152
            max-size-bytes: 10485760
            expiry-address: jms.queue.ExpiryQueue
            dead-letter-address: CCDLQ
            redistribution-delay: 1000
        security-settings:
          default:
            roles:
              guest:
                send: true
                delete-durable-queue: true
                create-non-durable-queue: true
                consume: true
        http-acceptors:
          http-acceptor-mq:
            http-listener: default
        http-connectors:
          http-connector-mq:
            socket-binding: http
            endpoint: http-acceptor
        cluster-password: ${jboss.messaging.cluster.password:CHANGEME}
        discovery-groups:
          activemq-discovery:
            jgroups-cluster: activemq-cluster
        broadcast-groups:
          activemq-broadcast:
            jgroups-cluster: activemq-cluster
            connectors:
              - &#39;http-connector&#39;
        cluster-connections:
          activemq-cluster:
            cluster-connection-address: jms
            connector-name: http-connector
            discovery-group: activemq-discovery

Full Exception on startup.

2020-04-08 14:55:27,032 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource &#39;/subsystem=messaging-activemq/connection-factory=RemoteConnectionFactory&#39; are not available:
    org.wildfly.messaging.activemq.connector.external.http-connector; Possible registration points for this capability: 
		/subsystem=messaging-activemq/connector=*
		/subsystem=messaging-activemq/in-vm-connector=*
		/subsystem=messaging-activemq/remote-connector=*
		/subsystem=messaging-activemq/http-connector=*
		/subsystem=messaging-activemq/server=*/connector=*
		/subsystem=messaging-activemq/server=*/in-vm-connector=*
		/subsystem=messaging-activemq/server=*/remote-connector=*
		/subsystem=messaging-activemq/server=*/http-connector=*
		/subsystem=messaging-activemq/server=*/http-acceptor=*
2020-04-08 14:55:27,036 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

答案1

得分: 0

以下是为我工作的内容... 遵循上面@Ladicek的评论

  messaging-activemq:
    in-vm-connectors:
      in-vm:
        server-id: 0
    http-connectors:
      http-connector:
        params:
          batch-delay: 50
        socket-binding: http
        endpoint: http-acceptor-throughput
    servers:
      default:
        jms-queues:
          ExpiryQueue:
            entries:
              - 'java:/jms/queue/ExpiryQueue'
          DLQ:
            entries:
              - 'java:/jms/queue/DLQ'
          CSIRequestQueue:
            entries:
              - 'java:/jms/queue/CSIRequestQueue'
          CsiDLQ:
            entries:
              - 'java:/jms/queue/CsiDLQ'
          CCDLQ:
            entries:
              - 'java:/jms/queue/CCDLQ'
          CCRequestQueue:
            entries:
              - 'java:/jms/queue/CCRequestQueue'
        address-settings:
          default:
            message-counter-history-day-limit: 10
            page-size-bytes: 2097152
            max-size-bytes: 10485760
            expiry-address: jms.queue.ExpiryQueue
            dead-letter-address: jms.queue.DLQ
            redistribution-delay: 1000
          CCRequestQueue:
            message-counter-history-day-limit: 10
            page-size-bytes: 2097152
            max-size-bytes: 10485760
            expiry-address: jms.queue.ExpiryQueue
            dead-letter-address: CCDLQ
            redistribution-delay: 1000
        security-settings:
          default:
            roles:
              guest:
                send: true
                delete-durable-queue: true
                create-non-durable-queue: true
                consume: true
        http-acceptors:
          http-acceptor-mq:
            http-listener: default
        http-connectors:
          http-connector-mq:
            socket-binding: http
            endpoint: http-acceptor
        cluster-password: ${jboss.messaging.cluster.password:CHANGEME}
        discovery-groups:
          activemq-discovery:
            jgroups-cluster: activemq-cluster
        broadcast-groups:
          activemq-broadcast:
            jgroups-cluster: activemq-cluster
            connectors:
              - 'http-connector'
        cluster-connections:
          activemq-cluster:
            cluster-connection-address: jms
            connector-name: http-connector
            discovery-group: activemq-discovery

英文:

This what worked for me... following the comment above from @Ladicek

  messaging-activemq:
    in-vm-connectors:
      in-vm:
        server-id: 0
    http-connectors:
      http-connector:
        params:
          batch-delay: 50
        socket-binding: http
        endpoint: http-acceptor-throughput
    servers:
      default:
        jms-queues:
          ExpiryQueue:
            entries:
              - &#39;java:/jms/queue/ExpiryQueue&#39;
          DLQ:
            entries:
              - &#39;java:/jms/queue/DLQ&#39;
          CSIRequestQueue:
            entries:
              - &#39;java:/jms/queue/CSIRequestQueue&#39;
          CsiDLQ:
            entries:
              - &#39;java:/jms/queue/CsiDLQ&#39;
          CCDLQ:
            entries:
              - &#39;java:/jms/queue/CCDLQ&#39;
          CCRequestQueue:
            entries:
              - &#39;java:/jms/queue/CCRequestQueue&#39;
        address-settings:
          default:
            message-counter-history-day-limit: 10
            page-size-bytes: 2097152
            max-size-bytes: 10485760
            expiry-address: jms.queue.ExpiryQueue
            dead-letter-address: jms.queue.DLQ
            redistribution-delay: 1000
          CCRequestQueue:
            message-counter-history-day-limit: 10
            page-size-bytes: 2097152
            max-size-bytes: 10485760
            expiry-address: jms.queue.ExpiryQueue
            dead-letter-address: CCDLQ
            redistribution-delay: 1000
        security-settings:
          default:
            roles:
              guest:
                send: true
                delete-durable-queue: true
                create-non-durable-queue: true
                consume: true
        http-acceptors:
          http-acceptor-mq:
            http-listener: default
        http-connectors:
          http-connector-mq:
            socket-binding: http
            endpoint: http-acceptor
        cluster-password: ${jboss.messaging.cluster.password:CHANGEME}
        discovery-groups:
          activemq-discovery:
            jgroups-cluster: activemq-cluster
        broadcast-groups:
          activemq-broadcast:
            jgroups-cluster: activemq-cluster
            connectors:
              - &#39;http-connector&#39;
        cluster-connections:
          activemq-cluster:
            cluster-connection-address: jms
            connector-name: http-connector
            discovery-group: activemq-discover

专注分享java语言的经验与见解，让所有开发者获益！

如何使用 project-defaults yaml 配置 messaging activemq – thorntail 或 swarm。

问题

答案1

Go like channels in Java

在低资源环境下使用Apache Cassandra和Go服务器

avatica-go客户端读取Phoenix查询服务器：[驱动程序：连接错误]

向Spring端点发送POST请求，返回状态码400。

Spring Boot控制器从Golang应用程序接收到的重定向请求会被重复执行两次。

可以在不将其读入内存的情况下多次重用HTTP请求体吗？

How to register my go lang microservice in Spring Eureka Service Discovery

在应用程序-go + BDD-java中模拟第三方服务

What is value, reference vs pointer and what these three example used to pass?

Do goroutines and light-weight Java threads mean we never need use thread pools and async code again?

发表评论