× 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 Danù

Thanks again for yout time;

Here the change to my catalina.sh:



# export -s JAVA_HOME=/QIBM/ProdData/Java400/jdk14

export -s JAVA_HOME=/QOpenSys/QIBM/ProdData/Java#VM/jdk50/32bit

# export -s JAVA_OPTS="-Dos400.awt.native=true -Djava.awt.headless=true -Djava.version=1.6 -Xms256m -Xmx512m"

export -s JAVA_OPTS="-Dos400.awt.native=true -Djava.awt.headless=true -Xms256m -Xmx512m"

cygwin=false

os400=true



when I run catalina.sh i see always this msg ....



/tomcat/bin/catalina.sh: 001-0019 Errore rilevato durante la ricerca del comando tty. Questo percorso o indirizzario non esiste.

Using CATALINA_BASE: /tomcat

Using CATALINA_HOME: /tomcat

Using CATALINA_TMPDIR: /tomcat/temp

Using JRE_HOME: /QOpenSys/QIBM/ProdData/Java#VM/jdk50/32bit

Using CLASSPATH: /tomcat/bin/bootstrap.jar

Usage: catalina.sh ( commands ... )

commands:

debug Start Catalina in a debugger (not available on OS400)

debug -security Debug Catalina with a security manager (not available on OS400)

jpda start Start Catalina under JPDA debugger

run Start Catalina in the current window

run -security Start in the current window with security manager

start Start Catalina in a separate window

start -security Start in a separate window with security manager

stop Stop Catalina, waiting up to 5 seconds for the process to end

stop n Stop Catalina, waiting up to n seconds for the process to end

stop -force Stop Catalina, wait up to 5 seconds and then use kill -KILL if still running

stop n -force Stop Catalina, wait up to n seconds and then use kill -KILL if still running

version What version of tomcat are you running?

Note: Waiting for the process to end and use of the -force option require that $CATALINA_PID is defined



How can I check if TOMCAT is started ??



I don’t see any spool files QPRINT and I if I go to browser and typy HTTP://myiseris:8080 I receive “impossible to display the web page”

Where I’m wrong ?

Thanks again









-----Messaggio originale-----
Da: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] Per conto di Dan Kimmel
Inviato: mercoledì 29 gennaio 2014 19:03
A: Java Programming on and around the IBM i
Oggetto: RE: Problem with Tomcat on iSeries



What you have done is just about right.



I hadn't read these two articles. They are both very good. Don Denoncourt's is dated 2005 when I was first installing Tomcat 5.028, though he says to install Tomcat 5.5 with Java 1.4. Personeni's article isn't dated, but he is also talking about 5.028 and Java 1.4.



Denoncourt errs a little. Tomcat 5.5 will run with Java 1.4 but is designed for Java 1.5 (Java 5.0 is another name for Java 1.5). Some of the JSP functions will fail using Tomcat 5.5 with Java 1.4. I found this out the hard way.



Tomcat 5.028 is the last release of Tomcat designed to run with any Java earlier than Java 1.5.



The version of Tomcat you are trying to install, Tomcat 6.037, is a very current release. It will start up under Java 1.4 but isn't going to work fully. At Java 1.5 many of the servlet container functions moved to the JVM. So if you try to run a container (Tomcat is a container) built for Java 5.0 with Java 1.4, many of the packages are duplicated in the classpath and some of those packages changed dramatically between the versions. It doesn't all "play nice".



I believe all you need to do is change the value of JAVA_HOME export in your script to /QOpenSys/QIBM/ProdData/Java#VM/jdk50/32bit and remove the -Djava.version setting from your java command line.



Ignore any messages about TTY function. That's a spurious message from QSH and I seem to remember is was fixed with a PTF on V5R4.



Make these changes, try it, and look at the QPRINT file that contains the stdout messages. If it still doesn't work, post those messages here and I'll help more.



I see JHHL has posted that Tomcat may not work under V5R4. That is incorrect. I ran it very successfully at V5R4 for several of my RJS customers.



-----Original Message-----

From: <mailto:java400-l-bounces@xxxxxxxxxxxx> java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-

<mailto:bounces@xxxxxxxxxxxx> bounces@xxxxxxxxxxxx] On Behalf Of gio.cot

Sent: Wednesday, January 29, 2014 10:34 AM

To: 'Java Programming on and around the IBM i'

Subject: R: Problem with Tomcat on iSeries



Hi

Many thanks for your reply, be patient but this are my first steps on

application server so many concepts are unknowed . I tried to install

Tomcat on iSeries following two links :

<http://iprodeveloper.com/rpg-programming/day-life-ifs-java-programmer> http://iprodeveloper.com/rpg-programming/day-life-ifs-java-programmer

<http://www.compomentis.com/papers/iSeriesTomcat.html> http://www.compomentis.com/papers/iSeriesTomcat.html

so i olny read this documents and tried to do what I have understand,

then as tomcat don't work I search in google and I have done many

tests that don't give me any result.



So, if possible, I would like to know how to modify the catalina.sh

file : what I have to add and or modify.

Thanks in advance for your help







-----Messaggio originale-----

Da: <mailto:java400-l-bounces@xxxxxxxxxxxx> java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-

<mailto:bounces@xxxxxxxxxxxx> bounces@xxxxxxxxxxxx] Per conto di Dan Kimmel

Inviato: mercoledì 29 gennaio 2014 17:01

A: Java Programming on and around the IBM i

Oggetto: RE: Problem with Tomcat on iSeries



Pick one JVM, you can't use all three (four) in one invocation. For

Tomcat

6.0.37 that has to be Java 5.0 at a minimum. This gives you the choice

of option 7 or 8. The 32 bit version (j9) runs better on V5R4 in most

cases. On

v5r4 there are many ways to set the version; and the version stated in

the java command line itself takes precedence over anything set in

JAVA_HOME or java.properties files. In your command line, you specify

Java 6 (- Djava.version=1.6). You don't have Java 6 on your machine.

The QSH java command works its way down through the selection

precedence until it finds a JVM, the one it finds is the last one you

specified in JAVA_HOME. The 32 bit version of Java 5.0 should be fine for Tomcat.



Most of the startup logging for Java and Tomcat goes to stdout. Stdout

is an abstract file that is directed by the OS to an actual file. File

in this case is in the unix sense, not the IBMi sense. QSH sets up

stdout to go to a spool file

(QPRINT) attached to the QSH job. (The job created when you first call

QSH from the QCMD command line.) QSH handles translation from ASCII

output to stdout into EBCDIC spool file content. Just display the

QPRINT spool file to see your primary log.



As Tomcat starts to fire up, it creates catalina.out and begins to log

there. This is another ascii stream file. Open it with Windows Notepad

so you can read the ascii. EDTF should translate it for display if the

code page is set properly. (I believe it is F15 that allows you to

change the code page.)



I've never used the startup.sh script to start Tomcat; I've always

called catalina.sh directly with the "start" option.





-----Original Message-----

From: <mailto:java400-l-bounces@xxxxxxxxxxxx> java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-

<mailto:bounces@xxxxxxxxxxxx> bounces@xxxxxxxxxxxx] On Behalf Of gio.cot

Sent: Wednesday, January 29, 2014 8:36 AM

To: <mailto:java400-l@xxxxxxxxxxxx> java400-l@xxxxxxxxxxxx

Subject: Problem with Tomcat on iSeries







Hi



i'm trying to install TOMCAT on iSeries but i have problems;



my scenario is :



* iSeries with V5R4 and



* 5722JV1 *BASE IBM Developer Kit per Java

5722JV1 5 Java Developer Kit 1.3

5722JV1 6 Java Developer Kit 1.4

5722JV1 7 Java Developer Kit 5.0

5722JV1 8 J2SE 5.0 32 bit



* Tomcat : apache-tomcat-6.0.37



i have installed Tomcat in a folder called TOMCAT and unzipped the

file apache-tomcat-6.0.37.zip in it; then i have modified

catalina.sh adding this

lines:



