• 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
Developing without direct connect and using a PPP connection - solution to "app not found" problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Developing without direct connect and using a PPP connection - solution to "app not found" problem


  • Subject: Developing without direct connect and using a PPP connection - solution to "app not found" problem
  • From: Miguel Arroz <email@hidden>
  • Date: Mon, 15 Jan 2007 22:24:20 +0000

Hi!

I don't know if any of you had already saw this irritating problem. I have seen it several times, and today I found a solution, so I'm sharing it with you. if you want, blog it on your WO blogs, I don't have one yet! :)

The problem is, when you are developing without direct connect (ie, when you are developing using apache to handle the requests), and your mac is connected to some sort of PPP line (56k model, GPRS, 3G, etc), when you run your application you see the "Instance not found" error on the browser. Even restarting apache wont solve it. I rarely find myself in this situation, as I usually use ethernet or wifi connections. But today I was many hours working in a place without internet connections, so I had to use GPRS to browse some online docs. And as I saw this problem again, I decided to fix it for good.

My first theory was that something related to multicast was going the wrong way (ie, to the PPP line and not for the loopback interface). After some investigation, I found out that the default WOTaskd configuration is to NOT use multicast, so that was not the problem.

The real problem is the fact that the application was binding to the wrong interface. When the PPP connection is active, the default route becomes the ppp interface. For some reason, WO apps bind to that port, and for some other reason, stuff sent to it apparently does not come back to the lookback interface. Well, I don't know exactly what is the problem an the network level, but it's there somewhere.

But the important thing is the solution! :) You need to force the app to bind to the loopback address, 127.0.0.1. To do that, just go to Eclipse run panel (or the equivalent in xCode) and add a new argument to the application launching command line (in the WO tab). Add "-WOHost" parameter with "127.0.0.1" argument. This way, the app will bind to the localhost, and will be able to communicate with WOTaskD and Apache Adaptors.

  Hope this helps anyone! :)

  Yours

Miguel Arroz

"We have no sympathy for the lost souls
We've chosen the path of disgrace
We give this life to our children
And teach them to hate this place" -- Apocalyptica, Life Burns!

Miguel Arroz
http://www.ipragma.com


_______________________________________________ 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
  • Prev by Date: Re: Servlets and FrontBase
  • Next by Date: NSUndoManager beginUndoGrouping and endUndoGrouping
  • Previous by thread: re: SSDD Tomcat - JDBC error
  • Next by thread: NSUndoManager beginUndoGrouping and endUndoGrouping
  • Index(es):
    • Date
    • Thread