Kanapathipillai Senthuran | 17 Sep 10:55 2014
Picon

I'd like to add you to my professional network on LinkedIn

 
Kanapathipillai Senthuran would like to stay in touch on LinkedIn.
Kanapathipillai Senthuran
Java Developer at Virtusa
Sri Lanka
I'd like to add you to my professional network on LinkedIn.
- Kanapathipillai
Confirm that you know Kanapathipillai
You received an invitation to connect. LinkedIn will use your email address to make suggestions to our members in features like People You May Know. Unsubscribe
Learn why we included this.
If you need assistance or have questions, please contact LinkedIn Customer Service.
© 2014, LinkedIn Corporation. 2029 Stierlin Ct. Mountain View, CA 94043, USA
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Fabrizio Giudici (JIRA | 10 Sep 17:11 2014
Picon

[JIRA] (LOGBACK-747) maxHistory doesnot normally work in SizeAndTimeBasedFNATP

Bump... Any news on this?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Somaiya, Deepak | 10 Sep 00:34 2014
Picon

In memory logging

We have a requirement to keep logEvents(logs) in memory for certain  configurable time even if logging is
turned off i.e in that case logback logger should just keep the logging data in memory and should not write
it to logfile.  Any help will be appreciated.

Deepak
Fyren (JIRA | 8 Sep 03:21 2014
Picon

[JIRA] (LOGBACK-1013) %contentResponse is always empty.

Issue Type: Bug
Affects Versions: 1.1.2, 1.0.13
Assignee: Logback dev list
Components: logback-access
Created: 08/Sep/14 3:19 AM
Description:

In my project, it appears that %contentResponse is always empty. If I instead use %fullResponse, I do see the headers for the response. With a pattern of "%date %requestURL\n%fullResponse\n-----" I get the following for a request:

07/09/2014:19:09:38 -0600 GET <path> HTTP/1.1
HTTP/1.1 200 OK
Date: Mon, 8 Sep 2014 01:09:38 GMT
Content-Length: 822
Expires: Mon, 8 Sep 2014 01:09:38 GMT
X-Lift-Version: 2.5.1
Content-Type: text/javascript; charset=utf-8
Cache-Control: no-cache, private, no-store
Pragma: no-cache

I snipped out the path, but otherwise didn't edit the output. You can see the Content-Length is 822 but there's no content in the output. I tried using versions 1.0.13 and 1.1.2 of logback-classic and logback-access.

Please let me know what additional information would be helpful.

Environment:

Jetty 8.1.12.v20130726, Lift 2.5.1, Windows

Project: logback
Priority: Major
Reporter: Fyren
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Fyren (JIRA | 8 Sep 03:09 2014
Picon

[JIRA] (LOGBACK-309) Getting Java java.lang.ClassNotFound except with v1.0.0 & Jetty 7

Fyren commented on LOGBACK-309

I was using the jetty maven plugin and came across the same issue. In my case, I was adding logback-access to the project dependencies but instead it had to be under the <plugin> for jetty.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Fyren (JIRA | 8 Sep 03:07 2014
Picon

[JIRA] (LOGBACK-1009) java.lang.NoClassDefFoundError when using embedded Jetty

Fyren commented on LOGBACK-1009

I was using the jetty maven plugin and came across the same issue. In my case, I was adding logback-access to the project dependencies but instead it had to be under the <plugin> for jetty.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Stefano Cardinale (JIRA | 7 Sep 19:06 2014
Picon

[JIRA] (CONSPLUG-44) Logback-Beagle doesn't work in Eclipse 4.3 Kepler

Thx a lot, Thomas, I tried your patch and the beagle plugin was loaded into Eclipse Luna, but I was unable to start it: there is no 'Logback' entry into the Show View menu. Any hint ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Troy Davis (JIRA | 6 Sep 16:59 2014
Picon

[JIRA] (LOGBACK-99) Can't use logback on GAE SDK 1.3.7 when configured with logback.xml

Troy Davis commented on LOGBACK-99

We wrote a logback appender which supports TCP and TCP with TLS and is tested with Google App Engine. It's called `com.papertrailapp.logback.Syslog4jAppender`.

While we wrote and tested it for aggregation with https://papertrailapp.com/ (hosted log management), it can send to any syslog destination. To install the appender, start here: http://help.papertrailapp.com/kb/hosting-services/google-app-engine/

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Troy Davis | 5 Sep 02:05 2014

PR review - SyslogAppender hostname support (LOGBACK-1011 / GH #139)

Hi all,

I recently opened http://jira.qos.ch/browse/LOGBACK-1011 about adding the ability to set a SyslogAppender hostname. I learned later that it's already been implemented here: https://github.com/qos-ch/logback/pull/139 (as of August of 2013).

Could I trouble someone to comment on the pull request? I'm happy to try to incorporate improvements if there are reasons not to merge it as-is.

Thanks,

Troy
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Troy Davis (JIRA | 5 Sep 01:19 2014
Picon

[JIRA] (LOGBACK-1011) SyslogAppender support for configurable hostname

Troy Davis commented on LOGBACK-1011

Looks like this is solved in a pull request that hasn't been commented on: https://github.com/qos-ch/logback/pull/139.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev
Jeffrey Aguilera (JIRA | 4 Sep 20:34 2014
Picon

[JIRA] (LOGBACK-1012) Documentation states that :- behaves like bash; it doesn't, but it should

Issue Type: Bug
Affects Versions: 1.1.2
Assignee: Logback dev list
Components: logback-core
Created: 04/Sep/14 8:33 PM
Description:

The :- operator in bash expands the right-hand-side when the left-hand-side is undefined or empty. logback only expands the RHS when the LHS is undefined. Thus, a system property that has been defined but not assigned (e.g., -Ddefined) does not trigger default expansion, because such parameters actually have the empty string as their value.

Chapter 3 of the documentation states that this operator is based on the operator with the same name in Bash. Bash, however, expands on blank:

X=""
echo $

{X:-3}

will echo 3.

I would prefer that logback adopt the same semantics as Bash; but if this is not possible due to backward-compatibility reasons, the documentation should be updated to point out that this differs from Bash for this corner case.

Environment:

Scala/java/OSX/Linux

Project: logback
Labels: substitution
Priority: Trivial
Reporter: Jeffrey Aguilera
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@...
http://mailman.qos.ch/mailman/listinfo/logback-dev

Gmane