07-21-04 01:57 AM
I have setup a Cluster using Network Deploy version of Websphere. The
cluster is up and I followed the instructions per IBM on how to setup the
nodes(portal install, DB, etc) and add them to the cluster.
Everything looks like it's running properly but when I try to hit the portal
on any of the nodes I get :
[7/20/04 21:01:50:601 CDT] 6ee657c3 ServletReques E SRVE0079E: Servlet h
ost
not found
[7/20/04 21:01:50:617 CDT] 6ee657c3 OSEListenerDi E PLGN0021E: Servlet
Request Processor Exception: Virtual Host/WebGroup Not Found : The host
<MYHOSTNAME> on port 9081 has not been defined
I replaced the actual host name with <MYHOSTNAME> to protect the guilty
parties involved, but you get the picture. I know that the transport on 9081
is started because earlier in the log is:
[7/20/04 20:58:14:419 CDT] d0757e6 HttpTransport A SRVE0171I: Transport
http is listening on port 9,081.
[7/20/04 20:58:14:434 CDT] d0757e6 HttpTransport A SRVE0171I: Transport
http is listening on port 9,092.
[7/20/04 20:58:14:450 CDT] d0757e6 HttpTransport A SRVE0171I: Transport
https is listening on port 9,045.
[7/20/04 20:58:14:450 CDT] d0757e6 SchedulerServ I SCHD0031I: The Sched
uler
Service is starting.
[7/20/04 20:58:14:450 CDT] d0757e6 SchedulerServ I SCHD0001I: The Sched
uler
Service has started.
[7/20/04 20:58:14:512 CDT] d0757e6 RMIConnectorC A ADMC0026I: RMI Conne
ctor
available at port 9811
[7/20/04 20:58:14:638 CDT] d0757e6 WsServer A WSVR0001I: Server
WebSphere_Portal open for e-business
[7/20/04 20:58:15:374 CDT] 612197df DiscoveryMBea I ADMD0023I: Process
discovered (name: nodeagent, type: NodeAgent, pid: 2892)
[7/20/04 20:59:06:941 CDT] 717bd7dc WCPLogger A
com.ibm.wcm.pcm.transport.JavaTransport <init> JavaTransport Created
Does anyone know why this is happening and how I can correct it?
The one thing that I'm not sure about is the install instructions mentioned
setting up a transport on the Deployment Manager machine for the same
transport as the primary node. This won't work for me because for reasons
beyond my control I had to install the Deployment Manager on the same
machine as the primary node, so they can't both use the same port.
[ Post a follow-up to this message ]
|