• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
More dumb deployment questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More dumb deployment questions


  • Subject: More dumb deployment questions
  • From: "Andrew R. Kinnie" <email@hidden>
  • Date: Tue, 22 Jun 2010 19:03:46 -0400

So I made the terrible mistake of trying to deploy the new version of my site, complete with migrations and D2W and it failed to do anything (not quite true, it actually runs but immediately threw a JDBC exception).  I then tried to redeploy the old version while I figured this out.  (basically, I re-named the old .woa then renamed it back after the failed deploy, then bounced the app in Monitor.)

The old app runs on the server.  She can click the link to load it, run it, do what she needs to do, etc.  However, the outside world can't access it.  No configuration files whatsoever were changed.

Anyone have any ideas what could cause the app to run and be usable on the server, by a user of the server, but not by the outside world?  With no changes to the apache files or anything else?

Thanks.

Andrew
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: More dumb deployment questions
      • From: Chuck Hill <email@hidden>
  • Prev by Date: Re: Avoiding java.lang.OutOfMemoryError: Java heap space
  • Next by Date: Re: More dumb deployment questions
  • Previous by thread: Re: Avoiding java.lang.OutOfMemoryError: Java heap space
  • Next by thread: Re: More dumb deployment questions
  • Index(es):
    • Date
    • Thread