Why JBR-listener, designed as HTTPS really work througth HTTP protocol?

[gdr]

Hi!

I make the service with jbr listener and SOAPProcessor action. In jbr provider I set protocol="https" and describe nessesary properties. Service starts and works well at development server, but when i try to deploy it to the production server i see, that jbr-listener available througth http protocol and not available througth https protocol.

I can't understand it...

There is my jboss-esb.xml file:

<?xml version="1.0"?>

<jbossesb parameterReloadSecs="5"

xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.2.0.xsd"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.2.0.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.2.0.xsd">

<providers>

  <jbr-provider name="HttpGateway" protocol="https">

   <property name="jbr-KeyStoreURL" value="keystore.jks"/>

   <property name="jbr-KeyStorePassword" value="11111"/>

   <property name="jbr-TrustStoreURL" value="keystore.jks"/>

   <property name="jbr-TrustStorePassword" value="11111"/>

   <property name="jbr-ClientAuthMode" value="need"/>

   <property name="serviceInvokerTimeout" value="20000"/>

   <jbr-bus busid="HttpGatewayChannel" port="3536"/>

  </jbr-provider>

  <jms-provider connection-factory="ConnectionFactory" name="InternalQueue">

   <jms-bus busid="InternalQueueChannel"/>

  </jms-provider>

</providers>

<services>

  <service category="SWS" description="Secure web service" name="SecureWebService">

   <listeners>

    <jbr-listener busidref="HttpGatewayChannel" is-gateway="true" name="HttpGateway"/>

    <jms-listener busidref="InternalQueueChannel" is-gateway="false" name="InternalQueue">

     <jms-message-filter dest-name="queue/InternalQueue"

      dest-type="QUEUE" persistent="false"/>

    </jms-listener>

   </listeners>

   <actions mep="RequestResponse">

    <action class="org.jboss.soa.esb.actions.soap.SOAPProcessor" name="MessageExchange">

     <property name="jbossws-endpoint" value="SecureWebService"/>

    </action>

   </actions>

  </service>

</services>

</jbossesb>

[tcunning]

When you say you "I see that jbr-listener available through http protocol and not available through https protocol" - what exactly are you looking at?

Are there possibly network differences (firewall, etc) between your development environment and the production server?

[gdr]

I open my browser and type: https://localhost:3536 and browser tell me that this url is invalid, then i type url http://localhost:3536 and browser show me call stack (call stack in this situation is normal, because my service handles only POST queries, not GET). On my dev server I see the same call stack when I use https://localhost:3536 url.

But, in http://localhost:8080/contract I see, that wsdl of my service available at url http://localhost:8080/contract/contract.jsp?serviceCat=SWS&serviceName=SecureWebService&protocol=https, and this url works.

[gdr]

Now I check the traffic by fiddler. It is really unencrypted HTTP traffic.

I was try to use standard configuration and configuration with binding manager - the same results (HTTPS works at development server and doesn't works at production).

What I should check more?

[tfennelly]

This sounds really odd for sure.  If it were me I'd be wonering am I looking at or deploying to the same server.  Your app is configured for https, yet after deployment you have http (not just a broken https).  That sounds like magic

Anyway... I think you should consider using the http gateway: http://community.jboss.org/wiki/HTTPGateway

[gdr]

I didn't understand the cause of problem, but I solve it: I just install JBoss ESB on JBoss AS 5.1. Before it I used the standalone version of JBossESB