Solved: N4S - SAP NetWeaver NW2004S for Linux,64 bit, J2EE...

Former Member · ‎02-04-2007

<img src=/images/reward-16x16.gif>Dear SAP Experts,<img src=/images/reward-16x16.gif>

I was installing a <a href="/people/piers.harding/blog/2006/12/29/n4s-linux-evaluation-edition-nw2004s-under-debian-ubuntu" target="_blank">Test Drive (Evaluation) edition of SAP NetWeaver NW2004S for Linux</a><img src="https://weblogs.sdn.sap.com/weblogs/images/1575/external.png" alt="" />

<img src="https://forums.sdn.sap.com/images/info-16x16.gif" alt="" /> based on

CPU: <a href=http://images.google.com/images?hl=en&q=intelpentium4processor5413.2ghz target=_blank>Intel Pentium 4 541 3.2GHz</a><img src="https://weblogs.sdn.sap.com/weblogs/images/1575/external.png" alt="" /><img src="https://weblogs.sdn.sap.com/weblogs/images/1575/googlelink.png" width="17" height="18" border="0" alt="image" />

Fedora Core 4 - Language : Korean

Linux n4shost 2.6.11-1.1369_FC4smp #1 SMP Thu Jun 2 23:16:33 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux

and

JDK 1.4.2 for SAP Customers- IBMJava2-AMD64-142-SDK-1.4.2-2.0.x86_64.rpm

Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)

IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142ifx-20051125 (JIT enabled)

J9VM - 20050524_1742_LHdSMr

JIT - r7_level20050518_1803)

Symptoms

Unfortunately, J2EE engine doesn't work properly.

and the CPU consumption is very high.

How can I solve this problem?

In order for you to understand my situation, I link some information

<ul><li> The list of processes is here <a href=http://mobilian.org/SDN/N4S/process-list.txt

target=_blank>process-list.txt</a><img src="https://weblogs.sdn.sap.com/weblogs/images/1575/external.png" alt="" />

</ul></div>

<ul>Under /usr/sap/N4S/DVEBMGS01/work, I found there are many useful files. you can download <a href=http://mobilian.org/SDN/N4S/work200702041301.zip target=_blank>the zip file - work200702041301.zip</a><img src="https://weblogs.sdn.sap.com/weblogs/images/1575/external.png" alt="" />

<li>Inside this /usr/sap/N4S/DVEBMGS01/work/dev_jcontrol file, I found the following issues (?) that possibly make troubles.

~~~~~~~~

[Thr 46912499499424] Sun Feb 4 11:54:00 2007

[Thr 46912499499424] *** WARNING => INFO: Unknown property [instance.box.number=N4SDVEBMGS01n4shost] [jstartxx_mt. 841]

[Thr 46912499499424] *** WARNING => INFO: Unknown property [instance.en.host=n4shost] [jstartxx_mt. 841]

[Thr 46912499499424] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx_mt. 841]

[Thr 46912499499424] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx_mt. 841]

~~~~~~~~

[Thr 46912499499424] SigISetDefaultAction : default handling for signal 17

[Thr 46912499499424] JControlExecuteBootstrap: execute bootstrap process [bootstrap]

[Thr 46912499499424] [Node: bootstrap] java home is set by profile parameter

Java Home: /usr/lib/java

[Thr 1074792800] JControlDPMessageFunc: Thread 1074792800 started as handler thread for R/3 dispatcher messages.

[Thr 46912499499424] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/N4S/SYS/exe/run/jvmx.jar

~~~~~~~~

I searched jvmx.jar through the entire Linux server, but jvmx.jar was not found.

~~~~~~~~

[Thr 46912499499424] JStartupICreateProcess: fork process (pid 11565)

[Thr 46912499499424] JControlICheckProcessList: process server0 started (PID:11565)

[Thr 46912499499424] Sun Feb 4 12:06:37 2007

[Thr 46912499499424] JControlICheckProcessList: process server0 (pid:11565) died (RUN-FLAG)

[Thr 46912499499424] JControlIResetProcess: reset process server0

[Thr 46912499499424] JControlIResetProcess: [server0] not running -> increase error count (4)

[Thr 46912499499424] JControlICheckProcessList: running flight recorder:

/usr/lib/java/bin/java -classpath ../j2ee/cluster/bootstrap/sap.com_tcbl_{offline_launcher}impl.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node ID14704950 1170558357 -bz /usr/sap/N4S/SYS/global

~~~~~~~~

<li>Inside this /usr/sap/N4S/DVEBMGS01/work/dev_bootstrap file,

~~~~~~~~

[Thr 46912499499424] Sun Feb 4 11:54:07 2007

[Thr 46912499499424] SigISetDefaultAction : default handling for signal 17

