On Tue, Aug 20, 2013 at 9:42 AM, Ishara Premadasa ish...@wso2.com wrote:
On Mon, Aug 19, 2013 at 11:29 PM, Kasun Gajasinghe kas...@wso2.comwrote:
However the only incident i have seen a rapid error log thrown
continuosly in the MB or ActiveMQ integration scenario is, when you start
AS
Hi Kasun,
I first tried the JMS transport reconnection mechanism with AS 5.1.0 and
then i tried with the newly built AS 5.2.0 pack. However with both these
packs the reconnection works fine where it waits for the JMSConnection to
come alive by retrying in exponentially increasing time intervals.
Hi Ishara,
Please note that I tried this with ActiveMQ. I didn't see the reconnection
attempts in the log rather a rapid generation of logs. The log file grew to
100MB in less than a minute.
On Mon, Aug 19, 2013 at 4:21 PM, Ishara Premadasa ish...@wso2.com wrote:
Hi Kasun,
I first tried the
However the only incident i have seen a rapid error log thrown continuosly
in the MB or ActiveMQ integration scenario is, when you start AS for the
first time, if you hadn't start the broker (MB/ActiveMQ etc.) before
starting AS it will throw a continuous error log as there is no
On Mon, Aug 19, 2013 at 11:29 PM, Kasun Gajasinghe kas...@wso2.com wrote:
However the only incident i have seen a rapid error log thrown
continuosly in the MB or ActiveMQ integration scenario is, when you start
AS for the first time, if you hadn't start the broker (MB/ActiveMQ etc.)
before
Hi,
It seems that AS 5.2.0 is not patched with the issue with JMS transport
where the services with JMS enabled repeatedly try to establish a
connection with the message broker. This results in GBs of logs in a matter
of minutes filling up the disk.
As I got to know from Shammi, the solution is
Hi Kasun,
We will be looking into this today and update.
Thanks!
On Sun, Aug 18, 2013 at 12:14 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi,
It seems that AS 5.2.0 is not patched with the issue with JMS transport
where the services with JMS enabled repeatedly try to establish a
Hi,
The error log that repeats is the following. The error logs stop when the
activemq server is started.
TID: [0] [AS] [2013-08-19 10:12:43,835] ERROR
{org.apache.axis2.transport.base.threads.NativeWorkerPool} - Uncaught
exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
