Re: Bug or Feature inside mod_jk loadbalancer algo?

[Peter Rossbach]

Sounds good to me.

Wrote a spec before implementation is very helpfull :-)

The domain case with sticky session and real clustered szenarios  is  
not easy.


Peter

Mladen Turk schrieb:


Peter Rossbach wrote:


Hey,

I have a strange loadbalancer behaviour at a customer site with 
Apache 2/mod_jk 1.2.14, JVM 1.5, Tomcat 5.5.9 (cluster), (Suse 9.1)




Hi guys,

Peter you are correct about this...
I found by myself too, that balancer is misbehaving in some cases.
One of them is 'domain' model, where multiple workers should behave
like one on the global scale, but still maintain internal load.

The other is for worker-like mpm's when cachesize is lower then
the ThreadsPerChild. I've been able to fix that (sort of), but I'm
not happy with the fix.

What would I suggest is that we gather all the 'use cases' and
write down what the predicted results should be.

I'll create a separate .txt file (that will later be part of
loadbalancer howto) upon which we can enter the configuration
and expected behavior.

How that sounds?

I'm moving this discussion to the tomcat-dev@, so that we have the
trace of it. OK?

Regards,
Mladen.

-
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]

Re: Releasing JK 1.2.15

[Peter Rossbach]

Hey Mladen,

can we also integrate the better domain loadbalancer support at 
jk_lb_worker.c?
I think that we don't change the lb_value inside sticky mode at every 
request.

Can we comment out or remove lines L413-431?

Thanks,
Peter

Mladen Turk schrieb:


There has been couple of major bug fixes
against 1.2.14, see:
http://jakarta.apache.org/tomcat/connectors-doc/changelog.html

They have been fixed in the CVS, and since
couple of them actually makes 1.2.14 unusable on
some platforms like Solaris 2.8 and Irix we need a release.

I plan to tag the 1.2.15 by the end of this week, and pursue
for a vote next week for this bug-fixing release.

Any objections?



Since there were no objections I plan to tag the 1.2.15 later this
evening at 19:00 GMT.

This will eventually be the last release from CVS, cause IIUC the
transition will be made this weekend.


Regards,
Mladen.

-
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]

Re: Releasing JK 1.2.15

[Peter Rossbach]

Yes,

is is only a real problem when workers are grouped inside an domain. I have
check this many times and without the lb_value change loadbalancing works as
I aspected, and with it not.
I also think that we need a real lb concept check. Greater changes can 
we better realize after jk 2.1.15.
But this little change was very helpful at some of my production 
customers sites :-)


Peter

Mladen Turk schrieb:


Peter Rossbach wrote:


Hey Mladen,

can we also integrate the better domain loadbalancer support at 
jk_lb_worker.c?
I think that we don't change the lb_value inside sticky mode at every 
request.



Yes we do. They will be updated only for domain workers.
This is needed to load balance between the workers that are
members of the same domain. In other case the total_factor will
be zero and lb_value will not be changed.


Regards,
Mladen.



-
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]

Re: [VOTE] 5.5.12 Stability

[Peter Rossbach]

Tested with Mac OS (10.4) , Win32 and Suse 9.3 prof.


Tomcat 5.5.12 is:
[x] Stable - no major issues,
[ ] Beta - at least one major issue: what is it?
[ ] Alpha - multiple things or a real showstopper: please provide details..

 




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

Please describe the new Logger System at cvs head.

[Peter Rossbach]

Hello Remy,
I have problems to configure the new logger system.
Can you send a log4J example to demonstrate the new commons-log Logger 
concept.

How I can configure a log4J system?
I have no success with add log4j.jar and log4j.xml to system class path 
via setclasspath.bat
set 
CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BASEDIR%\bin\log4j.jar;%BASEDIR%\bin

I see only the commons logging default messages.
Only my webapp find the log4j.jar and log4j.xml at my common/lib and 
common/classes
But I want see the server messages

The Logger names are:
Tomcat.
Tomcat..
Tomcat...
correct?
Regards
peter

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

Re: Please describe the new Logger System at cvs head.

[Peter Rossbach]

Hello Remy,
which logging system you used?
I thing every host and application can have there own logging devices.
My problem is:
   How can I configure dymamic logging device at runtime?
   For every new host or application
With the old server.xml Logger element this was easy, but now you must known
there concrete server technic log4j, JDK 1.4 or what ever
>>
The c-l-api JAR which is in bin doesn't include the log4j wrapper, this 
could be the cause of the problems.
>>
You mean, that I must add the commons-logging.jar to system-class path?
Ohh, then I must changed the META-INF from bootstrap.jar, right?

regards
Peter
PS: Some people (book writer)  must be the early birds :-)
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hello Remy,
I have problems to configure the new logger system.
Can you send a log4J example to demonstrate the new commons-log 
Logger concept.

How I can configure a log4J system?
I have no success with add log4j.jar and log4j.xml to system class 
path via setclasspath.bat
set 
CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BASEDIR%\bin\log4j.jar;%BASEDIR%\bin 

I see only the commons logging default messages.
Only my webapp find the log4j.jar and log4j.xml at my common/lib and 
common/classes
But I want see the server messages

The Logger names are:
Tomcat.
Tomcat..
Tomcat...
correct?

There's no difference with using log4j with the current Tomcat 5.0.x 
(which I've never done, sorry), except that there are a few more 
categories.
The c-l-api JAR which is in bin doesn't include the log4j wrapper, 
this could be the cause of the problems.

It's funny to always see you looking for trouble with odd builds ;)
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: Please describe the new Logger System at cvs head.

[Peter Rossbach]

Hello Remy,
I have made a deeper look at the current cvs logger code stage:
1) ContainerBase.getLogger()
With first getLogger call the Log was build with a strange name!
   public Log getLogger() {
   if (logger != null)
   return (logger);
   String loggerName = null;
   Container current = this;
   while (current != null) {
   loggerName = "[" + current.getName() + "]"
   + ((loggerName != null) ? ("." + loggerName) : "");
   current = current.getParent();
   }
   logger = LogFactory.getLog("Tomcat." + loggerName);
   return (logger);
   }
I think this can be done at init().
head
Context loggerTomcat.[context].[host].[engine]
Host.logger Tomcat.[host].[engine]
Engine.Logger Tomcat.[engine]
Strange syntax...
other convention?:
Context loggerTomcat.Logger...
  Tomcat.Logger...ROOT
Host.logger Tomcat.Logger..
Engine.Logger Tomcat.Logger.
Current getLogger method not handle ROOT Context!
2) StandardContext.start()
   L4051..
   String logName = "tomcat." + getParent().getName() + "." +
   ("".equals(getName()) ? "ROOT" : getName()) + ".Context";
   log = org.apache.commons.logging.LogFactory.getLog(logName);
Hmm.
Why the complete init() phase goes to Log with name 
StandardContext.class and
after start all logging goes to "tomcat..Context" ?

  other name convention Tomcat.Context.
I thing we must do that, before any code from StandardContext generate 
log message.
The CatalinaBase use "Tomcat" and StandarContext used "tomcat" with 
lowercase...

I hope this analyse help to refactor more :-(
regards
peter
Peter Rossbach schrieb:
Hello Remy,
which logging system you used?
I thing every host and application can have there own logging devices.
My problem is:
   How can I configure dymamic logging device at runtime?
   For every new host or application
With the old server.xml Logger element this was easy, but now you must 
known
there concrete server technic log4j, JDK 1.4 or what ever

>>
The c-l-api JAR which is in bin doesn't include the log4j wrapper, 
this could be the cause of the problems.
>>
You mean, that I must add the commons-logging.jar to system-class path?
Ohh, then I must changed the META-INF from bootstrap.jar, right?

regards
Peter
PS: Some people (book writer)  must be the early birds :-)
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hello Remy,
I have problems to configure the new logger system.
Can you send a log4J example to demonstrate the new commons-log 
Logger concept.

How I can configure a log4J system?
I have no success with add log4j.jar and log4j.xml to system class 
path via setclasspath.bat
set 
CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BASEDIR%\bin\log4j.jar;%BASEDIR%\bin 

I see only the commons logging default messages.
Only my webapp find the log4j.jar and log4j.xml at my common/lib and 
common/classes
But I want see the server messages

The Logger names are:
Tomcat.
Tomcat..
Tomcat...
correct?

There's no difference with using log4j with the current Tomcat 5.0.x 
(which I've never done, sorry), except that there are a few more 
categories.
The c-l-api JAR which is in bin doesn't include the log4j wrapper, 
this could be the cause of the problems.

It's funny to always see you looking for trouble with odd builds ;)
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: Please describe the new Logger System at cvs head.

[Peter Rossbach]

Hello Remy,
with your Logger naming convention log4j not working
log4j:ERROR Parsing error on line 57 and column 99
log4j:ERROR Attribute value 
"org.apache.catalina.core.CatalinaBase.[].[localhost
].[Catalina]" of type ID must be a name.

With this logger naming convention it works fine:
org.apache.catalina.core.ContainerBase.Catalina.localhost.ROOT
Patch
Index: catalina/src/share/org/apache/catalina/core/ContainerBase.java
===
RCS file: 
/home/cvspublic/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/ContainerBase.java,v
retrieving revision 1.36
diff -u -r1.36 ContainerBase.java
--- catalina/src/share/org/apache/catalina/core/ContainerBase.java24 
Jun 2004 15:28:27 -1.36
+++ catalina/src/share/org/apache/catalina/core/ContainerBase.java24 
Jun 2004 16:49:23 -
@@ -36,18 +36,7 @@
import javax.naming.directory.DirContext;
import javax.servlet.ServletException;

-import org.apache.catalina.Cluster;
-import org.apache.catalina.Container;
-import org.apache.catalina.ContainerEvent;
-import org.apache.catalina.ContainerListener;
-import org.apache.catalina.Lifecycle;
-import org.apache.catalina.LifecycleException;
-import org.apache.catalina.LifecycleListener;
-import org.apache.catalina.Loader;
-import org.apache.catalina.Manager;
-import org.apache.catalina.Pipeline;
-import org.apache.catalina.Realm;
-import org.apache.catalina.Valve;
+import org.apache.catalina.*;
import org.apache.catalina.connector.Request;
import org.apache.catalina.connector.Response;
import org.apache.catalina.util.LifecycleSupport;
@@ -1288,17 +1277,23 @@
}
String loggerName = null;
Container current = this;
+
while (current != null) {
-loggerName = "[" + current.getName() + "]"
+String theName;
+if(current instanceof StandardContext )
+   theName = "".equals(current.getName()) ? "ROOT" : 
current.getName();
+else
+   theName= current.getName();
+loggerName = theName
+ ((loggerName != null) ? ("." + loggerName) : "");
current = current.getParent();
}
logName = ContainerBase.class.getName() + "." + loggerName;
return logName;
-   
+
}

-   
+
//  JMX and Registration  
protected String type;
protected String domain;
@@ -1310,7 +1305,7 @@
public ObjectName getJmxName() {
return oname;
}
-   
+
public String getObjectName() {
if (oname != null) {
return oname.toString();
@@ -1326,7 +1321,7 @@
}
if( parent instanceof StandardEngine ) {
domain=((StandardEngine)parent).getDomain();
-}
+}
}
return domain;
}
@@ -1334,7 +1329,7 @@
public void setDomain(String domain) {
this.domain=domain;
}
-   
+
public String getType() {
return type;
}
@@ -1405,9 +1400,9 @@
Container context=null;
Container host=null;
Container servlet=null;
-   
+
StringBuffer suffix=new StringBuffer();
-   
+
if( container instanceof StandardHost ) {
host=container;
} else if( container instanceof StandardContext ) {
@@ -1421,7 +1416,7 @@
if( context!=null ) {
String path=((StandardContext)context).getPath();
suffix.append(",path=").append((path.equals("")) ? "/" : path);
-}
+}
if( host!=null ) suffix.append(",host=").append( host.getName() );
if( servlet != null ) {
String name=container.getName();

I have fix this and it works





OK, I muss changed the bootstrap.jar META-INF dependcies to 
common-logging.jar instead commons-logging-api-jar
Copy common-logging.jar, log4j.jar and log4.xml to bin
delete commons-logging-api.jar

Change bootstrap.jar Manifest
Manifest-Version: 1.0
Main-Class: org.apache.catalina.startup.Bootstrap
Class-Path: jmx.jar commons-daemon.jar commons-logging.jar
Specification-Title: Catalina
Specification-Version: 1.0
Also change setclasspath.bat
set 
CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BASEDIR%\bin\log4j.jar;%BASEDIR%\bin

..
Only thing that not nice with this patch is new StandardContext dependency!
regards
Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hello Remy,
I have made a deeper look at the current cvs logger code stage:
1) ContainerBase.getLogger()
With first getLogger call the Log was build with a strange name!
   public Log getLogger() {
   if (logger != null)
   return (logger);
   String loggerName = null;
   Container current = this;
   while (current != null) {
   loggerName = "[" + current.getName() + "]"
   + ((

Re: Please describe the new Logger System at cvs head.

[Peter Rossbach]

Hey Remy,
please look at the log4j.dtd
jakarta-log4j-1.2.8\src\java\org\apache\log4j\xml\log4j.dtd
All names from name attributes are from type "ID"
http://www.w3.org/TR/REC-xml/
XML Attribute from type ID can not have this characters "[]"
Please, accept my change or made a log4j.dtd/ XML conform  implementation.
Thanx,
Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hello Remy,
with your Logger naming convention log4j not working
log4j:ERROR Parsing error on line 57 and column 99
log4j:ERROR Attribute value 
"org.apache.catalina.core.CatalinaBase.[].[localhost
].[Catalina]" of type ID must be a name.

With this logger naming convention it works fine:

Sorry, I see nothing in the log4j docs that says that 
"org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[]" 
(BTW, I know who you are now: you really must be Yoda; "Hmmm, a bug I 
think there is") is an invalid logger name.

The replacement name you're proposing is bad, so I won't use it.
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: Please describe the new Logger System at cvs head.

[Peter Rossbach]

Sorry,
Can you configure a correct log4j.xml or log4j.properties with the 
current implementation?

I have spend a lot of time today, but it not working.





The current log4j 1.2.8 Logger.name type is ID not CDATA ...
log4j:ERROR Parsing error on line 58 and column 15
log4j:ERROR The value of attribute "name" associated with an element 
type "logge
r" must not contain the '<' character.
log4j:ERROR Could not parse input source [EMAIL PROTECTED]
org.xml.sax.SAXParseException: The value of attribute "name" associated 
with an
element type "logger" must not contain the '<' character.
   at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
   at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
   at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java
:665)
   at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java
:616)
   at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java
:602)
   at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionCon
verter.java:460)
   at org.apache.log4j.LogManager.(LogManager.java:113)
   at org.apache.log4j.Logger.getLogger(Logger.java:85)
   at 
org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.jav
a:229)
   at 
org.apache.commons.logging.impl.Log4JLogger.(Log4JLogger.java:6
5)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method)

   at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
   at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
   at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactory
Impl.java:529)
   at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:235)
   at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactory
Impl.java:209)
   at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
   at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:53)
log4j:WARN No appenders could be found for logger 
(org.apache.catalina.startup.C
lassLoaderFactory).
log4j:WARN Please initialize the log4j system properly.

---
Also log4j.properties not working
log4j.rootLogger=INFO, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
log4j.appender.catalina=org.apache.log4j.RollingFileAppender
log4j.appender.catalina.File=../logs/catalina-dev.log
log4j.appender.catalina.MaxFileSize=5Mb
log4j.appender.catalina.MaxBackupIndex=10
log4j.appender.catalina.layout=org.apache.log4j.PatternLayout
log4j.appender.catalina.layout.ConversionPattern=%p %t %c - %m%n
log4j.logger.org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[]= 
DEBUG, catalina

