MailActivationAgent isn't robust within Oracle BPEL 10.1.3 release

Question

Within the new Oracle BPEL 10.1.3 release the MailActivationAgent isn’t working as robust as in the Oracle BPEL 10.1.2. release.
The problem is that sometimes the emails are picked up correctly by the process from the IMAP mailbox, but sometimes not.
We tried already several things to solve this problem, but nothing worked out.
A list of actions we tried already to bypass this problem:
- sending mails to the IMAP mailbox using a different client than Outlook
- removed all tabs/whitespaces within account.xml mailbox config file, because
this was a known issue within release 10.1.2
- use a non-encrypted password field within the account.xml mailbox config file
We encountered this problem during a migration from release 10.1.2 to release 10.1.3.1.0 (Build 061009.0802).
We retested the executed scenarios once again on release 10.1.2, but on that release every mail within the IMAP mailbox is picked up correctly by the process.
Scenario
For a specific process we need to read out an IMAP mailbox, so therefore we have a MailActivationAgent within this process.
We analyzed the logs of the application server, and there the following messages are displayed:
<2006-12-04 15:08:25,546> <ERROR> <default.collaxa.cube.activation> <HeartBeatListenerJob::execute> Error while invoking onHeartBeat() method, exception is "Cannot load header".
Some snapshots of the code are attached below to get some insight within the process and code.
bpel.xml…
<activationAgents>
<activationAgent className="com.collaxa.cube.activation.mail.MailActivationAgent"
heartBeatInterval="60">
<property name="accountName">account</property>
</activationAgent>
account.xml
<mailAccount xmlns="http://services.oracle.com/bpel/mail/account">
<userInfo>
<displayName>Eneco Process lAyer</displayName>
<organization>iFactory</organization>
<replyTo>[email protected]</replyTo>
</userInfo>
<outgoingServer>
<protocol>smtp</protocol>
<host>10.126.16.73</host>
<port>25</port>
<authenticationRequired>false</authenticationRequired>
</outgoingServer>
<incomingServer>
<protocol>imap</protocol>
<host>10.126.20.8</host>
<port>143</port>
<email>IFACAORTA</email>
<password>CRYPT{IB3B7SrA3kMYHoBDzWwsEg==}</password>
<folderName>InBox</folderName>
</incomingServer>
</mailAccount>
The domain.log of the appserver
<2006-12-04 15:08:25,546> <ERROR> <default.collaxa.cube.activation> <HeartBeatListenerJob::execute> Error while invoking onHeartBeat() method, exception is "Cannot load header".
<2006-12-04 15:08:25,562> <ERROR> <default.collaxa.cube.activation> <HeartBeatListenerJob::execute> Error while invoking onHeartBeat() method, exception is "No content".

Answer 1

For some time it worked now ok, and suddenly after a restart of the SOA Suite process manager it didn't work anymore without doing anything on the process that is using the MailActivationAgent.
The error I've got is attached below:
<2006-12-05 15:06:04,351> <ERROR> <default.collaxa.cube.activation> <HeartBeatListenerJob::execute> Error while invoking onHeartBeat() method, exception is "Error creating mail account.
An exception occured while attempting to parse the mail account from the XML file "C:\oracle\products\10.1.3.1\OracleAS_1\bpel\domains\default\metadata\Mailservice\account.xml". The exception reported is: The XML data is invalid.
The XML data is invalid; the reason is "Begin van startelement wordt verwacht.".
Please verify xml data.