-
Notifications
You must be signed in to change notification settings - Fork 64
Replies: 2 comments · 6 replies
-
@Laveshsp can you try to follow the tutorial send_receive_ingress ? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Yes, I followed the same tutorial but its not working. I wanted this to work on EKS cluster but as it didnt work, tried it on minikube following the steps given but the same issue when using minikube too |
Beta Was this translation helpful? Give feedback.
All reactions
-
That tutorial is regularly tested on minikube, maybe your ssl secret is not correct. You can use the system property
|
Beta Was this translation helpful? Give feedback.
All reactions
-
For testing purposes, Im using ssl secrets using the below steps suggested in the tutorial and have created the k8s secret out of these files.
Here is the complete debug error logs giving Failed to create netty connection.
Not really able to understand what exactly is missing in the CRD manifest or ssl certs as its exactly same as given in tutorial docs |
Beta Was this translation helpful? Give feedback.
All reactions
-
That tutorial is only tested on Linux while it seems that you are using Windows (
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Just to add more context on my setup
Please find the broker pod logs which u requested for. (An observation that these logs are available as soon as broker pod comes up. I don't see any logs getting generated as soon as I hit the artemis check queue command )
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Your broker pod logs confirm that the exception client-side stops the client before it sends the IP packets to open the secure TCP connection. This error should not depend on the ArtemisCloud operator, you can double-check it by starting a standalone broker on your Windows laptop. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Standalone broker on windows laptop might not help me with my requirement as I have to set the broker on EKS cluster. As you are saying that its not an issue an the artemis broker server end, let me see to connect to broker via a linux WSL or some other means and observe the behavior. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I tried installing clustered brokers on EKS cluster using below manifest
apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
name: artemis-broker
spec:
resourceTemplates:
selector:
kind: "Ingress"
annotations:
nginx.ingress.kubernetes.io/enable-modsecurity: "false"
patch:
kind: "Ingress"
spec:
ingressClassName: nginx
selector:
kind: "StatefulSet"
name: artemis-broker-ss
patch:
kind: "StatefulSet"
spec:
template:
spec:
nodeSelector:
topology.ebs.csi.aws.com/zone: us-west-2a
ingressDomain: artemis.sbx.test.com
deploymentPlan:
size: 3
persistenceEnabled: true
podSecurityContext:
fsGroup: 0
messageMigration: true
clustered: true
acceptors:
port: 62626
expose: true
sslEnabled: true
sslSecret: send-receive-sslacceptor-secret
expose: true
port: 5672
protocols: all
brokerProperties:
console:
expose: true
I'm trying to perform below steps following the doc https://artemiscloud.io/docs/tutorials/send_receive_ingress/
$ export BROKER_URL="tcp://${INGRESS_URL}:443?sslEnabled=true&verifyHost=false&trustStorePath=${CERT_FOLDER}/broker.ks&trustStorePassword=000000&useTopologyForLoadBalancing=false"
$ artemis check queue --name TEST --produce 10 --browse 10 --consume 10 --url ${BROKER_URL} --verbose
I get below error
Executing org.apache.activemq.artemis.cli.commands.check.QueueCheck check queue --name TEST --produce 10 --browse 10 --consume 10 --url tcp://artemis-broker-sslacceptor-0-svc-ing-activemq-artemis-operator.artemis.sbx.test.com:443?sslEnabled=true&verifyHost=false&trustStorePath=/c/Users/username/Desktop/POC/k8s/artemis/activemq-artemis-operator/examples/artemis/ssl-certs/broker.ks&trustStorePassword=000000&useTopologyForLoadBalancing=false --verbose
Home::C:\apache-artemis-2.36.0, Instance::null
Connection brokerURL = tcp://artemis-broker-sslacceptor-0-svc-ing-activemq-artemis-operator.artemis.sbx.test.com:443?sslEnabled=true&verifyHost=false&trustStorePath=/c/Users/username/Desktop/POC/k8s/artemis/activemq-artemis-operator/examples/artemis/ssl-certs/broker.ks&trustStorePassword=000000&useTopologyForLoadBalancing=false
18:11:04.064 [pool-2-thread-1] ERROR org.apache.activemq.artemis.core.client - AMQ214016: Failed to create netty connection
io.netty.channel.StacklessClosedChannelException: null
at io.netty.channel.AbstractChannel$AbstractUnsafe.ensureOpen(ChannelPromise)(Unknown Source) ~[netty-transport-4.1.112.Final.jar:4.1.112.Final]
Connection failed::Failed to create session factory
--url:
Type in the connection URL for a retry (e.g. tcp://localhost:61616)
QueueCheck failed. Reason: timeout
I tried following this doc as well https://artemiscloud.io/docs/tutorials/external_mqtt_clients/ but not able to connect here too.
For starter, my goal is to to produce/consume messages to and from broker.
Request you to help me on this
Beta Was this translation helpful? Give feedback.
All reactions