cancel
Showing results for 
Search instead for 
Did you mean: 

Startup of XI Application REPOSITORY failed

Former Member
0 Kudos

Anybody:

After installing all patches (all the way to sp9 for WebAS 6.40) for XI 3.0 correctly I can't access the exchange repository website (localhost:50000/rep) The following error was in the log:

Date : 11/24/2004

Time : 13:11:37:531

Category : /Applications/ExchangeInfrastructure

Message ID : 00111174DBE8003800000003000012A40003E9A3581EF45A

Severity : Error

Location : com.sap.aii.ib.core.applcomp.ApplicationComponent

Source Name : /Applications/ExchangeInfrastructure

Thread : SAPEngine_Application_Thread[impl:3]_30

Message : Startup of XI Application "REPOSITORY" failed

Thrown:

java.lang.OutOfMemoryError: null

Datasource : 11862050:C:\usr\sap\ABC\DVEBMGS01\j2ee\cluster\server0\log\applications.log

Application : sap.com/com.sap.xi.repository

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : 84b997b03e3311d9877800111174dbe8

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : com.sap.aii.ib.core.applcomp.ApplicationComponent

Resource Bundlename :

Session : 0

Source : /Applications/ExchangeInfrastructure

ThreadObject : SAPEngine_Application_Thread[impl:3]_30

Transaction :

User : J2EE_GUEST

And after this fails I get the "Dispatcher running, but no server connected!" error even though all processes seem to be running in MMC.

It seems my system (details below) is running out of memory, which is weird because before the patches I was able to access the repository and the directory just fine. Has anybody run into a similar problem?

Thanks

Diego

Ps: My system (this is not a production but a demo environment) is running on:

Pentium 4 3.0GHZ

2GB RAM

80GB HD

Windows 2000 Service Pack 4

SQLServer 2000 latest patches & hotfix

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Check how much memory is allocated to the J2EE engine upon startup. This is probably set too high and consuming all of your free memory.

Cheers

Colin.

Former Member
0 Kudos

What I see is that I have a lot of disp+work process running, one jlaunch is consuming 214MB and the other 91MB. I configured the J2EE engine with the parameters from the XI installation guide. Here is the breakdown of my processes, not including the SQLServer which takes another 350MB and all the OS stuff...

Process--ID--Memory

jlaunch 5384 214MB

jlaunch 5056 91MB

disp+work 4996 27MB

disp+work 4804 2MB

disp+work 4624 60MB

disp+work 4408 .5MB

disp+work 3692 98MB

disp+work 3644 60MB

disp+work 3484 197MB

disp+work 3448 .3MB

disp+work 3364 79MB

disp+work 3036 114MB

disp+work 2828 21MB

disp+work 2608 257MB

Thanks

Diego

Former Member
0 Kudos

Hi Diego,

it's not about physical memory. It seems like the Java VM

runs out of heap memory. Please increase the "Max heap

size" setting of that server node in the config tool.

Regards,

Hermann