JBoss DTD loading exception behind proxy [Closed]

MyEclipse IDE

General Development

This topic has 20 replies, 3 voices, and was last updated 20 years, 8 months ago by Riyad Kalla.

Viewing 15 posts - 1 through 15 (of 21 total)

1 2 →

Author

Posts

August 18, 2004 at 9:37 am #212571 Reply

slicer

Member

– System Setup ——————————-
Operating System and version: Windows 2000 professionnal 5.00.2195 Service Pack 4
Eclipse version: 3.0.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: None
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8.0
Eclipse JDK version: 1.4.2
Application Server JDK version: 1.4.2
Are there any exceptions in the Eclipse log file? No

– Message Body ——————————-

I am using Jboss 3.2.5
When I start JBoss, I got an error
10:08:46,466 ERROR [XmlFileLoader] External entity not found: “http://java.sun.com/dtd/application_1_3.dtd”.:-1:2
java.io.IOException: Error in opening uri http://java.sun.com/dtd/application_1_3.dtdstatus code=403
…

Looks like it can’t find the file because of the proxy. (We have a proxy server).
The only way I got it to work was to pass the proxy settings to the JVM as
-DproxyPort=portNum -DproxySet=true -Dhttp.proxyHost=proxy.ic.gc.ca
but this is not a viable option because some applications access files in the *ic.gc.ca

I was previously using MyEclipse3.7.2 and did not have this problem.
I also try to set the proxy in “Internet Tools” & “Install/Update” without success.

Can you help me fix this error ?
Thanks

August 18, 2004 at 10:40 am #212584 Reply

Riyad Kalla

Member

Hang tight I’ve asked someone to take a look at this.

August 18, 2004 at 11:44 am #212624 Reply

Scott Anderson

Participant

slicer,

The only way I got it to work was to pass the proxy settings to the JVM as
-DproxyPort=portNum -DproxySet=true -Dhttp.proxyHost=proxy.ic.gc.ca
but this is not a viable option because some applications access files in
the *ic.gc.ca

This sounds like it used to work, but he can no longer do the same workaround due to
changes in his application setup and the files it references. Is that correct?

The Internet proxy settings in Eclipse will only govern how Eclipse accesses
the internet, not the remote JBoss VM so for that you’ll need another method.

August 18, 2004 at 1:03 pm #212642 Reply

slicer

Member

Hi Scott!

I understand that this may be a JBoss problem, but my configuration worked exactly the way it is with MyEclipse 3.7.2. When 3.8 came out, I upgraded Eclipse and MyEclipse, keeping my JBoss installation the same (without any proxy settings). For some reasone what was working when deployed from MyEclipse 3.7.2 does not work when deployed to JBoss using MyEclipse 3.8, due to the mentioned XML DTD resolution problem. One other thing to mention is that this problem seems to only be happening for the appliaction.xml’s DTD – If I reference this DTD locally, then redeploy, JBoss doesn’t complain about any other externally referenced DTD’s (web.xml, struts-config, etc …). Strange!

Thanks for your help!
Slicer.

August 18, 2004 at 1:09 pm #212643 Reply

Riyad Kalla

Member

Slicer,
Can you paste the doctype definition from the application file here for us to look at?

August 18, 2004 at 2:11 pm #212647 Reply

slicer

Member

Hi,
Here is my application.xml containing the doctype definition.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
   <display-name>MyEclipseDemo</display-name>
   <module id="myeclipse.1092236723614">
      <web>
         <web-uri>MyEclipseDemoWeb.war</web-uri>
         <context-root>/amis/myEclipseDemo</context-root>
      </web>
   </module>
   <module id="myeclipse.1092236723707">
      <ejb>MyEclipseDemoEJB.jar</ejb>
   </module>
</application>

Thanks,
Slicer

August 18, 2004 at 2:43 pm #212651 Reply

Riyad Kalla

Member

Slicer,

Lets try something… copy the contents of that file into TextPad or UltraEdit or some other good editor (not Notepad) then save the file and overwrite the application.xml file in your project with that new one and try again… sometimes it becomes a newline issue and the app server actually barfs because it can’t parse the file right.

If that doesn’t work do you mind download a new JBoss 3.2.5 download, unzip it to C:\Test\JBoss-3.2.5, setup the connector to point at it and start it? Then deploy your app and try it?