---
Currently the Logger Logname ist very long
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[]  ROOT App
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[myapps]  
normal web App

--
with my patch it works.
;-)
.---
Also I thing the the current implementation is not compatible with all 
Tomcat 5 releases
How we want migrate all the current Tomcat projects? How we made Logger 
configuration
at runtime? Hmm. :-(   

regards
Peter
Bill Barker schrieb:
Except that I can't see why you would want to use the
'Tomcat.[].[Catalina].[localhost].[myapp]' name except in a 'category'
element.  Here, the name is defined to be CDATA so you should be fine (or it
is a log4j bug :).
- Original Message -
From: "Peter Rossbach" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, June 24, 2004 11:02 AM
Subject: Re: Please describe the new Logger System at cvs head.
Hey Remy,
please look at the log4j.dtd
jakarta-log4j-1.2.8\src\java\org\apache\log4j\xml\log4j.dtd
All names from name attributes are from type "ID"
http://www.w3.org/TR/REC-xml/
XML Attribute from type ID can not have this characters "[]"
Please, accept my change or made a log4j.dtd/ XML conform  implementation.
Thanx,
Peter
Remy Maucherat schrieb:
 

Peter Rossbach wrote:
   

Hello Remy,
with your Logger naming convention log4j not working
log4j:ERROR Parsing error on line 57 and column 99
log4j:ERROR Attribute value
"org.apache.catalina.core.CatalinaBase.[].[localhost
].[Catalina]" of type ID must be a name.
With this logger naming convention it works fine:
 

Sorry, I see nothing in the log4j docs that says that
"org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[]"
(BTW, I know who you

Re: Please describe the new Logger System at cvs head.

[Peter Rossbach]

Hello Bill and Remy
your log4j example at new doumentation works fine. Thanx!
My fault I use the Logger tag instead the category one.
But that we can't change the Logger config at server.xml is not nice.
The only chance is, declare a Lifecycle Listner or used the Log4J MBean
direct.
Regards
Peter
Bill Barker schrieb:
About logging:
- it is a mistake (nowadays) to define custom loggers in applications
(JBoss doesn't, and yet it's far more complex); of course, an equally
big mistake is to provide "logging" services in the Servlet API ;)
 

This is only a dream. In a hosting enviroment every customer will
logging different. We offer own logfiles with the  configuartion
in the context.xml.
This were broken, if your changes are kept.
My greatest problem is the administration of the log4j configuration.
Where - or better - how can I do this automatically. This question you
don't answer? Is there a discussion done about this problem?
   

Well, the discussion of administering the log4j configuration belongs on
[EMAIL PROTECTED]  However, I'm sure that the Tomcat 5.5 docs
will likely have examples (and, yes, patches are always welcome :).  Either
that, or Ceki is going to be selling a lot of copies of his book ;-).
 

Your logger solution is maybe is well solution for a development or
company-intern-used tomcat installation but the UseCase "Webhosting"
have been ignored. If I must administrate every customer logger manually
this is very counterproductively.
   

Actually, with the JMX support in log4j, I would guess that Remy's changes
will make life much easier for the Webhosting crowd.  If there is interest
(meaning patches :), then the admin webapp could even be extended to help
with the configuration.
 

- the big problem which I want to solve here is that logs are going to
different places, which is wrong; now, all logs should go to
commons-logging (or directly to the actual logger that commons-logging
is wrapping)
 

What do you mean with "different places". If you man different places
the logs will be saved than can I say this is a normal behaviour. In
Germany there is a admin tool called "Confixx". This tool saves the logs
in the home directory of the user. Than the user can view and load his
logs with a normal ftp-client.
Best regards
Thorsten
--
Thorsten Kamann
Email: [EMAIL PROTECTED]
ICQ: 40746578
Yahoo: ThorQue
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   

 


This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.
 


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

--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Proposal: Change HostConfig/Deployer

[Peter Rossbach]

Tomcat 5.5 Proposal:
Adding More Flexibility to Config Listener and Deployer
Peter Roßbach & Frank Wegmann
[EMAIL PROTECTED] 
Date 29.06.2004
Based on 5.0.25/27 CVS Head
Currently, you can automatically deploy, delete or redeploy web 
applications automatically using the classes HostConfig and 
StandardHostDeployer. But this is tied to the single webapps directory.  
However, customer scenarios would benefit from flexible mechanisms that 
allow deployment of applications from different directories or even a 
central HTTP repository. The necessity of a revised deployment 
implementation is further stressed by the new undocumented FarmWar 
Deployer facilitating an automatic cluster deployment. Here, with the 
introduction of a StandardHostDeployer variant it gets clear that it 
makes much sense to use different deployment sources at a single host in 
a uniform manner

To satisfy these requirements changes are necessary in the following areas:
·Flexible ConfigListener configuration
·Configurable StandardHostDeployer
·More than one deployer or config Listener
·Faster war META-INF/context auto deployment after changing a 
lot of war files
·JMX Notification at StandardContext und StandardWrapper

The following sections each analyze the current state and then a 
proposal is made how to improve the code (change requests/enhancements) 
in order to match the goals sketched above.

You can also find the following text at
http://tomcat.objektpark.org/pdf/Proposal-HostConfig-Deployer.pdf

1) Config Classes of Container Elements
1.1)Status
HostConfig
   Autodeploy feature works for one webapps dir and one xml 
context descriptor dir
EngineConfig
   Start/Stop info
ContextConfig
   Context is configured as follows:
   Import DefaultContext
   Interpret the web.xml descriptor
   Auth Config
   Configure SessionManager
   Default web.xml Handling

a) The Config Listener can only be changed in server.xml:



See also the implementations for EngineRuleSet, HostRuleSet and
LifecycleListenerRule.

b)-d) Creating new container elements at runtime:
b) Create new host at runtime:
MBeanFactory.createStandardHost()(L. 943)
// add HostConfig for active reloading
   HostConfig hostConfig = new HostConfig();
   host.addLifecycleListener(hostConfig);
c)  Create new context at runtime:
MBeanFactory createStandardContext() (L.826)
ContextConfig contextConfig = new ContextConfig();
  context.addLifecycleListener(contextConfig);
d) Create new Service/Engine at runtime:
There is no correct setup for an EngineConfig. Currently the 
EngineConfig implementation only prints out start/stop!

e)  Only StandardHost has a default for Context 
configClass, but the StandardHostDeployer uses the ContextRuleSet to 
create the ConfigListener.

Deployment without context.xml or context definition at server.xml:
ContextRuleset. 117   
if (!isDefaultContext()) {
 digester.addRule(prefix + "Context",
  new CopyParentClassLoaderRule());
 // here is the override
   digester.addRule(prefix + "Context",
 new LifecycleListenerRule  
   ("org.apache.catalina.startup.ContextConfig",
 "configClass"));
 digester.addRule(prefix + "Context", new SetDocBaseRule());
 digester.addSetNext(prefix + "Context",
   "addChild",
   "org.apache.catalina.Container");
  
   Deployment with context.xml or context definition at 
server.xml:
Second Config Listeners at StandardHostDeployer L.276,  L 374
Case: No context.xml exists

if (context instanceof Lifecycle) {
   clazz = Class.forName(host.getConfigClass());
   LifecycleListener listener =
   (LifecycleListener) clazz.newInstance();
   ((Lifecycle) context).addLifecycleListener(listener);
   }
  
   The behaviour is not implemented in the method 
StandardHostDeployer.install(URL config, URL war) L . 424. - This case 
use the context.xml.
  
1.2) Change request:

All container elements in server.xml have a configListenerClass:

The default value is empty so we don't need it! And we would also have:



The default values are set in the class implementation themselves and 
the Listener is added either to the init() method or to the installation 
method of the StandardHostDeployer:

 if(configListenerClass != null) {
   Is LifeCycleListener
Create instance
Add to Listeners
Add getter and setter for this attribute
}
Using the configListenerClass would free us from the special 
MbeanFactory code and we could als

Re: [5.next] Progress

[Peter Rossbach]

Hello,
I have start a Server saved implementation.
- Externalize configuration saving out of StandardServer
features:
*   splitt implementation from StandardServer class
*   refactor the current save methods to some helper classes
*   every save element from server.xml dialect has it own save factory
*   central Mbean that have a registry for save factories
*   save complete Server,Engine,Host or Context xml's
*   support cluster elements
*   implement with testcases
options:
*  configure the save factories from xml or properties files.
*  better backup handling / not only for server.xml, also for 
context.xmls :-)

I hope the first implementation is ready at this weekend.
==
see some comments directly at the 5.next topics.
regards
peter
Remy Maucherat schrieb:
My upcoming change list:
- 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
Good option.
  * 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)
see some change requests at my today proposal... HostConfig/Deployer
- Use the webapp CL as the main CL (without the locking tricks it is 
likely
faster than the regular CL)
- Default servlet refactoring and optimization (avoid ResourceInfo 
class, MIME mapping matching)
- Resolve DBCP -> Pool -> Collections dependency which exposes too 
many JARs in the common classloader (using package renaming and some 
repackaging)
- Externalize configuration saving out of StandardServer
I can do that.

- Remove anything useless (spring cleaning time), such as configuration
options, container listeners (to be replaced with JMX notifications where
it matters), etc
Very good.
I have a made a NotificationEmitter Inteface support for StandardContext 
an StandardWrapper,
but it exist some problems at current JSR 77 notification support. 
Please look at my proposal or the bugreport

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29869
- BASIC auth optimization
- clutering module refactoring, to extend the regular Catalina 
objects, for
easier future maintenance
I have a talk with Rainer Jung, and his changes to cluster 
implementation looks very good.

- Possibly require JDK 1.5 (cleaner code, annotations, integrated JMX 
and JMX
remote, etc)
I have made prototype for mx4J JSR 160 support it looks very nice.
Can't we refactor the ServerLifecycleListener also?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29259
- And the ongoing: allow all config/management/embedding through JMX; 
note: I think this is almost there already (thanks Costin), so only a 
little tweaking will likely be needed

YES!
So there are still a number of big changes waiting to be implemented, 
and these should have a bigger impact than my initial changes. I'll do 
the deployer and classloader changes first, which is the biggest chunk.

When I'm done with the "remove anything useless" item, I'll propose a 
release plan. Any items to the list (anyone proposing something must 
be willing to timely implement what he's proposing, I'm not running a 
wish list ;) ) ?

Rémy


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

Re: [5.next] Progress

[Peter Rossbach]

Hey Remy,
OK, I am do my best that the save factory implementation work at weekend.
s. comments...
Regards
Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hello,
I have start a Server saved implementation.
- Externalize configuration saving out of StandardServer
features:
*   splitt implementation from StandardServer class
*   refactor the current save methods to some helper classes
*   every save element from server.xml dialect has it own save factory
*   central Mbean that have a registry for save factories
*   save complete Server,Engine,Host or Context xml's
*   support cluster elements
*   implement with testcases
options:
*  configure the save factories from xml or properties files.
*  better backup handling / not only for server.xml, also for 
context.xmls :-)

I hope the first implementation is ready at this weekend.

Sure, show me the code.
see some comments directly at the 5.next topics.
Remy Maucherat schrieb:
My upcoming change list:
- 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

Good option.

I'm so tired of Windows right now ...
But few of the developers wan't work at linux  :-\  ...
- Externalize configuration saving out of StandardServer

I can do that.

I was planning to do it in 5 minutes (take the current code, put it in 
separate class, )

Ohh, that was also my first step, but after a deeper look: I  made a 
bigger redesign step to
support also cluster and I hope more modules in the future.

- BASIC auth optimization
- clutering module refactoring, to extend the regular Catalina 
objects, for
easier future maintenance

I have a talk with Rainer Jung, and his changes to cluster 
implementation looks very good.

Ah ok. Filip was planning (to be forced through any means necessary) 
to do that, so ask him.

- Possibly require JDK 1.5 (cleaner code, annotations, integrated 
JMX and JMX
remote, etc)

I have made prototype for mx4J JSR 160 support it looks very nice.
Can't we refactor the ServerLifecycleListener also?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29259

No, that listener needs to go IMO. This listener is useless in the end 
(for this branch): this is done at the VM level much more cleanly, and 
the VM also provides tons of runtime statistics that nobody will want 
to live without. I'll rethink my position if J2SE 5 (I'm learning ;) ) 
turns out bad somehow, but I don't think the core VM is a big rewrite, 
so I expect it to be stable. I'll start using it soon for my builds 
and testing, and I'll see how it goes.

OK, I thing also that a VM-JMX support are a better way.
- And the ongoing: allow all config/management/embedding through 
JMX; note: I think this is almost there already (thanks Costin), so 
only a little tweaking will likely be needed

YES!

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Connector LifecycleListener not send Events

[Peter Rossbach]

Hey,
I have find the following code at org.apache.catalina.connector.Connector:
   /**
* Get the lifecycle listeners associated with this lifecycle. If this
* Lifecycle has no listeners registered, a zero-length array is 
returned.
*/
   public LifecycleListener[] findLifecycleListeners() {

   return null ; // lifecycle.findLifecycleListeners();
   }
Why we not emitt Events to the Listeners?
I think we can also send PAUSE and RESUME Events to the 
lifecycleListener from Connector.

Alternativ: We delete the dead Lifecycle implementations and redesign 
the code to JMX-notifcation...

Regards
Peter

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

Discuss: Why stopped StandardHost send check events?

[Peter Rossbach]

hey,
I have see that a stopped Host send all 10 sec check events to
all LifecycleListeners.
A stop HostConfig can't reload or deploy new webapp really at a stopped 
host.
  
StandardHost code
  public void backgroundProcess() {
   lifecycle.fireLifecycleEvent("check", null);
   }

better
StandardHost emitted check event only on started host.
  public void backgroundProcess() {
   if(started)
lifecycle.fireLifecycleEvent("check", null);
   }
regards
Peter

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

Re: [5.next] Progress

[Peter Rossbach]

Hello Jess,
I have made a test with MX4J 2.0.1 and JSR 160 Connector.
See my patches
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29259
Testet with MC4J Console and works very well.
regards
Peter
Jess Holle schrieb:
Remy Maucherat wrote:
Jess Holle wrote:
In my case even with 1.5 I need a pluggable (2) from above.  Why?  
Because I need to work with port ranges and grab the first free port 
(with MBeans then proxied to a daemon with a consistent port #).  
1.5 has no automatic machinery for this as best I can tell.

It's true that (1) is simple getPlatformMbeanServer() [or whatever 
it is called again] in 1.5, but I believe it should be light and 
easy enough to stick something else under the covers here.

I'm tired of interfaces, so I have to say I'm against this, 
especially for a specific purpose (I would tend to believe you can 
configure lots of stuff with JDK 1.5, though). You should simply use 
your own server listener (I think server lifecycle listeners are here 
to stay).

Cool.  As I said though, I've got my own processes to instrument 
first.  I'd just like to see Tomcat progress in a similar fashion so 
that one monitor Tomcat in the same fashion sooner rather than later.

Regardless on how the JMX connector is configured on the server side, 
it will work the same from the client's perspective.

Yep.  I'm just anxious to see JMX RMI remoting support in Tomcat soon, 
i.e. in a stable shipping version that supports a stable, shipping JRE 
(i.e. 1.4.2).

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: JavaService Tomcat4.1 or tomcat 5

[Peter Rossbach]

Hey,
I used successfull the Java Service Wrapper.
see http://wrapper.tanukisoftware.org/doc/english/introduction.html
Look at http://centaurus.sourceforge.net project to integrate tomcat
with gui installer at Linux and Windows.
Very good option to used Tomcat as service on different platforms
regards
Peter
jean-frederic clere schrieb:
Hi,
It seems that www.alexandriasc.com does not work any more, does 
someone knows why?

In Tomcat5 we are using procrun, should n't we do the same on Tomcat4?
Cheers
Jean-Frederic
-
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]

Re: Ready for mod_jk 1.2.6 release?

[Peter Rossbach]

+1
important features to help customers to have a stable loadbalancer...
At Linux Suse 9.0 it works fine.
regards
Peter
Rainer Jung schrieb:
Hi,
the last release of mod_jk 1.2.x (1.2.5) is more than 9 months old. 
Since then there have been important improvements (CPing/CPong and 
recovery_options). Especially recovery_options is very useful in 
transparent administration (start/stop) of cluster nodes.

The 1.2 branch is still the preferred branch for combination with 
apache 1.3. Is there any volunteer to make an official 1.2.6 release? 
I do hope so ;-)

Another good argument: The documentation of the new features is 
already there 
(http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html), 
so no additional work and furthermore, the documentation up to now 
does not mention, that all these features are still not available, 
because 1.2.6 has never been released. Many thanks to whoever wrote 
that document.

I worked with a cvs build under solaris for some weeks without 
problems, but for production purposes people need an official release.

The last changes in the native jk code is more then 6 weeks old and 
there is no code change activity at the moment. So this might be a 
good point in time to release mod_jk 1.2.6.

Looking forward for positive feedback
Rainer Jung
-
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]

Re: [VOTE] 5.0.27 as Stable

[Peter Rossbach]

Release 5.0.27 as Stable:
[ ] Yes
[X] No

Currently we can't auto deploy war with META-INF/context.xml included
At HostConfig is a wrong patch included .  Look at my patch with bug report
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29688
regards
peter
Shapira, Yoav schrieb:
Hi,
5.0.27-beta has been out for a few weeks, the TCKs pass, the tester and
watchdog tests pass, and there has been positive feedback for it on the
user list without any show stopper bug reports.  This change is simply a
label change and minor website update, no code change or new binaries.
Changelog:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/changelog.html

I vote Yes ;)
 


Yoav

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]

Re: mod_jk 1.0.26 release ?

[Peter Rossbach]

cool status and it works fine,
+1
Thanx
peter
Henri Gomez schrieb:
jk 1.2.6 seems to be in a good shape and a release should be welcome
for many users.
I'd like to release jk 1.2.6 next week.
Any objections ?
Vote please ;-)
-
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]

Re: [VOTE] 5.0.27 as Stable

[Peter Rossbach]

Hey,
the problem with 5.0.27 is not the NullPointerException check.
My problem is, that the 5.0.27 autodeployment for war's with 
META-INF/context.xml
included not work as before. Currently the HostConfig generate a 
directory at conf///.xml/.

Ok, no problem with the spec, but a real problem to have easy and quick 
deployment.

regards
peter
Shapira, Yoav schrieb:
Hola,
Even though you don't have a vote, I wanted to address this: a release
being stable doesn't mean it's the end-all-be-all of releases ;)  There
has to be a showstopper part or incompatibility with the specifications
to prevent this label.  This one isn't IMHO, although of course that's
subjective.
BTW on this issue, the JavaDoc for java.io.File#list() since null would
be returned if the file object is not a directory or an I/O error
occurs: it says an empty array will be returned for an empty directory.
Since we check in deployApps that appBase and configBase are
directories, we should be OK, but this point is a separate discussion
not having to do with the release vote.
Yoav Shapira
Millennium Research Informatics
 

-----Original Message-
From: Peter Rossbach [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 12:49 PM
To: Tomcat Developers List
Subject: Re: [VOTE] 5.0.27 as Stable

Release 5.0.27 as Stable:
[ ] Yes
[X] No

Currently we can't auto deploy war with META-INF/context.xml included
At HostConfig is a wrong patch included .  Look at my patch with bug
   

report
 

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29688
regards
peter
Shapira, Yoav schrieb:
   

Hi,
5.0.27-beta has been out for a few weeks, the TCKs pass, the tester
 

and
 

watchdog tests pass, and there has been positive feedback for it on
 

the
 

user list without any show stopper bug reports.  This change is simply
 

a
 

label change and minor website update, no code change or new binaries.
Changelog:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/changelog.html

I vote Yes ;)

 

Yoav

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]
   



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]

Re: [VOTE] 5.0.27 as Stable

[Peter Rossbach]

Hey Remy,
ok, the next patches are on the way... ;-)
Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hey,
the problem with 5.0.27 is not the NullPointerException check.
My problem is, that the 5.0.27 autodeployment for war's with 
META-INF/context.xml
included not work as before. Currently the HostConfig generate a 
directory at conf///.xml/.

Ok, no problem with the spec, but a real problem to have easy and 
quick deployment.

Peter, you have to be more pragmatic than that. Few people complained 
about this issue overall, so it's definitely not a showstopper.
I believe we'll incorporate a few of the patches which are lying 
around for the next release (and if you keep up with your good 
contributions, you'll be able to paticipate more directly in the 
future ;) ).

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: DO NOT REPLY [Bug 30128] New: - StandardDefaultContext don't handle LifecycleListener correct

[Peter Rossbach]

Hello Remy,
Yeah, good idea. I also thing it is a spezial context.xml parsing, but 
it is tricky at start/stop handling and
removed the defaults correct.  For saving a Context the current 
DefaultContext situation is more tricky.
The NamingContextListener have a very spezial handling and I see that 
LocalEjb are not well implement.

regards
peter
Remy Maucherat schrieb:
Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
PS: DefaultContext handling is very complicated. I hope we start a 
talk about
cleaner and better support for 5.next release.

I've been thinking about that for weeks, but I haven't found anything 
really simpler yet. Some solutions I've thought about include JMX 
tricks or adding code to the container. Still working on it.

Thinking about it more, it seems very simple actually, if it's done 
the same as for the default web.xml (with a separate "default" 
context.xml associated with the host). This is doable since I'll move 
the context.xml processing as part of the deployer refactoring, and 
will end up with something a lot more consistent (which will be well 
tested, since it'll use the same code as for the context.xml processing).

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Add managedResoruce to Realm, or auth operations

[Peter Rossbach]

Hello,
can we add managedResource attribute to Realm Mbean descriptors? With 
this feature we can used
the Realm authorisation API at the complete MBeanServer.

Add this to all Realm MBean declarations:
 
  description="The managed resource this MBean is 
associated with"
  type="java.lang.Object"
  writeable="false"/>

Other options was add following operations:
   


   
   


   

My idea is to wrote a better HTTP MX4J Adaptor with SSL and Realm based 
authorisation support.

Regards
Peter

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

Re: New committer: Peter Rossbach

[Peter Rossbach]

Hi all,
thank for all your votes!
I want to introduce a bit who I am and what I'm doing.
I am a freelancer and have a lot of experience at
servlet technologie and J2EE architecture development. I started 
servlet web development at 1997. The first project was
to design, organize and implement a distribute information
system with more than 1000 Linux nodes. And it works very fine. With
this knowlege I wrote with Hendrik Schreiber the "Java
Servlets and Server Book" and help to implement the 
first servlet 2.1 API conform servlet engine "jo!" 
( cool work from Hendrik) and the webapp framework (http://www.webapp.de).
This was the start writing a lot of german articles 
about web technologies.
In 2002 I wrote the frist german Tomcat Book ("Tomcat 4X").
The last year I wrote the monthly german Tomcat columne at 
Java Magazin and start a new german book project for 
Tomcat 5.next (http://tomcat.objektpark.org). Now I am working
with Thorsten Kamann at the Centaurus-Platform (http://centaurus.sourceforge.net).
We want to build a secure and easy Java web hosting platform.
Since the last four years I coach a lot of people at german 
conferences for tomcat knowledge, setup build verification systems 
and advanced web development.

I want start to help Remy with the new deployment method, made 
more JMX possible and hope to help save correct server.xml 
configuration. 

Thanks, I am very proud today to start more active tomcat development.
Peter
PS: I hope to get a good internet access by my family holiday place ...  :-D 


Remy Maucherat schrieb:
Hi,
I'd like to nominate Peter Rossbach  as a 
committer on the Tomcat project. Peter submitted a significant amount 
of useful patches for Tomcat, and wants to contribute more.

He has my +1.
Rémy
-
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]

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core StandardHost.java

[Peter Rossbach]

Hello Bill,
I see the change, but I missing the attribute managedResource at the 
Realms.mbeans-descriptors.xml.

Thanx
Peter
[EMAIL PROTECTED] schrieb:
billbarker2004/08/02 20:01:03
 Modified:catalina/src/share/org/apache/catalina/core
   StandardHost.java
 Log:
 Small changes for JMX deployment
 
 -- Create a Deployer for this Host.
 -- Fix the "discover orphaned Realm" logic.  This still requires that the Realm MBean exposes the "managedResource" attribute, but it was so broken before that nobody could have been using it.
 
 Revision  ChangesPath
 1.33  +10 -7 jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardHost.java
 
 Index: StandardHost.java
 ===
 RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardHost.java,v
 retrieving revision 1.32
 retrieving revision 1.33
 diff -u -r1.32 -r1.33
 --- StandardHost.java	28 Jul 2004 18:02:15 -	1.32
 +++ StandardHost.java	3 Aug 2004 03:01:03 -	1.33
 @@ -29,9 +29,11 @@
  import org.apache.catalina.Context;
  import org.apache.catalina.DefaultContext;
  import org.apache.catalina.Host;
 +import org.apache.catalina.Realm;
  import org.apache.catalina.LifecycleException;
  import org.apache.catalina.Valve;
  import org.apache.catalina.valves.ValveBase;
 +import org.apache.catalina.startup.HostConfig;
  import org.apache.commons.modeler.Registry;
  
  
 @@ -736,12 +738,11 @@
  if( realm == null ) {
  ObjectName realmName=null;
  try {
 -realmName=new ObjectName( domain + ":type=Host,host=" + getName());
 +realmName=new ObjectName( domain + ":type=Realm,host=" + getName());
  if( mserver.isRegistered(realmName ) ) {
 -mserver.invoke(realmName, "setContext", 
 -new Object[] {this},
 -new String[] { "org.apache.catalina.Container" }
 -);
 +Realm nrealm = (Realm)mserver.getAttribute(realmName,
 +   "managedResource");
 +setRealm(nrealm);
  }
  } catch( Throwable t ) {
  log.debug("No realm for this host " + realmName);
 @@ -830,7 +831,9 @@
  // Register with the Engine
  ObjectName serviceName=new ObjectName(domain + 
  ":type=Engine");
 -
 +
 +HostConfig deployer = new HostConfig();
 +addLifecycleListener(deployer);
  if( mserver.isRegistered( serviceName )) {
  log.debug("Registering with the Engine");
  mserver.invoke( serviceName, "addChild",
 
 
 

-
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]

Re: [VOTE] [5.5] Release plan votes

[Peter Rossbach]

Remy Maucherat schrieb:

I approve the release plan:
[x] Yes
[ ] No


Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[x] J2SE 1.4
[ ] J2SE 5.0


Yoav Shapira will act as the release manager for this branch:
[x] Yes
[ ] No

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: [VOTE] 5.0.28 Stability Rating

[Peter Rossbach]

[X] Stable
[ ] Beta
[ ] Alpha
Thanx
Peter

Yoav Shapira schrieb:
Hi,
Tomcat 5.0.28 has been available for a week, with no significant issues
reported, and passing the TCK tests.  Shall we call it:
[X] Stable
[ ] Beta
[ ] Alpha
My vote is for Stable.  If you're voting Alpha or Beta, please explain why. 
And remember, only committer votes are binding, although everyone's opinion is
of course welcome.

This vote will end in 72 hours.  Thanks,
Yoav
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

JSP Encoding changed between tomcat 5.0.27 and 5.5.x

[Peter Rossbach]

Hello,
I have test a small application with Tomcat 5.5 and CVS HEAD 5.5.1-dev
and with JDT something changed from 5.0.x to 5.5 with the JSP encoding.
see example. test.jspx 

The problem exit also with "normal" *.jsp with <%@ page pageEncoding="ISO-8859-1" %>
I thing the JDT compiles with UTF-8, right ?
Bug or what is wrong?
Regards
Peter
PS: Thanx, Michael Schuerig to report me this example!

test.jspx:
>>>

http://www.w3.org/1999/xhtml";
xmlns:jsp="http://java.sun.com/JSP/Page";
xmlns:c="http://java.sun.com/jsp/jstl/core";
xmlns:fmt="http://java.sun.com/jsp/jstl/fmt";
lang='de'

 

 http://www.w3.org/TR/xhtml-basic/xhtml1-strict.dtd"; />
 
 
 
   Test
 
 
   ä
   ö
   ü
   Ä
   Ö
   Ü
   " "
 

>>>
Tomcat 5.5 (falsch)
http://localhost:8080/myapp/test.jspx:
>>>

http://www.w3.org/TR/xhtml-basic/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; 
lang="de">Test

   Ãâ,¬
   ö
   ÃÅ'
   ÃÂ"
   ÃÂ-
   Ü
   "Ã, "
>>>
Tomcat 5.0.27 (korrekt)
http://localhost:8080/myapp/test.jspx:
>>>

http://www.w3.org/TR/xhtml-basic/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; 
lang="de">Test

   ä
   ö
   ü
   Ã"
   Ã-
   Ü
   "Â "
>>>


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

Re: JSP Encoding changed between tomcat 5.0.27 and 5.5.x

[Peter Rossbach]

Hello Remy,
your are right! I found the difference very quickly.
JDTCompiler default Encoding is UTF8
ANTCompiler default Encoding is ISO-8859-1
Set correct javaEncoding parameter to default conf/web.xml and all is 
working as 5.0.27 Release

   
   jsp
   org.apache.jasper.servlet.JspServlet
  
   javaEncoding
   ISO-8859-1
   
...
   
Nexttime I inspect first and then send a mail.
:-)
###
But the with my test.jspx example the following is strange:
   The concrete http response is UTF-8 encoded
---
HTTP/1.1 200 OK
Content-Type: text/html;charset=UTF-8
Content-Length: 431
Date: Mon, 06 Sep 2004 07:15:25 GMT
Server: Apache-Coyote/1.1


http://www.w3.org/TR/xhtml-basic/xhtml1-strict.dtd";>
http://java.sun.com/jsp/jstl/fmt"; 
xmlns:c="http://java.sun.com/jsp/jstl/core"; 
xmlns="http://www.w3.org/1999/xhtml"; 
lang="de">Test

   ä
   ö
   ü
   Ä
   Ö
   Ü
   "Â "
-
But at my Mozilla present the correct letters!
After I change the jsp directive to

both Tomcat Release 5.0.27 and 5.5.1-dev (CVS HEAD)
the response was generated with the correct encoding ISO-8859-1.

---
HTTP/1.1 200 OK
Content-Type: text/html;charset=ISO-8859-1
Content-Length: 429
Date: Mon, 06 Sep 2004 07:23:17 GMT
Server: Apache-Coyote/1.1


http://www.w3.org/TR/xhtml-basic/xhtml1-strict.dtd";>
http://java.sun.com/jsp/jstl/fmt"; 
xmlns:c="http://java.sun.com/jsp/jstl/core"; 
xmlns="http://www.w3.org/1999/xhtml"; 
lang="de">Test

   ä
   ö
   ü
   Ä
   Ö
   Ü
   " "

my fault
Thanx for the bug reporting hint, ;-)
Peter

Remy Maucherat schrieb:
Peter Rossbach wrote:
Hello,
I have test a small application with Tomcat 5.5 and CVS HEAD 5.5.1-dev
and with JDT something changed from 5.0.x to 5.5 with the JSP encoding.
see example. test.jspx
The problem exit also with "normal" *.jsp with <%@ page 
pageEncoding="ISO-8859-1" %>
I thing the JDT compiles with UTF-8, right ?

Bug or what is wrong?

I'm a little bit tired about that very popular way to present bug 
reports: "help, version XXX works while new version YYY is broken: 
something is wrong with version YYY".

Nothing relevant has changed between 5.0.x and 5.5.x (you should know 
that, you're a committer), except the change of the source compiler.

Now if you look in the code for JDT:
   if (ctxt.getOptions().getJavaEncoding() != null) {
   settings.put(CompilerOptions.OPTION_Encoding,
   ctxt.getOptions().getJavaEncoding());
   }
The behavior is the exact same for the Ant compiler. So if it doesn't 
work for you, I think you should look into it.

Rémy
-
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]

Re: Bugzilla 30936: secure attribute is persisted twice

[Peter Rossbach]

Hey,
we have many duplicate attributes at connector and protocolhandler classes-
I have spent a lot of time to fix that at my new server.xml/context.xml 
storage
module.
  Current design based on factory model with external description file 
to handle those issues.
  Very strange, but my only chance to implement the handler, without 
break the current codebase.

We must refactor the Connector/Protocoll class to make a clear cut,
between old and correct attributes. We drop maxProcessors and 
minProcessors attributes as example.

My current questions are:
Why we handle all connectors attributes as real class attributes
and dymamic properties?
Can we drop the attribute translation between Connector and 
ProtocolHandler?

Regards
Peter
PS: I am waiting to get cvs write access
Shapira, Yoav schrieb:
Hi,
 

I'm going to wait for Peter for save-to-XML rewriting, before bothering
with fixing the various issues.
(right now, saving data sources needs to be redone as well)
   

I contemplated that, but it seems that here the core problem is not the
persisting itself: it's the duplication of attributes.  Even if the XML
persistence issue is fixed soon (I have faith ;)), it'll be hackish to
have it check the buffer to see if an attribute has been persisted, and
only persist it if not.  It's an OK fix, but doesn't address the core
issue in this particular case, does it? ;)
Yoav

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]

Re: Bugzilla 30936: secure attribute is persisted twice

[Peter Rossbach]

Hmm,
   I thing we use different protocol handler classes for HTTP and AJP 
and that
   is the reason behind the late creation with the init method. :-\  
  
   I also thing we can remove a lot of the "unused" attributes that 
Remy has detected.

Peter
  
Shapira, Yoav schrieb:

Hi,
 

An option would be to
tie the Connector object creation with the creation of the protocol
handler instance.
   

That makes sense anyways.  Why delay, since the Connect isn't useful
without a ProtocolHandler anyways?
Yoav

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]

i18n Question Tomcat 5.5 cvs head

[Peter Rossbach]

Hey,
I have problems to load application with de_DE locale.
===  Stacktrace ===
04.10.2004 22:52:04 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-7380
04.10.2004 22:52:04 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2584 ms
04.10.2004 22:52:05 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
04.10.2004 22:52:05 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.0-dev
04.10.2004 22:52:05 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
04.10.2004 22:52:05 org.apache.catalina.startup.HostConfig deployDescriptor
SCHWERWIEGEND: Error deploying configuration descriptor admin.xml
java.util.MissingResourceException: Can't find bundle for base name 
org.apache.n
aming.resources.LocalStrings, locale de_DE
   at 
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle
.java:804)
   at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:773)
   at java.util.ResourceBundle.getBundle(ResourceBundle.java:511)
   at org.apache.naming.StringManager.(StringManager.java:67)
   at 
org.apache.naming.StringManager.getManager(StringManager.java:212)
   at 
org.apache.naming.resources.BaseDirContext.(BaseDirContext.java
:85)
   at 
org.apache.naming.resources.FileDirContext.(FileDirContext.java
:71)
   at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:3
889)
   at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:755)
   at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
9)
   at 
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)

   at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.ja
va:590)
   at 
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.j
ava:535)
   at 
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470
)
   at 
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1079)
   at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
:310)
   at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
eSupport.java:119)
   at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1011)

   at 
org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
   at 
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1003)

   at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:437
)
   at 
org.apache.catalina.core.StandardService.start(StandardService.java:4
50)
   at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:200
9)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:538)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
04.10.2004 22:52:05 org.apache.catalina.startup.HostConfig deployDescriptor
SCHWERWIEGEND: Error deploying configuration descriptor manager.xml
java.util.MissingResourceException: Can't find bundle for base name 
org.apache.n
aming.resources.LocalStrings, locale de_DE
   at 
java.util.ResourceBundle.throwMissingResourceException(ResourceBundle
.java:804)
   at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:694)

===
After add "-Duser.language=en" to my CATALINA_OPTS all is working.
Problem are the default LocaleStrings.properties from nameng resources ( 
naming-resources.jar) is at server loader and the web app load with 
webapp/common classloader.

regards
Peter

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

Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Peter Rossbach]

Hmm,
I also so think that the managedResource attribute is a hack. What we 
need is
a better JMX API. My wish is that we open some of the MBeans to add more 
operations.

Example realm:
We have only init/start/stop/destroy jmx operations but what I need  is
   authenticateXXX
   hasRole
Than I can easy used every realm for my JMX http adaptor (MX4J 2.0.1).
Peter
Bill Barker schrieb:
- Original Message -
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, October 04, 2004 4:23 PM
Subject: Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml
 

Bill Barker wrote:
   

It was on Peter's wish-list to add "managedResource" to the Realms.  This
was taken from (I think :) StandardHost, where the code was so broken that
it was impossible that anybody was using it, so waiting for
"managedResource" to be added to the mbean-descriptor was reasonable.
 

I tested with removing the relevant blocks in the containers: it's not
really used.
   

It would be only used by some custom JMX-embedding (and, like I said, it
never worked :).  The JMX-embedding method that does work is to invoke
"init" on the Realm, which will then add itself to whichever Container it
was registered for.
 

Except that "managedResource" is an internal-implementation artifact of
 

c-m.
 

There really isn't any point in getting rid of it before Remy's project to
make c-m an optional component.
 

Really, I'm supposed to do that ? ;)
   

It's your todo list ;).
 

I don't think "managedResource" needs anything special: it's just a
standard attribute (and is a hack) that is declared in the
mbean-descriptors. Its name makes it sound like it's somehow magically
provided by the model MBean implementation, but it's not (it would be
very insecure to do so). I would be happier if we tried removing the
"managedResource", actually.
   

It will make Peter unhappy, but it wouldn't be hard.  Probably the hardest
one to do would be Connector (since you can't add a Connector to an Engine
:).  The Realm stuff that started this could probably just invoke init on
the Realm instead.
 

Rémy
   


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


This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.
 


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

--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Peter Rossbach]

Hey Remy,
I have made a complete rebuild and a test. It works fine for me..
Ok, what you thing is a better name for ContextBase or you mean the 
refactoring is useless ?
I need this refactoring for eaiser identifiy the ContextXXX classes for 
my new xml saving code.

Peter
Remy Maucherat schrieb:
[EMAIL PROTECTED] wrote:
pero2004/10/04 23:57:20
 Modified:catalina/src/share/org/apache/catalina/deploy
   ContextEjb.java ContextLocalEjb.java
   ContextResource.java ContextResourceEnvRef.java
   ContextResourceLink.java
  webapps/docs changelog.xml
 Log:
 refactor o.a.c.deploy.ContextXXX classes to use new super class 
ContextBase.

- I think the ContextBase name for this class is quite bad.
- Please make sure you don't break the build. This means checking when 
adding files that they are indeed added (and same when removing).

Rémy
-
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]

Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Peter Rossbach]

Hey Remy,
sorry, to my checkin fault... I am change the name to ResourceBase and 
add it to the cvs.

Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hey Remy,
I have made a complete rebuild and a test. It works fine for me..

Apparently, you didn't "cvs add" the new ContextBase class. I think I 
can figure out what it contains, of course ;)

Ok, what you thing is a better name for ContextBase or you mean the 
refactoring is useless ?

No, the classname just sounds this is a superclass of StandardContext. 
So the classname is bad.

I need this refactoring for eaiser identifiy the ContextXXX classes 
for my new xml saving code.

Rémy
-
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]

Need help with mod_ajp

[Peter Rossbach]

Hello,
I have two simple question to the new mod_ajp:
Can we add a small documentation how people can compile and configure
the new mod_ajp? The mailing list are tell us a lot informations, but
please can someone desicribe the current state?
Thanks
Peter

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

Re: Need help with mod_ajp

[Peter Rossbach]

Cool,
that mean I checkout httpd 2.1 and all is working?
How I can find some mod_ajp configuration documentation?
   All new elements and option and a example for loadbalancing
Can you please, add some documentation ( jk/xdocs) that let people find the
  new module and configuration ?
Thanks
Peter
jean-frederic clere schrieb:
Remy Maucherat wrote:
jean-frederic clere wrote:
Peter Rossbach wrote:
Hello,
I have two simple question to the new mod_ajp:
Can we add a small documentation how people can compile and configure
the new mod_ajp? The mailing list are tell us a lot informations, but
please can someone desicribe the current state?


The developement of the proxy ajp has been moved to httpd-2.1.

To make sure I got everything right: so all the code and dev is done 
there now ?

Yes.
BTW, who's a committer on httpd ?

I and Mladen ([EMAIL PROTECTED]).
Cheers
Jean-Frederic
Rémy
-
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]

Re: Need help with mod_ajp

[Peter Rossbach]

Hello Jean Frederic,
fine, your example help me, but the current online balancer 
documentation is only a useless summary.
Exist a better one at cvs or is it a open ToDo item?

Thanx
Peter
jean-frederic clere schrieb:
Peter Rossbach wrote:
Cool,
that mean I checkout httpd 2.1 and all is working?

Yes
You have to configure httpd with:
--enable-proxy \
--enable-proxy-balancer \
--enable-proxy-ajp
How I can find some mod_ajp configuration documentation?

http://httpd.apache.org/docs-2.1/mod/mod_proxy_ajp.html
http://httpd.apache.org/docs-2.1/mod/mod_proxy_balancer.html
   All new elements and option and a example for loadbalancing

I have added to my httpd.conf:
+++
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
+++
And:
+++
ProxyRequests On
ProxyStatus full

Order deny,allow
Deny from all
Allow from localhost


   BalancerMember ajp://localhost:8009
   BalancerMember ajp://pgtr0327.mch.fsc.net:8009


   ProxyPass balancer://myCluster/examples/

+++
Can you please, add some documentation ( jk/xdocs) that let people 
find the
  new module and configuration ?

Thanks
Peter
jean-frederic clere schrieb:
Remy Maucherat wrote:
jean-frederic clere wrote:
Peter Rossbach wrote:
Hello,
I have two simple question to the new mod_ajp:
Can we add a small documentation how people can compile and 
configure
the new mod_ajp? The mailing list are tell us a lot informations, 
but
please can someone desicribe the current state?



The developement of the proxy ajp has been moved to httpd-2.1.


To make sure I got everything right: so all the code and dev is 
done there now ?


Yes.
BTW, who's a committer on httpd ?


I and Mladen ([EMAIL PROTECTED]).
Cheers
Jean-Frederic
Rémy
-
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]


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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: [5.5] Todo list

[Peter Rossbach]

Hey Remy,
very good new items.
It was very usefull that all elements can get time events. Then it was 
very easy to
control some reloading or monitoring things.

Yes, we can refactor the current AccessLogger. Let us have a look to the 
Apache httpd Module.
  Asynch mode very welcome
  Better support for Unix rotatelogs
  Faster output generation without patter parseing on every request.

Following I want to add:
   - wrote a better save-to-xml way
 I have factor out the current StandardServer method to 
separate  saving objects.
 Currently my module working well, but I have problems with the 
new default context.xml handling.
 I want contribute the new code as seperate module. Configure 
the new thing with seperate Listener and MBean.
 After a while of successful testing, we can remove the current 
StandardServer routines.

Peter
   
Remy Maucherat schrieb:

Remy Maucherat wrote:
My todo list currently includes:
- A simple host manager webapp (with Ant tasks)
- A String cache for MessageBytes (which could be enabled using a 
special system property)
- Decent default java.util.logging configuration
- Default JMX Remote configuration for Java 5 (ready to enable by 
uncommenting stuff)
- Allowing pluggability for commons-modeler

Adding new items:
- Extend the backgroundProcess() method to most other components, 
including: Valve, Loader, Realm, etc; 
ContainerBase.backgroundProcess() will call these methods
- Use this to try to provide an optimized version of the access 
logging valve (access logging is likely used in production for 
standalone Tomcat, and it has very bad performance right now) which 
would do asynchronous writes to its file (and hopefully be more 
efficient)

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: [5.0.22] Release vote

[Peter Rossbach]

Release 5.0.22 as Stable:
[ ] Yes
[ ] No

I vote -1
Autodeploy with HostConfig not working correct with Windows.
see my bug report with a fix.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28262
Regards
Peter
Remy Maucherat schrieb:


Release 5.0.22 as Stable:
[ ] Yes
[ ] No

I've tested the new Windows wrapper, and it did work for me (and it 
looks as if we did hire some M$ guy to do its UI). However, some more 
testing is needed (note: it's not suppoed to work on Win9x for now).
Another "risky" change is the upgrade to Xerces 1.6.2.
I didn't put the latest docs bundle on the website (AFAIK, the 
changelog will be the only update, so I think I'll only upload this 
file).
I didn't run the CTS yet with that build.

Rémy

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




--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]


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

Re: [5.0.22] Release vote

[Peter Rossbach]

Hello Remy,

the fix is also usefull at linux and all other systems 

following with current autodeploy host not working
a)   copy a webapp at host appBase (webapps dir)
b)   remove this new deployed application with manager app
c)   copy the same webapp again at host appBase.
Peter

PS: Your windows comment is out of comment

Remy Maucherat schrieb:

Peter Rossbach wrote:


Release 5.0.22 as Stable:
[ ] Yes
[ ] No

I vote -1
Autodeploy with HostConfig not working correct with Windows.
see my bug report with a fix.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28262


Windows is a very broken platform, and I don't quite care about this 
issue anyway.

Rémy

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




--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]




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

Re: WebappClassLoader: Lifecycle error : CL stopped

[Peter Rossbach]

Hello Mark,

it is fixed at cvs and I am sure the this work with the next release 
this days...

Regards,
Peter
Mark Thomas schrieb:

From: Remy Maucherat [mailto:[EMAIL PROTECTED] 
 

Sent: Tuesday, April 27, 2004 11:26 PM
To: Tomcat Developers List
Subject: Re: WebappClassLoader: Lifecycle error : CL stopped
Shapira, Yoav wrote:
   

Hi,

I like #2: in fact, it seems like it should be strictly enforced for
general stability and security, and I'm surprised the current code
doesn't restart a context after changing its loader already.
 

I think the admin webapp should stop the context before doing 
anything 
to its loader (and then start it again if it wants to).
   

A new root context in a new host (all created in the admin app) now works
correctly after a reboot but I just can't get it to work without a reboot.
Perhaps someone more talented than I  - there are plenty of people that
meet that description ;) - wants to have a look at this I would be happy
to share my (lack of) progress to date.
Mark



-
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]

Need help with admin app at 5.0.24

[Peter Rossbach]

Sorry,

but I have a very strange bug with the admin application at 5.0.24

