[
https://issues.apache.org/jira/browse/FELIX-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162640#comment-17162640
]
Veselin commented on FELIX-6308:
--------------------------------
No unfortunately this is not reproducible and I do not have any system logs
anymore.
Java:
java version "1.8.0_241-release"
Java(TM) SE Embedded Runtime Environment (build
1.8.0_241-release-microdoc-p107600-t20200406-linux-armv7a-le-gcc494-gnueabihf-b01,
headless)
Java HotSpot(TM) Embedded Client VM (build 25.241-b01, mixed mode)
OS:
uname -a
Linux vivalytic 4.1.46-fslc+gf134d1b #1 SMP PREEMPT Tue Jun 2 20:53:25 CEST
2020 armv7l GNU/Linux
PID is com.bosch.bhcs.vivalytic.workflow.management.process.context if this
helps anyhow.
> Bad File Descriptor while persisting service configuration
> ----------------------------------------------------------
>
> Key: FELIX-6308
> URL: https://issues.apache.org/jira/browse/FELIX-6308
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.9.16
> Reporter: Veselin
> Priority: Major
> Attachments: stacktrace.txt
>
>
> I got un unusual exception while flushing some configuration by calling
> ConfigurationAdapter.update() : java.io.IOException: Bad file descriptor. As
> I understood the exception this can happen in multithreading environment if
> the ouput stream is closed.
>
> Is update() threadsafe?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
