Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 88157 invoked from network); 17 Apr 2008 18:46:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Apr 2008 18:46:37 -0000 Received: (qmail 89795 invoked by uid 500); 17 Apr 2008 18:46:36 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 89749 invoked by uid 500); 17 Apr 2008 18:46:36 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 89722 invoked by uid 99); 17 Apr 2008 18:46:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2008 11:46:36 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2008 18:45:44 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JmZ7U-0003us-OT for dev@synapse.apache.org; Thu, 17 Apr 2008 11:46:04 -0700 Message-ID: <16750974.post@talk.nabble.com> Date: Thu, 17 Apr 2008 11:46:04 -0700 (PDT) From: cmurali To: dev@synapse.apache.org Subject: Re: Define listening IP for synapse In-Reply-To: <16722528.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: chakravarthym@sddc.army.mil References: <16722528.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org I am using Synapse 1.1. Here is the cut and paste of the log. Per this log it only displays the port number and not the IP address. So it binds to all IPs. Yes we are using Solaris 9 as shown below. Do you think moving to Synapse 1.1.1 solves this issue? As the software is in QA, I do not want to upgrade the version. Is there any way I can make this work in Synapse 1.1? Thanks, Muralidaran Chakravarthy ================ callisto% uname -a SunOS callisto 5.9 Generic_122300-13 sun4u sparc SUNW,Sun-Fire-280R callisto% ============== 5555 [WrapperSimpleAppMain] INFO SynapseInitializationModule (SynapseInitiali zationModule.java:118) - Synapse initialized successfully...! 5559 [WrapperSimpleAppMain] INFO HttpCoreNIOSender (HttpCoreNIOSender.java:10 5) - HTTP Sender starting 5580 [WrapperSimpleAppMain] DEBUG HttpCoreNIOListener (HttpCoreNIOListener.jav a:225) - Starting Listener... 5583 [WrapperSimpleAppMain] INFO HttpCoreNIOListener (HttpCoreNIOListener.jav a:239) - HTTP Listener starting on port : 6673 5583 [WrapperSimpleAppMain] INFO ServerManager (ServerManager.java:98) - Star ting transport http on port 6673 ============== cmurali wrote: > > Hi asankha > > Thanks for your reply. I added the following to axis2.xml. It still binds > to all the IP addresses as shown by the netstat command. > > locked="false">wlserver-qa > 6672 > > callisto% netstat -na | grep -i listen | grep 667 > *.6672 *.* 0 0 49152 0 LISTEN > > Please see Apache web server process attached to only one IP. Syanpse, as > shown below, should bind to only one IP address indicated in axis2.xml. > but it is not. > > callisto% netstat -na | grep -i listen | grep 808 > 192.168.0.18.8085 *.* 0 0 49152 0 LISTEN > 192.168.0.17.8081 *.* 0 0 49152 0 LISTEN > > > asankha wrote: > > Hi Muralidaran > > In your axis2.xml you can configure the address using the "bind-address" > parameter > > e.g. > > class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener"> > 8080 > true > hostname or IP > address > > > > If you frontend the Synapse server with a [load balancing] Apache etc. you > can use the WSDLEPRPrefix parameter to tell Synapse http/s transports how > they should prefix the service addresses for access from outside > > In future, can you post these types of questions to Synapse-user list, for > the benefit of others as well.. > > cheers > asankha > > Chakravarthy, Muralidaran (contractor) wrote: > > Hi Asankha > > I want to Define listening IP for synapse because we have more than one > IP > for the given box and we want to run multiple synapse servers for > different > environment. I see that in the wrapper.conf file we have defined a lot of > properties out of which the port is one (please see below) > > wrapper.java.additional.8=-Dport=6672 > > Please let me know what property should I use to set the listen IP? > > Thanks, > Muralidaran Chakravarthy > > > -- View this message in context: http://www.nabble.com/Define-listening-IP-for-synapse-tp16722528p16750974.html Sent from the Synapse - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org For additional commands, e-mail: dev-help@synapse.apache.org