× 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.







Hi Alex,

I had the same problem. It seems that the Tomcat server JVM needs to be set
to the same release as the AS400 system JVM.
Check your system's JVM in /QIBM/UserData/Java400/SystemDefault.properties.
It should have an entry like this:

java.version=1.4

Regards,
John

jthompson@xxxxxxxxxxx
Ph (09) 372-5010


|---------+------------------------------>
|         |           "Alex Pinsky"      |
|         |           <apinsky@aeropostal|
|         |           e.com>             |
|         |           Sent by:           |
|         |           java400-l-bounces@m|
|         |           idrange.com        |
|         |                              |
|         |                              |
|         |           12/05/2004 04:19 AM|
|         |           Please respond to  |
|         |           Java Programming on|
|         |           and around the     |
|         |           iSeries / AS400    |
|         |                              |
|---------+------------------------------>
  
>--------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                 |
  |       To:       <java400-l@xxxxxxxxxxxx>                                    
                                 |
  |       cc:                                                                   
                                 |
  |       Subject:  Configure Tomcat inprocess to use JDK1.4                    
                                 |
  
>--------------------------------------------------------------------------------------------------------------|




Hi All,
We run V5R2 and have a jdk1.2, jdk1.3 and jdk1.4 installed on the system.
(or at least I can see corresponding folders in /QIBM/ProdData/Java400)
Currently our Tomcat (in-process) configured to use jdk1.3
(workers.properties worker.inprocess.sysprops=java.version=1.3) - no
problem here
But when I change the value of worker.inprocess.sysprops=java.version=1.4
Tomcat can not start and fatal error message is issued:

Starting up StartupThread
Starting tomcat. Check logs/tomcat.log for error messages
Failed ??
JNIEndpoint:stopEndpoint() issuing notify()
End waiting
Error - why doesn't run ??
JNI In shutdown

I have 2 environment variables on *sys level set as:
QIBM_RPG_JAVA_PROPERTIES    '-Djava.version=1.4;'
java_home                   '/QIBM/ProdData/Java400/jdk14'

When trying to configure in Tomcat via IBM Web Administration parameter
Java version (JDK): has only 2 available values to select (1.2 and 1.3)

Any suggestions?

Alex Pinsky
Aeropostale, Inc.


"The information contained in this email message and any attachments is
confidential and is intended only for the use of the individual(s) or
entity to which it is addressed.  If you are not the intended recipient,
you are hereby notified that copying, distribution or dissemination of
this email and any associated documents is strictly prohibited. Thank
you"


_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.