Glad the connector issue worked out for you. As far as the 404s, I can't
say I've seen that much. Maybe you could enable connector logging inside
the JRun directive in httpd.conf. Then trace the requests just enough until
you get a 404 like this before turning off logging. The connector logging
> I've seen two cases resolved where this problem occurred, security was ok, &
> the user could telnet to the port and connect. Those two were resolved by
> finding misconfigurations in one of the two host config files (/etc/hosts/,
> /etc/sysconfig/network).
OK, you win. ;) There was a misco
I've seen two cases resolved where this problem occurred, security was ok, &
the user could telnet to the port and connect. Those two were resolved by
finding misconfigurations in one of the two host config files (/etc/hosts/,
/etc/sysconfig/network).
> -Original Message-
> From: Tim Blai
Nope, all network settings are OK.
Nothing else is listening on the JNDI port - I've even tried changing it
in the runtime/servers/default/SERVER-INF/jndi.properties and I still
get the same result.
Going through the "possible causes" listed when I try running the
connector:
> o Server not runni
lk
> Subject: RE: CFMX connector issues
>
> Is anything else listening on port 2901?
>
> Is the firewall blocking connections to that port? You might want to test
> this by running lokkit, temporarily setting firewall to disabled, then
> start
> CF again.
>
> > -
Is anything else listening on port 2901?
Is the firewall blocking connections to that port? You might want to test
this by running lokkit, temporarily setting firewall to disabled, then start
CF again.
> -Original Message-
> From: Tim Blair [mailto:[EMAIL PROTECTED]
> This morning I ha
6 matches
Mail list logo