export -s JAVA_HOME=/QIBM/ProdData/Java400/jdk14

export -s JAVA_HOME=/QOpenSys/QIBM/ProdData/Java#VM/jdk50/32bit

export -s JAVA_OPTS="-Dos400.awt.native=true

-Djava.awt.headless=true

-

Djava.version=1.6 -Xms256m -Xmx512m"



and changed the row "os400=true"



now if i run from QSH the startup.sh i receive this:



startup.sh

/tomcat/bin/catalina.sh: 001-0019 Error found searching for command

tty. No such path or directory.

Using CATALINA_BASE: /tomcat

Using CATALINA_HOME: /tomcat

Using CATALINA_TMPDIR: /tomcat/temp

Using JRE_HOME: /QOpenSys/QIBM/ProdData/Java#VM/jdk50/32bit

Using CLASSPATH: /tomcat/bin/bootstrap.jar



where could be the problem ? can some help me or suggest some link

that

could help to solve this ?



thanks in advance



p.s. if i open the catalina.out i see strange charatters like

""-@aØÖ-

…•â¨¢aØÉÂÔa×™-"ā£aс¥±åÔa'"'õðaóò'‰£a'‰•a'¥@•-•@£™-

¥£-

K%a£-"ƒ" is normal !!



this is the content of catalinaxxx.log



29-Gen-2014 11.32.52 org.apache.coyote.http11.Http11Protocol pause

INFORMAZIONI: Pausing Coyote HTTP/1.1 on http-8080

29-Gen-2014 11.32.53 org.apache.catalina.core.StandardService stop

INFORMAZIONI: Stopping service Catalina

29-Gen-2014 11.32.53 org.apache.coyote.http11.Http11Protocol destroy

INFORMAZIONI: Stopping Coyote HTTP/1.1 on http-8080



Thanks in advance







--

This is the Java Programming on and around the IBM i (JAVA400-L)

mailing list To post a message email: <mailto:JAVA400-L@xxxxxxxxxxxx> JAVA400-L@xxxxxxxxxxxx To

subscribe, unsubscribe, or change list options,

visit: <http://lists.midrange.com/mailman/listinfo/java400-l> http://lists.midrange.com/mailman/listinfo/java400-l

or email: <mailto:JAVA400-L-request@xxxxxxxxxxxx> JAVA400-L-request@xxxxxxxxxxxx Before posting, please take

a moment to review the archives at

<http://archive.midrange.com/java400-l> http://archive.midrange.com/java400-l.



--

This is the Java Programming on and around the IBM i (JAVA400-L)

mailing list To post a message email: <mailto:JAVA400-L@xxxxxxxxxxxx> JAVA400-L@xxxxxxxxxxxx To

subscribe, unsubscribe, or change list options,

visit: <http://lists.midrange.com/mailman/listinfo/java400-l> http://lists.midrange.com/mailman/listinfo/java400-l

or email: <mailto:JAVA400-L-request@xxxxxxxxxxxx> JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a

moment to review the archives at <http://archive.midrange.com/java400-l> http://archive.midrange.com/java400-l.





--

This is the Java Programming on and around the IBM i (JAVA400-L)

mailing list To post a message email: <mailto:JAVA400-L@xxxxxxxxxxxx> JAVA400-L@xxxxxxxxxxxx To

subscribe, unsubscribe, or change list options,

visit: <http://lists.midrange.com/mailman/listinfo/java400-l> http://lists.midrange.com/mailman/listinfo/java400-l

or email: <mailto:JAVA400-L-request@xxxxxxxxxxxx> JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a

moment to review the archives at

<http://archive.midrange.com/java400-l> http://archive.midrange.com/java400-l.



--

This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: <mailto:JAVA400-L@xxxxxxxxxxxx> JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,

visit: <http://lists.midrange.com/mailman/listinfo/java400-l> http://lists.midrange.com/mailman/listinfo/java400-l

or email: <mailto:JAVA400-L-request@xxxxxxxxxxxx> JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at <http://archive.midrange.com/java400-l> http://archive.midrange.com/java400-l.




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.