[OPENIDM1675] ON STARTUP ON LINUX FELIX INFO MESSAGES THAT

[OPENIDM-1675] On startup, on Linux, Felix info messages that are not relevant/important Created: 2014-02-19  Updated: 2015-03-27  Resolved: 2015-03-19

Status:

Closed

Project:

OpenIDM

Component/s:

Module - OSGi Container / Framework integration

Affects Version/s:

OpenIDM 3.0.0

Fix Version/s:

OpenIDM 3.2.0

Type:

Bug

Priority:

Minor

Reporter:

Laurent Bristiel [X] (Inactive)

Assignee:

Brendan Miller

Resolution:

Fixed

Votes:

0

Labels:

LEWIS, release-notes

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

CREST r2874, Linux Centos and Ubuntu

Story Points:

1

Sprint:

Sprint 14, Sprint 18, Sprint 20, Sprint 28, Sprint 29, Sprint 30, Sprint 36

Epic Link:

This is a catch-all Epic to address stability issues

On Linux, OpenIDM displays some INFO messages about Felix that are not very relevant and make the startup a bit noisy. Those message were not displayed in previous version of OpenIDM. Maybe we should hide them (change logging level for Felix ?)

[testuser@idm-centos64642 openidm]$ ./startup.sh
Executing ./startup.sh...
Using OPENIDM_HOME:   /home/testuser/Installs/openidm
Using OPENIDM_OPTS:   -Xmx1024m -Xms1024m
Using LOGGING_CONFIG: -Djava.util.logging.config.file=/home/testuser/Installs/openidm/conf/logging.properties
Using boot properties at /home/testuser/Installs/openidm/conf/boot/boot.properties
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Storing Memory Dumps in /home/testuser/Installs/openidm/felix-cache/bundle59/data/dumps
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Setting Automatic Memory Dump Threshold to 0% for pools [Code Cache, PS Old Gen, PS Perm Gen]
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Automatic Memory Dump cannot be set for pools [PS Eden Space, PS Survivor Space]
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Setting Automatic Memory Dump Interval to 21600 seconds
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Setting Automatic Memory Dump Threshold to 0% for pools [Code Cache, PS Old Gen, PS Perm Gen]
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Automatic Memory Dump cannot be set for pools [PS Eden Space, PS Survivor Space]
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Setting Automatic Memory Dump Interval to 21600 seconds
INFO : org.apache.felix.webconsole.plugins.memoryusage (59): Storing Memory Dumps in /home/testuser/Installs/openidm/felix-cache/bundle59/data/dumps
-> OpenIDM version "2.2.0-SNAPSHOT" (revision: 2874) jenkins-OpenIDM CREST branch-185 null
OpenIDM ready

Comment by chad.kienle [ 2014-02-20 ]

I'm unable to reproduce this issue. I've been testing on CentOS. Any more info on your environment?

Comment by Laurent Bristiel [X] (Inactive) [ 2014-03-05 ]

could you finally reproduce the issue Chad?

Comment by Mike Jang [X] (Inactive) [ 2014-11-20 ]

I can reproduce – from the latest rev, 4366:

[root@mjidm2 openidm]# ./startup.sh -p samples/openam/
Executing ./startup.sh...
Using OPENIDM_HOME: /root/openidm
Using PROJECT_HOME: /root/openidm/samples/openam/
Using OPENIDM_OPTS: -Xmx1024m -Xms1024m
Using LOGGING_CONFIG: -Djava.util.logging.config.file=/root/openidm/samples/openam//conf/logging.properties
Using boot properties at /root/openidm/samples/openam/conf/boot/boot.properties
INFO : org.apache.felix.webconsole.plugins.memoryusage (45): Storing Memory Dumps in /root/openidm/felix-cache/bundle45/data/dumps
INFO : org.apache.felix.webconsole.plugins.memoryusage (45): Setting Automatic Memory Dump Threshold to 0% for pools [Code Cache, Perm Gen, Tenured Gen]
INFO : org.apache.felix.webconsole.plugins.memoryusage (45): Automatic Memory Dump cannot be set for pools [Eden Space, Survivor Space]
INFO : org.apache.felix.webconsole.plugins.memoryusage (45): Setting Automatic Memory Dump Interval to 21600 seconds
-> OpenIDM version "3.1.0-RC3-SNAPSHOT" (revision: 4366) jenkins-OpenIDM-3795 null
OpenIDM ready

Comment by Jim Mitchener [ 2014-11-20 ]

I am able to reproduce on CentOS 6.

Comment by Brendan Miller [ 2015-03-19 ]

Updated osgi log service start order to start earlier in launcher.json.

Comment by Laurent Bristiel [X] (Inactive) [ 2015-03-20 ]

Tested with r5031

• Linux Centos => works OK

• Win 2008 => works OK

• Mac OS X with Java 6 => works OK

• Mac OS X with Java 7 or Java 8 => error message on startup:

  [MBP]$ ./startup.sh
  Executing ./startup.sh...
  Using OPENIDM_HOME:   /Users/laurent/Installs/openidm
  Using PROJECT_HOME:   /Users/laurent/Installs/openidm
  Using OPENIDM_OPTS:   -Xmx1024m -Xms1024m
  Using LOGGING_CONFIG: -Djava.util.logging.config.file=/Users/laurent/Installs/openidm/conf/logging.properties
  Using boot properties at /Users/laurent/Installs/openidm/conf/boot/boot.properties
  Mar 20, 2015 9:35:31 AM org.forgerock.openidm.logging.LogServiceTracker logEntry
  SEVERE: Bundle: org.xerial.snappy.snappy-java [12] FrameworkEvent ERROR
  org.apache.felix.log.LogException: org.osgi.framework.BundleException: Activator start error in bundle org.xerial.snappy.snappy-java [12].
          at org.apache.felix.framework.Felix.activateBundle(Felix.java:2196)
          at org.apache.felix.framework.Felix.startBundle(Felix.java:2064)
          at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)
          at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
          at java.lang.Thread.run(Thread.java:745)
  Caused by: java.lang.UnsatisfiedLinkError: no libsnappyjava.dylib in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)
          at java.lang.Runtime.loadLibrary0(Runtime.java:849)
          at java.lang.System.loadLibrary(System.java:1088)
          at org.xerial.snappy.SnappyBundleActivator.start(SnappyBundleActivator.java:52)
          at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
          at org.apache.felix.framework.Felix.activateBundle(Felix.java:2146)
          ... 4 more

Notes:
1) This seems to be discussed in snappy-java github issues
2) I know Mac is not supported version but many people will use Mac to discover/test the product, so I think we have to fix this problem

Comment by Brendan Miller [ 2015-03-26 ]

Added explicit snappy dependency on recent version that solves issue. (r5051)

Comment by Laurent Bristiel [X] (Inactive) [ 2015-03-27 ]

checked on r5054

• Mac => OK now

• Linux => still OK
  => closing this issue