cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Ribeiro (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12274) mx4j not work in 3.0.8
Date Mon, 08 Aug 2016 00:54:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-12274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Edward Ribeiro updated CASSANDRA-12274:
---------------------------------------
    Attachment: mx4j-error-log.txt

Hi [~snazy],

I've discovered by accident that this regression was indirectly caused by CASSANDRA-9402.
I am testing on C* 3.9 branch.

I could check that by putting the mx4j-tools.jar in the lib directory then commenting/uncommenting
this line: https://github.com/apache/cassandra/blob/143d16961a67cc9d5608605ee2561253de629d2c/src/java/org/apache/cassandra/service/CassandraDaemon.java#L189

Looks like, the addition of a {{SecurityManager}} makes {{mx4j}} throws an exception and show
a blank page. I have attached the Runtime error exception. {{Mx4jTool}} is the class in charge
of loading mx4j if it is in the classpath.

Last but not least, I found a small typo ("panalty") here: https://github.com/apache/cassandra/blob/3dcbe90e02440e6ee534f643c7603d50ca08482b/src/java/org/apache/cassandra/cql3/functions/ThreadAwareSecurityManager.java#L36


I am sorry for not being able to provide a ready solution, but this SecurityManager + ClassLoader
+ XSLT stuff is beyond me now. :(


> mx4j not work in 3.0.8
> ----------------------
>
>                 Key: CASSANDRA-12274
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12274
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: suse 12
> java 1.8.0_60
> mx4j 3.0.2
>            Reporter: Ilya
>         Attachments: mx4j-error-log.txt
>
>
> After update from 2.1 to 3.x version mx4j page begin empty
> {code}
> $ curl -i cassandra1:8081
> HTTP/1.0 200 OK
> expires: now
> Server: MX4J-HTTPD/1.0
> Cache-Control: no-cache
> pragma: no-cache
> Content-Type: text/html
> {code}
> There are no errors in the log.
> logs:
> {code}
> ~ $ grep -i mx4j /local/apache-cassandra/logs/system.log | tail -2
> INFO  [main] 2016-07-22 13:48:00,352 CassandraDaemon.java:432 - JVM Arguments: [-Xloggc:/local/apache-cassandra//logs/gc.log,
-XX:+UseThreadPriorities, -XX:ThreadPriorityPolicy=42, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/local/tmp,
-Xss256k, -XX:StringTableSize=1000003, -XX:+AlwaysPreTouch, -XX:+UseTLAB, -XX:+ResizeTLAB,
-XX:+UseNUMA, -Djava.net.preferIPv4Stack=true, -Xms512M, -Xmx1G, -XX:+UseG1GC, -XX:G1RSetUpdatingPauseTimePercent=5,
-XX:MaxGCPauseMillis=500, -XX:InitiatingHeapOccupancyPercent=25, -XX:G1HeapRegionSize=32m,
-XX:ParallelGCThreads=16, -XX:+PrintGCDetails, -XX:+PrintGCDateStamps, -XX:+PrintHeapAtGC,
-XX:+PrintTenuringDistribution, -XX:+PrintGCApplicationStoppedTime, -XX:+PrintPromotionFailure,
-XX:+UseGCLogFileRotation, -XX:NumberOfGCLogFiles=10, -XX:GCLogFileSize=10M, -XX:CompileCommandFile=/local/apache-cassandra//conf/hotspot_compiler,
-javaagent:/local/apache-cassandra//lib/jamm-0.3.0.jar, -Djava.rmi.server.hostname=cassandra1.d3,
-Dcom.sun.management.jmxremote.port=7199, -Dcom.sun.management.jmxremote.rmi.port=7199, -Dcom.sun.management.jmxremote.ssl=false,
-Dcom.sun.management.jmxremote.authenticate=false, -Dcom.sun.management.jmxremote.password.file=/etc/cassandra/jmxremote.password,
-Djava.library.path=/local/apache-cassandra//lib/sigar-bin, -Dmx4jport=8081, -Dlogback.configurationFile=logback.xml,
-Dcassandra.logdir=/local/apache-cassandra//logs, -Dcassandra.storagedir=/local/apache-cassandra//data,
-Dcassandra-pidfile=/local/apache-cassandra/run/cassandra.pid]
> INFO  [main] 2016-07-22 13:48:04,045 Mx4jTool.java:63 - mx4j successfuly loaded
> {code}
> {code}
> ~ $ sudo lsof -i:8081
> COMMAND   PID      USER   FD   TYPE    DEVICE SIZE/OFF NODE NAME
> java    14489 cassandra   86u  IPv4 381043582      0t0  TCP cassandra1.d3:sunproxyadmin
(LISTEN)
> {code}
> I checked versions 3.0.8  and 3.5, result the same - not work.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message