Hi Mike,
that doesn't sounds to me like an adaptor problem.
I think there must be something mixed up in the configuration.
What do yo get as answer from http://localhost:1085 (or
http://127.0.0.1:1085 or http://servername:1085) ?
Stefan
Am 09.11.10 21:44, schrieb Michael Gargano:
I'm newish to WO deployment. I've deployed a few apps on an XP
machine (internal network access only).
Here's what I did...
1) Brand new W2K3 install on a virtual machine given to me by our IT
staff (has internal private IP and external NATed IP, both have
forward and reverse lookups)
2) Installed WO frameworks with WOInstaller.jar into C:\Apple
3) Setup ENV vars
4) installed Apache 2.2
5) copied mod_WebObjects.so from mdimension site into modules directory
6) configured apache (added WO mod, included WO conf file, changed
server name, changed doc root, set allow all on doc root, configured
SSL through mod_ssl, configured webobjects.conf)
7) copied app over (split install, embedded frameworks)
8) started apache (no errors)
9) turned up wotaskd (started fine)
10) turned up JavaMonitor (starts fine)
11) configured my app through JavaMonitor (app starts fine no errors
in log)
after this I can't get to the app at all unless I turn on
DirectConnect and access it that way. I also can only access
JavaMonitor through DirectConnect, so it seems as if the adaptor isn't
working at all.
Occasionally I'll see this error message in my JavaMonitor terminal...
[2010-11-8 16:40:2 EST] <WorkerThread14> <WOWorkerThread id=14
socket=Socket[addr=/127.0.0.1,port=4709,localport=56789]> Exception
while sending response: java.net.SocketException: Software caused
connection abort: socket write error
I've played with a whole bunch of settings (tried disabling ssl,
accessing the app with the internal name, external name, localhost,
127.0.0.1, and internal and external IPs) and nothing seems to do it.
I also compared it with my working XP deployments and everything
seems to match up. If you need me to try something to get more
information please let me know.
Thanks again.
-Mike
On Nov 9, 2010, at 3:23 PM, Stefan Klein wrote:
Hi Mike,
can you explain your issue with the Apache Adaptor.
There are some people (2 I know :-D ) who use it on deployment systems.
If there is anybody other using the Apache under Windows, can you
tell us your experience ?
Stefan
Am 09.11.10 17:35, schrieb Michael Gargano:
Okay,
So, I've given up on getting my app deployed to W2K3. Direct Connect
works fine, but there's definitely an issue with the Apache adaptor. (*sigh*)
So, I moved on to Tomcat 6 since I need this app deployed by tomorrow the
latest. I changed my build settings for servlet deployment, and told it to
auto generate the web.xml. But when I deploy to tomcat on a windows box (from
my mac) I receive this error...
Servlet WOServletAdaptor is not available
So I checked that the JavaWOJSPServlet_client.jar is in the WEB-INF/lib
directory and I even tried adding it to the classpath of the web.xml without
success.
Do the variables WOROOT, LOCALROOT, and WOINSTALLROOT even do anything since
the frameworks are all bundled in the war?
I don't think I've ever gotten my war to deploy. I must be missing something.
Thanks.
-Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/stefan.klein%40buero-sde.de
This email sent [email protected]
<ATT00001..txt>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
