Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: 
 <1428697681.2849174.251879073.4D4B7FB5@webmail.messagingengine.com>
From: Upayavira <uv@odoko.co.uk>
To: solr-user@lucene.apache.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
In-Reply-To: <1428675482920-4198938.post@n3.nabble.com>
References: <1428675482920-4198938.post@n3.nabble.com>
Subject: Re: Negatives of binding multiple ports in jetty.xml?
Date: Fri, 10 Apr 2015 21:28:01 +0100

Why do you want to do this?

Bear in mind that over time, the fact that Solr uses Jetty will become
more and more of an implementation detail, and not something you are
expected to interact with, so it might work, but that doesn=E2=80=99t mean =
it
will work with all future versions.

Upayavira

On Fri, Apr 10, 2015, at 03:18 PM, eirik wrote:
> Hi,
>=20
> I have not experienced any negatives with having more than 1
> "addConnector"
> (using bio.SocketConnector) specified in jetty.xml. e.g 8983, 8984, 8985
> etc
> Without knowing to much of whats going on in the background I wanted to
> ask
> here if anyone know about any problems this might cause?=20
>=20
> Many thanks!
> Eirik.
>=20
>=20
>=20
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Negatives-of-binding-multiple-ports-in=
-jetty-xml-tp4198938.html
> Sent from the Solr - User mailing list archive at Nabble.com.