[
https://issues.apache.org/jira/browse/STONEHENGE-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Dewey updated STONEHENGE-90:
Attachment: MetroDeploy_Troubleshoot_Walkthru.doc
Vineet and Ranjitha,
Joby emailed me and said
There seems to be a conflict in the service names between METRO and WSAS from
the DB.
Metro uses JAVA_CLIENT and JAVA_BS, while WSAS uses JAVA_BS and JAVA_OPS.
What should we do here? Should we uses METRO_CLIENT/BS and WSAS_BS/OPS, or is
it first come-first serve? Who gets JAVA_?
-Ben Dewey
-- Forwarded message --
From: Vineet ghatge
Date: Mon, Aug 10, 2009 at 9:57 PM
Subject: Re: Metro Contribution
To: ben.de...@26ny.com
Hi Ben,
I tried the instructions given by you and ming.However I tried changing the
port number from "8080" to "8090",this worked for all the URL
Hi Ben,
Just so you know, I need to help out with ODG for part of the day today to fix
a bug. As we all heard from Jay at the last company meeting, they're going
live today.
Joby
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 webservice
is NOT working.
Also, check your glassfish/autodeploy directory for the war files. This will
tell you if there was a failure in the build. I
Hi, Avantika
I've tested this patch. Everything works fine. Well done.
Here is one more question: if the address of config service was changed from
page, is the config service used in BSL also be updated dynamically?
On Sat, Aug 8, 2009 at 6:02 AM, Avantika Agrawal wrote:
> Hi Ming,
>
> Sorry a
