Re: TC 4.1.3: JK2 connector dies?

[Liam Morley <lm...@gdc.wpi.edu>]

  I'm not sure if the port is my problem or not (and if everything is 
using the same port, would it matter which one it was?), but as far as 
the port goes, I get the following two lines in my jk2.properties.save 
document:

port=8019
channelSocket.port=8009

Port = 8019 regardless of what's in jk2.properties, workers2.properties, 
or server.xml (channelSocket.port is equal to whatever's in 
jk2.properties, I think). have I have no idea where "port=8019" is 
coming from, as I searched for any document under Apache (both httpd and 
tomcat) that contains the string '8019'; the search came up with 
nothing. I'd be curious to know where it came from.. I plan on 
downloading the connectors source soon and looking into that when I have 
time.

Other than that, I have a few jk2 log questions I'd like to iron out.

why is this an error: "[error] workerEnv.init() create default worker 
lb:lb" It has an "info" or "debug" sound to it, unless creating a worker 
is a bad thing. this shows up every time tomcat starts up, located in 
between a few notices. Are other people getting this as well? I'm also 
getting a LOT of [warn]s that look like info or debug messages. For example:
[warn] config.setConfig():  process uriMap:
[warn] config: set uriMap: / info / 63e7b0 / uriMap:.info = Maps the 
requests.
Of course I can set the log level higher to avoid these messages, but 
what am I supposed to be warned about?
After I make a request to http://localhost/my_webapp/, I get the 
following errors and warns:
[error] ajp13.service() error sending, reconnect 
channel.socket:localhost:8019 -1 9 Bad file descriptor
[warn] workerEnv.callbacks() channel.socket:localhost:8019
[error] msgAjp.receive(): Bad signature 00
[warn] BAD MESSAGE:  pos=4 len=4 max=8300
[error] channelSocket.receive(): Bad header
[error] workerEnv.processCallbacks() Error reading reply
[error] ajp13.service() ajpGetReply unrecoverable error 21000
[warn] ajp13.service() done ajp13:localhost:8019
[warn] endpoint.close() ajp13:localhost:8019
[warn] ajp13.done() close endpoint ajp13:localhost:8019 error_state 0
[warn] ajp13.done() return to pool ajp13:localhost:8019
[error] lb.service() worker failed ajp13:localhost:8019
[error] lb.service() unrecoverable error...
[error] mod_jk.handler() Error connecting to tomcat 21000

It would be nice to know where the "bad message" or "bad file 
descriptor" is.. I suppose that's another thing I'll have to go 
searching for in the source code?

I've also been wondering about the following line in stderr.log:
"INFO: APR not loaded, disabling jni components: java.io.IOException: no 
jkjni in java.library.path"
That sounds bad. I searched the mailing list for prior questions 
involving this, but didn't see any answers.

Let me know if I should post my jk2.properties or workers2.properties 
file if it will help.

Thanks all for your time,
Liam Morley


Ignacio J. Ortega wrote:

>>De: Jacob Kjome [mailto:hoju@visi.com]
>>Enviado el: 27 de junio de 2002 20:23
>>    
>>
>
>  
>
>>default.  If you comment all the stuff out in jk2.properties, Tomcat
>>just generates a jk2.properties.save which has the following for me:
>>    
>>
>
>Good, my statments continue correct.. just checked what is on the dist
>package for 4.1.3, below is pasted, if you do *nothing* i think the port
>is 8019, if you comment it may be it's saved.. i really dont know..
>
>8<----------------------- jk2.properties
>--------------------------------
>## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED
>## WHEN YOU EDIT THE FILE.
>
>## COMMENTS WILL BE _LOST_
>
>## DOCUMENTATION OF THE FORMAT IN JkMain javadoc.
>
># Override the default port for the socketChannel
>channelSocket.port=8019
># Default: 
># channelUnix.file=${jkHome}/work/jk2.socket
># Just to check if the the config  is working
>shm.file=${jkHome}/work/jk2.shm
>
>apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
>8<----------------------- jk2.properties
>--------------------------------
>
>
>
>Saludos ,
>Ignacio J. Ortega
>
>
>  
>
>>-----Mensaje original-----
>>Para: Tomcat Users List
>>Asunto: Re[2]: TC 4.1.3: JK2 connector dies? cant get isapi_redirector
>>to t alkto tomcat
>>
>>
>>Hello Ignacio,
>>
>>I don't think yours statement that jk2.properties is on port 8019 by
>>
>>#AUTOMATICALLY GENERATED
>>#Tue Jun 25 11:09:03 CDT 2002
>>maxThreads=75
>>port=8009
>>soTimeout=20000
>>jkHome=C\:\\Progra~1\\Apache~1\\Jakarta\\tomcat-4.1.3
>>tcpNoDelay=true
>>timeout=20000
>>secure=false
>>backlog=10
>>
>>I think it generated all that based on what was defined in the Coyote
>>jk2 connector.
>>
>>Jake
>>
>>Thursday, June 27, 2002, 12:19:38 PM, you wrote:
>>
>>    
>>
>>>>De: Mark Prins [mailto:Mark.Prins@caris.nl]
>>>>Enviado el: 27 de junio de 2002 16:38
>>>>        
>>>>
>>>>I'm not sure I understand, but in my server.xml the connector 
>>>>is specified
>>>>as listening to 8009, so how's that?
>>>>        
>>>>
>>IJO> Please post the log you get when starting tomcat just to 
>>be sure..
>>
>>IJO> What i say is that by default the Coyote/JK2 ajp13 port 
>>is 8019 no 8009,
>>IJO> regarles of what is on server.xml, because jk2 uses 
>>jk2.propeties in
>>IJO> addition to server.xml, and there by default the JK2 
>>port is 8019..
>>
>>IJO> To be able to use isapi_redirector.dll with jk2 you 
>>shopuld change the
>>IJO> por in workers.properties for ajp13 to 8019..
>>
>>IJO> Saludos ,
>>IJO> Ignacio J. Ortega
>>
>>IJO> --
>>IJO> To unsubscribe, e-mail:   
>><ma...@jakarta.apache.org>
>>IJO> For additional commands, e-mail: 
>><ma...@jakarta.apache.org>
>>
>>
>>
>>-- 
>>Best regards,
>> Jacob                            mailto:hoju@visi.com
>>
>>
>>--
>>To unsubscribe, e-mail:   
>><ma...@jakarta.apache.org>
>>For additional commands, e-mail: 
>><ma...@jakarta.apache.org>
>>
>>
>>    
>>
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
>  
>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>