Hello Richard,

Well, the documentation has so far assumed that the user understands the
concept of different URL schemes and different protocols (like http://,
ftp:// or ormi://) and understand that they are not the same thing and
use different ports, but that you normally don't need to specify the
port unless you change something. We will somehow explain this in the
FAQ to avoid more confusion about this.

However, there is a reason why there is no admin port mentioned in the
documentation. It's simply because no special admin port exists. The
admin traffic use the regular ormi port.

Regards,
Karl Avedal

Richard Landon wrote:

> Wow, thanks. Perhaps, I'm lame, but that was not obvious in the
> documentation?
>
>
>      -----Original Message-----
>      From: Jason von Nieda [mailto:[EMAIL PROTECTED]]
>      Sent: Friday, September 08, 2000 4:09 PM
>      To: Orion-Interest
>      Subject: Re: Orion Difficulities....
>      Remove the port (8080) from your ormi URL. The admin port is
>      different from the web port and is configuredin
>      orion/config/rmi.xml
>
>           ----- Original Message -----
>           From:Richard Landon
>           To: Orion-Interest
>           Sent: Friday, September 08, 2000 4:51 PM
>           Subject: Orion Difficulities....
>           I am have some major problems with the learning
>           curve with this server. I have previously used
>           (succesfully)(1) J2EE RI(2) Web Logic 5.1(3)
>           IAS(4) Silverstream(5) Gemstone/JI start the
>           server as follows:[C:/orion] java -jar orion.jar
>           Orion/1.2.9 initializedI take this to mean the
>           server is running.I then do a
>           http://blazer.youbet.com:8080 and see the web
>           page.(I modified the port since I'm already
>           running Apache on port 80).For example, according
>           to the documentation, to shutdown the
>           server:[C:/orion] java -jar admin.jar
>           ormi://blazer.youbet.com:8080 admin root -shutdown
>
>           Error: javax.naming.NamingException: Lookup error:
>           java.io.StreamCorruptedException: Caught
>           EOFException while reading t
>           he stream header; nested exception is:
>                   java.io.StreamCorruptedException: Caught
>           EOFException while reading the stream header
>           So after two-days, it is not possible to figure
>           out how to shutdown the server.I'll try a little
>           bit long, then remove this server from our vendor
>           list.
>


Reply via email to