This crash seems to be related to a JVM bug. It sounds quite strange that a
method requires more than 100MB heap for Jit Compilation. You can find
several similar failure reports in the hotspot bug database.
In this case it could be useful to monitor the following parameters through
jvmstat:
1)
Hi all
I am trying to create a distributed locking mechanism for POP3 in james.
What I am trying to do is a very simple table-based mechanism, to lock some
resource in POP3Handler.doPASS and release it in POP3Handler.doQUIT.
At the moment the problem is how to get a valid db connection using Avalon
zkn ha scritto:
On 27.03.2007, at 14:31, Stefano Bagnara wrote:
zkn ha scritto:
I run it on RedHat EL3. James is running as root - I don't know if it
is possible to run it as different user and bind it on port 25.
No, with james 2.3 this is not possible.
In trunk we added support for common
Adding a gateway is the right solution.
Can you tell us what is your James version?
And what are the logs? in the jamesfolder/apps/james/logs/mailet*.log
you should at least see the attempts.
Stefano
Mark Waschkowski ha scritto:
Hi,
I just switched over to a godaddy dedicated server and re
Hi,
I just switched over to a godaddy dedicated server and realized that they
require the use of an smtp gateway (and also come with a default limit of
1000 relays / day) as described here:
http://help.godaddy.com/article.php?article_id=122
Ugh. Well, I've already spent the time to configure ev
Hi Stefano,
thank you for your hint. By the way MimeMessage is either not serialized.
I used the workaround to send to a JMS Que (as you proposed):
ByteArrayOutputStream os = new ByteArrayOutputStream();
mimeMessage.writeTo(os);
String content = os.toString();
ObjectMessage mesg = jmsSession.cre
