Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-3277

[JDV] HQ224018 occurred when starting up second jdv pod

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • JDV
    • None
    • Hide

      Add the following environment variables to deployment config.
      HORNETQ_CLUSTER_PASSWORD="1234abcd"
      HORNETQ_QUEUES=""
      HORNETQ_TOPICS=""

      Or customizing template to add the above variables. And use it when oc new-app.

      - apiVersion: v1
  kind: DeploymentConfig
  ...
      spec:
        containers:
        - env:
          - name: OPENSHIFT_KUBE_PING_LABELS
            value: application=${APPLICATION_NAME}
        ...
        # Add the follwoing 3 valiables.
          - name: HORNETQ_CLUSTER_PASSWORD 
            value: 1234abcd
          - name: HORNETQ_QUEUES
          - name: HORNETQ_TOPICS
          ...
      Show
      Add the following environment variables to deployment config. HORNETQ_CLUSTER_PASSWORD="1234abcd" HORNETQ_QUEUES="" HORNETQ_TOPICS="" Or customizing template to add the above variables. And use it when oc new-app. - apiVersion: v1 kind: DeploymentConfig ... spec: containers: - env: - name: OPENSHIFT_KUBE_PING_LABELS value: application=${APPLICATION_NAME} ... # Add the follwoing 3 valiables. - name: HORNETQ_CLUSTER_PASSWORD value: 1234abcd - name: HORNETQ_QUEUES - name: HORNETQ_TOPICS ...
    • Hide

      1. create a pod with quickstart as jdv-app-demo according to the following documentation.
      https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtualization/6.4/html/red_hat_jboss_data_virtualization_for_openshift/tutorials#deploy_your_project_using_the_red_hat_jboss_data_virtualization_for_openshift_image

      2. scaling up to 2 pods.

      Show
      1. create a pod with quickstart as jdv-app-demo according to the following documentation. https://access.redhat.com/documentation/en-us/red_hat_jboss_data_virtualization/6.4/html/red_hat_jboss_data_virtualization_for_openshift/tutorials#deploy_your_project_using_the_red_hat_jboss_data_virtualization_for_openshift_image 2. scaling up to 2 pods.

      After starting up with the JDV templates [1] such as datavirt64-basic-s2i.json, the following hornetq error occurred when scaling up 2 pods.
      [1] https://github.com/jboss-container-images/jboss-datavirt-6-openshift-image/blob/datavirt64-dev/resources/openshift/templates/datavirt64-basic-s2i.json

      ERROR [org.hornetq.core.server] (Old I/O server worker (parentId: 775636724, [id: 0x2e3b46f4, /172.17.0.11:5445]), runningThread=Thread-3 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=07797d5c-9724-11e9-a7fb-97f229d675c7-2140071753-804070275)) HQ224018: Failed to create session: HornetQException[errorType=CLUSTER_SECURITY_EXCEPTION message=HQ119099: Unable to authenticate cluster user: HORNETQ.CLUSTER.ADMIN.USER]
	at org.hornetq.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:123) [hornetq-server-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.server.impl.HornetQServerImpl.createSession(HornetQServerImpl.java:1131) [hornetq-server-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:150) [hornetq-server-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:78) [hornetq-server-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:653) [hornetq-core-client-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:616) [hornetq-core-client-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:574) [hornetq-core-client-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:589) [hornetq-server-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:72) [hornetq-core-client-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:281) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [hornetq-core-client-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [hornetq-core-client-2.3.25.SP28-redhat-1.jar:2.3.25.SP28-redhat-1]
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.socket.oio.OioWorker.process(OioWorker.java:71) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.socket.oio.AbstractOioWorker.run(AbstractOioWorker.java:73) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:51) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_212]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_212]
	at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_212]

              Unassigned Unassigned
              rhn-support-hdaicho Hiroki Daicho (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: