Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / Tools / August 2004

Tip: Looking for answers? Try searching our database.

jakarta tomcat 3.3.1a - initialization of dispatcher failed error

Thread view: 
cschmidt - 04 Aug 2004 00:20 GMT
My Tomcat starts up fine.  However when I attempt to load the SAP PDK
portal homepage, i receive this error:

Error: 503
Location: /irj/servlet/prt/portal
Initialization of Dispatcher failed

Service is permanently unavailable

In addition, the tomcat window show an OutOfMemoryError...
I have rebooted the machien several times, and there have been no
changes to the physical memory on the machine.

I am using jakarta tomcat 3.3.1a, Eclipse 2.1, and the SAP Portal PDK
on a windows XP machine

Any ideas what is causing this?

Thank you in advance.
Robert Klemme - 04 Aug 2004 09:31 GMT
> My Tomcat starts up fine.  However when I attempt to load the SAP PDK
> portal homepage, i receive this error:
[quoted text clipped - 13 lines]
>
> Any ideas what is causing this?

Check whether there are any mem settings employed for the VM that runs
tomcat.  The default is quite low (64MB).  Look for "Modify the Default
JVM Settings" here:

http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ug.html

You can change it with -Xmx256m to 256MB for example.

You can do that with an environment var with newer versions.  I'm not sure
about 3.3, maybe you have to set it in the batch file.

Regards

   robert
cschmidt - 04 Aug 2004 13:54 GMT
> My Tomcat starts up fine.  However when I attempt to load the SAP PDK
> portal homepage, i receive this error:
[quoted text clipped - 11 lines]
> I am using jakarta tomcat 3.3.1a, Eclipse 2.1, and the SAP Portal PDK
> on a windows XP machine

here is the screen output:
*****begin screen output******
2004-08-04 07:48:33 - ServerXmlReader:
Config=$TOMCAT_HOME\conf\server.xml
EmbededTomcat: Init time 741
2004-08-04 07:48:33 - PathSetter: home=C:\tomcat\jakarta-tomcat-3.3.1a
2004-08-04 07:48:33 - ContextXmlReader: Context
config=$TOMCAT_HOME\conf\apps-127.0.0.1.xml
2004-08-04 07:48:33 - ContextXmlReader: Context
config=$TOMCAT_HOME\conf\apps-admin.xml
2004-08-04 07:48:33 - ContextXmlReader: Context
config=$TOMCAT_HOME\conf\apps-examples.xml
2004-08-04 07:48:33 - AutoWebApp: Loaded from config: DEFAULT:/admin
2004-08-04 07:48:33 - AutoWebApp: Loaded from config:
DEFAULT:/examples
2004-08-04 07:48:33 - AutoWebApp: Auto-Adding DEFAULT:/irj
2004-08-04 07:48:33 - AutoWebApp: Auto-Adding DEFAULT:/
2004-08-04 07:48:33 - ContextManager: Tomcat configured and in stable
state
2004-08-04 07:48:33 - ContextManager: Adding  DEFAULT:/admin
2004-08-04 07:48:33 - ContextManager: Adding  DEFAULT:/examples
2004-08-04 07:48:33 - ContextManager: Adding  DEFAULT:/irj
2004-08-04 07:48:33 - ContextManager: Adding  DEFAULT:/ROOT
2004-08-04 07:48:34 - Http10Interceptor: Starting on 8080
2004-08-04 07:48:34 - Ajp12Interceptor: Starting on 8007
2004-08-04 07:48:34 - Ajp13Interceptor: Starting on 8009
EmbededTomcat: Startup time 190
KeyContainer instantiiert.
static block of JNIUtils finished.
Copying pse to file C:\winnt\system32\verify.pse
INFO: Found properties file
C:\tomcat\jakarta-tomcat-3.3.1a\webapps\irj\WEB-INF\plugins\portal\services\usermanagement\data\usermanageme
nt.properties
Repository.get_instance(): creating instance
Aug 4, 2004 7:48:49 AM # IRJ Init thread      Fatal          
LOCK_CLIENT - OK: Lock client connected. Server: ACCENTUR-Q1CSX0
client: A
CCENTUR-Q1CSX0 port: 3299 pid: 1 #
Read license from lockserver: HWKEY=E1843542653 LIC=0
[com.sapportals.portal.prt.dispatcher.Dispatcher@497904, 8/4/04
7:49:18 AM CDT, IRJ Init thread] Exiting main initialization procedure
b
ecause of exception:
java.lang.OutOfMemoryError
With Stack Trace:

java.lang.OutOfMemoryError
       <<no stack trace available>>
WARNING: Dispatcher could not be set up:

javax.servlet.UnavailableException: Initialization of Dispatcher
failed
javax.servlet.UnavailableException: Initialization of Dispatcher
failed
       at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:521)
       at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:51)
       at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:146)
       at java.lang.Thread.run(Thread.java:479)
*******end screen output*******
> Any ideas what is causing this?
>
> Thank you in advance.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.