Hi

Yeah the default log4j.properties in AMQ is ERROR for Camel
https://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/log4j.properties

I will raise a ticket to lower that to WARN or maybe even INFO if that
makes more sense.


On Mon, Oct 25, 2010 at 3:36 PM, Mark Webb <[email protected]> wrote:
> ActiveMQ 5.4.1
>
> In conf/log4j.properties, I uncommented out the 2 lines they say to in
> the comments:
>
> # Or for more fine grained debug logging uncomment one of these
> log4j.logger.org.apache.activemq=INFO
> log4j.logger.org.apache.camel=INFO
>
>
>
>
> On Sat, Oct 23, 2010 at 3:53 AM, Claus Ibsen <[email protected]> wrote:
>> On Fri, Oct 22, 2010 at 8:13 PM, Mark Webb <[email protected]> wrote:
>>> With the default ActiveMQ configuration, that stack trace is not sent
>>> to the console.  So if people send text messages longer than 1024
>>> characters to ActiveMQ the messages will not get processed and there
>>> will be no log entry as to why.
>>>
>>
>> What AMQ version?
>>
>> And maybe you can post the "default" configuration from AMQ which
>> doesn't print the stacktrace?
>> I would be surprised if it suppress WARN logs.
>>
>>
>>
>>>
>>> On Thu, Oct 21, 2010 at 1:36 PM, Claus Ibsen <[email protected]> wrote:
>>>> So are you saying that you dont notice the WARN? That is a really high 
>>>> level.
>>>>
>>>>
>>>> On Thu, Oct 21, 2010 at 6:15 PM, Mark Webb <[email protected]> wrote:
>>>>> Here is the stack trace.  It is a WARN, not DEBUG.  Sorry about that.
>>>>>
>>>>> I cut out the "Hexdump" dump for brevity.
>>>>>
>>>>>  WARN | [/127.0.0.1:53690] Unexpected exception from exceptionCaught 
>>>>> handler.
>>>>> org.apache.camel.CamelException:
>>>>> org.apache.mina.filter.codec.ProtocolDecoderException:
>>>>> org.apache.mina.common.BufferDataException: Line is too long: 1973
>>>>> (Hexdump: 5C 3D 0D 0A)
>>>>>        at 
>>>>> org.apache.camel.component.mina.MinaConsumer$ReceiveHandler.exceptionCaught(MinaConsumer.java:91)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.exceptionCaught(AbstractIoFilterChain.java:564)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain.callNextExceptionCaught(AbstractIoFilterChain.java:345)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain.access$1000(AbstractIoFilterChain.java:53)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.exceptionCaught(AbstractIoFilterChain.java:643)
>>>>>        at 
>>>>> org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:224)
>>>>>        at 
>>>>> org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264)
>>>>>        at 
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>>>>>        at 
>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>>>>        at java.lang.Thread.run(Thread.java:619)
>>>>> Caused by: org.apache.mina.filter.codec.ProtocolDecoderException:
>>>>> org.apache.mina.common.BufferDataException: Line is too long: 1973
>>>>> (Hexdump: 5C 3D 0D 0A)
>>>>>        at 
>>>>> org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:165)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilterChain.java:53)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceived(AbstractIoFilterChain.java:648)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain$HeadFilter.messageReceived(AbstractIoFilterChain.java:499)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(AbstractIoFilterChain.java:299)
>>>>>        at 
>>>>> org.apache.mina.common.support.AbstractIoFilterChain.fireMessageReceived(AbstractIoFilterChain.java:293)
>>>>>        at 
>>>>> org.apache.mina.transport.socket.nio.SocketIoProcessor.read(SocketIoProcessor.java:228)
>>>>>        at 
>>>>> org.apache.mina.transport.socket.nio.SocketIoProcessor.process(SocketIoProcessor.java:198)
>>>>>        at 
>>>>> org.apache.mina.transport.socket.nio.SocketIoProcessor.access$400(SocketIoProcessor.java:45)
>>>>>        at 
>>>>> org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(SocketIoProcessor.java:485)
>>>>>        at 
>>>>> org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)
>>>>>        ... 3 more
>>>>> Caused by: org.apache.mina.common.BufferDataException: Line is too long: 
>>>>> 1973
>>>>>        at 
>>>>> org.apache.mina.filter.codec.textline.TextLineDecoder.decodeAuto(TextLineDecoder.java:188)
>>>>>        at 
>>>>> org.apache.mina.filter.codec.textline.TextLineDecoder.decode(TextLineDecoder.java:112)
>>>>>        at 
>>>>> org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:158)
>>>>>        ... 14 more
>>>>>
>>>>>
>>>>> On Thu, Oct 21, 2010 at 10:14 AM, Claus Ibsen <[email protected]> 
>>>>> wrote:
>>>>>> On Thu, Oct 21, 2010 at 3:33 PM, Mark Webb <[email protected]> wrote:
>>>>>>> First off, thanks for the work.  The more I use Camel, the more I love
>>>>>>> it.  Here are 2 'bugs' I have run across:
>>>>>>>
>>>>>>> 1. On the page http://camel.apache.org/mina.html, for the list of
>>>>>>> configuration parameters you list "decorderMaxLineLength", this is a
>>>>>>> typo and should be "decoderMaxLineLength".  I copy and pasted the word
>>>>>>> into my code and took me a few minutes to find the problem.
>>>>>>>
>>>>>>
>>>>>> Fixed the typo.
>>>>>>
>>>>>>
>>>>>>> 2. Secondly, I am sending long lines of data to the Camel-MINA
>>>>>>> component and needed to increase the decoderMaxLineLength.  Until I
>>>>>>> bumped the ActiveMQ log4j.properties file to "ALL", I did not see the
>>>>>>> exception that stated the line was too long.  Shouldn't this exception
>>>>>>> be logged as an error?  If so I would have seen it sooner.  IIRC right
>>>>>>> now the exception is logged as a DEBUG.
>>>>>>>
>>>>>>
>>>>>> Can you post the stacktrace?
>>>>>>
>>>>>>
>>>>>>> Thank you,
>>>>>>> Mark
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> Apache Camel Committer
>>>>>>
>>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>>> Open Source Integration: http://fusesource.com
>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>> Twitter: http://twitter.com/davsclaus
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> Apache Camel Committer
>>>>
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>> Open Source Integration: http://fusesource.com
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Twitter: http://twitter.com/davsclaus
>>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Author of Camel in Action: http://www.manning.com/ibsen/
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: [email protected]
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Reply via email to