[lfhaddix]

If I use that exact same <loader-repository> as you do, I get the illegal access error.

Do you have the xbean.jar for 2.0.3 in the "root" of your esb? or in a lib directory?

[lfhaddix]

Its working now.

I didn't have all of the jar files that used xmlbean compiled classes.


THANK YOU for your help

[lfhaddix]

This worked 1 time, then when I stopped and restared the server it stopped working again.


java.lang.NoClassDefFoundError: com/ibm/websphere/crossworlds/x2002/boSchema/add
ress/AddressDocument


This class is in the Address_BDE.jar file

My deployment.xml:
<?xml version="1.0" encoding="UTF-8"?>
<jbossesb-deployment>
jboss.esb:deployment=jbossesb.esb
<loader-repository>
com.mycompany.test:loader=simple-scoped
<loader-repository-config>
java2ParentDelegaton=false
</loader-repository-config>
</loader-repository>
</jbossesb-deployment>


This is from the JMX console:


MBean Name: Domain Name: com.mycompany.test
loader: simple-scoped
MBean Java Class: org.jboss.mx.loading.HeirarchicalLoaderRepository3

CacheSize int R 591 MBean Attribute.
URLs [Ljava.net.URL; R file:/D:/jboss-4.2.3.GA/server/erpln/deploy/bluebird/bb-parts123-app.esb/
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33823saxon8.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33818Parts123_RGA_SalesOrder.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33820Parts123_XRef.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33817Item_BDE.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33821SalesOrder_BDE.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33816Address_BDE.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33824xbean.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33819Parts123_SalesOrder.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33822jsr173_1.0_api.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33741xmlpublic-2.2.0.jar
file:/D:/jboss-4.2.3.GA/server/erpln/lib/warrantyresponse.jar
file:/D:/jboss-4.2.3.GA/server/erpln/lib/jbosssx.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33842dom4j.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33922aspectjweaver.jar
file:/D:/jboss-4.2.3.GA/server/erpln/tmp/deploy/tmp33859mvel-1.3.1-java1.4.jar
file:/D:/jboss-4.2.3.GA/server/erpln/deploy/smooks.esb/
file:/D:/jboss-4.2.3.GA/server/erpln/lib/jboss-saaj.jar
file:/D:/jboss-4.2.3.GA/server/erpln/lib/jboss-vfs.jar

[kconner]

Could you send me your log file? There may be something obvious that I could see.

Any luck with sending your app yet?

Kev

[lfhaddix]

No luck. It acts like it is not seeing the jar files in the esb

[kconner]

Your server.log will hopefully show something, especially if you have debug enabled. Could you please send it to me?

[kconner]

Thanks for the logs.

I have been through them but cannot see anything obvious. The jar file you mentioned earlier is definitely on the classpath and is mentioned in the log and the previous output you attached.

Could you try going to JMImplementation:name=Default,service=LoaderRepository and execute the displayClassInfo() mehod on this class?

What output do you see?

[lfhaddix]

I have just located the problem. The class that is acessing AddressDocument is not inside the esb. It is in the server/erpln/lib directory.

When I move it into the esb directory the jobs run.

The problem with this is there are 10 applications that use the classes in this jar. With the new jboss-esb 4.4, I am going to have to update 10 applications everytime I change a class is this jar file.

Thanks again for all of your help, Kevin.

[kconner]

Thanks for letting us know.

If you do want to sort out the replication of that jar then please create a simple example of the problem and email it to me. I would be more than happy to look at it and suggest alternatives.