Noel J. Bergman wrote:
Serge,
Noel J. Bergman wrote
I am still concerned about the Derby related crash that I saw earlier.
Anyone have a clue? And is there anything that we need to do to cleanly
shut Derby down?
I'm at -0 over using Derby at this point.
Well, we aren't talking about
> AFAIK if it has it's own virtual machine (so it's in network mode) and if
has
> more than 64MB it can gracefully handle such situations. The problem is
that under
> 64MB it can do to much for such situations - it's like an IDE that doesn't
do well
> without a minimal size :).
see below...
> No
Given that the whole crash starts with: java.lang.OutOfMemoryError, then
maybe that caused the problem with derby.
From the derby list, 64MB for it only looks like not enough.
Does anyone know anything about derby's behaviour when it runs out of
memory? I'd imagine that these errors are caught
> I am still concerned about the Derby related crash that I saw earlier.
> Anyone have a clue? And is there anything that we need to do to cleanly
> shut Derby down?
>
> --- Noel
Given that the whole crash starts with: java.lang.OutOfMemoryError, then
maybe that caused the problem with derb
Serge,
> Noel J. Bergman wrote
> > I am still concerned about the Derby related crash that I saw earlier.
> > Anyone have a clue? And is there anything that we need to do to cleanly
> > shut Derby down?
> I'm at -0 over using Derby at this point.
Well, we aren't talking about it being the only
On 11/7/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> OK, I ran another set of tests overnight, and didn't see any sign of a
> memory leak.
>
> I am still concerned about the Derby related crash that I saw earlier.
> Anyone have a clue? And is there anything that we need to do to cleanly
> shut
> [...] The next
> thing after that will be more aggressive looking for memory
> leaks, and the interesting task of converting my production
> configuration to the new scheme. If that works, great. If
> not, we have some tweaking to do.
> :-) Plus whatever comes back from user tests.
OK, I ran
Serge Knystautas wrote:
> Any chance we can use ASF hardware to conduct these tests
> so other people can help?
Interesting thought. We could ask for a JAMES zone, but we will have to be
very careful (a) not to permit others to access JAMES there for spam, and
(b) to make sure that we don't undu
> [...] The next
> thing after that will be more aggressive looking for memory
> leaks, and the interesting task of converting my production
> configuration to the new scheme. If that works, great. If
> not, we have some tweaking to do.
> :-) Plus whatever comes back from user tests.
>
> So
On 10/30/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Noel J. Bergman <[EMAIL PROTECTED]> wrote on Oct 19th:
>
> > I have run a first test, but also encountered a problem. Not with
> > JAMES, but > with the test environment. At home, I run JAMES on
> > one server, postal and rabid on another.
Noel J. Bergman <[EMAIL PROTECTED]> wrote on Oct 19th:
> I have run a first test, but also encountered a problem. Not with
> JAMES, but > with the test environment. At home, I run JAMES on
> one server, postal and rabid on another. I hadn't noticed before,
> but postal and rabid are not CPU fri
Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Planning on it. I need to re-do my testing configuration with the new
> config and test that, and then re-do my production configuration and give
> that a whirl. If those look good, I'll propose an alpha for vote. I
don't
> like posting anything that
On 10/17/05, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Planning on it. I need to re-do my testing configuration with the new
> config and test that, and then re-do my production configuration and give
> that a whirl. If those look good, I'll propose an alpha for vote. I don't
> like posting a
Serge Knystautas wrote:
> This feels extremely lame to say, but why don't we just put an alpha
> release out (once you get derby properly set as default, steps to
> migrate, whatever core issues you addressed) and not worry about all
> the other project-level issues?
Planning on it. I need to re
On 10/15/05, Scott Carr <[EMAIL PROTECTED]> wrote:
> >make changes, primarily in the smtphandler. But for now, I'm calling it
> >2.3.
> >
> Configuration changes may warrant a 3.0 release, depending on how much
> and how in depth the changes are.
+1
This feels extremely lame to say, but why don'
> So, I'm sitting here starting to work on the release.
> Amongst my questions is whether this is 2.3 or 3.0. One
> basis for the latter are the changes not so much in API, but
> in the configuration files. Administrators will need to make
> changes, primarily in the smtphandler. But for no
Noel J. Bergman wrote:
So, I'm sitting here starting to work on the release. Amongst my questions
is whether this is 2.3 or 3.0. One basis for the latter are the changes not
so much in API, but in the configuration files. Administrators will need to
make changes, primarily in the smtphandler.
Noel J. Bergman wrote:
So, I'm sitting here starting to work on the release. Amongst my questions
is whether this is 2.3 or 3.0. One basis for the latter are the changes not
so much in API, but in the configuration files. Administrators will need to
make changes, primarily in the smtphandler.
So, I'm sitting here starting to work on the release. Amongst my questions
is whether this is 2.3 or 3.0. One basis for the latter are the changes not
so much in API, but in the configuration files. Administrators will need to
make changes, primarily in the smtphandler. But for now, I'm calling
19 matches
Mail list logo
