Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-260
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-259
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-258
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-257
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-256
Here is an overview of the issue:
-
noel2004/04/16 14:02:04
Modified:.Tag: branch_2_1_fcs build.xml
Log:
updated build version
Revision ChangesPath
No revision
No revision
1.116.2.26 +2 -2 james-server/build.xml
Index: build.xml
===
noel2004/04/16 13:59:53
Modified:src/java/org/apache/james/transport/mailets/listservcommands
Tag: branch_2_1_fcs BaseCommand.java
Log:
Fix JAMES-238. Added code to set the Date: header
Revision ChangesPath
No revision
No
noel2004/04/16 13:59:14
Modified:src/java/org/apache/james/transport/mailets Tag:
branch_2_1_fcs CommandListservProcessor.java
Log:
Fix JAMES-239. Replaced the normalizeSubject code with the code from
GenericListserv. Also changed to use the AbstractRed
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Fri, 16 Apr 2004 1:52 PM
Added call to set the message's date.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-238
Here i
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Fri, 16 Apr 2004 1:51 PM
Copied the working normalizeSubject and setSubject code from the old list manager.
-
View the issue:
http://is
Noel J. Bergman wrote:
I appreciate that you are pushing hard to have a defined release *NOW* and
do NOT want to wait for the DSN mailet. I do not want to lose the fixes in
the common code that are already in place since 2.2.0a18, and I really have
no idea how much coverage we've had on 2.2.0a-any
> There are /always/ changes to be made. The a18 release we have out has
> no new show stoppers, and it represents 11 months of improvements and
> fixes.
> Any work you do over the next several days will require a good week of
> additional testing, so that means we won't have 2.2.0 out until late
I'm on it - JAMES-155 that is. I agree that it's probably not a bug so
I've pinged the reporter to get more information.
Steve
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 16, 2004 8:52 AM
> To: James Developers List
> Subject: RE: Vote to
Noel J. Bergman wrote:
I am eager to get v2.2.0 out the door and done, but we know that there is a
short list of outstanding defects. Plus there are defects already fixed for
the next drop, which I was planning to do today.
There are /always/ changes to be made. The a18 release we have out has
n
As a user rather than a developer, my comment would be:
The James team did exactly what I wanted - cut a16 - now followed by a17 and
a18 to incorporate the improvements over 2.1.3.
There has been significant activity on the mailing lists since a16 and I
think this has confirmed the product has an
> Please can you send me a copy of the thread dump at [EMAIL PROTECTED]
Sent, along with a copy of the code that was exhibiting it. Please let me
know what you figure out.
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROT
+1 from me!
I'm using in production the various 2.2.0.ax since the very beginning, and
they have been always super, and much stronger then 2.1.3.
Currently I have in production 2.2.0a15, so I haven't tested 2.2.0a18 at
all, but I "swear" at least up to a15 :-)
I'm only sorry for not having helped
Noel,
Please can you send me a copy of the thread dump at [EMAIL PROTECTED]
This sounds very similar to another problem I've seen recently and I'd
like to see if it's possibly related.
Thanks
Steve
> -Original Message-
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Friday, Ap
I am eager to get v2.2.0 out the door and done, but we know that there is a
short list of outstanding defects. Plus there are defects already fixed for
the next drop, which I was planning to do today.
Fixes already made since a18:
InetAddress caches without regarding to DNS TTL. Switch
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:41 AM
Changes:
Component changed to Matchers/Mailets (bundled)
-
For a full history
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:39 AM
Changes:
Fix Version changed to 2.2.0
-
For a full history of the issue, see:
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Fri, 16 Apr 2004 8:37 AM
As far as I can see, this is not a defect present in James.
-
View the issue:
http://issues.apache.org/jira/br
The following comment has been added to this issue:
Author: Noel J. Bergman
Created: Fri, 16 Apr 2004 8:35 AM
Body:
Are you typing:
DATA
.
If so, that is a different issue. Try typing:
DATA
.
And let us know if that works. If so, the problem is a different one than reporte
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:31 AM
Changes:
Fix Version changed to 2.2.0
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:32 AM
Changes:
Fix Version changed to 2.2.0
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:31 AM
Changes:
Fix Version changed to 2.2.0
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:29 AM
Changes:
Component changed to Matchers/Mailets (bundled)
Component changed from Mailet API
-
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 8:28 AM
Changes:
Fix Version changed to 2.2.0
-
For a full history of the issue, see:
+1 from me
I am now using a18 as my production build.
It does what it says on the tin :) (UK advert)
> -Original Message-
> From: Serge Knystautas [mailto:[EMAIL PROTECTED]
> Sent: 16 April 2004 16:00
> To: [EMAIL PROTECTED]
> Subject: Vote to officially release a18 build
>
> I've just
I've just watched Noel lose 2 days of his life to trying to fix a
combination of JVM, MySQL, and ***the database connection pool we
deprecated 8 months ago***!!!
IMHO, the a18 build is as worthy of official release status as much as
any open source or Microsoft release. The website and docs ar
Marcus,
Would you please review and test the version of JdbcDataSource I just
committed?
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
noel2004/04/16 07:49:48
Modified:src/java/org/apache/james/util/mordred Tag: branch_2_1_fcs
JdbcDataSource.java
Log:
Attempt to fix JAMES-254. Change to ArrayList from Vector, and simplify
synchronization. This version has been tested with JDK 1.4.2 and
Message:
The following issue has been resolved as WON'T FIX.
Resolver: Noel J. Bergman
Date: Fri, 16 Apr 2004 7:45 AM
This is not a problem in James. Apparently, it is a problem using Hotspot, possibly
just tthe server version, in JDK 1.4.0 and 1.4.1. Apparently fixing a deadlock
The following issue has been updated:
Updater: Noel J. Bergman (mailto:[EMAIL PROTECTED])
Date: Fri, 16 Apr 2004 7:42 AM
Changes:
description changed from This definitely (empirically) effects
SMTPServer. It may also effect the other protocol handlers, since their str
> is this a previously known bug in the JVM?
> If it's a known bug, do you have a link with more details?
I haven't found a link. I had heard from a friend at BEA about it, who also
looked over the thread dump. Last night Dain Sundstrom also told me about
bugs in 1.4.0 and 1.4.1 related to synch
Noel, I'm curious, is this a previously known bug in the JVM? If it's a
known bug, do you have a link with more details?
Thanks...
Reportedly, this is a sign of a problem present in Sun JVM 1.4.0 and 1.4.1. It seems to have been exacerbated by the fix for JAMES-253.
36 matches
Mail list logo
