Lukas Schlud created LOGBACK-1379:
-------------------------------------
Summary: logback in android app with 2 processes just logs on 1
process
Key: LOGBACK-1379
URL: https://jira.qos.ch/browse/LOGBACK-1379
Project: logback
Issue Type: Bug
Components: logback-classic, logback-core
Affects Versions: 1.1.1
Environment:
Reporter: Lukas Schlud
Assignee: Logback dev list
Priority: Blocker
Hello
I'm using version 1.1.1-4 and having following problem:
In an android-app environment I'm using a Service, which is configured to run
in a separately Process defined in the AndroidManifest.xml like this:
{code}
<application>
<service
android:name="com.myfirm.myproject.MyService"
android:enabled="true"
android:exported="true"
android:process=":MyServiceProcessName">
<intent-filter>
<action
android:name="com.myfirm.myproject.MyService.ANDROID_MYSERVICE_BINDING_ACTION"
/>
</intent-filter>
</service>
</application>
{code}
When I let the service running in the app-process (remove the android:process
attribute) all Log statements of the service-class and the
app-classes(activities,etc...) are getting logged as expected.
When I use the android:process statement above in the manifest, and therewith
using a separate Process for the Service the behavior is in the way, that from
the app-Process (which gets created first) all Log statements are missing in
the log file.
It seems to be an bug that this constellation is not being supported, or does a
workaround exists?
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
