This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi,
When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
But sometimes on our clusters we have an application server trying to use the same session connection as another server.
For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
Any ideas on why this happens and what can be done to prevent it?
Thanks,
Dave Bone
I have the same problem on occassion, but typically I can attribute it to how I started our cluster by accidentally clicking 'Start' instead of 'Ripplestart'.
Have you been able to confirm 'how' the cluster is started?
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
>
> But sometimes on our clusters we have an application server trying to use the same session connection as another server.
>
> For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
>
> This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
>
> Any ideas on why this happens and what can be done to prevent it?
>
> Thanks,
> Dave Bone
>
Hi,
Ripplestart causes it also.
To fix the issue I have to make idle and stop the application servers using the same connection. Wait 500 seconds until that session entry in maxsessions times out. So the session for Maximo is removed from maxsessions and then do a Start on one server. Once it is done then I start the next server.
Dave Bone
--- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@...> wrote:
>
> I have the same problem on occassion, but typically I can attribute it to how I started our cluster by accidentally clicking 'Start' instead of 'Ripplestart'.
>
> Have you been able to confirm 'how' the cluster is started?
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
> >
> > But sometimes on our clusters we have an application server trying to use the same session connection as another server.
> >
> > For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
> >
> > This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
> >
> > Any ideas on why this happens and what can be done to prevent it?
> >
> > Thanks,
> > Dave Bone
> >
>
Dave,
Are these servers in the same custer? What does your environment look like including versions? Default names will pull from Maximo.properties.
Jason
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> Ripplestart causes it also.
>
> To fix the issue I have to make idle and stop the application servers using the same connection. Wait 500 seconds until that session entry in maxsessions times out. So the session for Maximo is removed from maxsessions and then do a Start on one server. Once it is done then I start the next server.
>
> Dave Bone
>
> --- In MAXIMO@yahoogroups.com, "Jason Verly" <jason.verly@> wrote:
> >
> > I have the same problem on occassion, but typically I can attribute it to how I started our cluster by accidentally clicking 'Start' instead of 'Ripplestart'.
> >
> > Have you been able to confirm 'how' the cluster is started?
> >
> > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > >
> > > Hi,
> > >
> > > When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
> > >
> > > But sometimes on our clusters we have an application server trying to use the same session connection as another server.
> > >
> > > For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
> > >
> > > This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
> > >
> > > Any ideas on why this happens and what can be done to prevent it?
> > >
> > > Thanks,
> > > Dave Bone
> > >
> >
>
Dave,
I'd definitely take a second look at your cluster setup. As far as starting the cluster I have not seen any difference between the ways we've started them. I usually start the cluster one of two ways, ticking the box next to the cluster and then selecting Start and from the Application servers link ticking the box next to each cluster member and clicking start (this will start the cluster).
WebSphere 7.1.1.9
Maximo 7.5.0.2
JR
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
>
> But sometimes on our clusters we have an application server trying to use the same session connection as another server.
>
> For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
>
> This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
>
> Any ideas on why this happens and what can be done to prevent it?
>
> Thanks,
> Dave Bone
>
Hi,
I have four VM Ware servers each running WebSphere 6.1 and Maximo 7.1.1.6.
Three are UI servers and on those I have a cluster of three application servers.
There is one report server running a cluster of four application servers. This server seems to have the issue more than the application servers.
All connect to one database server.
Naming of the UI application servers is MXServer, NODEUI01 and NODEUI02.
On the report server MXServerRIP, NODERIP01, NODERIP02, NODERIP03.
Cluster names are MAXIMOUICLUSTER and MAXRIPCLUSTER.
If I start the application servers one at a time I have found that I can avoid the issue by starting them in a certain order. On the report server I can start NODERIP01 first and it will come up as MXServerRIP. Then start the MXServer and it comes up as MXServerRIPc1. Then NODERIP02 and it comes up as MXServerRIPc2 and last NODERIP03 which comes up as MXServerRIPc3.
If I don't follow that order then they start using the other connections already in use.
I'll try using the JVM Generic argument to assign distinct names to the application servers. I only have to restart the application servers to do that.
When I upgrade to 7.5 I'll be doing a clean install so maybe this will go away.
Dave Bone
--- In MAXIMO@yahoogroups.com, "ecirnhoj@..." <ecirnhoj@...> wrote:
>
> Dave,
>
> I'd definitely take a second look at your cluster setup. As far as starting the cluster I have not seen any difference between the ways we've started them. I usually start the cluster one of two ways, ticking the box next to the cluster and then selecting Start and from the Application servers link ticking the box next to each cluster member and clicking start (this will start the cluster).
>
> WebSphere 7.1.1.9
> Maximo 7.5.0.2
>
> JR
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
> >
> > But sometimes on our clusters we have an application server trying to use the same session connection as another server.
> >
> > For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
> >
> > This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
> >
> > Any ideas on why this happens and what can be done to prevent it?
> >
> > Thanks,
> > Dave Bone
> >
>
Hi, Do you have the RMIRegistry server configured & running for your cluster ?
you don't mention it in your list.
--- In MAXIMO@yahoogroups.com, "in2data" <in2data@...> wrote:
>
> Hi,
>
> I have four VM Ware servers each running WebSphere 6.1 and Maximo 7.1.1.6.
>
> Three are UI servers and on those I have a cluster of three application servers.
>
> There is one report server running a cluster of four application servers. This server seems to have the issue more than the application servers.
>
> All connect to one database server.
>
> Naming of the UI application servers is MXServer, NODEUI01 and NODEUI02.
>
> On the report server MXServerRIP, NODERIP01, NODERIP02, NODERIP03.
>
> Cluster names are MAXIMOUICLUSTER and MAXRIPCLUSTER.
>
> If I start the application servers one at a time I have found that I can avoid the issue by starting them in a certain order. On the report server I can start NODERIP01 first and it will come up as MXServerRIP. Then start the MXServer and it comes up as MXServerRIPc1. Then NODERIP02 and it comes up as MXServerRIPc2 and last NODERIP03 which comes up as MXServerRIPc3.
>
> If I don't follow that order then they start using the other connections already in use.
>
> I'll try using the JVM Generic argument to assign distinct names to the application servers. I only have to restart the application servers to do that.
>
>
> When I upgrade to 7.5 I'll be doing a clean install so maybe this will go away.
>
> Dave Bone
>
>
>
> --- In MAXIMO@yahoogroups.com, "ecirnhoj@" <ecirnhoj@> wrote:
> >
> > Dave,
> >
> > I'd definitely take a second look at your cluster setup. As far as starting the cluster I have not seen any difference between the ways we've started them. I usually start the cluster one of two ways, ticking the box next to the cluster and then selecting Start and from the Application servers link ticking the box next to each cluster member and clicking start (this will start the cluster).
> >
> > WebSphere 7.1.1.9
> > Maximo 7.5.0.2
> >
> > JR
> >
> > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > >
> > > Hi,
> > >
> > > When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
> > >
> > > But sometimes on our clusters we have an application server trying to use the same session connection as another server.
> > >
> > > For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
> > >
> > > This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
> > >
> > > Any ideas on why this happens and what can be done to prevent it?
> > >
> > > Thanks,
> > > Dave Bone
> > >
> >
>
Hi,
No it's not set up. I'm working on that now.
Using the -Dmxe.name=servername in the JVM Generic arguments appears to have resolved the issue.After setting that up on my sandbox and report servers I could not get either to "share" sessions in maxsessions. I'll know more after this weekend when they reboot the servers.
Setting up the RMI should be done anyway.
It appears the RMI set up just makes certain that the RMI registry is successfully started before any application servers. But does it still create a single point of failure since the RMI server could stop and that kills the RMI registry?
I have not noticed the RMI registry not starting with the first application server but I don't check the logs every time the servers are restarted.
Dave Bone
--- In MAXIMO@yahoogroups.com, "peter.males" <peter.males@...> wrote:
>
> Hi, Do you have the RMIRegistry server configured & running for your cluster ?
> you don't mention it in your list.
>
> --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> >
> > Hi,
> >
> > I have four VM Ware servers each running WebSphere 6.1 and Maximo 7.1.1.6.
> >
> > Three are UI servers and on those I have a cluster of three application servers.
> >
> > There is one report server running a cluster of four application servers. This server seems to have the issue more than the application servers.
> >
> > All connect to one database server.
> >
> > Naming of the UI application servers is MXServer, NODEUI01 and NODEUI02.
> >
> > On the report server MXServerRIP, NODERIP01, NODERIP02, NODERIP03.
> >
> > Cluster names are MAXIMOUICLUSTER and MAXRIPCLUSTER.
> >
> > If I start the application servers one at a time I have found that I can avoid the issue by starting them in a certain order. On the report server I can start NODERIP01 first and it will come up as MXServerRIP. Then start the MXServer and it comes up as MXServerRIPc1. Then NODERIP02 and it comes up as MXServerRIPc2 and last NODERIP03 which comes up as MXServerRIPc3.
> >
> > If I don't follow that order then they start using the other connections already in use.
> >
> > I'll try using the JVM Generic argument to assign distinct names to the application servers. I only have to restart the application servers to do that.
> >
> >
> > When I upgrade to 7.5 I'll be doing a clean install so maybe this will go away.
> >
> > Dave Bone
> >
> >
> >
> > --- In MAXIMO@yahoogroups.com, "ecirnhoj@" <ecirnhoj@> wrote:
> > >
> > > Dave,
> > >
> > > I'd definitely take a second look at your cluster setup. As far as starting the cluster I have not seen any difference between the ways we've started them. I usually start the cluster one of two ways, ticking the box next to the cluster and then selecting Start and from the Application servers link ticking the box next to each cluster member and clicking start (this will start the cluster).
> > >
> > > WebSphere 7.1.1.9
> > > Maximo 7.5.0.2
> > >
> > > JR
> > >
> > > --- In MAXIMO@yahoogroups.com, "in2data" <in2data@> wrote:
> > > >
> > > > Hi,
> > > >
> > > > When an application server starts in a cluster it gets a server name from WebSphere(??) and then an entry is made in the Maximo maxsession table for the maximo user session connection. Tha connection has the servername and logindatetime.
> > > >
> > > > But sometimes on our clusters we have an application server trying to use the same session connection as another server.
> > > >
> > > > For instance I can start server1:9080 and it will show in maxsession the connection as servername MXServerRIP. If I then start server1:9081 it will sometimes show the connection as MXServerRIP with an updated logindatetime. When this happens then server1:9081 server is not actually working. If you try to login to that server in Maximo you just get a white screen. Maximo shows that the user logged into that server but the Star Center screen never displays.
> > > >
> > > > This happens when we do a restart of the servers. If I start the application servers one at a time then they all make separate connections.
> > > >
> > > > Any ideas on why this happens and what can be done to prevent it?
> > > >
> > > > Thanks,
> > > > Dave Bone
> > > >
> > >
> >
>