× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Does anyone have the last V5R2 cumulative PTF from March 22, 2006 ("TC06080?")? We are one cume behind on these systems and perhaps that would solve my problem.

Scott Lindstrom
Pactiv Corporation


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lindstrom, Scott R.
Sent: Wednesday, October 12, 2011 11:37 AM
To: midrange-l@xxxxxxxxxxxx
Subject: HTTP *ADMIN server won't start

My pair of newly acquired V5R2 LPARS both run HTTP servers. (These were built from SAVE 21 images after being spun off from another company).

One partition starts HTTP *ADMIN with no problem. The other fails with:

HTP8703 Diagnostic 40 10/10/11 12:04:53.216472 QZSRAPR QHTTPSVR *STMT QZTCJK QHTTP
From module . . . . . . . . : QZSRSNDM
From procedure . . . . . . : sendMessageToJobLog
Statement . . . . . . . . . : 13
To module . . . . . . . . . : JKJNIWK
To procedure . . . . . . . : validate
Statement . . . . . . . . . : 257
Message . . . . : An attempt to initialize a Java Virtual Machine failed.
Cause . . . . . : In the properties file specified by the JkWorkersFile
directive, a worker was configured with the type "jni". This configuration
requires that the worker process URL requests in a Java Virtual Machine in
the HTTP server job. The attempt to initialize the Java Virtual Machine has
failed. The HTTP server did not start. Recovery . . . : Look for other
messages in the job log that may provide more information. It is possible
that the classpath that is configured in the properties file is not correct.
Configure the JkLogFile directive to specify a file where detailed tracing
information can be stored. Configure the JkLogLevel directive specifying a
value of "debug" to enable detailed tracing information. Start the HTTP
server again and examine the output. If you can not determine the cause of
the error, contact your service provider for assistance.

Both servers are at the same PTF level for both 5722JV1 and 5722DG1.

I have added the -vv option on the start command to get verbose output.

One of the logs points to this file being the problem, yet the file is the same on each LPAR:

0000005D:473312 mod_jk: Error while processing the workers properties file /QIBM/ProdData/HTTPA/admin/conf/workers.propertie [s]
0000005D:473336 mod_jk: jk_error_exit()
0000005D:473344 ap_log_error()
0000005D:473344 log_error_core()
0000005D:473456 log_error_core(): "[Wed Oct 12 12:04:57 2011] [emerg] Error while opening the workers"

I am at a loss on what else to look at. Any ideas would be greatly appreciated.

Scott Lindstrom


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.