Re: Cannot communicate with Activemq over https using DNS name

2019-11-05 Thread Jean-Baptiste Onofré
Hi, It sounds like 443 is not assume as default if the port is not specified. I would suggest to create a Jira about that. Regards JB On 31/10/2019 08:36, black&white wrote: > We are trying to communicate with ActiveMQ from JMS adapter in weblogic over > https. > But while we are trying to do s

Re: Cannot communicate with Activemq over https using DNS name

2019-11-05 Thread Tim Bain
I had hoped to check the code to answer you with certainty, but circumstances haven't allowed that, so... The behavior you're seeing certainly seems to indicate that the HTTPS transport requires the port to be specified explicitly, and doesn't default to the default HTTPS port (443). If you think

Cannot communicate with Activemq over https using DNS name

2019-10-31 Thread
We are trying to communicate with ActiveMQ from JMS adapter in weblogic over https. But while we are trying to do same (https:///activemq), we are getting below error message. If we give https port along with DNS name (https://:443/activemq) it is going through fine. Any idea if https transport i