cancel
Showing results for 
Search instead for 
Did you mean: 

Dispatcher stopped after upgrade kernel

Former Member
0 Kudos

Hi All

I have a problem with the dispatcher is stopped and I restar the services and I checked the logs (defaultrade, dev_server0, etc) and the date of these files is not updated for example the date this November 6 and today it restarts (Nov. 11) but the date continued (Noviembre 6).

This problem occurred after to update theKernel of 111 to 133, then I go back to the original version (111) but the problem continues

Any suggestion to solve this problem??

Thanks a lot

Danny

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I have in my server installed 3 instances to SAP, but in the instance to BW, the dispatcher is stopped, don't work.

My server is windows 2003 and the kernel is 133.

I changed to 159 but after to upgrade the dispatcher don't work, I returned to 133 but the dispatcher is gray color.

Can you any suggestion to solve this problem?

Regards,

Ale

vikash_pakhrin
Explorer
0 Kudos

look for jvm_dispatcher.out and std_dispatcher.out. What does it show.

Usually it is due to DB connection.

In order to check DB connection. Open the configtool. If it opens successfully then DB connection for JAVA stack is ok.

Former Member
0 Kudos

Hi Vikash,

Thank you very much for your prompt response,

I reviewed the logs that suggests to me, but in the jvm_dispatcher.out I do not have any data on the std_dispatcher.out the following erroros:

Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect

Loading: LogManager ... 5187 ms.

Loading: PoolManager ... 0 ms.

Loading: ThreadManager ... 78 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ConnectionsManipulator ... 31 ms.

Loading: ClassLoaderManager ... 0 ms.

Loading: ClusterManager ... 250 ms.

Loading: PortsManager ... 0 ms.

Loading: LockingManager ... 78 ms.

Loading: ConfigurationManager ... 1688 ms.

Loading: LicensingManager ... 78 ms.

Loading: CacheManager ... 140 ms.

Loading: ServiceManager ...

Loading services.:

Service licensing started. (0 ms).

Service httptunneling started. (0 ms).

Service memory started. (0 ms).

Service sld started. (0 ms).

Service r3startup started. (32 ms).

Service timeout started. (47 ms).

Service shell started. (79 ms).

Service telnet started. (16 ms).

Service iiop started. (391 ms).

Service keystore started. (0 ms).

Service p4 started. (1297 ms).

Service jmx_notification started. (16 ms).

Service jmx started. (156 ms).

Service ssl started. (78 ms).

Service security started. (31 ms).

Service classload started. (0 ms).

Service webservices started. (0 ms).

Service log_configurator started. (9187 ms).

Service configuration started. (16 ms).

Service basicadmin started. (125 ms).

Service http started. (140 ms).

Service jms_provider started. (94 ms).

Service adminadapter started. (0 ms).

Service tc.monitoring.logviewer started. (343 ms).

Service monitor started. (1203 ms).

ServiceManager started for 15094 ms.

Framework started for 22734 ms.

SAP J2EE Engine Version 7.00 PatchLevel is running!

PatchLevel September 11, 2006 16:35 GMT

>

Login :[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor12]

[Unloading class sun.reflect.GeneratedMethodAccessor3]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor7]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor13]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor5]

[Unloading class sun.reflect.GeneratedMethodAccessor8]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor11]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor8]

[Unloading class sun.reflect.GeneratedMethodAccessor4]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor6]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor14]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor1]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor9]

[Unloading class sun.reflect.GeneratedMethodAccessor5]

[Unloading class sun.reflect.GeneratedMethodAccessor7]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor4]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor3]

[Unloading class sun.reflect.GeneratedMethodAccessor6]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor2]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor10]

-


stdout/stderr redirect

-


node name : dispatcher

pid : 2532

system name : WTP

system nr. : 02

started at : Tue Oct 14 13:25:58 2008

Error occurred while preloading classes of security providers from jre/lib/ext folder: java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect

Loading: LogManager ... 453 ms.

Loading: PoolManager ... 0 ms.

Loading: ThreadManager ... 47 ms.

Loading: IpVerificationManager ... 0 ms.

Loading: ConnectionsManipulator ... 15 ms.

Loading: ClassLoaderManager ... 16 ms.

Loading: ClusterManager ... Oct 14, 2008 1:26:02 PM ...anagerImpl.init(java.util.Properties) [Thread[Thread-1,5,main]] Fatal: Cannot attach to the Message Server. Can't open port [3903] on host [Jupiter/192.168.0.14] (Connection refused: connect).

Loading: ClusterManager returned false!

Kernel not loaded. System halted.

I do configtool I can already access the entire configuration, however the dispatcher remains in yellow, is not taken completamete, I can do to fix this?

Best Regards,

Ale.

Former Member
0 Kudos

thanks

Former Member
0 Kudos

Hi,

Manually check whether all files in the kernel are having the latest kernel of 133

I had the same issue in the past and found that some files did not get copied properly. after i recopied the failed files, the Server was up and running

Former Member
0 Kudos

Hi, can you say how you upgrade your server? if you have JAVA or ABAP+JAVA stacks you can update kernel using JSPM. Can you say step by step what you do?

--

Regards.

Former Member
0 Kudos

Thanks Sergo, Sanul

I have java + abap in this instance.

these are the steps that I did to upgrade the kernel:

1.- download the files kernel 133 ( part I and part II )

2.- stop all services sap

3.- I made a backup of kernel111

4.- unzip of files SAPCAR_NEW -xvf archive

5.- this files I copied in the folder kernel111

6.- start all services sap

This process I made in other system and it's running normality

How do you upgrade the kernel through JSMP??

Is the same The process in windows and hp-unix?

Regards

Former Member
0 Kudos

Sorry

In this time I'm reviewing the links that You send me in the previuos message

thanks a lot

Danny

JPReyes
Active Contributor
0 Kudos

4.- unzip of files SAPCAR_NEW -xvf archive

5.- this files I copied in the folder kernel111

You need to copy the files into the kernel directory not in the kernel111 directory.

Regards

Juan

Former Member
0 Kudos

Thanks, Juan

Yes, I replaced the new files of kernel133 in the folder kernel111, then I got this problem with the dispatche and I back to kernel111

I don´t know What do I review in this system?

Thanks

Former Member
0 Kudos

stop DB and R/3 including saposcol.

Take backup of current kernel directory-:

check whether you have sufficient free space under /sapmnt/<SID>

login <SID>adm

1) cd /sapmnt/<SID>

2) cp -Rp <SID> <SID>_backup

3) Download latest kernel from service market place put it in directory latest_kernel

create a directory

mkdir /sapmnt/<SID>/latest_kernel

download and then copy your new kernel SAPEXE_, SAPDB_ and java releted to above directory.

cd /sapmnt/<SID>/latest_kernel

chmod 777 *

4) Upgrade the kernel using following commands

cd /sapmnt/<SID>/latest_kernel

execute following command

/sapmnt/<SID>/<SID>_backup/SAPCAR -xvf SAPEXE_* -R /sapmnt/EQA/exe

/sapmnt/<SID>/<SID>_backup/SAPCAR -xvf SAPDB_* -R /sapmnt/EQA/exe

follow same command for Java kernel.

5) go to /sapmnt/<SID>/exe

execute ./saproot.sh

start database and check

R3trans -d

if the output is 0000 then start SAP

cheers,

-Sunil

Former Member
0 Kudos

check your database is up or not,

then try (R3trans -d) and then check the trans.logs file

which OS/Database you are using?

cheers,

-Sunil