[Thr 46912499499424] Sun Feb 4 11:54:10 2007

[Thr 46912499499424] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 46912499499424] Sun Feb 4 11:54:11 2007

[Thr 46912499499424] CPIC (version=700.2005.12.02)

[Thr 46912499499424] [Node: bootstrap] java home is set by profile parameter

Java Home: /usr/lib/java

[Thr 46912499499424] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/N4S/DVEBMGS01/exe/jvmx.jar

~~~~~~~~

<li>Inside this /usr/sap/N4S/DVEBMGS01/work/stderr1 file,

~~~~~~~~

--- Unicode interface [u16_prnt.c line 1970] pid = 10611 :

Error in format string at or near 'S':

%SLIC_HWIDKEY_LN.SLIC_HWIDKEY_LN

--- Unicode interface -

End of message -

--- Unicode interface [u16_prnt.c line 1970] pid = 10616 :

Error in format string at or near 'S':

%SLIC_HWIDKEY_LN.SLIC_HWIDKEY_LN

--- Unicode interface -

End of message -

--- Unicode interface [u16_prnt.c line 1970] pid = 10616 :

Error in format string at or near 'S':

%SLIC_HWIDKEY_LN.SLIC_HWIDKEY_LN

--- Unicode interface -

End of message -

Can't find Java Class: com.sap.engine.offline.OfflineToolStart

--- Unicode interface [u16_prnt.c line 1970] pid = 10610 :

Error in format string at or near 'S':

%SLIC_HWIDKEY_LN.SLIC_HWIDKEY_LN

--- Unicode interface -

End of message -

~~~~~~~~

</ul>

</div>

I'm looking forward to seeing any suggestion.

Many thanks,

David

Former Member · ‎02-05-2007

Hi David

pls take a look at your dev_w.. developer traces .

Best regards

dirk

Former Member · ‎09-16-2007

- go to /sapmnt/N4S/profile or /usr/sap/N4S/SYS/profile or use on shell the command "cdD"

- edit the following line in InstanceProfile "N4S_DVEBMGS01_n4shost"

before:

jstartup/vm/home = /usr/lib/java

after:

jstartup/vm/home = /usr/lib64/jvm/java-1_4_2-ibm-1.4.2_sr7

ok - thats on SLES10SP1, i dont know, where you have your jvm.

we have a 64bit system hurray.

thanks and more success,

christoph

Former Member · ‎09-16-2007

hello david,

i have the same problem.

i use the standard jdk/jre from sles10sp1 from ibm.

java -fullversion

java vollständige Version "J2RE 1.4.2 IBM build j9xa64142-20061124 (SR7)"

maybe -

the problem is the java_home in LD_LIBRARY_PATH > /usr/lib/java - does not exist.

/usr/lib64/java exist and a symbolic link to /usr/lib64/jvm/java .

the really jvm is here /usr/lib64/jvm/java-1_4_2-ibm-1.4.2_sr7, right?

I will try it out.

see ya.

christoph

Former Member · ‎02-06-2007

Hi David

Check the ownership of :

/usr/sap/N4S/SYS/profile/N4S_JCXX_XX

it should be n4sadm:sapsys . Give execute permissions.

Start the instance now .

Also try to increase the memory settings using the configtool.Increase the bootstrape memory.If you have any problem feel free to ask.

Pls Award points

Former Member · ‎02-04-2007

and from std_server0.out

I found the issue related to "Logon".

~~~~~~~~

Service dbpool started. (29421 ms).

Feb 4, 2007 12:02:17 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available.

Error message: " Logon not possible (error in license check) ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{

passwd=********

receiverid=master

sysnr=$$

client=001

poolmaxsize=10

user=SAPJSF

receiverid_guest=master

ashost=localhost

poolmaxwait=10000

}

".

Feb 4, 2007 12:02:25 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.

Feb 4, 2007 12:02:25 PM com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_54] Fatal:

service com.sap.security.core.ume.service ================= ERROR =================

Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: <~~Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []~~> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Logon not possible (error in license check)

at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

----

caused by -

com.sap.security.api.UMException: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Logon not possible (error in license check)

at com.sap.security.core.InternalUMFactory.instantiateClass(InternalUMFactory.java:1285)

at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1243)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)

at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

~~~~~~~~

N4S - SAP NetWeaver NW2004S for Linux,64 bit, J2EE engine doesn't work.

Accepted Solutions (1)

Accepted Solutions (1)

Answers (4)

Answers (4)

Re: SAP BUILD deployment to production

Re: SAP Build process Automation - Document Extrac...

Re: Error for Document Date in AR Invoice #59921

Re: Trigger Basic Idoc from scratch

Re: How to navigate from ALV report output to Outl...