fixunix
Tags Register FAQ Members List Social Groups Calendar Search Today's Posts Mark Forums Read

jboss console fills up qprint - IBM AS400

This is a discussion on jboss console fills up qprint - IBM AS400 ; Hi can anyone help me. We have a jboss server installed on as400/iseries, and have created a subsystem to stop and start, using the run.sh file. But the console output is no piped into a file in qprint, and after ...


Fix Unix > Technologies & Tools > Systems > IBM AS400 > jboss console fills up qprint

Reply
 
LinkBack Tools
  #1  
Old 03-03-2008, 08:36 AM
Junior Member
 
Join Date: Sep 2009
Posts: 0
Default jboss console fills up qprint

Hi can anyone help me.

We have a jboss server installed on as400/iseries, and have created a
subsystem to stop and start, using the run.sh file.

But the console output is no piped into a file in qprint, and after
some time it runs full and stops the jboss server, until you allow
more pages or restart the server.

Is there a way to supress the console output, or put it into a dev/
null.

It is possible on unix, but I'm new to the AS400/Iseries world, so I'm
a bit blank how to do it.

Reply With Quote
  #2  
Old 03-03-2008, 10:59 AM
Junior Member
 
Join Date: Sep 2009
Posts: 0
Default Re: jboss console fills up qprint

On Mar 3, 8:36*am, sasmussen wrote:
> Hi can anyone help me.
>
> We have a jboss server installed on as400/iseries, and have created a
> subsystem to stop and start, using the run.sh file.
>
> But the console output is no piped into a file in qprint, and after
> some time it runs full and stops the jboss server, until you allow
> more pages or restart the server.
>
> Is there a way to supress the console output, or put it into a dev/
> null.
>
> It is possible on unix, but I'm new to the AS400/Iseries world, so I'm
> a bit blank how to do it.


To start run.sh do you use qsh or pase ?
If so just redirect as you would in unix. /dev/null works too AFAIR.

HTH
Jonathan.
Reply With Quote
  #3  
Old 03-03-2008, 02:11 PM
Junior Member
 
Join Date: Sep 2009
Posts: 0
Default Re: jboss console fills up qprint

il 03/03/2008 9.36, Scrive sasmussen 40437696:
> Hi can anyone help me.
>
> We have a jboss server installed on as400/iseries, and have created a
> subsystem to stop and start, using the run.sh file.
>
> But the console output is no piped into a file in qprint, and after
> some time it runs full and stops the jboss server, until you allow
> more pages or restart the server.
>
> Is there a way to supress the console output, or put it into a dev/
> null.
>
> It is possible on unix, but I'm new to the AS400/Iseries world, so I'm
> a bit blank how to do it.
>

It's matter of JVM stdout and stderr properties at start-up, as any
other java application.
By default stdout and stderr will output on two distinct QPRINT spooled
files, to avoid you should start jboss with e.g.:
-Dstdout=file:///home/jboss/stdout.log
-Dstderr=file:///home/jboss/stderr.log
(or another url as file:///dev/null to lose any output).
unless you have mean to activate Jboss logging elsewhere.

--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñe joAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'
Reply With Quote
  #4  
Old 03-03-2008, 03:29 PM
Junior Member
 
Join Date: Sep 2009
Posts: 0
Default Re: jboss console fills up qprint

On Mar 3, 2:36*am, sasmussen wrote:
> Hi can anyone help me.
>
> We have a jboss server installed on as400/iseries, and have created a
> subsystem to stop and start, using the run.sh file.
>
> But the console output is no piped into a file in qprint, and after
> some time it runs full and stops the jboss server, until you allow
> more pages or restart the server.
>
> Is there a way to supress the console output, or put it into a dev/
> null.
>
> It is possible on unix, but I'm new to the AS400/Iseries world, so I'm
> a bit blank how to do it.


chgprtf qprint records(*nomax) then either use the calendar thingie to
dltf or write a little autostart cl program to dlt the outfile every
so often.
Reply With Quote