loader-repository help

[acervi]

I Guys,

I need to create an EAR with its own class loader.

I have read that it is possible to do it using the <loader-repository> tag in the jboss-app.xml file.

The syntax that I have implemented is the following:

<loader-repository>DBUclLoader:loader=DB.ear</loader-repository>

I do not know how to create the JMX object named DBUclLoader.

Do some of you explane me how to do?

Best Regards,

Andrea

[raja05]

Its just a unique name, it could be anything. You dont have to create the jmx object, just use it as it is in the name.
When you look in the jmx-console, you would see a header for DBUclLoader and ur ear entry would be listed under that

-raj

[acervi]

Hi Raj,

I have done as You suggested but Jboss throw me thw following exception:

003-11-14 11:33:43,384 INFO Logger -> Init J2EE application: file:/dati1/cervia/app-server/jboss-3.0.6/server/default/deploy/DB.ear
2003-11-14 11:37:36,816 ERROR Logger -> Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@9d8ff385{ url=file:/dati1/cervia/app-server/jboss-3.0.6/server/default/deploy/DB.ear, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: Connection timed out; - nested throwable: (java.net.ConnectException: Connection timed out)
at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:277)
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:112)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:679)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:435)
at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:656)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:212)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:225)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:202)
Caused by: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:426)
at java.net.Socket.connect(Socket.java:376)
at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:386)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:602)
at sun.net.www.http.HttpClient.(HttpClient.java:303)
at sun.net.www.http.HttpClient.(HttpClient.java:264)
at sun.net.www.http.HttpClient.New(HttpClient.java:336)
at sun.net.www.http.HttpClient.New(HttpClient.java:317)
at sun.net.www.http.HttpClient.New(HttpClient.java:312)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:481)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:472)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:574)
at java.net.URL.openStream(URL.java:960)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:257)
... 17 more

I am using jboss3.0.6 on Sun Solaris 8 with Sun j2sdk1.4.2_02.

The jboss-app.xml is the following:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE jboss-app PUBLIC
"-//JBoss//DTD J2EE Application 1.3//EN"
"http://www.jboss.org/j2ee/dtd/jboss-app_3_0.dtd">
<jboss-app>
<loader-repository>DBUclLoader:loader=DB.ear</loader-repository>
</jboss-app>

On the jmx-console i do not view any entry named DBUclLoader.

Is it a bug or it is a my fault?

Regards,
Andrea

[acervi]

Hi Guys,

I have discovered that my problem is a Jboss 3.0.6 bug because, the suggested solution, works with jboss3.0.8.

Best Regards,

Andrea