The only thing that I can think of is hostname lookups - doesnt your dialup
handler have a way of monitoring what prompts the dialup?
As for the DTDs they are local resources (ie loaded locally from the jar,
not from the URL, even if you use validation) so that shouldnt
be the problem. Check if you use hostnames anywhere (as opposed to IPs) and
if that leads to the dialup.

/Magnus Stenman, the Orion team

----- Original Message -----
From: "Robert Hargreaves" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 02, 2000 11:49 AM
Subject: RE: Disabling everthing but EJB


> I've managed to download and reference locally every dtd in the xml files.
> The only one I can't do anything with is in orion-ejb-jar.xml in my
> <working_dir>\orion\ dir.
> Every time I change the reference of the dtd in this xml, the Orion
> deployment process overwrites it with the original
> http://www.orionserver.com/dtds/orion-ejb-jar.dtd reference. Not sure what
> else I can do now.
>
> Regards,
>
> Robert Hargreaves
>
> -----Original Message-----
> From: Mike Fontenot [mailto:[EMAIL PROTECTED]]
> Sent: 01 March 2000 16:38
> To: Robert Hargreaves
> Subject: RE: Disabling everthing but EJB
>
>
> The xml files themselves have a reference to the Sun website where the DTD
> for the xml document actually lives, and to the OrionServer specific
config
> files.  Take a look at EACH header in all of the orion xml documents. For
> example, Server.xml has this line:
>
> <!DOCTYPE application-server PUBLIC "Orion Application Server Config"
> "http://www.orionserver.com/dtds/application-server.dtd">
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Robert
> > Hargreaves
> > Sent: Wednesday, March 01, 2000 8:41 AM
> > To: Orion-Interest
> > Subject: RE: Disabling everthing but EJB
> >
> >
> > Rich,
> >
> > I suspected as much. We're using NT SBServer and Nt workstations. I've
> > turned off the Winsock Proxy service on the Proxy server console
> > the problem
> > has gone away. Trouble is we can't use our FTP software now.
> >
> > After talking to out sys admin people, they said Orion probably
> > has a ref in
> > its config files to an external IP address and therfore our NT server
was
> > dialling out to resolve a name (a DNS lookup).
> > Trouble is finding this external ref in the config xml files. Any
> > suggestions?
> >

Reply via email to