Thanks Dejan.
I hope my certificates are appropriate as same certificates works with ssl.
So, I assume that its not a certificate issue.
Also, when I used http instead of https, i got a response back from broker,
but then the connection was closed. My debug log says,
533 [main] DEBUG org.apache.commons.httpclient.methods.EntityEnclosingMethod
- Request body sent
533 [main] DEBUG httpclient.wire.header - << "HTTP/1.1 200 OK[\r][\n]"
533 [main] DEBUG httpclient.wire.header - << "Content-Length: 0[\r][\n]"
533 [main] DEBUG httpclient.wire.header - << "Server:
Jetty(7.1.6.v20100715)[\r][\n]"
534 [main] DEBUG org.apache.commons.httpclient.HttpMethodBase - Buffering
response body
534 [main] DEBUG org.apache.commons.httpclient.HttpMethodBase - Resorting
to protocol version default close connection policy
534 [main] DEBUG org.apache.commons.httpclient.HttpMethodBase - Should NOT
close connection, using HTTP/1.1
534 [main] DEBUG org.apache.commons.httpclient.HttpConnection - Releasing
connection back to connection manager.
And at the activemq end, the log says,
INFO | Transport failed:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long:
blockingQueue_11020816
Any suggestion, what could be the reason for this.
Am I missing some settings in activemq.xml.
Please let me know your inputs.
Thanks
Manu
--
View this message in context: http://activemq.2283324.n4.nabble.com/Java-client-doesnt-work-with-https-tp4222791p4225347.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
|