DO NOT REPLY [Bug 30164] New: - compile jk/jk2 source under SCO OpenServer 5.0.6, not ok

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30164

compile jk/jk2 source under SCO OpenServer 5.0.6, not ok

   Summary: compile jk/jk2 source under SCO OpenServer 5.0.6, not ok
   Product: Tomcat 5
   Version: 5.0.25
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Native:JK
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Making  in server/apache2
gmake[1]: Entering directory `/tmp/jakarta-tomcat-connectors-jk2-2.0.4-
src/jk/na
tive2/server/apache2'
/tmp/httpd-2.0.50/srclib/apr/libtool  --mode=compile gcc  -g -O2-DSCO5 -
D_RE
ENTRANT   -I../../include -I/tmp/httpd-2.0.50/include -I/tmp/httpd-
2.0.50/os/uni
x -g -O2 -I/tmp/httpd-2.0.50/srclib/apr-util/include -I/tmp/httpd-
2.0.50/srclib/
apr/include   -DCHUNK_SIZE=4096 -DUSE_APACHE_MD5   -c ../../common/jk_channel.c
-o ../../../build/jk2/apache2/jk_channel.lo
rm -f ../../../build/jk2/apache2/.libs/jk_channel.lo
gcc -g -O2 -DSCO5 -D_REENTRANT -I../../include -I/tmp/httpd-2.0.50/include -
I/tm
p/httpd-2.0.50/os/unix -g -O2 -I/tmp/httpd-2.0.50/srclib/apr-util/include -
I/tmp
/httpd-2.0.50/srclib/apr/include -DCHUNK_SIZE=4096 -DUSE_APACHE_MD5 -
c ../../com
mon/jk_channel.c  -fPIC -DPIC -o ../../../build/jk2/apache2/.libs/jk_channel.lo
In file included from ../../include/jk_global.h:117,
from ../../include/jk_pool.h:25,
from ../../include/jk_map.h:26,
from ../../common/jk_channel.c:23:
/usr/include/sys/socketvar.h:54: field `so_proto' has incomplete type
/usr/include/sys/socketvar.h:73: syntax error before `mblk_t'
/usr/include/sys/socketvar.h:73: warning: no semicolon at end of struct or 
union
/usr/include/sys/socketvar.h:73: warning: no semicolon at end of struct or 
union
/usr/include/sys/socketvar.h:74: warning: data definition has no type or 
storage
class
/usr/include/sys/socketvar.h:75: syntax error before `*'
/usr/include/sys/socketvar.h:75: warning: data definition has no type or 
storage
class
/usr/include/sys/socketvar.h:91: syntax error before `}'
/usr/include/sys/socketvar.h:91: warning: data definition has no type or 
storage
class
/usr/include/sys/socketvar.h:195: syntax error before `queue_t'
/usr/include/sys/socketvar.h:195: warning: no semicolon at end of struct or 
unio
n
/usr/include/sys/socketvar.h:202: syntax error before `*'
/usr/include/sys/socketvar.h:202: warning: data definition has no type or 
storag
e class
/usr/include/sys/socketvar.h:209: syntax error before `}'
gmake[1]: *** [../../../build/jk2/apache2/jk_channel.lo] Error 1
gmake[1]: Leaving directory `/tmp/jakarta-tomcat-connectors-jk2-2.0.4-
src/jk/nat
ive2/server/apache2'
gmake: *** [jk2-build] Error 1

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 30115] - Sessions are Not expiring even when I restart the Tomcat

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30115

Sessions are Not expiring even when I restart the Tomcat





--- Additional Comments From [EMAIL PROTECTED]  2004-07-17 07:42 ---
Hello,

no problem:



regards
Peter
PS: Please,
 ask user questions as tomcat user mailing list...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.next] Progress

[Filip Hanik \(lists\)]

hi Remy,
Time will open up in a week or so. And yes, I am wide open to any ideas.
My personal feeling about the farm deployer, is that it would work exactly
like auto deployment to Tomcat, and maybe just an entry in web.xml makes it
send to other servers.
I do need a temp directory to store the fragments of data sent across the
wire, so that we don't take up too much RAM.

Let me put together a todo list for review next week!

Filip

-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 15, 2004 12:11 PM
To: Tomcat Developers List
Subject: Re: [5.next] Progress


My updated TODO. So I'll do the deployer next, followed by trying to
optimize startup time.
Then, there's tweaking.

Filip, do you have time to refactor the clustering soon ? I think we
should tweak your farming feature as well, as it should likely be done
the way the manager servlet is (rather, will be) doing its stuff. The
idea is to have only one big entry point for deployments, rather than
have 20 different components calling various deploy methods (which is
impossible to maintain). I need to write some code and experiment, and
then I'll have a clearer view of what this refactoring will look like
(sorry, it's just a little too messy right now for me to enumerate the
list of changes).

- Attempt to redo a bit the deployer:
   * remove the CL code which is there to avoid JAR locking (or at least
allow disabling this feature for non-Windows OSes); when enabling anti
locking
code, move everything to a temp "deploy" folder where everything will be
referenced from; controlled by a "development" flag on the Context to allow
disabling this on Windows
   * move processing of context.xml to StandardContext (at the expense of
being able to specify the context class, which will move to an attribute
on the Host), as I realize it is important to get context level
configurability without adding too much complexity in the embedding
application; this could also go in ContextConfig, but this should be done in
another event (START occurs too late)
- Use the webapp CL as the main CL (without the locking tricks it is likely
faster than the regular CL)
- Resolve DBCP -> Pool -> Collections dependency, using package renaming
- Remove anything useless (spring cleaning time), such as configuration
options, container listeners (to be replaced with JMX notifications where
it matters), etc
- clutering module refactoring, to extend the regular Catalina objects, for
easier future maintenance
- Possibly require JDK 1.5 (cleaner code, annotations, integrated JMX
and JMX
remote, etc)
- Externalize configuration saving out of StandardServer
- And the ongoing: allow all config/management through JMX (actually, we
could consider going to a JMX config format)

Rémy


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.713 / Virus Database: 469 - Release Date: 6/30/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.721 / Virus Database: 477 - Release Date: 7/16/2004


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [5.next] Progress

[Remy Maucherat]

Filip Hanik (lists) wrote:
hi Remy,
Time will open up in a week or so. And yes, I am wide open to any ideas.
My personal feeling about the farm deployer, is that it would work exactly
like auto deployment to Tomcat, and maybe just an entry in web.xml makes it
send to other servers.
Yes for the first part. I think it's misleading to call that the 
autodeployer, though, as that component will become the deployer (the 
deployment code is spread and duplicated right now, so the spaghetti 
needs to go).

For the second part, I don't understand. This seems to hint at the 
existence of a master node, which would be bad, no ?

I do need a temp directory to store the fragments of data sent across the
wire, so that we don't take up too much RAM.
I don't get that sent data thing, but you can use either the workdir or 
the tempdir (as usual).

Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 29938] - cygwin windows dirs treated as path vars instead of dirs (includes PATCH)

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29938

cygwin windows dirs treated as path vars instead of dirs (includes PATCH)





--- Additional Comments From [EMAIL PROTECTED]  2004-07-17 18:57 ---
actually noticed that JSSE_HOME needs to be updated too. Here's the new patch:

$ diff catalina-new.sh catalina-1.14.sh
75c75
<   [ -n "$JSSE_HOME" ] && JSSE_HOME=`cygpath --unix "$JSSE_HOME"`
---
>   [ -n "$JSSE_HOME" ] && JSSE_HOME=`cygpath --path --unix "$JSSE_HOME"`
117,120c117,120
<   JAVA_HOME=`cygpath --absolute --windows "$JAVA_HOME"`
<   CATALINA_HOME=`cygpath --absolute --windows "$CATALINA_HOME"`
<   CATALINA_BASE=`cygpath --absolute --windows "$CATALINA_BASE"`
<   CATALINA_TMPDIR=`cygpath --absolute --windows "$CATALINA_TMPDIR"`
---
>   JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
>   CATALINA_HOME=`cygpath --path --windows "$CATALINA_HOME"`
>   CATALINA_BASE=`cygpath --path --windows "$CATALINA_BASE"`
>   CATALINA_TMPDIR=`cygpath --path --windows "$CATALINA_TMPDIR"`
122c122
<   JSSE_HOME=`cygpath --absolute --windows "$JSSE_HOME"`
---
>   JSSE_HOME=`cygpath --path --windows "$JSSE_HOME"`

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 30168] New: - warning message needed when workers2.properties not found

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30168

warning message needed when workers2.properties not found

   Summary: warning message needed when workers2.properties not
found
   Product: Tomcat 4
   Version: 4.1.30
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:Coyote JK 2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Starting Apache without a proper location for the workers2.properties file
produces no warning message.  Instead, the JK2 module reports cryptic errors:

[Fri Jul 16 22:14:11 2004] [info] Server: Apache/2.0.49, Interface:
mod_ssl/2.0.49, Library: OpenSSL/0.9.7c
[Fri Jul 16 22:14:11 2004] [notice] Apache/2.0.49 (Debian GNU/Linux)
mod_jk2/2.0.4 mod_ssl/2.0.49 OpenSSL/0.9.7c mod_webapp/1.2.0-dev configured --
resuming normal operations
[Fri Jul 16 22:14:11 2004] [info] Server built: Apr  4 2004 14:31:19
[Fri Jul 16 22:14:11 2004] [error] uriEnv.init() map to invalid worker
/jkstatus/* status:
[Fri Jul 16 22:14:11 2004] [error] uriEnv.init() map to invalid worker
/jkstatus/* status:

(Adding an absolute location makes the difference, e.g.:

JkSet config.file /etc/apache2/workers2.properties

and the errors go away.)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [5.next] Progress

[Filip Hanik \(lists\)]

This is how it works currently.
There is a "listen" directory. If you deploy an app to any of the nodes on
the cluster, into the listen directory,
it will deploy that app to the other nodes in the cluster. It deploys it
into a "deployed" dir, if an app is removed from that dir, a message is
broadcasted to the other nodes to undeploy the app.
So it could work the same way, but use the tomcat dirs instead of new ones.
And yes, the work dir is the place to store the file fragments.
cheerios
Filip

-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 17, 2004 1:05 PM
To: Tomcat Developers List
Subject: Re: [5.next] Progress


Filip Hanik (lists) wrote:
> hi Remy,
> Time will open up in a week or so. And yes, I am wide open to any ideas.
> My personal feeling about the farm deployer, is that it would work exactly
> like auto deployment to Tomcat, and maybe just an entry in web.xml makes
it
> send to other servers.

Yes for the first part. I think it's misleading to call that the
autodeployer, though, as that component will become the deployer (the
deployment code is spread and duplicated right now, so the spaghetti
needs to go).

For the second part, I don't understand. This seems to hint at the
existence of a master node, which would be bad, no ?

> I do need a temp directory to store the fragments of data sent across the
> wire, so that we don't take up too much RAM.

I don't get that sent data thing, but you can use either the workdir or
the tempdir (as usual).

Rémy


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.721 / Virus Database: 477 - Release Date: 7/16/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.721 / Virus Database: 477 - Release Date: 7/16/2004


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

about JSR 116 SIP Servlet

[KASAI Hiroyoshi]

Hi, tomcat folks.

I am interested in Jain SIP Servlet (JSR 116).
They say telephony and web applications are going to converse each other,
such one very simple example is 'Click to call'.

Apache Software Foundation(who?) voted YES to JSR 116 as the JCP executive committee.

How do you think about supporting SIP Serlet? 
Or already going on?
--
KASAI Hiroyoshi (FAMILY Given)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]