After a login I see following message:

 HTTP Status 408 - The time allowed for the login process has been
 exceeded. If you wish to continue you must either click back twice and
 re-click the link you requested or close and re-open your browser


*type* Status report

*message* _The time allowed for the login process has been exceeded. If 
you wish to continue you must either click back twice and re-click the 
link you requested or close and re-open your browser_

*description* _The client did not produce a request within the time that 
the server was prepared to wait (The time allowed for the login process 
has been exceeded. If you wish to continue you must either click back 
twice and re-click the link you requested or close and re-open your 
browser)._



 Apache Tomcat/5.0.24


I have testet with 5.0.22 and it work every time. Friend tell me, that 
same admin Application works with 5.0.24 (Suse 8.x jdk 1.4.2_04) well
OK!

My  env
Windows XP
JDK 1.4.2_03
Tomcat 5.0.24
Mozilla 1.6
and IE 6
Suse 9.0
jdk 1.4.2_04
Mozilla 1.3
Tomcat 5.0.24
same bug
On second  XP computer the admin app also not working, but after I 
installed 1.4.2_04 it goes well.
But only when I type http://localhost:8080/admin/
with http://localhost:8080/admin I can sometimes reproduce the bug. 
Chance somebody the cookiehandling ?

Strange but with 5.0.22 or 5.0.19 the form based login process working 
without any problems.

Tips welcome ?

Regards
Peter


Regards,





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

Re: Need help with admin app at 5.0.24

[Peter Rossbach]

Next Information,

I have analyse the traffic between Browser and Tomcat 5.0.24 (tcpmon)and the
see following:
cookie= JSESSIONID=1097F923FE5514A29042ABAC28E01CB8.node2; nde-textsize=13px

other thing is, that I see more than one JSESSIONID Cookie for the admin 
application.
With 5.0.22 I can't reproduce this behaviour.

Regards
Peter
Peter Rossbach schrieb:

Sorry,

but I have a very strange bug with the admin application at 5.0.24

After a login I see following message:

 HTTP Status 408 - The time allowed for the login process has been
 exceeded. If you wish to continue you must either click back twice and
 re-click the link you requested or close and re-open your browser


*type* Status report

*message* _The time allowed for the login process has been exceeded. 
If you wish to continue you must either click back twice and re-click 
the link you requested or close and re-open your browser_

*description* _The client did not produce a request within the time 
that the server was prepared to wait (The time allowed for the login 
process has been exceeded. If you wish to continue you must either 
click back twice and re-click the link you requested or close and 
re-open your browser)._



 Apache Tomcat/5.0.24


I have testet with 5.0.22 and it work every time. Friend tell me, that 
same admin Application works with 5.0.24 (Suse 8.x jdk 1.4.2_04) well
OK!

My  env
Windows XP
JDK 1.4.2_03
Tomcat 5.0.24
Mozilla 1.6
and IE 6
Suse 9.0
jdk 1.4.2_04
Mozilla 1.3
Tomcat 5.0.24
same bug
On second  XP computer the admin app also not working, but after I 
installed 1.4.2_04 it goes well.
But only when I type http://localhost:8080/admin/
with http://localhost:8080/admin I can sometimes reproduce the bug. 
Chance somebody the cookiehandling ?

Strange but with 5.0.22 or 5.0.19 the form based login process working 
without any problems.

Tips welcome ?

Regards
Peter


Regards,





-
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]

Vote for new 5.0.25

[Peter Rossbach]

Hello,
I have last week much problems with the admin app and Form based Auth.
A lot of my session pepole at jax 2004 conference can't access the Admin 
app at 5.0.24.

With news cvs head all is working now.
I analysed that the wrong cookie handling is the fix.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28971
Vote +1 to Release new 5.0.25
Regards
Peter


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

Re: [5.0.25] Release vote

[Peter Rossbach]

Hello Yoav,
It is stable !
Vote YES
Regards
Peter
Shapira, Yoav schrieb:
Hi,
5.0.25-alpha has been out for a few days, the TCKs pass, the tester and
watchdog tests pass, and there has been positive feedback for it on the
user list without any show stopper bug reports.
Changelog:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/changelog.html

Release 5.0.25 as Stable:
[ ] Yes
[ ] No

I vote Yes ;)
Yoav

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]

Re: Tomcat 5 - Proposal: move commons-fileupload-1.0.jar to common/li b

[Peter Rossbach]

hello,
used the shared/lib directory to add your web app shared jars to your 
catalina.base.

Regards
Peter
Detlef Pleiß schrieb:
hello, 

Tomcat 5 comes with commons-fileupload-1.0.jar in server/lib. 
I believe it's in there as to make it available to the server/webapps admin
and manager. 
Now I make use of commons fileupload in one of my "normal" webapps.
But, as for the classloaders, that only works after moving
commons-fileupload-1.0.jar from server/lib to common/lib.
I don't use admin or manager, so I don't know, but believe, that moving
fileupload to common should not break these. 
But, having fileupload in common would enable its immediate use for normal
webapps. 
IMHO this could be documented in the RELEASE-NOTES just like how Xerces is
available for web applications,
that commons fileupload is available to web applications as well. 
BTW: the RELEASE-NOTES still speak of "Xerces 2.6.0 is included" where
Xerces 2.6.2 is included with Tomcat 5.0.24.
If I overlooked any good reason for not moving fileupload to common, I would
be grateful to learn about it. 

ciao - thanks - Det.
-
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]

Re: How to configure a tomcat project in Eclipse.

[Peter Rossbach]

Hello,
used following plugins:
Lomboz Plugin
download:
http://forge.objectweb.org/project/showfiles.php?group_id=97
info
http://www.objectlearn.com/projects/lomboz.jsp
or search to the eclipse plugin pages:
http://www.eclipse-plugins.info/eclipse/plugins.jsp?category=Tomcat
or programming help with
http://www.eclipse-plugins.info/eclipse/plugins.jsp?category=Web
regards
Peter
Nagendra Shukla schrieb:
Hi friend
me too want want auch type of help so please if u got any document regarding
this, please forward it to me.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 10:14 AM
To: [EMAIL PROTECTED]
Subject: How to configure a tomcat project in Eclipse.
Hi all,
Can anaybody help me configure the Tomcat Project in Eclipse.
Just what to compile and where to put the classes. If somebody has
prepared a document or has access to any such document please forward
the same.
Regards & Regards,
Jagsir
-
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]

--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: UTF8 or sys prop value?

[Peter Rossbach]

Helo Yoav,
I think we must change it, as system property and a encoding Server 
attribute.
I have start a implementation to a flexible new store engine for the 
tomcat 5 format.
At weekend I wrote the proposal and I start the coding.

Features:
Seperate MBean to store the configuration.
Flexible management to extensions, like cluster configuration
store at Stream, Writer or File
store complete Server, Service, Host or Context
Flexible Handling from transient Attributes and Childs
regards
Peter
Shapira, Yoav schrieb:
Hi,
I see in StandardServer#storeConfig and MemoryUserDatabase#save that
we're creating the output writers for server.xml and tomcat-users.xml
using a hard-coded "UTF8" encoding.
Should we modify this?  Maybe look for the specified java.file.encoding
system property, and if that's specified, use it, otherwise use UTF* as
default?
The reason I'm asking is for
http://issues.apache.org/bugzilla/show_bug.cgi?id=29091.
Yoav Shapira
Millennium Research Informatics


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]

 


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: [ANN] Apache Tomcat 5.0.27 Beta released

[Peter Rossbach]

Hey,
I thing following things are also include with 5.0.27
Cluster (fhanik):
   FarmWARDeployer
A farm war deployer is a class that is able to
deploy/undeploy web applications in WAR form
within the cluster
Coyote/JK2
Add small patch that we can used MX4J 1.1.1 and 2.0.1 add JkMX.java ( 
Bill Baker and Peter Rossbach)
Also added a "mx.useXSLTProcessor" flag
   With value false you get XML Results with the mx4j http-adaptor

regards
peter
Shapira, Yoav schrieb:
The Tomcat Team announces the immediate availability of Apache Tomcat 
5.0.27 Beta.

Please refer to the change log for the list of changes:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/changelog.html
Release notes:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/RELEASE-NOTES
Downloads:
Binaries: http://jakarta.apache.org/site/binindex.cgi
Sources: http://jakarta.apache.org/site/sourceindex.cgi
The Apache Tomcat Team

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]

 


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://www.webapp.de/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: Tomcat 5.5.4 tomorrow (Friday) instead of Saturday?

[Peter Rossbach]

Great Yoav,
do it on friday is very good
Peter
Shapira, Yoav schrieb:
Hi,
Would everyone be OK with cutting the 5.5.4 release tomorrow (Friday,
October 29th) instead of Saturday (October 30th) as we originally
agreed?  It'd be more convenient for me, that's the only reason.  If it
can't be done on Friday, it'll likely have to be Monday afternoon
instead, but Saturday I can't do.
As for the release time of day, it'll be the same whether Friday or
Monday: 1900h GMT which is 1400h my time (US Eastern time zone).
Yoav Shapira http://www.yoavshapira.com


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]

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session JDBCStore.java PersistentManagerBase.java StoreBase.java mbeans-descriptors.xml

[Peter Rossbach]

Hoho,
I reformat a little but I work with Eclipse and format the code again 
and replace tab to space.

thanks
Peter
Bill Barker schrieb:
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 02, 2004 11:07 AM
Subject: cvs commit:
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session
JDBCStore.java PersistentManagerBase.java StoreBase.java
mbeans-descriptors.xml
 

pero2004/11/02 11:07:51
  if (preparedKeysSql == null) {
 + String keysSql =
 + "SELECT " + sessionIdCol + " FROM " + sessionTable +
 + " WHERE " + sessionAppCol + " = ?";
  preparedKeysSql =
   

_conn.prepareStatement(keysSql);
 

  }
   

I can hear the sirens from the dreaded tab-police :).
 


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

Question about new mod_jk jk_lb_worker.c

[Peter Rossbach]

Hello Mladen,
I have see your checkin's and Rainer Jung very fine mod_jk extension 
concept mail.

I have two questions about lb changes:
a)   Why you not change the lb_value value after successful recovery at 
service() function ?
  After a longer fail the recovered worker get for a long time all 
new sessions...
  See also Rainers Jung mail
b)   I have play around with the mod_jk2  lb algo and find the level 
feature (hot-standby) very usefull.
 With this feature I have setup to apache with two separate clusters.
  Apache 1
  Worker   T1.1   level 0
  Worker   T1.2   level 0
  Worker  T1.3level 0

  Worker   T2.1   level 1
  Worker   T2.2   level 1
  Worker  T2.3level 1
  Apache 2
  Worker   T1.1   level 1
  Worker   T1.2   level 1
  Worker  T1.3level 1
  Worker   T2.1   level 0
  Worker   T2.2   level 0
  Worker  T2.3level 0
  T1.1-T1.3   Cluster 1
  T2.1-T2.3  Cluster 2
   With this configuration every Apache has a preferred cluster.
   Ok small patch are needed:
   After a crashed node the algo find prefered worker at same 
level.

   I thing the domain concept from Rainer Jung in combination with 
preferred worker from mod_jk2 can be very usefull for clustered env.

Regards
Peter

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

Re: Question about new mod_jk jk_lb_worker.c

[Peter Rossbach]

Hello Mladen,
I have two use case for the Multi Cluster Routing:
Use Case 1: More Scaling cluster
=
A tomcat standard we replicated the session to all tomcat node at a cluster.
This replication strategie not scale very well, but when we split
the tomcat nodes to some domain  and the lb knows that, the system scale 
better.

   Apache 1
   domain and cluster 1
worker   w1.1 for T1.1
worker   w1.2 for T1.2
worker   w1.3 for T1.3
  domain and cluster 2
worker   w2.1 for T2.1
worker   w2.2 for T2.2
worker   w2.3 for T2.3
  When a worker w1 at domain 1 failed the  made the next try to w1.2 
and w1.3,
  only this worker fail also, the balancer give the w2.x worker a 
chance. Ok, the client
  lose the session but than you have really hardware problems...

Use Case 2: Switch smoothly to next software generation ( preferred domain)

Release a new software at runtime without drop the current user sessions.
Start complete new tomcat instances with new application release.
Say the Loadbalancer that all new sessions start to domain 2 workers,
but as you lost a worker at domain 1 (old release) switch to worker at 
same domain.

Apache 1
   domain and cluster 1  ( Software Release 1)
worker   w1.1 for T1.1
worker   w1.2 for T1.2
worker   w1.3 for T1.3
  domain and cluster 2 ( Software Release 2) - preferred
worker   w2.1 for T2.1
worker   w2.2 for T2.2
worker   w2.3 for T2.3
  Both use case work perfect with the mod_jk2 level concept, with a 
little patch.
  Only the level limit is a real problem for scaling well..

---
I check also the newest jk_lb_worker and it works fine for me...
The increment technic is simple and powerful :-)
Some examples
w1+ w2   lb_factor 1 lb_value 0
   values after calc
   request  |   w1   w2|  comment
   1   |0*   2   |w1 get the Session
   2   |0 0* |w2 get the Session
   3   |0 0* |w2 get the Session, w1 is in 
error state

w1 lb_factor 3 lb_value 0
w2 lb_factor 1 lb_value 0
  values after calc
   request   |  w1   w2   |comment
   1|   -1*   1| w1 get the Session
   2|   -2*   2| w1 get the Session
   3|   -3 3| w1 get the Session, w1 is 
first lb worker
   4|   0 0*| w2 get the Session
   5|   -1*   1| w1 get the Session
   6|   -1 0*  | w2 get the Session, w1 is in error
   7|   -1 0*  | w2 get the Session, w1 is in error
   7|   -1*   1| w1 get the Session, w1 recover

great.
regards
peter
Mladen Turk schrieb:
Rainer Jung wrote:
I include my original posting.
Hi Rainer,
First of all thank you for ideas.
They are great!
1) Limiting new application sessions if load is to high.
There is a problem with that. I made a implementation counting the
number of busy childs/threads from scoreboard (took me entire day),
but again we should count the number of connections to tomcat, cause
the apache might be serving static content.
Anyhow the idea is great and I'll implement it in the new mod_proxy
for Apache 2.2 where we have extra slots in the scoreboard.
Sad but we can not do that inside mod_jk unless we implement our
own shared memory, that was prover to be bogus in jk2.

2) Multi-Cluster-Routing
Can you write some use case for that and perhaps some simple algo
too. What about sticky-sessions and forcing failower if we do not have
session replication?
3) Idle connection disconnect
Use worker mpm. We just can not make maintainer thread for
non-treaded mpm's like apache1.2 or prefork.

4) Open Problem
I didn't check your new code, but at least before there was the 
problem, that a recovered worker that was offline a long time (in 
means of load) 

This should work now with the latest patches.
Best regards,
Mladen.
-
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]

Re: Website updates

[Peter Rossbach]

Good  idea that people can read the jk doc without internet access.
regards,
Peter
Remy Maucherat schrieb:
I propose the following changes to the main website:
- in the "Documentation" section, add "JK 1.2"
- add the new JK documentation to the website
- in the "Documentation" section, add "mod_proxy", linking to the 
Apache 2.1 documentation
- when the next Tomcat 5.5 stable is released, update the "Tomcat 
Versions" chart with 5.5, and move the Tomcat 5.0 documentation link 
to the archives

Rémy
-
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]

Re: Releasing JK1.2.7

[Peter Rossbach]

Hey Mladen,
   please do it, I am ready for testing the new staff :-)..
