From stonehenge-dev-return-1648-apmail-incubator-stonehenge-dev-archive=incubator.apache.org@incubator.apache.org Mon Aug 10 15:20:41 2009 Return-Path: Delivered-To: apmail-incubator-stonehenge-dev-archive@minotaur.apache.org Received: (qmail 59455 invoked from network); 10 Aug 2009 15:20:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Aug 2009 15:20:41 -0000 Received: (qmail 52706 invoked by uid 500); 10 Aug 2009 15:20:48 -0000 Delivered-To: apmail-incubator-stonehenge-dev-archive@incubator.apache.org Received: (qmail 52665 invoked by uid 500); 10 Aug 2009 15:20:48 -0000 Mailing-List: contact stonehenge-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stonehenge-dev@incubator.apache.org Delivered-To: mailing list stonehenge-dev@incubator.apache.org Received: (qmail 52655 invoked by uid 99); 10 Aug 2009 15:20:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 15:20:48 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [216.82.250.3] (HELO mail75.messagelabs.com) (216.82.250.3) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 15:20:39 +0000 X-VirusChecked: Checked X-Env-Sender: Ben.Dewey@26ny.com X-Msg-Ref: server-12.tower-75.messagelabs.com!1249917617!12538996!1 X-StarScan-Version: 6.1.3; banners=-,-,- X-Originating-IP: [63.100.53.109] Received: (qmail 23543 invoked from network); 10 Aug 2009 15:20:18 -0000 Received: from mailserver.citigatehudson.com (HELO 26NY-ES4.26ny.local) (63.100.53.109) by server-12.tower-75.messagelabs.com with AES128-SHA encrypted SMTP; 10 Aug 2009 15:20:18 -0000 Received: from 26NY-ES3.26ny.local ([fe80::d50b:ddec:2dc0:4ee5]) by 26NY-ES4.26ny.local ([fe80::c4e7:6f5c:7beb:8eae%11]) with mapi; Mon, 10 Aug 2009 11:20:15 -0400 From: Ben Dewey To: "stonehenge-dev@incubator.apache.org" Date: Mon, 10 Aug 2009 11:17:29 -0400 Subject: RE: Metro Contribution Thread-Topic: Metro Contribution Thread-Index: AcoZbUUNYIUX3adURj2pLHhdC1e41QAYGgHd Message-ID: <0797E98FF7451041939CF35232C75B065604C5C750@26NY-ES3.26ny.local> References: <0797E98FF7451041939CF35232C75B0656050D7DA5@26NY-ES3.26ny.local>,<108b2bf40908092046j3df5b5ebmbf758b2ca17de8ad@mail.gmail.com> In-Reply-To: <108b2bf40908092046j3df5b5ebmbf758b2ca17de8ad@mail.gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Ranjitha, I don't see anyting attached, you can send it to me directly. Essentially the 503 error means that the server IS running, but that webser= vice is NOT working. Also, check your glassfish/autodeploy directory for the war files. This wi= ll tell you if there was a failure in the build. If the war files are pres= ent, then you'll have to track down the errors in you logs. -Ben ________________________________________ From: Ranjitha V [ranjitha123@gmail.com] Sent: Sunday, August 09, 2009 11:46 PM To: stonehenge-dev@incubator.apache.org Subject: Re: Metro Contribution Hello all, Well, I did make sure that my glassfish server was running before I verifie= d deployment. I was successful in deployment of config service. The only thing not workin= g right now is OP. I noted the contents of my server.log file as Ming had mentioned but I foun= d that no new error message corresponding to the failure of OP had been added. I have shortened the ser= ver.log file and added only important events and sent it as an attachment. Do let me know if there is something I am missing here. -Ranjitha On Mon, Aug 10, 2009 at 3:04 AM, Ben Dewey > wrote: It should be noted that the wampserver for PHP uses 8080. Thats why in some= places, and in my environment, the default glassfish port of 8080 is chang= ed to use 8090 so it doesn't conflict with php. For consistency i think the doc should all use 8090 and provide instruction= s on changing the glassfish port number. Thoughts? -Ben Dewey -----Original Message----- Date: Sunday, August 09, 2009 9:26:05 am To: stonehenge-dev@incubator.apache.org From: "Ming Jin" > Subject: Re: Metro Contribution Hi, Vineet It's a bug in the manual.doc, the port should be 8080. We'll correct that. The addresses in manual.doc use the specific port GlassFish uses for the HTTP connection. By default, Glassfish uses 8080 as its HTTP port for domain1, so here you should use 8080 rather than 8090 for the verification. Furthermore, to any URL related to Glassfish Server, port 8080 should be th= e right one(if you didn't change the default configuration in Glassfish). On Sun, Aug 9, 2009 at 12:22 AM, Vineet ghatge > wrote: > Hi Ben, > > In the manual documents/manual.doc,Under "deployment" > > The last step named "verify deployment" there are the following step > ? Verify Deployment > a. BS > Open browser with > http://localhost:8090/business_service/TradeServiceWsas?wsdl > b. OP > ? Secure > Open browser with > http://localhost:8090/order_processor/OrderProcessorSec?wsdl > ? Non-Secure > Open browser with > http://localhost:8090/order_processor/OrderProcessor?wsdl > c. Config Service >