#8 Error occurs when running on Jetty+SQLServer

[Anonymous]

When profiling again jetty+SQL Server, I got this error.

[java] [PROFILER4J:0] javassist.CannotCompileException:
cannot find jcifs.smb.SmbNamedPipe
[java] [PROFILER4J:0] at
javassist.CtBehavior.insertAfter(CtBehavior.java:610)[PROFILER4J:0]
at
net.sf.profiler4j.agent.BytecodeTransformer.transformMethod(BytecodeTransformer.java:174)[PROFILER4J:0]
at
net.sf.profiler4j.agent.BytecodeTransformer.transform(BytecodeTransformer.java:127)[PROFILER4J:0]at
net.sf.profiler4j.agent.Transformer.transform(Transformer.java:56)[PROFILER4J:0]
at
sun.instrument.TransformerManager.transform(TransformerManager.java:122)[PROFILER4J:0]
at
sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:155)[PROFILER4J:0]
at
sun.instrument.InstrumentationImpl.redefineClasses0(Native
Method)[PROFILER4J:0] at
sun.instrument.InstrumentationImpl.redefineClasses(InstrumentationImpl.java:79)[PROFILER4J:0]
at
net.sf.profiler4j.agent.Agent.reloadClasses(Agent.java:178)[PROFILER4J:0]
at
net.sf.profiler4j.agent.Server.serveClient(Server.java:133)[PROFILER4J:0]
at
net.sf.profiler4j.agent.Server.run(Server.java:73)[PROFILER4J:0]
Caused by: javassist.NotFoundException:
jcifs.smb.SmbNamedPipe[PROFILER4J:0] at
javassist.ClassPool.get(ClassPool.java:389)[PROFILER4J:0]
at
javassist.bytecode.Descriptor.toCtClass(Descriptor.java:549)[PROFILER4J:0]
at
javassist.bytecode.Descriptor.getReturnType(Descriptor.java:446)[PROFILER4J:0]
at
javassist.CtBehavior.getReturnType0(CtBehavior.java:184)[PROFILER4J:0]
at
javassist.CtBehavior.insertAfter(CtBehavior.java:571)[PROFILER4J:0]
... 10 more
[PROFILER4J:0] Profiler stopped[2006-09-21

[Antonio S. R. Gomes]

Logged In: YES
user_id=486433

Have you tried to remove jcifs from the profiling session?
Eventually this may avoid the problem. Just add a REJECT
rule to the pattern "jcifs.*(*)" at the top of the rule
list. Even more, you want to remove all rules and add s
single rule that ACCEPTs only your classes.

Two further questions:
(1) What do you mean by "profiling again"? Does that mean
that you modified the profiling rules on-the-fly? There are
cases in which redefining a class on-the-fly causes an error.
(2) Are you using a custom classloader?