Peter
Mladen Turk schrieb:
Hi,
There has been lots of changes in the JK,
and I'd like to tag and release 1.2.7-beta tomorrow.
Any objections?
Also,
This release will be marked as beta, and thus not
production ready. If it passes user's testing, in
a week or two I plan to release 1.2.8 stable.
The reason for that are couple of new things added like
extensive logging, socket timeouts, new load balancer
algorithm, etc... that needs 'real-world' testing.
Any comments?
Regards,
Mladen.


-
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]

Re: tomcat 5.0.29 and request.getScheme

[Peter Rossbach]

Hey,,
please use secure="true"

  

Don't forget to create the Server keystore.
Please read the Connector docs:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/ssl-howto.html
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html
Regards
Peter
Luis Fernando Pardo schrieb:
Hello,
I have just upgraded my tomcat version from 5.0.16 to 5.0.29 and I 
have found a problem with the request.getScheme method. I have set 
apache server to listen on 443 port (SSL) and proxypass to Tomcat on 
local address (127.0.0.1) and port 9080. This is the connector 
configuration in Tomcat:

   
   

With this configuration in Tomcat 5.0.16, when I call to getScheme 
method, it returns "https" value, but in the new version 5.0.29 I 
always get "http".

Does anyone know if connector configuration in 5.0.29 has changed from 
5.0.16? or may I have doing something wrong?

Thanks  in advance


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

Re: New committer: Jean-Jacques Clar

[Peter Rossbach]

Günter Knauf schrieb:
I'd like to nominate Jean-Jacques Clar <[EMAIL PROTECTED]> as committer for the 
JTC connectors.
Jean-Jacques works for Novell where I met him already; he's there working with 
the Apache and Tomcat stuff, and since Mike left the company there's now no 
other commiter from Novell anymore with karma for the Tomcat stuff. 
Jean-Jacques is already commiter of httpd, and I think now also of apr, so I 
believe he's a good candidate.
Guenter.
 

+1
More people, More fun :-)
Great.
Peter

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

Re: Next release?

[Peter Rossbach]

Hey Remy,
I have ready my first storeconfig module to better save server.xml and 
context.xml. At the
first step I add the implementation as new module. I have wrote a 
StoreConfigLifecycleListener to register
a new Mbean .

  


Please read the short readme at 
jakarta-tomcat-catalina/modules/storeconfig/docs after my checkin.

Regards
Peter
Remy Maucherat schrieb:
Yoav Shapira wrote:
Hi,
Happy new year everyone ;)  I just got back from vacation and don't 
have time
to read all the archives.  What's the feeling as to a good time for 
the next
5.5 release?

I did some more bugfixing. Hopefully the hot deployer will be fully 
functional in this build :)

Is it ok to do a 5.5.7 tag ?
Rémy
-
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]

Re: Next release?

[Peter Rossbach]

Hey Remy,
yes, but I thing we need some test. Than I can made the complete 
integration.

Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hey Remy,
I have ready my first storeconfig module to better save server.xml 
and context.xml. At the
first step I add the implementation as new module. I have wrote a 
StoreConfigLifecycleListener to register
a new Mbean .

   


Please read the short readme at 
jakarta-tomcat-catalina/modules/storeconfig/docs after my checkin.

So I say we delay 5.5.7 so that it is integrated well (I would assume 
the main thing to do is to remove the old code).

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: Next release?

[Peter Rossbach]

OK, I can do that at monday.
Thanx
Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hey Remy,
yes, but I thing we need some test. Than I can made the complete 
integration.

I vote in favor of doing the complete integration right now. Worst 
case it's as bad as the current code, which isn't exactly well tested 
in the 5.5 branch ;)

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: cvs commit: jakarta-tomcat-catalina/webapps/docs changelog.xml

[Peter Rossbach]

Hello Remy,
Thanx for your help and I hope we have now a better server.xml saving 
support.

The new features are:
-  Clustering support
-   new 5.5 Connector attribute mapping support (with correct https saving)
-   backup the context.xml also as default mode
-   Internally you can save Server/Service/Host/Context at PrintWriter
-   configurable and extendable
I hope we have fun with the new modul :-)
Peter
s.u
Remy Maucherat schrieb:
Remy Maucherat wrote:
I've thought about this more. Actually, maybe it's better to leave an 
indirection (and keep the compatibility as a bonus). Otherwise, we 
start to have to hardcode (or make configurable = more complexity) an 
ObjectName. So I think you probably have made the right choice.

Now that I have looked at it, I have some comments:
- nearly all of the logging is done as log.error(e), which isn't cool, 
because it logs e.toString() rather than a stack trace
Yes, this is a ToDO and I spent time for this.
- I think some special cases are needed for Context handling (but it's 
not very high priority, the current stuff does the job):

  * avoid saving information which is in the default context 
configuration (I think MBeans should be added for exposing the context 
defaults)
Yes, the Context handling is very spezial. Currently the only chance is 
parse context defaults at a fresh new Context and strip down the real 
Context. Bad,Bad and no easy :-(  I hope we have at future a 
DefaultContext MBean and use this at HostConfig and StoreConfig.

  * don't save "path" except in server.xml
I thing that can I fix!
  * don't save "docBase" if the webapp is in the host "appBase"   
OK!

It seems to work as well as the old code, so it's great :)

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: 5.5.7 ?

[Peter Rossbach]

Yes, I thing the first step to better saving server.xml is done!
+1
Vote for Release 5.5.7
Peter
Remy Maucherat schrieb:
I think the initial work on the new config save is now done, and it 
appears to be working at least as well as the old one.

Yoav, would it be ok to do a new build picking up all the changes and 
fixes ?

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


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: 5.5.7 ?

[Peter Rossbach]

Well, that really OK!
Peter
Yoav Shapira schrieb:
Hi,
It's certainly OK for you to do one ;)  If you want me to do it, that's also
OK, but it will have to wait until this weekend.  Either way is fine with
me.  I haven't looked at (much less written) any code recently, as I
expected for this January boot camp at school...
Yoav
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 13, 2005 8:00 AM
To: Tomcat Developers List
Subject: 5.5.7 ?

I think the initial work on the new config save is now done, and it 
appears to be working at least as well as the old one.

Yoav, would it be ok to do a new build picking up all the changes and 
fixes ?

Rémy
-
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]

 


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: Sorry, no time to cut release

[Peter Rossbach]

Hey ,
I have test it and it works for me, but you are right, I have also two  
mx4j-2.1.0  directories
The old MX4j.2.0.1 has no main directory inside the zip, the new one has 
one. :-)

Regards
Peter
Dominik Drzewiecki schrieb:
Remy Maucherat <[EMAIL PROTECTED]> wrote:
 

I updated the dependencies to current builds.
 

FYI. mx4j-2.1.0 seems to bee unpacked to wrong directory (one mx4j-2.1.0 
too far), so that the next build pass doesn't find libraries and downloads 
mx4j-2.1.0 again.

/dd

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

 


--
J2EE Systemarchitekt und Tomcat Experte
http://objektpark.de/
http://tomcat.objektpark.org/
http://centaurus.sourceforge.net/
Am Josephsschacht 72, 44879 Bochum, Deutschland
Telefon:  (49) 234 9413228
Mobil:(49) 175 1660884
E-Mail:  [EMAIL PROTECTED]

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

Re: [VOTE] Tomcat 5.5.7 Stability

[Peter Rossbach]

Yoav Shapira schrieb:
Hi,
Tomcat 5.5.7 was released a week ago, and now it's time for a stability vote ;)
I have yet to see TCK results, but this has been a crazy month for everyone it
seems...
[ ] Alpha: leave it as-is, numerous bugs, etc.
[ ] Beta: good quality release, at least one issue preventing stable vote
[X] Stable: solid, no major issues (minor issues possible)
 

Stable
:-)
Peter
Thanks for voting,
Yoav
-
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]

Re: [VOTE] Proposed API change to the Manager interface

[Peter Rossbach]

Hmm,
I think that Remy's patch is working correct. But I think we must 
controll the jvmRoute
from those client sessions id's (ManagerBase include this at a comment :-)).
I must check my cluster failover szenarios. I can to that tomorrow.

Peter
Rainer Jung schrieb:
Both Cluster Managers (Delta and SimpleTcpReplication) extend ManagerBase
but override createSession().
Maybe Filip or Peter can check how to make them long-time compatible with
your proposal?
 

Managers extending ManagerBase should work and compile as before with no
   

changes unless they override the createSession method.


-
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]

Some Compiler Error with mod_jk Windows

[Peter Rossbach]

Morning Mladen,
I checkout the news Tomcat 5.5 head and can't compile mod_jk today.
Yesterday morning it works great
Use Windows XP
MSDEV 6.0
Apache 2.0.49
regards
Peter
D:\tomcat\jakarta-tomcat-connectors\jk\native\apache-2.0>MSDE
V mod_jk.dsp /MAKE ALL
Konfiguration: apache - Win32 Debug
Kompilierung läuft...
jk_ajp12_worker.c
jk_ajp13_worker.c
jk_ajp14_worker.c
D:\tomcat\jakarta-tomcat-connectors\jk\native\common\jk_ajp14
_worker.c(105) : warning C4013: 'apr_snprintf' undefiniert; Annahme: 
extern mit
Rueckgabetyp int
jk_jni_worker.c
jk_lb_worker.c
jk_status.c
D:\tomcat\jakarta-tomcat-connectors\jk\native\common\jk_statu
s.c(138) : warning C4013: 'apr_vsnprintf' undefiniert; Annahme: extern 
mit Rueck
gabetyp int
jk_worker.c
Generieren von Code...
Linker-Vorgang läuft...
  Bibliothek Debug/mod_jk.lib und Objekt Debug/mod_jk.exp wird erstellt
jk_status.obj : error LNK2001: Nichtaufgeloestes externes Symbol 
_apr_vsnprintf
jk_util.obj : error LNK2001: Nichtaufgeloestes externes Symbol 
_apr_vsnprintf
Debug/mod_jk.so : fatal error LNK1120: 1 unaufgeloeste externe Verweise
Fehler beim Ausführen von link.exe.

mod_jk.so - 3 Fehler, 2 Warnung(en)
Konfiguration: apache - Win32 
Release
Kompilierung läuft...
jk_ajp12_worker.c
jk_ajp13_worker.c
jk_ajp14_worker.c
D:\tomcat\jakarta-tomcat-connectors\jk\native\common\jk_ajp14
_worker.c(105) : warning C4013: 'apr_snprintf' undefiniert; Annahme: 
extern mit
Rueckgabetyp int
jk_jni_worker.c
jk_lb_worker.c
jk_status.c
D:\tomcat\\jakarta-tomcat-connectors\jk\native\common\jk_statu
s.c(138) : warning C4013: 'apr_vsnprintf' undefiniert; Annahme: extern 
mit Rueck
gabetyp int
jk_worker.c
Generieren von Code...
Linker-Vorgang läuft...
  Bibliothek Release/mod_jk.lib und Objekt Release/mod_jk.exp wird erstellt
jk_status.obj : error LNK2001: Nichtaufgeloestes externes Symbol 
_apr_vsnprintf
jk_util.obj : error LNK2001: Nichtaufgeloestes externes Symbol 
_apr_vsnprintf
Release/mod_jk.so : fatal error LNK1120: 1 unaufgeloeste externe Verweise
Fehler beim Ausführen von link.exe.

mod_jk.so - 3 Fehler, 2 Warnung(en)
D:\tomcat\jakarta-tomcat-connectors\jk\native\apache-2.0>

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

Re: Some Compiler Error with mod_jk Windows

[Peter Rossbach]

Hello Mladen,
now I have update to Apache 5.0.53, but the failure changed a little bit :
D:\tomcat\jakarta-tomcat-connectors\jk\native\apache-2.0>MSDE
V mod_jk.dsp /MAKE ALL
Konfiguration: apache - Win32 Debug
Kompilierung läuft...
jk_ajp12_worker.c
jk_ajp13.c
jk_ajp13_worker.c
jk_ajp14.c
jk_ajp14_worker.c
jk_ajp_common.c
D:\tomcat\akarta-tomcat-connectors\jk\native\common\jk_ajp_c
ommon.c(756) : warning C4018: '==' : Konflikt zwischen signed und unsigned
D:\tomcat\jakarta-tomcat-connectors\jk\native\common\jk_ajp_c
ommon.c(757) : warning C4018: '==' : Konflikt zwischen signed und unsigned
jk_connect.c
jk_context.c
jk_jni_worker.c
jk_lb_worker.c
jk_map.c
jk_md5.c
jk_msg_buff.c
jk_pool.c
jk_shm.c
jk_sockbuf.c
jk_status.c
jk_uri_worker_map.c
jk_util.c
jk_worker.c
Generieren von Code...
Kompilieren...
mod_jk.c
Generieren von Code...
Linker-Vorgang läuft...
  Bibliothek Debug/mod_jk.lib und Objekt Debug/mod_jk.exp wird erstellt
Regards
Peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Morning Mladen,
I checkout the news Tomcat 5.5 head and can't compile mod_jk today.
Yesterday morning it works great
Use Windows XP
MSDEV 6.0
Apache 2.0.49
Fixed, thanks.
Also I would suggest that you use more recent apaches for Windows.
Pre 2.0.52 have bugs with transmitfile if you have third party
winsock, like firewalls etc.
Regards,
Mladen
-
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]

First look at new mod_jk status page

[Peter Rossbach]

Hello Mladen,
new status page work fine. Really cool ;-)
Only the type of a workers was currently not correct displayed. 
I got "unknown" as value. opps! Is it planned that we can save the worker configuration as seperate workers.properties? How we can transfer the information to an Tomcat MBeanServer? Can I help to fix the old Java AJP jk2 handler or start with a new implementaion? Can we get the status information as XML document? Not really important but easier to integrate in some monitoring products.

What are your next steps?
Here my working configuration:
workers.properties

