mod jk2 problem, segmetation fault
Hi there,
I have a problem with integrating tomcat and apache using jk2.
System configuration: suse 8.1
apache 1.3.26
tomcat 4.1.24
Correct me if I am wrong, but to establish link bw. apache and tomcat I
need to:
- add a connector in server.xml
Connector acceptCount=10 bufferSize=2048
className=org.apache.ajp.tomcat4.Ajp13Connector
port=8009 minProcessors=5 maxProcessors=75 debug=0
enableLookups=true
Factory
className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
- load jk2 module in httpd.conf
- configure workers2.properties
[shm]
file=/srv/www/logs/jk2.shm
[channel.socket:192.168.230.14:8009]
info=Ajp13 forwarding over socket
tomcatId=192.168.230.14:8009
[uri:/examples/*]
info=Map the whole webapp
- configure jk2.properties
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
shm.file=/srv/www/logs/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
It seems that in tomcat everything is fine (catalina.out after starting
tomcat ends with:
2003-07-01 17:24:33 HttpConnector[8443] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][0] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][1] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][2] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][3] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][4] Starting background thread
2003-07-01 17:24:34 Ajp13Connector[8009] Opening server socket on all host
IP addresses
2003-07-01 17:24:34 Ajp13Connector[8009] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][0] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][1] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][2] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][3] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][4] Starting background thread
However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (292)]: mod_jk.post_config()
init worker env
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (320)]: cfg.update()
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:08 2003] ( info) [jk_workerEnv.c (403)]:
workerEnv.init() ok /srv/www//conf/workers2.properties
Create config for main host
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (292)]: mod_jk.post_config()
init worker env
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (320)]: cfg.update()
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:09 2003] ( info) [jk_workerEnv.c (403)]:
workerEnv.init() ok /srv/www//conf/workers2.properties
[Tue Jul 1 16:47:10 2003] [notice] Apache/1.3.26 (Linux/SuSE)
mod_jk2/2.0.0 configured -- resuming normal operations
[Tue Jul 1 16:47:10 2003] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Tue Jul 1 16:47:10 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
Finally when I try to open a page from tomcat without specifying port 8080
in apache a following error is added:
[Tue Jul 1 16:47:49 2003] [notice] child pid 16282 exit signal
Segmentation fault (11)
While in tomcat there is no information, that some page was requested.
Does anyone have any idea what is causing this Segmentation fault?
Regards,
Przemek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
RE: mod jk2 problem, segmetation fault
Howdy,
However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (284)]: mod_jk child
init
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (292)]:
mod_jk.post_config()
init worker env
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't
open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (320)]:
cfg.update()
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't
open
log file ${serverRoot}/logs/mod_jk.log
Stop. You might be in better shape if you can actually write to the log
file.
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
Step 1 is unnecessary.
Tomcat comes with a JK2 compatible connector enabled by default on port
8009. The class name for this connector is CoyoteConnector.
Ajp13Connector is for JK and is incompatible with JK2...it will never work.
If you need to use JK2, you don't need to do anything to server.xml except
make sure your Hosts and your Contexts are correct, everything else is done
on the Apache configuration side.
I don't know of any JK2 binaries for SuSe, so unless you built your own, I
would say your problem is a combination of an incompatible Apache module
and the configuration of Ajp13Connector.
Also, I am still not clear on the compatibility of JK2 (mod_jk2) with
Apache 1.x. My guess is you would be better off with mod_jk (JK).
John
On Tue, 01 Jul 2003 17:52:18 +0200, Przemys³aw Korona
[EMAIL PROTECTED] wrote:
Hi there,
I have a problem with integrating tomcat and apache using jk2.
System configuration: suse 8.1
apache 1.3.26
tomcat 4.1.24
Correct me if I am wrong, but to establish link bw. apache and tomcat I
need to:
- add a connector in server.xml
Connector acceptCount=10 bufferSize=2048
className=org.apache.ajp.tomcat4.Ajp13Connector port=8009
minProcessors=5 maxProcessors=75 debug=0 enableLookups=true
Factory className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
- load jk2 module in httpd.conf
- configure workers2.properties
[shm]
file=/srv/www/logs/jk2.shm
[channel.socket:192.168.230.14:8009]
info=Ajp13 forwarding over socket
tomcatId=192.168.230.14:8009
[uri:/examples/*]
info=Map the whole webapp
- configure jk2.properties
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
shm.file=/srv/www/logs/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
It seems that in tomcat everything is fine (catalina.out after starting
tomcat ends with:
2003-07-01 17:24:33 HttpConnector[8443] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][0] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][1] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][2] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][3] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][4] Starting background thread
2003-07-01 17:24:34 Ajp13Connector[8009] Opening server socket on all
host IP addresses
2003-07-01 17:24:34 Ajp13Connector[8009] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][0] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][1] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][2] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][3] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][4] Starting background thread
However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (292)]:
mod_jk.post_config() init worker env
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (320)]:
cfg.update() Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:08 2003] ( info) [jk_workerEnv.c (403)]:
workerEnv.init() ok /srv/www//conf/workers2.properties
Create config for main host
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (292)]:
mod_jk.post_config() init worker env
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (320)]:
cfg.update() Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:09 2003] ( info) [jk_workerEnv.c (403)]:
Re: mod jk2 problem, segmetation fault
Thank you all, for your quick responses. Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. You mean: org.apache.coyote.tomcat4.CoyoteConnector ? If you need to use JK2, you don't need to do anything to server.xml except make sure your Hosts and your Contexts are correct, everything else is done on the Apache configuration side. I guess I have this part ok, because on port 8080 it works fine. I don't know of any JK2 binaries for SuSe, so unless you built your own, I would say your problem is a combination of an incompatible Apache module and the configuration of Ajp13Connector. This apache module is jk2_mod.so? Should I compile it from the source? Also, I am still not clear on the compatibility of JK2 (mod_jk2) with Apache 1.x. My guess is you would be better off with mod_jk (JK). John It seems that I just have chosen a wrong tool. I just hope, this mod_jk works with ssl (documentation says it should ;-)) Thanks again Przemek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
On Tue, 01 Jul 2003 18:27:47 +0200, Przemys³aw Korona [EMAIL PROTECTED] wrote: Thank you all, for your quick responses. Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. You mean: org.apache.coyote.tomcat4.CoyoteConnector ? Right on. If you need to use JK2, you don't need to do anything to server.xml except make sure your Hosts and your Contexts are correct, everything else is done on the Apache configuration side. I guess I have this part ok, because on port 8080 it works fine. Right on...just make sure that there is a CoyoteConnector listening on 8009 (default) or any other port that you wish to use. When you are in production, you can disable the connector on 8080. It seems that I just have chosen a wrong tool. I just hope, this mod_jk works with ssl (documentation says it should ;-)) Thanks again Przemek JK should work fine with SSL...in an Apache + Connector + Tomcat environment, Apache does all of the SSL heavy-lifting. Communications between Apache and Tomcat via mod_jk and mod_jk2 are done without SSL. So, you just need to focus on getting Apache doing your SSL. If you need a HOWTO, check out mine: http://www.johnturner.com/howto They're for Red Hat, and Apache 2, but the steps are the same. The only differences would be which mod_jk.so file you use for Apache 1.3 on SuSE. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Howdy, Actually I have found this not to be true (the part about you can use any port). There is some kind of limitation on how high the port you use can be. For example: 8009 works 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
John Turner wrote: Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. Ajp13Connector is for JK and is incompatible with JK2...it will never work. Whoa! I couldn't get the CoyoteConnector to work with 4.0.4 (I got errors in catalina.out about the CoyoteConnector not being found), but the Ajp13Connector behaved fine with JK2 - at least I *thought* - we *have* had some odd things going on with Tomcat 4.0.4 lately, but attributed that to trying too many upgrades at one time (like JDK 1.3 - JDK 1.4, upgrade of an EDBC driver) as we didn't see anything obvious in any Tomcat or Apache logs...I can see (thru ps -ef) when Tomcat and/or Apache are/is running, and from the messages in the various logs, it appears things are working right, but...what would I see that might tell me that there was a problem with Ajp13Connector? Thanks! -- Lynn Hollerman. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Hi, 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. You got it. :) 32767 yes, 32768 no. So is this still a bug? or is this a workaround? -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Howdy, Well, that provided a bit of amusement for today ;) ;) You can put in an enhancement request to use 32bits for the port number. It's a low-priority item, not sure it will be done any time soon. Yoav Shapira 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. You got it. :) 32767 yes, 32768 no. So is this still a bug? or is this a workaround? This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;) In any case, my point (perhaps not clearly stated) was that: 1) there is no need to do anything in server.xml to allow a default Tomcat install to work with one of the connectors 2) Ajp13Connector is not the preferred connector for either JK or JK2 in recent versions of Tomcat ( 4.1.12?) There's bound to be people that have unusual/uncommon environments that work...but for people just getting started, I think its less traumatic to guide them towards the usual/common environments until they get some experience. John On Tue, 01 Jul 2003 12:32:12 -0500, Geralyn M Hollerman [EMAIL PROTECTED] wrote: John Turner wrote: Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. Ajp13Connector is for JK and is incompatible with JK2...it will never work. Whoa! I couldn't get the CoyoteConnector to work with 4.0.4 (I got errors in catalina.out about the CoyoteConnector not being found), but the Ajp13Connector behaved fine with JK2 - at least I *thought* - we *have* had some odd things going on with Tomcat 4.0.4 lately, but attributed that to trying too many upgrades at one time (like JDK 1.3 - JDK 1.4, upgrade of an EDBC driver) as we didn't see anything obvious in any Tomcat or Apache logs...I can see (thru ps -ef) when Tomcat and/or Apache are/is running, and from the messages in the various logs, it appears things are working right, but...what would I see that might tell me that there was a problem with Ajp13Connector? Thanks! -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;) It works *sorta*. It connects and passes data but some freakish things happen once in a while. We had a problem with this configuration (JK2 to Ajp13Connector, that was put in by mistake) and it would do stuff like forget to pass HTTP headers every so often. Wierd stuff like that. -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
Cool, thanks for the confirmation. John On Tue, 1 Jul 2003 15:40:37 -0400 (EDT), Eric J. Pinnell [EMAIL PROTECTED] wrote: I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;) It works *sorta*. It connects and passes data but some freakish things happen once in a while. We had a problem with this configuration (JK2 to Ajp13Connector, that was put in by mistake) and it would do stuff like forget to pass HTTP headers every so often. Wierd stuff like that. -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Hi, For anyone that cares I changed the 'long's to 'unsigned short's with some advice from Jeff Trawick. Still looks good after a some load. It's not being hammered but it looks ok. -e On Tue, 1 Jul 2003, Eric J. Pinnell wrote: Hi, This tweak on jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/common/jk_channel_socket.c seems to fix the high TCP port issue. Alhtough I haven't found any trouble with it yet I have never written anything for JK2 and am unfamiliar with it's inner workings. So I wouldn't bet the farm on it. bash-2.04$ diff jk_channel_socket.c.old jk_channel_socket.c.new 94c94 short port; --- long port; 110c110 short port, --- long port, 204c204 static int JK_METHOD jk2_channel_socket_resolve(jk_env_t *env, char *host, short port, --- static int JK_METHOD jk2_channel_socket_resolve(jk_env_t *env, char *host, long port, -e On Tue, 1 Jul 2003, Shapira, Yoav wrote: Howdy, Well, that provided a bit of amusement for today ;) ;) You can put in an enhancement request to use 32bits for the port number. It's a low-priority item, not sure it will be done any time soon. Yoav Shapira 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. You got it. :) 32767 yes, 32768 no. So is this still a bug? or is this a workaround? This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
