Since you posted in this thread I'll assume that you are using 2.0.CR7.
JBoss-4.2.2.GA and JDK-1.5.0_13 is supported by the 2.0.CR7 release.
It seems that something went wrong either in the download or the unpacking of the ZIP file. Try to download it again and post full details if the problem still is there - e.g. your JAVA_OPTS setting.
Make sure that "jar tf jboss-profiler.jar" doesn't show any errors - and follow the instructions in the README.txt file regarding installation inside JBossAS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112300#4112300
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112300
Hi, I am trying this JBoss Profiler with a clean JBoss4.2.2 installation on a linux box and I get this error:
| Error opening zip file: jboss-profiler.jar
| Error occurred during initialization of VM
| agent library failed to init: instrument
|
¡Help appreciated!
My linux box is running:
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)
And it is a:
Linux santander 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112278#4112278
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112278
"adrian(a)jboss.org" wrote :
| I don't get the reference to OO?
|
OK, this is a mechanism for taking apart non serializable objects.
If we only remember its interface and then have a map 'interface --> default impl', then we forget about polymorphism.
e.g. I would still like to have MyInterface1 and MyInterface2, both implementing Interface, taken apart, but when I want to re-construct them, I very much care about the impl details.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112248#4112248
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112248
"alesj" wrote : "adrian(a)jboss.org" wrote :
| | Generically, we could allow some kind of plugin mechanism to allow
| | somebody to configure:
| | interface -> implementation class or factory
| Even for non collection classes?
| The composite ones.
| Doesn't that defeat the whole purpose of OO? :-)
I don't get the reference to OO? This is reflection/serialization where we've
taken apart the object to split its state into "primitives".
The issue is how do we reconstruct it.
e.g.
| @ManagementProperty
| public void setSomething(Interface i) {}
|
| public interface Interface
| {
| void setInteger(int i);
| void setString(String s);
| }
|
This is a composite with two primitive properties, but we don't know
what the implementation is.
There are two options
1) Create a proxy
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/mbeans/src/main/...
2) Allow somebody to define what the implementation class is (or a factory to create one)
The proxy approach doesn't work for collections since they aren't javabeans.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112241#4112241
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112241