cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup 6.5.3 Java Console (Windows) is hung

Jay_Son
Level 5

The NetBackup (NBU) Java administration console (6.5.3) hangs after attempting to expand the host list for clients, Host Properties.  (Windows XP)

 

I've trive this Tech Note but w/ no avail. http://support.veritas.com/docs/293857

 

Is there another fix for this or do I need to open up a case w/ Symantec?

 

Thanks in advance.

 

Jay Son

 

Here is my current setconf.bat file:

 

SET INSTALL_PATH=C:\\Program Files\\Veritas\\java
SET VXSSAT_INSTALL_PATH=C:\\Program Files\\VERITAS\\Security\\Authentication
REM The following three lines are inserted above this line during installation:
REM Two backslashes are required as a path separator.
REM   SET INSTALL_PATH=<java gui install path>
REM   SET NB_INSTALL_PATH=<netbackup install path>
REM   SET VXSSAT_INSTALL_PATH=<Symantec Product Authentication component install path>
REM e.g., SET INSTALL_PATH=C:\\Program Files\\VERITAS\\java
REM       SET NB_INSTALL_PATH=C:\\Program Files\\Veritas\\NetBackup
REM       SET VXSSAT_INSTALL_PATH=C:\\Program Files\\Veritas\\vxss

SET INITIAL_MEMORY=36M
SET MAX_MEMORY=256M
SET MEM_USE_WARNING=80
SET NBJAVA_CONNECT_OPTION=1
SET NBJAVA_CLIENT_PORT_WINDOW=0 0
SET FORCE_IPADDR_LOOKUP=1
SET USE_NBJAUTH_WITH_ENHAUTH=0
SET BPJAVA_PORT=13722
SET VNETD_PORT=13724
SET NBJAVA_CORBA_DEFAULT_TIMEOUT=60
SET NBJAVA_CORBA_LONG_TIMEOUT=1800
SET NBJDIR=%INSTALL_PATH%
SET VXSSATLIBPATH=%VXSSAT_INSTALL_PATH%\bin
SET JAVALIBPATH=%NBJDIR%;%VXSSATLIBPATH%
SET PATH=.\jre\bin;..\netbackup\bin;%PATH%
SET NBUCLASSPATH=%NBJDIR%\nbjP.jar;%NBJDIR%;%NBJDIR%\allNB.jar;%NBJDIR%\nbCommon.jar;%NBJDIR%\dbext.jar;%NBJDIR%\allHSM.jar;%NBJDIR%\allFSA.jar;%NBJDIR%\servicelayer.jar;%NBJDIR%\emmidl.jar
SET THIRDPARTYCLASSPATH1=%NBJDIR%\pvxSpin.jar;%NBJDIR%\pvxDates.jar;%NBJDIR%\jcfield401K.jar;%NBJDIR%\jdom.jar;%NBJDIR%\VxHelpViewer.jar;%NBJDIR%\SchedUI.jar;%NBJDIR%\vxrep-v2.20.jar;%NBJDIR%\mcharts.jar
SET THIRDPARTYCLASSPATH2=%NBJDIR%\jcchart.jar;%NBJDIR%\jacorb.jar;%NBJDIR%\logkit-1.2.jar;%NBJDIR%\pbxiop.jar;%NBJDIR%\vxssiop.jar;%NBJDIR%\avalon-framework-4.1.5.jar;%VXSSATLIBPATH%\AtWrapper.jar
SET CORBACLASSPATH=%NBJDIR%\concurrent-1.3.2.jar;%NBJDIR%\antlr-2.7.2.jar

if "[%NB_INSTALL_PATH%]"=="[]" goto skip
@REM generate a unique file name ...
for /f "tokens=5-8 delims=:. " %%a in ('echo.^|time') do set thh=%%a&set tmm=%%b&set tss=%%c&set ths=%%d
for /f "tokens=1-4 delims=/ " %%i in ('date /t') do set dday=%%i&set dmm=%%j&set ddd=%%k&set dyyyy=%%l
set nbjLogFileName=jbp.%dyyyy%%dmm%%ddd%%thh%%tmm%%tss%%ths%.log
set logFile=%NB_INSTALL_PATH%\logs\user_ops\nbjlogs\%nbjLogFileName%
:skip

SET INSTALL_PATH > "%NBJDIR%"\nbjconf
SET INITIAL_MEMORY >> "%NBJDIR%"\nbjconf
SET MAX_MEMORY >> "%NBJDIR%"\nbjconf
SET MEM_USE_WARNING >> "%NBJDIR%"\nbjconf
SET BPJAVA_PORT >> "%NBJDIR%"\nbjconf
SET VNETD_PORT >> "%NBJDIR%"\nbjconf
SET NBJAVA_CORBA_DEFAULT_TIMEOUT >> "%NBJDIR%"\nbjconf
SET NBJAVA_CORBA_LONG_TIMEOUT >> "%NBJDIR%"\nbjconf
SET NBJAVA_CONNECT_OPTION >> "%NBJDIR%"\nbjconf
SET NBJAVA_CLIENT_PORT_WINDOW >> "%NBJDIR%"\nbjconf
SET FORCE_IPADDR_LOOKUP >> "%NBJDIR%"\nbjconf
SET USE_NBJAUTH_WITH_ENHAUTH >> "%NBJDIR%"\nbjconf

REM SET INSTALLED_RELEASE and BUILDNUMBER lines added during build.
SET INSTALLED_RELEASE=650000
SET BUILDNUMBER=20070723

SET FORCE_RESET=1
SET INITIAL_MEMORY=128M
SET MAX_MEMORY=256M
SET MEM_USE_WARNING=80
SET NBJAVA_CONNECT_OPTION=1
SET NBJAVA_CLIENT_PORT_WINDOW=0 0
SET FORCE_IPADDR_LOOKUP=0
SET USE_NBJAUTH_WITH_ENHAUTH=0
SET BPJAVA_PORT=13722
SET VNETD_PORT=13724
SET NBJAVA_CORBA_DEFAULT_TIMEOUT=60
SET NBJAVA_CORBA_LONG_TIMEOUT=1800

3 REPLIES 3

Andy_Welburn
Level 6

There's an additional Tech Note that mentions the IP lookup change that you've actioned, but also changing the amount of Java memory too. It may help?

 

Reduce java console load time and improve performance

Andy_Welburn
Level 6

Another thing to 'possibly' consider: have you decommissioned a media server recently or maybe removed some clients?

 

There can be issues if a media server is incorrectly/incompletely decommissioned - it can take some time looking for a media server that no longer exists.

 

There was also an instance last year of several clients being removed but were still being referred to in the bp.conf file (master server properties, firewall port connection options) which were causing the interface to become sluggish. (Again looking for clients that no longer exist).

 

This may, however, not be relevant to your environment ... but you never know!

Jay_Son
Level 5

Thank you all for your assistance. I found a patch that worked for me.

 

Here's the link to the Java patch:
http://seer.entsupport.symantec.com/docs/314602.htm