We finally found a work-around to this problem.

We changed the default port assignment for bpjobd in /etc/services from
13723 to something else and the activity monitor worked!

I don't know if every installation of NB 4.5 FP3 will experience this
problem or not, but that's the fix for us so far.

--stuart liddle

-----Original Message-----
From: Liddle, Stuart [mailto:liddles AT amgen DOT com]
Sent: Thursday, June 05, 2003 12:44 PM
To: 'Kennedy, Jeffrey'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] java gui and activity monitor


I have been having the exact problem with this as well.  We did an upgrade
from 3.4.1 in our lab and everything seemed to work fine (including the
Activity Monitor).  I have to mention here that in our test environment we
have a graphics terminal connected directly to our SUN master server, so
there's no display-back issues.

When we did the upgrade to our production system, the Activity Monitor does
not work and we get the same message that you describe below.  We also tried
using the non-Java Windows admin client and got a similar message.  

We could not run the jnbSA on the server and have the display set back to
either a UNIX workstation or a Windows desktop and have the Activity monitor
work!

We have had a case open with Veritas since last Friday and they are working
on the issue for us, but so far, no answers.

If anyone has any clues as to what is going on, please respond.

thanks,

--Stuart Liddle
Amgen

-----Original Message-----
From: Kennedy, Jeffrey [mailto:jkennedy AT qualcomm DOT com]
Sent: Thursday, May 29, 2003 3:39 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] java gui and activity monitor


Anyone else experiencing the scenario where you full permissions to
everything from the java gui but when you try to view the Activity
Monitor you get:

Activity Monitor failed and must be restarted. To recover:
1) Exit Activity Monitor.
2) Correct the problem that caused the error.
3) Restart Activity Monitor.

Connection refused: connect


I don't think it's a permission problem but I could be wrong....

~JK

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu