Hello! I’ve managed to identify the problem nearer. The FileOutputStream apparently was attempting to write onto Karaf console, because after pressing Ctrl+C in the console, the process un-hanged and I’ve got that log message onto console.
I’d like to report issue, but I’m not sure to which project it belongs, because there are no clear indicators in stack trace. Do you have any suggesions? Does it belong to pax-logging? Actually, it’s the logging system that misbehaves (log calls should never block). Best regards, Lukasz Lech From: [email protected] [mailto:[email protected]] On Behalf Of Lukasz Lech Sent: Mittwoch, 6. September 2017 12:01 To: [email protected] Subject: pax-logging mysterious blocks in karaf (4.1.0) Hello, I’m experiencing mysterious blocks in karaf (version 4.1.0). The method that experiences the block is FileOutputStream.writeBytes. The block happens always in the same place: when entity manager tries to log into the database. I’ve retrieved the ‘stack trace’ with Eclipse connected with remote debugger to karaf server: https://i.stack.imgur.com/D7hcz.png however, I’m unable to retrieve any details (file name, for example). Karaf.log looks normally, and subsequent log lines appear there, so it doesn’t look like the issue is writing there. I suppose EntityManager tries to write to ‘another place’, however my digging into sources lead me to impression, the logging infrastructure for JPA is provided by server (so karaf, in that case). I’m using following features: feature:repo-add mvn:org.apache.aries.jpa/jpa-features/2.5.0/xml/features feature:install jpa/2.5.0 feature:install transaction-api/1.2.0 feature:install transaction feature:install eclipselink feature:install pax-jdbc-config feature:install pax-jdbc-sqlite feature:install pax-jdbc-mysql feature:install pax-jdbc-postgresql feature:install jersey-karaf-feature/2.2.0 Did I incidentally chosen incompatibile features? Is it a possible windows issue? (in which case I could ignore this, because production servers are linux). The issue happens randomly from time to time, restarting karaf helps. Anybody got similar issues? Where should I look for, where JPA tries to write logs? The lack of full class names is annoying, but it’s what Eclipse is showing me… Best regards, Lukasz Lech -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected]<mailto:[email protected]> --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