worker.list=lb,status
worker.node1.port=9012
worker.node1.host=localhost
worker.node1.type=ajp13
worker.node2.port=9022
worker.node2.host=localhost
worker.node2.type=ajp13
worker.node3.port=9032
worker.node3.host=localhost
worker.node3.type=ajp13
worker.lb.balanced_workers=node1,node2,node3
worker.lb.type=lb
worker.status.type=status
And at httpd.conf
JkMount /status/* status
Many Thanx
Peter

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

Re: [VOTE] Propose Jim Jagielski and William A. Rowe as JakartaTomcatConnectors commiters

[Peter Rossbach]

++1
welcome on board, we need help
Thanks
Peter
Mladen Turk schrieb:
I'd like to nominate Jim Jagielski ([EMAIL PROTECTED]) and
William A. Rowe ([EMAIL PROTECTED]) as commiters for the
JTC connectors.
Both of them are long time ASF members. Jim is even a
director of Apache Software Foundation.
They both are core apache httpd designers and developers
for years now, and IMHO we should be proud tho have them
on board :). I'm sure they will help us with the better
apache httpd integration.
So...
[x] Yes, Jim is really a cool guy.
[ ] No way.
and..
[x] Sure, wellcome Bill.
[ ] I think I know httpd better then him.
The both have my ++1.
Regards,
Mladen

-
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]

Re: JK Removing local_worker and local_worker_only directives

[Peter Rossbach]

Hello Mladen,
after a very long thinking I have missing a hot Standby feature, when we 
remove local_work flag.

Example
two   tomcat instance with local_worker=true and domain=A
one   tomcat instance with local_worker=false and domain=B
New session only generate to domain A  tomcat instance
After complete disable all domain A instance, the new sessions fork to 
tomcat  instances at domain B ( hot standby)
After complete domain A instances failure all requests forward to domain 
B instances.

How I can configure this without local_work flag?
I thing we can rename the flag to preferred_worker.
Peter
Mladen Turk schrieb:
Hi,
I would like to deprecate the local_worker and local_worker_only
directives.
The reason is that we have now shared memory, and thus more powerful
ways to accomplish it's use.
Now, we two new directives 'redirect' and 'domain' that are more
powerful then exiting ones.
Here is how it works:
1. If there is a session the request is routed to the worker.
2. If there is no session and the worker is disabled, meaning not
   accepting new connections then the request is redirected to
   the 'redirect' router if present or 'domain' if not.
3. If there is a session and the worker is in error state and
   the 'sticky_session_force' is not set then the 'redirect'
   and 'domain' are checked.
4. If there is a session and the worker is in error state and
   the 'sticky_session_force' is set the 500 is returned.
Here is the simple state table:
('x' means don't care, '-' means not set)
 
| worker | session | route | domain | force | err | dis | result |
 
| w1 | w1  |   x   |   x| x | 0   |  x  | w1 |
 
| w1 | w1  |   x   |   x| 1 | 1   |  x  | 500|
 
| w1 | w1  |   w2  |   x| 0 | 1   |  x  | w2 |
 
| w1 | w1  |   -   |   grp  | 0 | 1   |  x  | grp|
 
| w1 | -   |   -   |   -| x | 0   |  0  | any|
 
| w1 | -   |   -   |   grp  | x | 0   |  0  | grp|
 
| w1 | -   |   -   |   -| x | 0   |  1  | !w1|
 
So, basically the local_worker_only will become 'sticky_session_force',
that is more descriptive meaning of the actual usage.
Regards,
Mladen.
-
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]

Re: JK Removing local_worker and local_worker_only directives

[Peter Rossbach]

Hello Mladen,
hmm, with your example I got a Internal Server Error after I disable or 
drop active node2 and start a new session request! :-(
All request with active node2 session work properly when node2 shutdown! 
What I want is that after a failure,
the node1 got all requests. This szenario work very well with old 
local_worker mode.

Here my test confguration:
worker.list=lb,status
worker.node1.port=9012
worker.node1.host=localhost
worker.node1.type=ajp13
worker.node1.disabled=true
worker.node2.port=9022
worker.node2.host=localhost
worker.node2.type=ajp13
worker.node2.disabled=false
worker.node2.redirect=node1
worker.lb.balance_workers=node1,node2
worker.lb.type=lb
worker.status.type=status
Peter

Mladen Turk schrieb:
Peter Rossbach wrote:
Hello Mladen,
after a very long thinking I have missing a hot Standby feature, when 
we remove local_work flag.

How I can configure this without local_work flag?
I thing we can rename the flag to preferred_worker.
OK.
Worker B used as hot standby:
worker.A.redirect=B
worker.B.disabled=True
worker.LB.sticky_session=True
worker.LB.balance_workers=A,B
If you wish to have a hot-standby
tomcat cluster group, then use domains.
For single workers use worker names.
So worker B is initially disabled.
Worker A has redirect of 'failover' to B.
Worker B will not receive any requests unless
worker A gets in error state or disabled.
If worker A gets disabled existing sessions will
be still served, new one will go to B.
Later you can use jkstatus, and switch their roles.
Mladen.
-
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]

Re: JK Removing local_worker and local_worker_only directives

[Peter Rossbach]

Well,
but at my test following is not the case:
>>Other thing is if Node2 breaks, then Node1 will
>>take old and new requests.
It works only for old requests, but new request get an Internal Server 
Error!

Test with Apache 2.053, Windows XP, mod_jk CVS Head, Tomcat 5.5.8, JDK 1.5.0
Peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Hello Mladen,
hmm, with your example I got a Internal Server Error after I disable 
or drop active node2 and start a new session request! :-(
All request with active node2 session work properly when node2 
shutdown! What I want is that after a failure,
the node1 got all requests.

Sorry, but this works well and as expected.
1. Node2:in_error -> redirect to node1
2. Node2:disabled -> exiting sessions to node2
   if Node1 disabled too -> 500
3. Enable Node1 -> new sessions to Node1
So you will need to enable node1 then disable node2
if you are doing maintenance.
Other thing is if Node2 breaks, then Node1 will
take old and new requests.
Mladen.
-
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]

Re: JK Removing local_worker and local_worker_only directives

[Peter Rossbach]

Morning Mladen,
I have build with newest patch and the redirect working well. Thanks :-)
But the same szenario with domains don't work
workers.properties:

worker.list=lb,status
worker.node1.port=9012
worker.node1.host=localhost
worker.node1.type=ajp13
worker.node1.disabled=true
worker.node1.domain=A
#worker.node1.redirect=node2
worker.node2.port=9022
worker.node2.host=localhost
worker.node2.type=ajp13
worker.node2.disabled=false
worker.node2.domain=A
#worker.node2.redirect=node1
worker.node3.port=9032
worker.node3.host=localhost
worker.node3.type=ajp13
worker.node3.disabled=false
worker.node3.domain=A
worker.lb.balance_workers=node1,node2,node3
worker.lb.type=lb
worker.status.type=status
szenarios:
node1 is disabled
node2 is active
node3 is active
start only node1
start firefox
Request failed with Internal Error
szenario 2
node1 is disabled
node2 is active
start node1, node2
request successfull
stop node2
request failed
Start a new Browser (mozilla) request failed again with Internat Error
Peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Well,
It works only for old requests, but new request get an Internal 
Server Error!

Yes, seems that my test case was broken.
It should work now. Can you check?
Mladen.
-
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]

Re: JK Removing local_worker and local_worker_only directives

[Peter Rossbach]

Hello Mladen,
no, the redirect domain feature don't work for me.
Here my configuration:
worker.list=lb,status
worker.node1.port=9012
worker.node1.host=localhost
worker.node1.type=ajp13
worker.node1.disabled=true
worker.node1.domain=B
worker.node2.port=9022
worker.node2.host=localhost
worker.node2.type=ajp13
worker.node2.disabled=false
worker.node2.domain=A
worker.node2.redirect=B
worker.node3.port=9032
worker.node3.host=localhost
worker.node3.type=ajp13
worker.node3.disabled=false
worker.node3.domain=A
worker.node3.redirect=B
worker.lb.balance_workers=node1,node2,node3
worker.lb.type=lb
worker.status.type=status
Both described szenarios (last email) don't work with the domain 
redirect config.

Peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Morning Mladen,
I have build with newest patch and the redirect working well. Thanks :-)

Great.
But the same szenario with domains don't work
You will still need the redirect for hot-standby to work.
It's just like for workers, except that instead worker
name the domain is used, so you can have multiple
failover boxes.
worker.node1.domain=A
worker.node1.redirect=B
worker.node2.domain=A
worker.node2.redirect=B
worker.node3.domain=B
Tell me if it's work.
Mladen.
-
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]

Re: JK Removing local_worker and local_worker_only directives

[Peter Rossbach]

Hello Mladen,
Great, now my cluster hot standby works as aspected. Thanks for your 
quick help!
Current support of redirect is enough for me.

The domain 
redirect use case to startup very save a next software generation
is working with the existing domain concept.

You have two tomcat cluster domains.
Two Apaches and three tomcat instances at every cluster domain.
worker.nodeA01.domain=A0
worker.nodeA02.domain=A0
worker.nodeA03.domain=A0
worker.nodeB01.domain=B0
worker.nodeB02.domain=B0
worker.nodeB03.domain=B0
worker.list=lb,status
worker.lb.balance_workers=nodeA01,nodeA02,nodeA03,nodeB01,nodeB02,nodeB03
worker.lb.type=lb
worker.status.type=status
Now you want start a new software generation under high load
Start the new Instance A1x, B1x
change the workers.properties at apache A and B
gracefull restart the apaches.
worker.nodeA01.domain=A0
worker.nodeA01.disabled=True
worker.nodeA02.domain=A0
worker.nodeA02.disabled=True
worker.nodeA03.domain=A0
worker.nodeA03.disabled=True
worker.nodeB01.domain=B0
worker.nodeB01.disabled=True
worker.nodeB02.domain=B0
worker.nodeB02.disabled=True
worker.nodeB03.domain=B0
worker.nodeB03.disabled=True
worker.nodeA11.domain=A1
worker.nodeA12.domain=A1
worker.nodeA13.domain=A1
worker.nodeB11.domain=B1
worker.nodeB12.domain=B1
worker.nodeB13.domain=B1
worker.list=lb,status
worker.lb.balance_workers=nodeA11,nodeA12,nodeA13,nodeB11,nodeB12,nodeB13,nodeA01,nodeA02,nodeA03,nodeB01,nodeB02,nodeB03
worker.lb.type=lb
worker.status.type=status
Old Session A0x, B0x working very well for old existing session and 
replicated backup.
All new sessions goes to A1x,B1x nodes
After a some times, the admin can drop the old nodes (A0x, B0x) with 
zero sessions active and than remove the
A0x and B0x workers.

How can I force a autoreloading with update the workers.properties, 
without gracefull restart the apache?

Thanks very much,
Peter
Mladen Turk schrieb:
Mladen Turk wrote:
You will still need the redirect for hot-standby to work.
It's just like for workers, except that instead worker
name the domain is used, so you can have multiple
failover boxes.
Sorry, It won't failover to domain, so:
worker.node1.domain=A
worker.node1.redirect=node3
worker.node2.domain=A
worker.node2.redirect=node3
worker.node3.domain=A
worker.node3.disabled=True
I'll see if and how a failover redirection
for hot standby can be made to a group of workers.
Not sure if this will have any real world usage, but
it can be made.
Convince me why would someone need 5 boxes not doing
anything just in case. I mean, a single one should be
enough ;).
Mladen.
-
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]

Re: Release status ?

[Peter Rossbach]

Hey Remy,
I also think we can plan next week a 5.5.9 release and I test the new 
logging feature later today.

Other question:
I have wrote a JKStatusUpdateTask ant task for the new jk 1.2.9 status 
worker and
use the o.a.c.ant.AbstractCatalinaTask as super class.
I am not sure that o.a.c.ant is really the correct package for those 
connector ant task

What are the planed feature for the new host manager tool? Have you
see the Centaurus-Platform (http://centaurus.sf.net) Management Console 
from Thorsten Kamann?.
OK, all docs are in german, but install it and look at 
http://localhost:8280/management the very great
admin tool.

Dowload it at
http://prdownloads.sourceforge.net/centaurus/centaurus-platform-1.0beta6-full-gui-installer.jar?download
Peter
Remy Maucherat schrieb:
Hi,
This week, I will work on adding the host manager tool that I promised 
long ago.

As 5.5.8 is in limbo, I think we should plan for a 5.5.9 instead. Or 
is there still some interest in that build ?

Last, did anyone test the new logging defaults ?
Thanks :)
Rémy
-
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]

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/ant JKStatusUpdateTask.java catalina.tasks

[Peter Rossbach]

Hello Mladen,
I have not implement multi output mode. I have made a very straigth forward
implementation to JkStatusUpdateTask. The current implementation can't 
read the current Apache jk config

The following statements are used
loadbalancer update
http://localhost/status?cmd=textupdate&w=lb&lf=false&ls=true
   lr is int >= 1
   lt is int >= 59
worker update
http://localhost/status?cmd=textupdate&w=node1&l=lb&wf=1&wd=false
   here I used for the parameter l for the name of the loadbalancer! I 
not need it for textupdate command

I also thing that next stepfor jk_status is a multi channel output mode! :-)
All worker names are URLEncoded and you can setup the charset at the ant 
task.
I wan't deal directly with the worker names at my script and not with 
the internal id's.

Peter

Mladen Turk schrieb:
Hey this is cool :).
[EMAIL PROTECTED] wrote:
  Log:
  add JkStausUpdate task for mod:jk status worker (greater mod_jk 
1.2.9 only)
  

I thought it was meant to be an XML, to pick up the config from apache.
Also, can you keep the cmd=update and add something like:
"&mime=html|xml|txt" ?
Further more 'lr' and 'lb' params are using integer values (worker id's)
so you will need to use integers or change the code to accept strings.
The reason why I choose the integers or id's was because in that case
there is no need to url encode worker names. Of course we can what
documentation says accept only alnums for worker names, but that will
break backward compatibility in some cases.
I would like for this version to add ERROR message in the log if
worker name is non-url safe, but still allow it for now.
IMO ant task should pick up default values from apache directly by
parsing xml output.
Regards,
Mladen
-
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]

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/ant JKStatusUpdateTask.java catalina.tasks

[Peter Rossbach]

Hello Mladen,
OK, I made a try to extract the jk status information from html.
I hope I can do that in the next week
Peter
Mladen Turk schrieb:
Peter Rossbach wrote:
I have not implement multi output mode. I have made a very straigth 
forward
implementation to JkStatusUpdateTask. The current implementation 
can't read the current Apache jk config

Any chance to enable reading jkstatus, so that manager can display
mod_jk config. I was thinking that we would build that in such
a way. I know it's a lot of work, but ...
Regards,
Mladen.
-
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]

Re: cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/ant JKStatusUpdateTask.java catalina.tasks

[Peter Rossbach]

Cool,
after you intergrate that xml mode  I wrote the Ant task
Great :-)
peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Hello Mladen,
OK, I made a try to extract the jk status information from html.
I hope I can do that in the next week
There is no need to do that.
I'll make a complete xml dump for jkstatus.
We already have xml mode for mod_proxy so in that
case this will be reusable.
Html should be used only in standalone mode.
Mladen.
-
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]

Re: [JK] Releasing 1.2.9

[Peter Rossbach]

Great,
i have fix the JkStatusUpdateTask and hope I can implement a 
JkStatusListTask to parse
the new xml output format.

Only thing that I missing is that we can add a css style sheet to html 
output and xsl style
sheet to xml output.

worker.status.type=status
worker.status.css=jkstatus.css
or
worker.status.css=http://host//jkstatus.css
worker.status.xsl=jkstatus.xsl
worker.status.xsl= http://host//jkstatus.xsl
How the status worker parameter parsing work?
Peter
Mladen Turk schrieb:
Hi,
I wish to release the 1.2.9 as beta
when Peter updates the jkstatus ant task for manager :).
I think that the amount of work done last couple of
months since 1.2.8 was released, deserves that.
What's left is updating documentation, that I wish
to finish during the beta release.
Comments?
Regards,
Mladen.
-
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]

Re: Time for TLP?

[Peter Rossbach]

Yoav Shapira schrieb:
I think we're ready to move Tomcat to a TLP.  There's a lot of support for
it in the general Jakarta and ASF ranks.  Before we write and vote on a
proposal, I wanted to see informally what the opinions are within our own
group about this potential move.  I'm obviously +1.
 

+1, I think the tomcat community is big ... :-)
Peter

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

Re: JK 1.2.9 Release

[Peter Rossbach]

Hello Mladen,
Sounds good, some of my customers wait for a new stable release :-)
Can we change the xml status format to attribute semantic?
http://jakarta.apache.org";>
   
   
  
   
   
 
   


currently the format is:
-
   

-
   
-
   
0
lb
lb
True
False
3
60
-
   
0
node1
ajp13
localhost
9012
127.0.0.1:9012
.

The attribute format is much eaisier to parse with diegster! I want 
implement a Jk Proxy Mbean
for easy report the status with mc4j.

Regards
Peter
Mladen Turk schrieb:
Hi,
There has been some commits since 1.2.9 was released as beta.
Since they are non-critical, because they do not change
the operation, but rather the return error messages, I would
still like to tag the release as 1.2.9.
I'll give couple of days and propose a vote for official
announcement. If passed, then we'll just declare it as stable.
If some critical errors gets discovered, I'll just drop the
release and go for 1.2.10.
How that sounds?
Regards,
Mladen.
-
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]

Re: JK 1.2.9 Release

[Peter Rossbach]

OK,
I look inside the code and made the changes.
peter
Mladen Turk schrieb:
Peter Rossbach wrote:
Hello Mladen,
Can we change the xml status format to attribute semantic?
Feel free to commit the changes :)
This is also syntactic sugar, so if it's valid xml
se no reason why not.
Regards,
Mladen
-
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]

Re: [VOTE] PMC Chair

[Peter Rossbach]

Hello Henri,
here ist my vote ([EMAIL PROTECTED])
The initial Tomcat PMC chair should be:
[X ] Remy Maucherat
[  ] Yoav Shapira

regards
Peter
Henri Yandell schrieb:
Just as an update, I've recorded 11 public/private votes from:
Keith Wannamaker (keith)
Mark Thomas (markt)
Larry Isaacs (larryi)
Filip Hanak (fhanak)
Tim Funk (funkman)
Kin-man Chung (kinman)
Henri Gomez (hgomez)  
Mladen Turk (mturk)
Costin Manolache (costin)
Jim Jagielski (jim)
Bill Barker (billbarker)

There are 70 committers, and it's a holiday weekend (4 day weekend in
some places, so not back til Tuesday) so I suspect it's best to keep
the vote open for some more time.
The above, plus Remy and Yoav, would represent the proposed PMC list,
and I'll report on additional votes on Tuesday night.
Hen
-
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]

Question: Strange Session Remove Attribute

[Peter Rossbach]

Hey
I have review the getIdInteral changes. At expire (StandardSession, DeltaSession) we 
send first the "SessionDestory events" and after this the "Remove Session Attribute" events. Before we send the remove attribute events the session set to invalid. Hmm: Why we do that? I have read the spec 2.4 but I can find a hint. With this handling nobody can access the getId without IllegalStateException in a HttpSessionBindingListener or HttpSessionAttributeListener! That I can't find this very nice?

Can anyone explain this session event handling?
regards
Peter

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

Re: Question: Strange Session Remove Attribute

[Peter Rossbach]

Hmm,
I see the following problem with the current session expire strategie.
Today
   a) Notify session destroy event
 => All session attributes are active
   b) Set session as invalid
   c) Notify session remove attribute event - Hups
=> Now the listener detect IllegalStateExceptions
The session attribute listener in normal mode can access the session and 
this is very usefull
to monitoring the app behaviour. At expire session the listener have no 
chance to detect the
invalidation mode.

Now I see to chance to make better support for this case:
1)  add HttpSession.isValid() method
   => Very fine then also other code filter, and jsp can detect the 
Session invalidation.
2)  Add event methods to HttpSessionListener
   public void sessionDestroyed ( HttpSessionEvent se );
   public void sessionAfterDestroyed ( HttpSessionEvent se );
=> Second method emit after all attribute remove from session and now 
session is invalid ;-(

I vote for the first case, but this means wait for Servlet API 2.5.

Another problem I detect is at StandardContext listener event notification
   At listenerStop (L 3721)
  we remove the ApplicationEvent Listeners
<<
  setApplicationEventListeners(null);
  setApplicationLifecycleListeners(null);
>>
but we need the Listener at
  StandardContext#clearAttributes => 
ApplicationContext#removeAttribute L695

=> Currently we don't emit removeAttribute Events when Context. stop.
Simple fix integrate clearAttributes at listenerStop before remove 
listeners.
OK?

=
Other thing is: that we don't emit remove request attribute events after 
ServletRequestListener was notify with requestDestory.
I can find this handling at org.apache.catalina.connector.Request.recycle
At L 391 we clear the attributes, but don't notify the request 
attribute listener.
Is this behaviour spec conform?
What is with request attributes that exist before or after request 
wrapper is active ( s. StandardContextValve#invoke)?
Must we have extra map for real application request attributes and 
another one for container side request attributes ?
  Sounds really strange :-)

Regards
Peter
Remy Maucherat schrieb:
Bill Barker wrote:
Hey
I have review the getIdInteral changes. At expire (StandardSession, 
DeltaSession) we send first the "SessionDestory events" and after 
this the "Remove Session Attribute" events. Before we send the 
remove attribute events the session set to invalid. Hmm: Why we do 
that? I have read the spec 2.4 but I can find a hint. With this 
handling nobody can access the getId without IllegalStateException 
in a HttpSessionBindingListener or HttpSessionAttributeListener! 
That I can't find this very nice?

What can I say, we needed to generate more BZ reports to mark as 
INVALID ;-).

The tester actually has example code of using getId in a 
HttpSessionAttributeListener to get an ISE.

Can anyone explain this session event handling?

There was just a long discussion of this.  For the details, check the 
list archives.  The short version is that it's mandated by section 
15.1.7 + Errata 
(http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/154errata.txt). 

(maybe I shouldn't have mentioned it, as Jan didn't appear to have 
noticed it before: I may have started the trouble ...)

Rémy
-
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]

Re: Question: Strange Session Remove Attribute

[Peter Rossbach]

Hey Remy,
can you please explain why the remove attribute event notification is 
wrong when
context is destroy?

Thanks
Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hmm,
I see the following problem with the current session expire strategie.
Today
   a) Notify session destroy event
 => All session attributes are active
   b) Set session as invalid
   c) Notify session remove attribute event - Hups
=> Now the listener detect IllegalStateExceptions
The session attribute listener in normal mode can access the session 
and this is very usefull
to monitoring the app behaviour. At expire session the listener have 
no chance to detect the
invalidation mode.

Now I see to chance to make better support for this case:
1)  add HttpSession.isValid() method
   => Very fine then also other code filter, and jsp can detect the 
Session invalidation.
2)  Add event methods to HttpSessionListener
   public void sessionDestroyed ( HttpSessionEvent se );
   public void sessionAfterDestroyed ( HttpSessionEvent se );
=> Second method emit after all attribute remove from session and now 
session is invalid ;-(

I vote for the first case, but this means wait for Servlet API 2.5.

Another problem I detect is at StandardContext listener event 
notification
   At listenerStop (L 3721)
  we remove the ApplicationEvent Listeners
<<
  setApplicationEventListeners(null);
  setApplicationLifecycleListeners(null);
 >>

but we need the Listener at
  StandardContext#clearAttributes => 
ApplicationContext#removeAttribute L695

=> Currently we don't emit removeAttribute Events when Context. stop.
Simple fix integrate clearAttributes at listenerStop before remove 
listeners.
OK?

No, it's not ok, it's wrong ;)
This came up recently, and caused problems.
=
Other thing is: that we don't emit remove request attribute events 
after ServletRequestListener was notify with requestDestory.
I can find this handling at 
org.apache.catalina.connector.Request.recycle
At L 391 we clear the attributes, but don't notify the request 
attribute listener.
Is this behaviour spec conform?
What is with request attributes that exist before or after request 
wrapper is active ( s. StandardContextValve#invoke)?
Must we have extra map for real application request attributes and 
another one for container side request attributes ?
  Sounds really strange :-)

This is also outside the application scope.
Rémy
-
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]

Re: Question: Strange Session Remove Attribute

[Peter Rossbach]

Good answer!
But why we emit remove session attribute events when sesssion is destroy?
I think the session expire is also a clean up thing and nobody need the 
remove attribute events.

Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hey Remy,
can you please explain why the remove attribute event notification is 
wrong when
context is destroy?

Because you're not actually removing them, you're just cleaning up 
objects.
Did you notice you don't get notifications on start, etc ?

Rémy
-
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]

Re: Question: Strange Session Remove Attribute

[Peter Rossbach]

Hups,
the remove session attribute events after session destory is documented 
at the servlet spec?
Any hint welcome

Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Good answer!
But why we emit remove session attribute events when sesssion is 
destroy?
I think the session expire is also a clean up thing and nobody need 
the remove attribute events.

Because the stupid wording which explicitely mandates the nonsense for 
sessions isn't present for context attributes ;)
Rémy

-
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]

Re: Question: Strange Session Remove Attribute

[Peter Rossbach]

Hmm,
but I can't find a statement that the valueUnbound get an invalid 
session, when it called after sessionDestoryed.

HttpSessionBindingListener ===
  /**
*
* Notifies the object that it is being unbound
* from a session and identifies the session.
*
* @param eventthe event that identifies
*the session
*   
* @see #valueBound
*
*/

   public void valueUnbound(HttpSessionBindingEvent event);
  


