Dear all,
We write a html page on STB(set-top box) using mqttws31.js and try to
connect MQ with MQTT protocol over websocket. But it always post an error with
‘AMQJSC000E Connect timed out’. It’s weird that if I just write javascript
direct with websocket it’s work.
That’s to
Have you made config changes to allow the broker to trust your self-signed
cert?
On Aug 27, 2015 1:17 PM, "ArturoBelano" wrote:
> I tried to connect using the openssl client and got:
> connect: Connection refused
> connect:errno=61
> That doesn't narrow the issue down too much for me though. I'm
I tried to connect using the openssl client and got:
connect: Connection refused
connect:errno=61
That doesn't narrow the issue down too much for me though. I'm using a
self-signed cert with the ssl connection. Any ideas?
--
View this message in context:
http://activemq.2283324.n4.nabble.com
I still get a connection refused notice. Is there a good way to debug wss
connections? Maybe openssl?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-over-secure-websocket-tp4701435p4701457.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I just accidently removed the ending quote when I posted. Sorry about that.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-over-secure-websocket-tp4701435p4701456.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 08/27/2015 12:55 PM, Chaomei Lo wrote:
> That was exactly I did, however, the consumer did not get what the producer
> sent. Is there any other thing cause it ?
>
> Thanks.
>
> On Wed, Aug 26, 2015 at 5:22 PM, Timothy Bish wrote:
If sending and receiving from Topics remember that the consumer
That was exactly I did, however, the consumer did not get what the producer
sent. Is there any other thing cause it ?
Thanks.
On Wed, Aug 26, 2015 at 5:22 PM, Timothy Bish wrote:
> On 08/26/2015 08:13 PM, Chaomei Lo wrote:
> > Thanks, Tim.
> >
> > Let me rephrase my question - is the Message c
On 08/27/2015 04:40 AM, spamtrap wrote:
> When I call the cms:Message acknowledge() method I get the message
> "Pointer operator-> - Pointee is NULL." printed to stdout/err. How
> can I avoid this?
>
>
>
There isn't enough info here to make a guess, usually some sample code
can make it more obvious
Your config snippet is also missing a closing quote on the wss URI; is that
just an artifact of posting your question?
On Aug 27, 2015 6:02 AM, "Christopher Shannon" <
christopher.l.shan...@gmail.com> wrote:
> You should just use wss://myurl:61616 for your URL. I don't believe you
> need the stom
I believe you said that PFC kicked in based on the per-destination limit
without setting ProducerWindowSize; is that accurate? If so, I'm assuming
it was whole-connection PFC. If you wanted per-producer PFC, I expect you
would need to set ProducerWindowSize, though I've never run with batches
and
You should just use wss://myurl:61616 for your URL. I don't believe you
need the stomp+wss at the end.
On Wed, Aug 26, 2015 at 9:01 PM, ArturoBelano
wrote:
> I configured and restarted activemq according to the documentation to allow
> ssl, wss and stomp+ssl (abbrevated here just to show you wh
When I call the cms:Message acknowledge() method I get the message
"Pointer operator-> - Pointee is NULL." printed to stdout/err. How
can I avoid this?
12 matches
Mail list logo