[GLASSFISH-11480] Not possible to use log TRACE in Felix console of GlassFish v3 Created: 25/Jan/10  Updated: 12/Oct/12

Status: Open
Project: glassfish
Component/s: OSGi
Affects Version/s: V3
Fix Version/s: not determined

Type: Improvement Priority: Major
Reporter: charliem Assignee: Richard S. Hall
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,480

 Description   

Hi,

I'm connected to the Felix OSGI server of Glassfish v3 (using telnet localhost
6666) and when I try to use the command :

-> log DEBUG

I receive the following message : No LogReaderService available



 Comments   
Comment by Sanjeeb Sahoo [ 25/Jan/10 ]

All glassfish logs appear in $

{domain_dir}

/logs/server.log. Either you can open
the log file in your favorite editor or use "GlassFish admin console" to view
the log file entries. To use the later option, open "http://localhost:4848,"
select enterprise server node, select "view Log" tab.

We will enhance GF to add a OSGi Log Reader as well.

Comment by Richard S. Hall [ 15/Jun/11 ]

The value of this depends on what you hope to see in the logs. You will not see logs from the Felix framework since it doesn't use the OSGi Log Service to log its messages (we tried to do this a long time ago, but it lead to deadlock issues since you tend to log at sensitive times and calling out to external code is problematic).

If you want to see logs from installed bundles, then this could be accomplished as simply as installing the Apache Felix Log Service bundle. Not much else needs to be done, no?

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Comment by TangYong [ 12/Oct/12 ]

Hi sahoo,

Now, trunk has merged gf osgi shell command, so, whether not resolving felix console related issues or not? If yes, should close the issue.

Generated at Fri Feb 27 00:56:47 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.