Thanks Dejan, Gary - I still can't get fatal Spring errors logging as the
context startup code doesn't use normal logging. I'm sure there is a good
reason for this though and I can modify the shell script too so shouldn't be
a problem.
Regards,
Tom
On Fri, Jun 24, 2011 at 1:38 PM, Dejan Bosanac
BTW. you need to set trashold for the console logger to debug as well
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale
./activemq console
with that flag it will run in the foreground and output to the console.
On 24 June 2011 09:46, Tom <808...@gmail.com> wrote:
> On 23 Jun 2011 12:41, "Dejan Bosanac" wrote:
>>
>> Sure, ActiveMQ uses Spring to load the configuration, so just set
>> "org.springframework" log
On 23 Jun 2011 12:41, "Dejan Bosanac" wrote:
>
> Sure, ActiveMQ uses Spring to load the configuration, so just set
> "org.springframework" logger to desired level.
That's what I am saying though - I have everything at DEBUG and still don't
see any logging. It seems that Spring Exceptions bubble up
Sure, ActiveMQ uses Spring to load the configuration, so just set
"org.springframework" logger to desired level.
Regards
--
Dejan Bosanac - http://twitter.com/dejanb
-
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.mann