August 19, 2004 at 8:47 am #212718 Reply

slicer

Member

Hello,

First, I copied the content of the application.xml to textpad, saved the file and overwrote the application.xml but it did not work.

Then, I downloaded & re-installed JBoss and re-deployed the application and it did not work. So what I did is completely re-install
J2SDK1.4.2_05,
Eclipse 3.0.0 Build id: 200406251208,
MyEclipse 3.8
JBoss 3.2.5
and created the simplest EAR file possible with only a JSP and when I start the application, I still got the error.
External entity not found: “http://java.sun.com/dtd/application_1_3.dtd”.:-1:2
java.io.IOException: Error in opening uri http://java.sun.com/dtd/application_1_3.dtdstatus code=403

So, just to prove to myself that I was not crazy, I re-installed my old configuration
Eclipse 3.0.0 Build id: 200403261517
MyEclipse 3.2.7
Same JBoss as new installation above(3.2.5)
Same J2SDK as new installation above(1.4.2_05)
and it did work!

So here are the console messages for both settings:
New Settings not working:

09:25:56,140 INFO  [Server] Starting JBoss (MX MicroKernel)...
09:25:56,140 INFO  [Server] Release ID: JBoss [WonderLand] 3.2.5 (build: CVSTag=JBoss_3_2_5 date=200406251954)
09:25:56,140 INFO  [Server] Home Dir: C:\Test\jboss-3.2.5
09:25:56,140 INFO  [Server] Home URL: file:/C:/Test/jboss-3.2.5/
09:25:56,140 INFO  [Server] Library URL: file:/C:/Test/jboss-3.2.5/lib/
09:25:56,140 INFO  [Server] Patch URL: null
09:25:56,140 INFO  [Server] Server Name: default
09:25:56,152 INFO  [Server] Server Home Dir: C:\Test\jboss-3.2.5\server\default
09:25:56,152 INFO  [Server] Server Home URL: file:/C:/Test/jboss-3.2.5/server/default/
09:25:56,152 INFO  [Server] Server Data Dir: C:\Test\jboss-3.2.5\server\default\data
09:25:56,152 INFO  [Server] Server Temp Dir: C:\Test\jboss-3.2.5\server\default\tmp
09:25:56,152 INFO  [Server] Server Config URL: file:/C:/Test/jboss-3.2.5/server/default/conf/
09:25:56,152 INFO  [Server] Server Library URL: file:/C:/Test/jboss-3.2.5/server/default/lib/
09:25:56,152 INFO  [Server] Root Deployment Filename: jboss-service.xml
09:25:56,156 INFO  [Server] Starting General Purpose Architecture (GPA)...
09:25:56,281 INFO  [ServerInfo] Java version: 1.4.2_05,Sun Microsystems Inc.
09:25:56,281 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_05-b04,Sun Microsystems Inc.
09:25:56,281 INFO  [ServerInfo] OS-System: Windows 2000 5.0,x86
09:25:56,437 INFO  [Server] Core system initialized
09:25:57,164 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
09:25:57,297 INFO  [WebService] Using RMI server codebase: http://IPT-BRISSONP:8083/
09:25:57,324 INFO  [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
09:25:58,867 INFO  [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA drivers
09:25:58,871 INFO  [RARMetaData] Required license terms present. See deployment descriptor.
09:26:00,953 INFO  [MailService] Mail Service bound to java:/Mail
09:26:01,246 INFO  [Embedded] Catalina naming disabled
09:26:01,543 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
09:26:01,566 INFO  [Catalina] Initialization processed in 285 ms
09:26:01,566 INFO  [StandardService] Starting service jboss.web
09:26:01,574 INFO  [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.26
09:26:01,578 INFO  [StandardHost] XML validation disabled
09:26:01,597 INFO  [Catalina] Server startup in 31 ms
09:26:01,636 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:26:01,644 INFO  [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/Test/jboss-3.2.5/server/default/deploy/http-invoker.sar/invoker.war/
09:26:02,117 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:26:02,121 INFO  [TomcatDeployer] deploy, ctxPath=, warUrl=file:/C:/Test/jboss-3.2.5/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
09:26:02,215 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:26:02,218 INFO  [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/Test/jboss-3.2.5/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
09:26:02,308 INFO  [DefaultDS] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name 'java:/DefaultDS'
09:26:02,480 INFO  [A] Bound to JNDI name: queue/A
09:26:02,480 INFO  [B] Bound to JNDI name: queue/B
09:26:02,484 INFO  [C] Bound to JNDI name: queue/C
09:26:02,484 INFO  [D] Bound to JNDI name: queue/D
09:26:02,484 INFO  [ex] Bound to JNDI name: queue/ex
09:26:02,508 INFO  [testTopic] Bound to JNDI name: topic/testTopic
09:26:02,508 INFO  [securedTopic] Bound to JNDI name: topic/securedTopic
09:26:02,508 INFO  [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
09:26:02,508 INFO  [testQueue] Bound to JNDI name: queue/testQueue
09:26:02,547 INFO  [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
09:26:02,578 INFO  [DLQ] Bound to JNDI name: queue/DLQ
09:26:02,590 INFO  [JmsXA] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA'
09:26:02,633 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/Test/jboss-3.2.5/server/default/deploy/jmx-console.war/
09:26:03,117 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/Test/jboss-3.2.5/server/default/tmp/deploy/tmp36717web-console.war/
09:26:03,383 INFO  [EARDeployer] Init J2EE application: file:/C:/Test/jboss-3.2.5/server/default/deploy/DEMO__AMIS_MyEclipseDemo.ear/
09:26:03,535 ERROR [XmlFileLoader] External entity not found: "http://java.sun.com/dtd/application_1_3.dtd".:-1:2
java.io.IOException: Error in opening uri http://java.sun.com/dtd/application_1_3.dtdstatus code=403
    at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3376)
    at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.java:3064)
    at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1347)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:656)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:293)
    at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:247)
    at org.jboss.deployment.EARDeployer.init(EARDeployer.java:123)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:700)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:635)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
    at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy7.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:367)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
    at org.jboss.Main.boot(Main.java:145)
    at org.jboss.Main$1.run(Main.java:399)
    at java.lang.Thread.run(Thread.java:534)
