Getting error 503: Unknown Queue [Subcode:20]

General Discussions
1

Hi there,
Thanks for the reply on my earlier question.
Here is the new problem statement:
I am using Solace connector to connect my broker and consume messages. I have a dataflow streaming pipeline started but its throwing below error.

com.solacesystems.jcsmp.JCSMPErrorResponseException: 503: Unknown Queue [Subcode:20]

Here is the state of my message broker on the destination side:

Message VPN
Messaging Stats
Client Data Messages
- Received message 1
- Sent message 0
Message Discards
Incoming Message Discards 1
Outgoing Message Discards 0

Bridges
Static bridge - red_to_blue - status is up
Local and Remote Queue Name - blue_test_red_test_Queue
Subscription - Nothing is subscribed
Stats
Messages
Client Data Messages - 1
Message Discards
Incoming Message Discards 0
Outgoing Message Discards 0

Queues
blue_test_red_test_Queue - incoming is on and outgoing is on. type exclusive. consumer 1. durable yes
no subscriptions
Consumers
#bridge/local/red_to_blue/solacesolace0/877/9
Delivery State - Deliver from Input Stream
Stats
Cumulative Statistics (since reload/clear)
Messages Redelivered 0
Messages Queued (MB) 0
Messages Queued (msgs) 0

Configuration in java code

String host = "tcp://<ip>:55555";
queues.add("blue_test_red_test_Queue");
Collection<SolaceTextRecord> input1 =
        pipeline
          .apply(SolaceIO.<SolaceTextRecord>readMessage()
            .withConnectionConfiguration(SolaceIO.ConnectionConfiguration.create(host, queues)

On pushing the message to my source message vpn, I am getting this error. What am I missing?

503: Unknown Queue [Subcode:20]

Thanks
Sumit

2

Hi Sumit. the .withUserName() will act in one of two ways .withUsername(name) it would connect to the default messageVpn. If you set .withUsername(name@vpn) you would connect to message vpn “vpn”. Is it possible you are connecting into the default message vpn when you expected to connect elsewhere?

3

Of course .withVpn() would also achieve the result of putting you in the correct VPN.

4

Moving the last question to separate discussion. On stopping the connector these messages stopped on destination broker which shows that its the connector that was throwing something to the broker. Thanks!