Return-Path: 
 <users-return-39729-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C570A115EB
	for <apmail-activemq-users-archive@www.apache.org>;
 Thu, 14 Aug 2014 17:49:49 +0000 (UTC)
Received: (qmail 90279 invoked by uid 500); 14 Aug 2014 17:49:49 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 90241 invoked by uid 500); 14 Aug 2014 17:49:49 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 90216 invoked by uid 99); 14 Aug 2014 17:49:48 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Aug 2014 17:49:48 +0000
X-ASF-Spam-Status: No, hits=0.6 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of mattrpav@gmail.com designates
 209.85.219.52 as permitted sender)
Received: from [209.85.219.52] (HELO mail-oa0-f52.google.com) (209.85.219.52)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Aug 2014 17:49:22 +0000
Received: by mail-oa0-f52.google.com with SMTP id o6so1270201oag.11
        for <users@activemq.apache.org>; Thu, 14 Aug 2014 10:49:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to;
        bh=e8r9Ri7bh0etWwWEzYM0mwmI/1kEBpmUwtwXlC5Bsps=;
        b=bFI1WMrBQFqLQs14Xb3Yts14l7gO+vXKGPQeUWXBNGV+RKBpYWztu7l+CM66QYAVE5
         cyvPfBhGdaQiH0t2pZawsCy1PE4tVqK9wttV1+8z/BGOLCD/qf8OO9IDHOtTtcn5ePQ5
         0fLDTvtv/rrQPj45SlLbdaw06CwYSgrTc6zHRfn5powVTQzrVqmabnhiUZjbu88kL/E7
         efqtfu2os0dLCZjrfLQttP8k5kzVQxCudL+spRloJMF1jGBK7YFtEeaG9GnuFntOjqYO
         /0ADbIWUMcU2Kbwexm4enFf9bCmbHI6saL46srVeqpz4uW4IMnZ9JBYLDV4Ce2o0I9jK
         kPaQ==
X-Received: by 10.60.51.106 with SMTP id j10mr5770806oeo.77.1408038561012;
        Thu, 14 Aug 2014 10:49:21 -0700 (PDT)
Received: from [192.168.17.102] ([192.252.76.202])
        by mx.google.com with ESMTPSA id hu1sm6170499obb.0.2014.08.14.10.49.18
        for <users@activemq.apache.org>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Thu, 14 Aug 2014 10:49:18 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Securing JMS queque
From: Matt Pavlovich <mattrpav@gmail.com>
In-Reply-To: <1407929367203-4684509.post@n4.nabble.com>
Date: Thu, 14 Aug 2014 12:49:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B49F93AD-20A8-4757-BACF-43BD7143AB12@gmail.com>
References: <1407929367203-4684509.post@n4.nabble.com>
To: users@activemq.apache.org
X-Mailer: Apple Mail (2.1878.6)
X-Virus-Checked: Checked by ClamAV on apache.org

This "tcp://127.0.0.1:49881=94 looks like the client-side port, which is =
standard for TCP/IP client-server traffic. If you have confirmed that =
messages are moving, than you should feel confident that SSL is working. =
 if you want to validate with complete certainty, open a network sniffer =
and you should see the traffic is encrypted.

On Aug 13, 2014, at 6:29 AM, akshattandon <akshat.mbx@gmail.com> wrote:

> Hi=20
>=20
> I am facing an issue while configuring ssl for JMS on apache service =
mix ,=20
>=20
> I have configured the broker in its blueprint file=20
>=20
> <bean id=3D"jms" class=3D"org.apache.camel.component.jms.JmsComponent">
> 		<property name=3D"connectionFactory">
> 			<bean =
class=3D"org.apache.activemq.ActiveMQSslConnectionFactory">
> 				  <property name=3D"trustStore" =
value=3D"C:/client.ts" />
> 				  <property name=3D"trustStorePassword" =
value=3D"abc" />
> 				  <property name=3D"keyStore" =
value=3D"C:/broker.ks" />
> 				  <property name=3D"keyStorePassword" =
value=3D"password" />
> 				  <property name=3D"brokerURL"
> value=3D"nio+ssl://localhost:61617?trace=3Dtrue" />
> 				  <property name=3D"userName" =
value=3D"smx" />=20
> 				  <property name=3D"password" =
value=3D"smx" />
> 			</bean>
> 		</property>
> 	</bean>
>=20
> along with it i have configured activemq.xml with following entries=20
>=20
> 	<sslContext>
> 			<sslContext=20
> 			  keyStore=3D"C:/broker.ks" =
keyStorePassword=3D"abc"=20
> 			  trustStore=3D"C:/client.ts" =
trustStorePassword=3D"abc" />
> 		</sslContext>
>        <transportConnectors>
>=20
> 			  <transportConnector name=3D"openwire"
> =
uri=3D"nio+ssl://localhost:61617?trace=3Dtrue&amp;needClientAuth=3Dtrue&am=
p;maximumConnections=3D1000&amp;wireFormat.maxFrameSize=3D104857600"/>
>        </transportConnectors>
>=20
>=20
> the broker is started sucessfully and started publishing on=20
> Publishing: nio+ssl://127.0.0.1:61617 for broker transport URI:
> =
nio+ssl://127.0.0.1:61617?trace=3Dtrue&needClientAuth=3Dtrue&maximumConnec=
tions=3D1000&wireFormat.maxFrameSize=3D104857600
>=20
> but somehow connections are created on tcp=20
> and being displayed like following=20
>=20
> tcp://127.0.0.1:49881=09
>=20
>=20
> can someone guide us how to make the connection as ssl as well=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> --
> View this message in context: =
http://activemq.2283324.n4.nabble.com/Securing-JMS-queque-tp4684509.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.