I thing the part "identifies the session" is in conflict with the 
current tomcat implementation.

Today the user get a IllegalStateException at event.getSession().getId() 
instead the session identifier.
The current servlet spec is not clear at this session event definition. :(

What is correct?
-   current handling
-   emit remove session event and after this the session is invalid
-   remove emit event after invalidation
What we can do?
-   document the situation
   Add lifecycle diagrams ( state flow)
-propose a change to the spec team
Don't emit remove session attribute events, when session 
destoryed, like ServletContext and ServletRequest handling ( my favorit)
Only direct removeAttribute calls, emit remove event.

Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
Hups,
the remove session attribute events after session destory is 
documented at the servlet spec?
Any hint welcome

Yes, read the javadoc for HttpSessionBindingListener.
Rémy
-
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]

Syntax from JkEnvVar is changed

[Peter Rossbach]

Hey,
I want transfer a static version number with every request
SetEnv config.version 1.0
JkEnvVar config.version
but I got this apache startup failure

Syntax error on line 25 of 
D:/tomcat//mod_jk/mod_jk.conf:
JkEnvVar takes two arguments, Adds a name of environment variable that 
should be sent to servlet-engine

<<<
Env: Windows XP (SP2) Apache 2.0.53, mod_jk 1.2.10, Tomcat 5.5 HEAD
After I change it to
SetEnv config.version 1.0
JkEnvVar config.version none
config is working.
Other issue is, that only a request.getAttribute("config.version") give me 
access to the env attribute. The request.getAttributeNames() get only real container 
attribute names back.
Why mod_jk not transfer only those env var that really exists? How transfer a 
env var without value?
We must update the jk doc or change the semantic.
Peter

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

Re: [VOTE] 5.5.9 Stability

[Peter Rossbach]

Hey,
[X] Stable -- good build (Normal Tomcat)
[X] unstable and buggy cluster code, Argg!
The normal Tomcat features are very stable on my tests. But my  cluster 
code refactorings has
drop the clustering. I have test the cluster under load this week and 
find some very bad bugs :-(
-   Complete cluster hang sometimes
-   In some situation the async mode can't dequeue

I have build some quick fixes and can build a patch for some 5.5.9 
cluster classes (Monday evening).

Vote for a server classes fix pack or package the catalina-cluster.jar 
again.

Sorry,
Peter
Yoav Shapira schrieb:
Hi,
Tomcat v5.5.9 has been out for more than a week now, so hopefully we have
had time to test/use it.  We're still waiting for the TCK results, but let's
hear your opinion:
[ ] Stable -- good build
[ ] Beta -- minor bad stuff: what is it?
[ ] Alpha -- something serious is wrong: what is it?
The vote will run for about 72 hours as usual.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [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]

Re: [VOTE] 5.5.9 Stability

[Peter Rossbach]

Hey,
the problem is arround the keep a live handling code and the auto 
reconnect at SimpleTcpCluster.
   One thread can say: I drop the connection and open new one, then 
start transfer message and wait for ack.
   Other thread comes and see ups. the connection is not there. ( Arrg 
missing sychronized). I open a new socket and close the old current use 
socket.
   Under Suse Linux 9.1, the first thread wait for keepAlive timeout 
(60 sec). BAD!!!

   =>
  Asnyc mode the queue grow very fast.
  Sometimes all other nodes have the same problem and the complete 
cluster standing still. Nothing todo wait for ACK

  I am made very limited testing the effects at sync,pooled mode. I 
preferred the async modes.

I have merge my fix  at the 5.5.10 CVS Head Basis. Currently my customer 
start a weekend load test.
I also merge the changes at 5.5.9 Basis. Both version needs testing and 
documentation, but my time
and ressource are limited. Need help, setup clusters and start loading 
tests.

I start to open a bug report for better community discussion and add my 
fix pack for testing.
build-src
bin pack

I must review my changes and document my szenario.
Than Filip can start to review the changes and testing  the clustering.
Thanks for you help. :-)
My customers needs the new 5.5.9 Release. The best thing is, we package a
separate patch-cluster-fix and mark 5.5.9 as beta.
Peter
Filip Hanik - Dev Lists schrieb:
Hi Peter, what's up with the cluster code?
I will have some time to load test and debug any problems you might 
have, also, do you have problems on the synced-pooled setting, or on 
all connectors?

Filip

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

Re: [VOTE] 5.5.9 Stability

[Peter Rossbach]

Congratulation, too!
Peter

Yoav Shapira schrieb:
Hi,
 

The problem is that clustering only patches in HEAD may pick up
incompatible changes, like the Session.getId patch. We also shouldn't do
a new 5.5.10 tag based on HEAD, as it would pick up the risky stuff.
Maybe one solution would be to do a new 5.5.9 build, and reverting
clustering (aka, everything in the "cluster" folder) to the 5.5.8 tag.
Would that work out well enough ?
   

I think that's the best approach.  We can call it 5.5.9-beta when released,
and have a stability vote right afterwards.
I'll be incommunicado from the 14th through the 20th or so: I'm getting
married on the 17th ;)
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [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]

Re: [VOTE] 5.5.9 Stability

[Peter Rossbach]

I thing the instability is also included at 5.5.7 clustering.
>>Are you certain reverting to 5.5.8 clustering is not possible 
(meaning that it contains the same problems - or worse - as 5.5.9) ? If 
so, I think we >>need to forget about clustering stability for now, and 
mention that it is experimental in this build.

Ok, this give me and Filip time for real stability testing and review 
the 5.5.10 codebase.
I also package my fixes to the 5.5.9 codebase for some test user as bug 
report..

Peter
Remy Maucherat schrieb:
Peter Rossbach wrote:
My customers needs the new 5.5.9 Release. The best thing is, we 
package a
separate patch-cluster-fix and mark 5.5.9 as beta.

Given the state of HEAD, and given some the 5.5.7 issues, I would like 
5.5.9 to be stable. This means we would need a way to fix 5.5.9 
without new major patches (which may work well for your customer, but 
this is still very limited testing) ;)

Are you certain reverting to 5.5.8 clustering is not possible (meaning 
that it contains the same problems - or worse - as 5.5.9) ? If so, I 
think we need to forget about clustering stability for now, and 
mention that it is experimental in this build.

Rémy
-
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]

Re: [VOTE] 5.5.9 Stability

[Peter Rossbach]

Hi,
I have add my 5.5.9 clustering fix pack to the following bug report:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34389
Vote for stable 5.5.9 [X]
All clustering user can extract the fix pack and all is working well. :-)
Peter
Yoav Shapira schrieb:
Hi,
 

Ok, this give me and Filip time for real stability testing and review
the 5.5.10 codebase.
I also package my fixes to the 5.5.9 codebase for some test user as bug
report..
 

I'll let Yoav decide what he wants to do with all these builds before he
gets married (congratulations ;)). I'm very happy to not be the release
manager and have to make the tough decisions :) Go Yoav !
   

Peter, when you have a Bugzilla item and a cluster fix/test package attached
to that item, please let us know.  At that time I'll send out the vote
results, calling 5.5.9 beta and nothing that this issue (and I'll provide a
link to bugzilla) is the only thing preventing 5.5.9 from being stable, and
that users not needing/using clustering should consider 5.5.9 stable.
Yoav Shapira
System Design and Management Fellow
MIT Sloan School of Management / School of Engineering
Cambridge, MA USA
[EMAIL PROTECTED] / [EMAIL PROTECTED]
 


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