09:26:03,539 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Test/jboss-3.2.5/server/default/deploy/DEMO__AMIS_MyEclipseDemo.ear/
org.jboss.deployment.DeploymentException: External entity not found: "http://java.sun.com/dtd/application_1_3.dtd".; - nested throwable: (java.io.IOException: Error in opening uri http://java.sun.com/dtd/application_1_3.dtdstatus code=403)
    at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:307)
    at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:247)
    at org.jboss.deployment.EARDeployer.init(EARDeployer.java:123)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:700)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:635)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
    at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy7.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:837)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:367)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:185)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
    at org.jboss.Main.boot(Main.java:145)
    at org.jboss.Main$1.run(Main.java:399)
    at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: Error in opening uri http://java.sun.com/dtd/application_1_3.dtdstatus code=403
    at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3376)
    at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.java:3064)
    at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1347)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:656)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:293)
    ... 67 more
09:26:03,539 INFO  [EARDeployer] Init J2EE application: file:/C:/Test/jboss-3.2.5/server/default/deploy/MyTest.ear/
09:26:03,566 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:26:03,574 INFO  [TomcatDeployer] deploy, ctxPath=/MyTestWeb, warUrl=file:/C:/Test/jboss-3.2.5/server/default/deploy/MyTest.ear/MyTestWeb.war/
09:26:03,648 INFO  [EARDeployer] Started J2EE application: file:/C:/Test/jboss-3.2.5/server/default/deploy/MyTest.ear/
09:26:03,652 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Incompletely deployed packages:
org.jboss.deployment.DeploymentInfo@80ad9181 { url=file:/C:/Test/jboss-3.2.5/server/default/deploy/DEMO__AMIS_MyEclipseDemo.ear/ }
  deployer: org.jboss.deployment.EARDeployer@4e2f0a
  status: null
  state: FAILED
  watch: file:/C:/Test/jboss-3.2.5/server/default/deploy/DEMO__AMIS_MyEclipseDemo.ear/
  lastDeployed: 1092921963539
  lastModified: 1092918743832
  mbeans:


09:26:03,738 INFO  [Server] JBoss (MX MicroKernel) [3.2.5 (build: CVSTag=JBoss_3_2_5 date=200406251954)] Started in 7s:582ms
09:26:03,738 INFO  [Tomcat5] Saw org.jboss.system.server.started notification, starting connectors
09:26:03,840 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
09:26:04,246 INFO  [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
09:26:04,277 INFO  [JkMain] Jk running ID=0 time=0/109  config=null

Old Settings Working:


09:20:40,765 INFO  [Server] Starting JBoss (MX MicroKernel)...
09:20:40,953 INFO  [Server] Release ID: JBoss [WonderLand] 3.2.5 (build: CVSTag=JBoss_3_2_5 date=200406251954)
09:20:40,968 INFO  [Server] Home Dir: C:\Test2\jboss-3.2.5
09:20:40,968 INFO  [Server] Home URL: file:/C:/Test2/jboss-3.2.5/
09:20:40,968 INFO  [Server] Library URL: file:/C:/Test2/jboss-3.2.5/lib/
09:20:40,968 INFO  [Server] Patch URL: null
09:20:40,968 INFO  [Server] Server Name: default
09:20:40,968 INFO  [Server] Server Home Dir: C:\Test2\jboss-3.2.5\server\default
09:20:40,968 INFO  [Server] Server Home URL: file:/C:/Test2/jboss-3.2.5/server/default/
09:20:40,968 INFO  [Server] Server Data Dir: C:\Test2\jboss-3.2.5\server\default\data
09:20:40,984 INFO  [Server] Server Temp Dir: C:\Test2\jboss-3.2.5\server\default\tmp
09:20:40,984 INFO  [Server] Server Config URL: file:/C:/Test2/jboss-3.2.5/server/default/conf/
09:20:40,984 INFO  [Server] Server Library URL: file:/C:/Test2/jboss-3.2.5/server/default/lib/
09:20:40,984 INFO  [Server] Root Deployment Filename: jboss-service.xml
09:20:40,984 INFO  [Server] Starting General Purpose Architecture (GPA)...
09:20:41,656 INFO  [ServerInfo] Java version: 1.4.2_05,Sun Microsystems Inc.
09:20:41,656 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_05-b04,Sun Microsystems Inc.
09:20:41,656 INFO  [ServerInfo] OS-System: Windows 2000 5.0,x86
09:20:42,015 INFO  [Server] Core system initialized
09:20:45,421 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
09:20:45,890 INFO  [WebService] Using RMI server codebase: http://IPT-BRISSONP:8083/
09:20:46,031 INFO  [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
09:20:53,406 INFO  [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA drivers
09:20:53,406 INFO  [RARMetaData] Required license terms present. See deployment descriptor.
09:20:58,093 INFO  [MailService] Mail Service bound to java:/Mail
09:20:59,281 INFO  [Embedded] Catalina naming disabled
09:21:00,468 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
09:21:00,562 INFO  [Catalina] Initialization processed in 1141 ms
09:21:00,578 INFO  [StandardService] Starting service jboss.web
09:21:00,593 INFO  [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.26
09:21:00,609 INFO  [StandardHost] XML validation disabled
09:21:00,703 INFO  [Catalina] Server startup in 125 ms
09:21:00,843 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:21:00,875 INFO  [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/Test2/jboss-3.2.5/server/default/deploy/http-invoker.sar/invoker.war/
09:21:02,890 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:21:02,906 INFO  [TomcatDeployer] deploy, ctxPath=, warUrl=file:/C:/Test2/jboss-3.2.5/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
09:21:03,296 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:21:03,312 INFO  [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/Test2/jboss-3.2.5/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
09:21:03,718 INFO  [DefaultDS] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name 'java:/DefaultDS'
09:21:04,187 INFO  [A] Bound to JNDI name: queue/A
09:21:04,203 INFO  [B] Bound to JNDI name: queue/B
09:21:04,203 INFO  [C] Bound to JNDI name: queue/C
09:21:04,203 INFO  [D] Bound to JNDI name: queue/D
09:21:04,203 INFO  [ex] Bound to JNDI name: queue/ex
09:21:04,656 INFO  [testTopic] Bound to JNDI name: topic/testTopic
09:21:04,656 INFO  [securedTopic] Bound to JNDI name: topic/securedTopic
09:21:04,671 INFO  [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
09:21:04,671 INFO  [testQueue] Bound to JNDI name: queue/testQueue
09:21:04,812 INFO  [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
09:21:04,921 INFO  [DLQ] Bound to JNDI name: queue/DLQ
09:21:04,984 INFO  [JmsXA] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA'
09:21:05,156 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/Test2/jboss-3.2.5/server/default/deploy/jmx-console.war/
09:21:05,968 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/Test2/jboss-3.2.5/server/default/tmp/deploy/tmp47117web-console.war/
09:21:07,171 INFO  [EARDeployer] Init J2EE application: file:/C:/Test2/jboss-3.2.5/server/default/deploy/test.ear/
09:21:07,218 WARN  [DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=null
09:21:07,234 INFO  [TomcatDeployer] deploy, ctxPath=/testWeb, warUrl=file:/C:/Test2/jboss-3.2.5/server/default/deploy/test.ear/testWeb.war/
09:21:07,515 INFO  [EARDeployer] Started J2EE application: file:/C:/Test2/jboss-3.2.5/server/default/deploy/test.ear/
09:21:07,828 INFO  [Server] JBoss (MX MicroKernel) [3.2.5 (build: CVSTag=JBoss_3_2_5 date=200406251954)] Started in 26s:844ms
09:21:07,828 INFO  [Tomcat5] Saw org.jboss.system.server.started notification, starting connectors
09:21:07,953 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
09:21:08,390 INFO  [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
09:21:08,421 INFO  [JkMain] Jk running ID=0 time=0/125  config=null

I hope this helps,
Slicer

August 19, 2004 at 10:03 am #212730 Reply

Riyad Kalla

Member

OOHHHH <slaps forhead> I wish we had seen that problem to start off… go into your JBoss connector settings and for the two Builder classes, change the “crimson” part to “xerces” and it will work. This is a known bug that should be fixed in GA.

August 19, 2004 at 10:29 am #212734 Reply

slicer

Member

Great! It works!

Thanks for your help and quick response.

Just to let you know, the fix you posted worked but I was using the GA version,
MyEclipse Enterprise Workbench 3.8.0 GA for Windows 98/NT/2000/XP (8/16/2004)

Did you mean it will be fixed in your next release ?

Slicer

August 19, 2004 at 11:07 am #212741 Reply

Riyad Kalla

Member

Slicer,
sorry I double checked on this. We *had* to make that change for the JBoss 4 connector, but for JBoss 3, up until the 3.2.3 version, the “crimson” libraries worked fine, but then 3.2.4 and 3.2.5 aparently need this change which is a PIA for us because we don’t know if you are launching JBoss <3.2.3. or >= 3.2.4, so we cant’ really automate that step.

Either way I’m glad you are up and running.

September 22, 2004 at 9:33 am #215738 Reply

slicer

Member

Hello,

I just updated eclipse & Myeclipse version to
Eclipse version: 3.0.1
MyEclipse version: 3.8.1
I added this message to this post because it is a continuity of this previous problem with dtd & proxy.

I set the proxy setting in the internet Proxy tab and I verified that the XML parser for Jboss 3 were xerces. When I try to run my application which is using tiles, I get this error from the files-defs.xml

javax.servlet.ServletException: IO Error while parsing file ‘/WEB-INF/config/tiles-defs.xml’. Server returned HTTP response code: 403 for URL: http://jakarta.apache.org/struts/dtds/tiles-config.dtd

Can you help me again with that.
Thanks

September 22, 2004 at 9:42 am #215742 Reply

Riyad Kalla

Member

slicer,
The proxy settings are just used by Eclipse and the editors to be able to access the files, when JBoss is running it won’t be using the Eclipse proxy settings. Can you try and start JBoss outside of MyEclipse from the command line and see if it works?

September 22, 2004 at 9:55 am #215744 Reply

slicer

Member

Hi,
I have the same error outside of MyEclipse. Your answer put me on a trail. It does not complain about the other DTDs, so I turned off the parser validation for this tiles-defs.xml and it did work. So is it because different XML parser are used to parse, for example, the web.xml and the tiles-defs.xml ?

Thanks

September 22, 2004 at 9:59 am #215745 Reply

Riyad Kalla

Member

So is it because different XML parser are used to parse, for example, the web.xml and the tiles-defs.xml ?

I honestly have no idea how JBoss is written… I’d imagine it would be the same parser… try and open the file you posted above in your browser: http://jakarta.apache.org/struts/dtds/tiles-config.dtd

If you can’t, then its a general proxy issue, if you can… then I’m officially confused 🙂

Author

Posts

Viewing 15 posts - 1 through 15 (of 21 total)

1 2 →