[GLASSFISH-4013] When activating snmp monitoring on the JVM glassfish does not log anymore Created: 18/Jan/08  Updated: 06/Jan/11

Status: Open
Project: glassfish
Component/s: logging
Affects Version/s: v2.1
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: akhenakh Assignee: sultal
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Solaris
Platform: Sun


Issuezilla Id: 4,013

 Description   

After enabling snmp monitoring on the jvm:
-Dcom.sun.management.snmp.interface=10.16.248.48
-Dcom.sun.management.snmp.acl.file=/etc/snmp/conf/jvm-appserv.acl
-Dcom.sun.management.snmp.port=1161

Glassfish logs everything in stdout AND server.log until the start is complete,
then it stops logging in server.log (but the access log is working).



 Comments   
Comment by Alexis MP [ 18/Jan/08 ]

CC's myself

Comment by harpreet [ 08/Feb/08 ]

downgrading to P3 as it is not a critical issue. Will ask Dinesh to confirm.

Comment by dpatil [ 08/Feb/08 ]

yes this is not critical.

Comment by harpreet [ 26/Mar/08 ]

marking for 9.2 as not critical for 9.1.1

Comment by sultal [ 13/Jun/08 ]

Unfortunately glassfish V2 logging infrastructure is not designed to handle
calls to logging manager prior to main(), so this issue is only fixed in
Glassfish v3 by way of complete logging infrastructure redesign.
See: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3256 for reference.
Will not fix.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.





Generated at Thu Sep 03 18:50:22 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.