[Design of JBoss Profiler] - cannot ant or build profiler
by pgtaviator
SunOS 5.9 Generic_118558-39 sun4u sparc SUNW,Sun-Fire-V240
build of jvmpi appears to go ok.
build of jvmti fails via compile.sh
../native-src/jbossAgentJNI.cpp: In function `void
Java_org_jboss_profiler_jvmti_JVMTIInterface_notifyInventory(JNIEnv*,
_jobject*, unsigned char, _jstring*, _jstring*, _jobject*)':
../native-src/jbossAgentJNI.cpp:814: warning: cast from pointer to integer of
different size
../native-src/jbossAgentJNI.cpp: In function `_jstring*
Java_org_jboss_profiler_jvmti_JVMTIInterface_getMethodName(JNIEnv*,
_jobject*, long long int)':
../native-src/jbossAgentJNI.cpp:920: warning: cast to pointer from integer of
different size
../native-src/jbossAgentJNI.cpp: In function `_jstring*
Java_org_jboss_profiler_jvmti_JVMTIInterface_getMethodSignature(JNIEnv*,
_jobject*, long long int)':
../native-src/jbossAgentJNI.cpp:941: warning: cast to pointer from integer of
different size
../native-src/jbossAgentJNI.cpp: In function `_jclass*
Java_org_jboss_profiler_jvmti_JVMTIInterface_getMethodClass(JNIEnv*,
_jobject*, long long int)':
../native-src/jbossAgentJNI.cpp:961: warning: cast to pointer from integer of
different size
ANT also fails
Buildfile: build.xml
init:
compile:
[javac] Compiling 5 source files to /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/output/classes
BUILD FAILED
/holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/build.xml:23: /holder/jboss_profiler/jboss-profiler-1.0.CR4/build/jar not found.
mkdir -p ../build/jar (from directory containing build.xml for jvmti).
fails again
Buildfile: build.xml
init:
compile:
[javac] Compiling 5 source files to /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/output/classes
BUILD FAILED
/holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/build.xml:23: /holder/jboss_profiler/jboss-profiler-1.0.CR4/java/libs not found.
java/libs does not exist in the distribution so I mkdir -p ../java/libs
failed again.
Buildfile: build.xml
init:
compile:
[javac] Compiling 5 source files to /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/output/classes
[javac] /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/java-src/org/jboss/profiler/jvmti/JVMTIInterface.java:25: package gnu.trove does not exist
[javac] import gnu.trove.TLongObjectHashMap;
[javac] ^
[javac] /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/java-src/org/jboss/profiler/jvmti/JVMTIInterface.java:51: package org.jboss.logging does not exist
[javac] import org.jboss.logging.Logger;
[javac] ^
[javac] /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/java-src/org/jboss/profiler/jvmti/JVMTIInterface.java:60: cannot find symbol
[javac] symbol : class Logger
[javac] location: class org.jboss.profiler.jvmti.JVMTIInterface
[javac] private static final Logger log = Logger.getLogger(JVMTIInterface.class);
[javac] ^
[javac] /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/java-src/org/jboss/profiler/jvmti/JVMTIInterface.java:921: cannot find symbol
[javac] symbol : class TLongObjectHashMap
[javac] location: class org.jboss.profiler.jvmti.JVMTIInterface.InnerCallBack
[javac] TLongObjectHashMap classesMap = new TLongObjectHashMap();
[javac] ^
[javac] /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/java-src/org/jboss/profiler/jvmti/JVMTIInterface.java:60: cannot find symbol
[javac] symbol : variable Logger
[javac] location: class org.jboss.profiler.jvmti.JVMTIInterface
[javac] private static final Logger log = Logger.getLogger(JVMTIInterface.class);
[javac] ^
[javac] /holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/java-src/org/jboss/profiler/jvmti/JVMTIInterface.java:921: cannot find symbol
[javac] symbol : class TLongObjectHashMap
[javac] location: class org.jboss.profiler.jvmti.JVMTIInterface.InnerCallBack
[javac] TLongObjectHashMap classesMap = new TLongObjectHashMap();
[javac] ^
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 6 errors
BUILD FAILED
/holder/jboss_profiler/jboss-profiler-1.0.CR4/jvmti-src/build.xml:23: Compile failed; see the compiler error output for details.
Sorry, I'm not a developer and would certainly appreciate any information regarding potential cause of these problems.
Thank you!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142425#4142425
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142425
18 years
[Design of JBossCache] - Design of JBCACHE-1316
by galder.zamarreno＠jboss.com
Re: http://jira.jboss.com/jira/browse/JBCACHE-1316
I've got this one ready to go into trunk. If everyone's happy with the approach below, I'll port it to 2.1.x and the 1.4.x branch.
I've created a new test class called org.jboss.cache.eviction.BaseEvictionAlgorithmTest rather than extending one of existing LRU/LFUAlgorithm test classes because the test focuses on what BaseEvictionAlgorithm does rather than the specifics of each algorithm. Within it, we test whether the eviction algorithm process blocks forever if the recycle queue gets filled up.
The fix itself consists of changing the following line in BaseEvictionAlgorithm.evict(NodeEntry ne):
recycleQueue.put(ne.getFqn());
To look like this and avoid potentially blocking forever:
boolean result = recycleQueue.offer(ne.getFqn(), 5, TimeUnit.SECONDS);
| if (!result)
| {
| log.warn("Unable to add Fqn[" + ne.getFqn() + "] to recycle " +
| "queue because it's full. This is often sign that " +
| "evictions are not occurring and nodes that should be " +
| "evicted are piling up waiting to be evicted.");
| }
The recycle queue size is not configurable and so, don't think the recycle queue offer timeout should be either. 5 seconds looks to me a reasonable timeout to be able to put an Fqn in the recycle queue.
Thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142412#4142412
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142412
18 years
[Design of JBoss Profiler] - Re: JBoss Profiler 2
by mgearhart
Hi
I'm trying to get this profiler working with my setup. I'm running on
Windows:
JBoss: 4.3.0 GA
jboss-profile-2.0.CR8
I am following the instructions in the readme.txt. When a start up, I get
the following error:
2008-04-08 10:23:53,068 DEBUG [org.jboss.deployment.SARDeployer] Registering service UCL=jmx.loading:UCL=177fa9a
2008-04-08 10:23:53,068 DEBUG [org.jboss.system.ServiceCreator] About to create bean: org.jboss.profiler:service=Profiler with code: org.jboss.profiler.as.Profiler
2008-04-08 10:23:53,068 ERROR [org.jboss.mx.server.registry.BasicMBeanRegistry] Cannot register MBean
java.lang.NoClassDefFoundError: org/jboss/profiler/shared/Visibility
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
at java.lang.Class.privateGetPublicMethods(Class.java:2519)
at java.lang.Class.getMethods(Class.java:1406)
I have jboss-profile.jar in my bin directory, and jar tf shows
org/jboss/profiler/shared/Visibility.class
Not sure how to resolve. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142400#4142400
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142400
18 years
[Design of Messaging on JBoss (Messaging/JBoss)] - AIO/DirectIO Integration
by clebert.suconic＠jboss.com
I'm integrating libaio on the Journal, and I had to make few changes on my local box to make it work correctly.
When you are dealing with DirectIO, every write has to be aligned to 512 bytes. To make both AIO and NIO work correctly, I'm adding tail bytes to the end of each record to complete a block of 512 bytes.
Say... you are writing a PrepareRecord
On the regular layout (before this change), you would do this:
1 BYTE - Prepare Record
8 BYTES - Long TXID
1 BYTE Done
After the change I'm making.. you will have
1 Byte - Prepare Record
8 Bytes - Long TXID
4 Bytes - Int fillerSize
1 Byte Done
N Bytes to complete the block (as determined by fillerSize)
With the second layout, both NIO and AIO can work on the same layout.
After we add an intermediate buffer on AIO, we will be able to remove these filler bytes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142379#4142379
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142379
18 years