[Design of JBoss ESB] - ESB4.x/AS 5 classloading
by beve
In the ESB a .esb archive may contain action classes that the ESB needs to have access to and load. The same goes for resources in these archives.
There is also the case were there are services that provide services to other esb services. For example, there is a smooks.esb that provides a SmooksAction which provides data transformation. To use the SmooksAction, a user creates an .esb archive and referenses the SmooksAction from the ESB configuration. They will also need to specify that their .esb archive depends on smooks.esb which they specify in the file deployment.xml.
This worked well with JBoss AS 4.x but with AS 5 this does not work and I think some sort of classloading configuration will be needed simliar to OSGI where a .esb archive might need to contain a META-INF/jboss-classloading.xml file and declare what packages/modules it imports/exports.
Without any configuration this is what happens upon deployment :
java.lang.RuntimeException: java.lang.RuntimeException: Failed to find action class 'org.jboss.soa.esb.smooks.SmooksAction'.
| at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:138)
| at org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment.start(EsbDeployment.java:112)
| ... // Cut out some of the stacktrace to make it more readable /Daniel
| ...
| Caused by: java.lang.RuntimeException: Failed to find action class 'org.jboss.soa.esb.smooks.SmooksAction'.
| at org.jboss.soa.esb.listeners.config.mappers.XMLBeansModel.getContractPublisher(XMLBeansModel.java:378)
| at org.jboss.soa.esb.listeners.config.mappers.XMLBeansModel.getServicePublishers(XMLBeansModel.java:351)
| at org.jboss.soa.esb.listeners.config.model.Model101SchemaParser$Model101Adapter.getServicePublishers(Model101SchemaParser.java:116)
| at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:117)
| ... 53 more
| Caused by: java.lang.ClassNotFoundException: org.jboss.soa.esb.smooks.SmooksAction
| at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
| at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
| at java.lang.Class.forName0(Native Method)
| at java.lang.Class.forName(Class.java:242)
| at org.jboss.soa.esb.util.ClassUtil.forName(ClassUtil.java:93)
| at org.jboss.soa.esb.listeners.config.mappers.XMLBeansModel.getContractPublisher(XMLBeansModel.java:376)
| ... 56 more
| 08:46:16,523 INFO [EsbDeployment] Destroying ESB Deployment 'transformation-pojo-quickstart'
| 08:46:16,586 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS IN ERROR:
| Deployment "jboss.esb.vfszip:/opt/jboss/as/jboss-5.0.1.GA/server/default/deploy/transformation-pojo-quickstart.esb/" is in error due to the following reason(s): java.lang.ClassNotFoundException: org.jboss.soa.esb.smooks.SmooksAction
|
The org.jboss.soa.esb.smooks.SmooksAction class lives in smooks.esb. Now the transformation-pojo-quickstart.esb does state that it depends on smooks.esb but this does not give it access to the classes from smooks.esb as far as I can tell (from server.log):
2009-04-16 10:59:14,468 DEBUG [org.jboss.soa.esb.listeners.deployers.mc.EsbConfigParser] (main)
| Parsed ESB configuration'EsbMetaData [archiveName='transformation-pojo-quickstart.esb/META-INF/jboss-esb.xml', deploymentName='transformation-pojo-quickstart',
| dependencies='[
| jboss.esb.quickstart.destination:service=Queue,name=quickstart_simple_transformation_Response,
| jboss.esb.quickstart.destination:service=Queue,name=quickstart_transform_pojo_gw,
| jboss.esb:deployment=smooks.esb,
| jboss.esb.quickstart.destination:service=Queue,name=quickstart_transform_pojo_esb]']'
|
Now, if smooks.esb contains a META-INF/jboss-classloading.xml that exports the org.jboss.soa.esb.smooks.SmooksAction will that mean that this deployment, the transformation-pojo-quickstart.esb, will have access to that class?
I'm thinking no, as the quickstart does to say that it requires access to the package. Just becasue smooks.esb exports a class does not mean that other deployment will see it.
So if .esb archives are to be able to get deployed as is, we may need to inquire the services that it depends on and add the equivalent ClassLoadingMetaData during deployment.
I'll start by trying to manually add a jboss-classloading.xml to the quickstart and see if that works.
If anyone has comments or suggestions they are always welcome.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225937#4225937
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225937
16 years, 11 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XML configuration changes
by jmesnil
Doing things in correct order this time: 1st talk about it, then implement it.
XSD forces to have these "containers" element inside a xsd:all when the same element must appear mulitple times.
In order to be consistent, I'll add the same "queues" container to jbm-queues.xml. Wether the queue are defined in jbm-configuration or jbm-queues, the XML will look the same
I'll also change the queue definition to match the style of other elements definition (i.e. elements instead of attributes to define the element characteristics).
Lastly, I've added a "entries" container to the jbm-jms.xml's connection-factory but not for topic or queues.
To be consistent, either I add "entries" container for queue and topic (-1 for that). Or I remove the "entries" container from connection-factory and put all the cf configuration elements in a "configuration" container.
Instead of:
| <connection-factory name="MyExampleConnectionFactory">
| <connector-ref connector-name="netty"/>
| <entries>
| <entry name="/MyExampleConnectionFactory"/>
| <entry name="/acme/MyExampleConnectionFactoryDupe"/>
| <entry name="java:/xyz/CF1"/>
| <entry name="java:/connectionfactories/acme/connection_factory"/>
| </entries>
| <ping-period>5000</ping-period>
| <call-timeout>30000</call-timeout>
| <!-- This is the window size in bytes to use when using consumer window based flow control -->
| <consumer-window-size>1048576</consumer-window-size>
| <!-- This is the maximum producer send rate that will be applied when using rate based consumer flow control -->
| <consumer-max-rate>5000</consumer-max-rate>
| <!-- This is the send window size in bytes -->
| <producer-window-size>1048576</producer-window-size>
| <!-- This is the maximum producer send rate that will be applied when using rate based producer flow control -->
| <producer-max-rate>100</producer-max-rate>
| <!-- When using this ConnectionFactory, messages beyond this limit are considered largeMessages and will be sent using smaller packets -->
| <min-large-message-size>10240</min-large-message-size>
| <!-- You can specify the default Client ID to use for connections created using this factory -->
| <client-id>MyClientID</client-id>
| <!-- The batch size in bytes to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode -->
| <dups-ok-batch-size>1048576</dups-ok-batch-size>
| <!-- The batch size in bytes to use when using transactional sessions -->
| <transaction-batch-size>1048576</transaction-batch-size>
| <!--Whether or not we use a blocking call when acknowledging a message-->
| <block-on-acknowledge>false</block-on-acknowledge>
| <!--Whether we send non persistent messages synchronously-->
| <send-np-messages-synchronously>true</send-np-messages-synchronously>
| <!--Whether we send persistent messages synchronously-->
| <send-p-messages-synchronously>true</send-p-messages-synchronously>
| <!--If true, any connections will automatically set a unique group id (per producer) on every message sent-->
| <auto-group-id>true</auto-group-id>
| <!--if true then the server will pre ack any message before delivery to a consumer-->
| <pre-acknowledge>false</pre-acknowledge>
| </connection-factory>
|
we will have
| <connection-factory name="MyExampleConnectionFactory">
| <configuration>
| <connector-ref connector-name="netty"/>
| <ping-period>5000</ping-period>
| <call-timeout>30000</call-timeout>
| <!-- This is the window size in bytes to use when using consumer window based flow control -->
| <consumer-window-size>1048576</consumer-window-size>
| <!-- This is the maximum producer send rate that will be applied when using rate based consumer flow control -->
| <consumer-max-rate>5000</consumer-max-rate>
| <!-- This is the send window size in bytes -->
| <producer-window-size>1048576</producer-window-size>
| <!-- This is the maximum producer send rate that will be applied when using rate based producer flow control -->
| <producer-max-rate>100</producer-max-rate>
| <!-- When using this ConnectionFactory, messages beyond this limit are considered largeMessages and will be sent using smaller packets -->
| <min-large-message-size>10240</min-large-message-size>
| <!-- You can specify the default Client ID to use for connections created using this factory -->
| <client-id>MyClientID</client-id>
| <!-- The batch size in bytes to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode -->
| <dups-ok-batch-size>1048576</dups-ok-batch-size>
| <!-- The batch size in bytes to use when using transactional sessions -->
| <transaction-batch-size>1048576</transaction-batch-size>
| <!--Whether or not we use a blocking call when acknowledging a message-->
| <block-on-acknowledge>false</block-on-acknowledge>
| <!--Whether we send non persistent messages synchronously-->
| <send-np-messages-synchronously>true</send-np-messages-synchronously>
| <!--Whether we send persistent messages synchronously-->
| <send-p-messages-synchronously>true</send-p-messages-synchronously>
| <!--If true, any connections will automatically set a unique group id (per producer) on every message sent-->
| <auto-group-id>true</auto-group-id>
| <!--if true then the server will pre ack any message before delivery to a consumer-->
| <pre-acknowledge>false</pre-acknowledge>
| </configuration>
|
| <entry name="/MyExampleConnectionFactory"/>
| <entry name="/acme/MyExampleConnectionFactoryDupe"/>
| <entry name="java:/xyz/CF1"/>
| <entry name="java:/connectionfactories/acme/connection_factory"/>
| </connection-factory>
|
wdyt?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225925#4225925
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225925
16 years, 11 months