cancel
Showing results for 
Search instead for 
Did you mean: 

Clicking on SLD Data Supplier crashes Visual Admin for NWA 7.0

manish_kumar8
Participant
0 Kudos

Hi All,

I have a SAP NWA 7.0 Java system .  I am trying to configure data supplier through Visual admin for my java system. When I am clicking on "SLD Data Supplier" in Visual Admin, it is crashing Visual admin and my session closes automatically. Clicking on any other items is working fine. Only clicking SLD Data supplier is having issues.

Could anyone of you can help what may be the issue ??

Regards,

Manish

Accepted Solutions (0)

Answers (2)

Answers (2)

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Manish,

Hope you are doing good.

Open the VA executable file and increase the memory parameter so that VA can process more load .
Once this is done and the issue persists,  trigger some thread dumps and you should find more details of the error is:

/usr/sap/<SID>/JC<nr>/j2ee/admin/visual_administration.trc

/usr/sap/<SID>/JC<nr>/j2ee/admin/visual_administration.log

/usr/sap/<SID>/JC<nr>/j2ee/cluster/server0/logs/default trace (latest).

/usr/sap/<SID>/JC<nr>/j2ee/cluster/dispatcher/logs/default trace(latest)

 

Thank you!

_____________

Kind Regards,

Hemanth

SAP AGS
 

manish_kumar8
Participant
0 Kudos

Hi Hemant,

Your comment "Open the VA executable file and increase the memory parameter so that VA can process more load ."

How to achieve this ?? I see the executable file ( go ) for VA  doesn't have any memory parameters inside it.

Hi Divyanshu,

We don't have SAP JVM applied on this system due to some constraints with the application running on this. We have Java version is 1.4.2_13

There is no dump or heap generated.

Regards,

Manish

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Manish,

Goto Launcher.properties and check for ReqJavaVersion=?

Check this in - /j2ee/admin/cfg

Also, go in log directory and check the trace file. As per log configuration, error should be in these trace file.

Divyanshu

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi manish,

Hope you are doing good.

Please, try the following: Edit the go.bat or go.sh file.

Set the -Xmx=1024M. The default size of this is usually 512 wich is obviously not enough in your
case.

The entry would be something like:

Eg:

%JAVA_CMD% -Xmx512m -Xms512m -showversion .......

Also the JDK that you are being using is very very old and can be the main issue of this.

Other 3rd party JDKs are out of support now. SAP recommends users to upgrade to the latest SAPJVM as soon as possible. Please see:

SAP Note No. 1920326 - Oracle JDK support agreement terminated

"
The JDK support contract between Oracle and SAP was terminated
by Oracle (effective 31.12.2013).
Due to Oracle's termination of the agreement, SAP cannot
provide Oracle JDK support coverage starting from January 2014.
"

SAP JVM 4 is the standard JDK included in the follow-up SAP NetWeaver release. As of today appropriate performance for SAP applications, comparable to currently used vendor JDKs.

Below will help:

SAP Note No. 1367498 - SAP JVM installation prerequisites

SAP Note No. 1442124 How to download a SAP JVM patch from the SMP

SAP Note No. 1133020 How to import a SAP JVM patch into an AS Java

SAP Note No. 1603093- SAP JVM 4.1 parameters NetWeaver 2004 and 7.0

Thank you!

_____________

Kind Regards,

Hemanth

SAP AGS
 

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Manish,

Which JVM are you using ?

Was there any dump created, like for heap or something ?

Regards,

Divyanshu