activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Siddle (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1330) SslTransport doesn't set the client certificate chain as transportContext
Date Thu, 06 Sep 2007 15:17:22 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40089
] 

Jon Siddle commented on AMQ-1330:
---------------------------------

Having just submitted AMQ-1381, I realise that this is the same issue (I didn't spot it while
I've been debugging what I thought was a configuration problem for the past three days).

As Erik says, the fix is simple, and I've even attached a patch to the issue I submitted.

> SslTransport doesn't set the client certificate chain as transportContext
> -------------------------------------------------------------------------
>
>                 Key: AMQ-1330
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1330
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 4.1.1
>            Reporter: Erik Jõgi
>             Fix For: 5.2.0
>
>   Original Estimate: 1 minute
>  Remaining Estimate: 1 minute
>
> org.apache.activemq.transport.tcp.SslTransport is supposed to override the doConsume()
method of TransportSupport and set the client certificate chain as transportContext. 
> However the method signature is incorrect - instead of overriding:
> public void doConsume(Object command)
> it defines a new method:
> public void doConsume(Command command)
> which is never called.
> So it is fixed very easily - just change Command to Object in the method signature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message