Skip to main content

Unknown Host exception when using the latest weekly build

4 replies [Last post]
isingh1
Offline
Joined: 2005-09-30
Points: 0

Hi,
I am getting the java.net.UnknownHostException error when deploying the sample fromjava war file on Sun or Weblogic application server. I am using the latest weekly build. It looks like createModelAndMetadata method in WSServletContextListenor is looking for /WEB-INF/jax-ws-catalog.xml which is not generated by the tool. Please let me know if anyone has encountered similar problem.

Error Description-
java.net.UnknownHostException: C
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.NetworkClient.openServer(NetworkClient.java:118)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:488)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:475)
at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:270)
at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:352)
at java.net.URL.openStream(URL.java:1007)
at com.sun.org.apache.xml.internal.resolver.Catalog.parseCatalogFile(Unknown Source)
at com.sun.org.apache.xml.internal.resolver.Catalog.parsePendingCatalogs(Unknown Source)
at com.sun.org.apache.xml.internal.resolver.Catalog.parseCatalog(Unknown Source)
at com.sun.org.apache.xml.internal.resolver.Catalog.loadSystemCatalogs(Unknown Source)
at com.sun.org.apache.xml.internal.resolver.CatalogManager.getPrivateCatalog(Unknown Source)
at com.sun.org.apache.xml.internal.resolver.CatalogManager.getCatalog(Unknown Source)
at com.sun.xml.ws.util.xml.XmlUtil.createEntityResolver(Unknown Source)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.createModelAndMetadata(Unknown Source)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(Unknown Source)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:336)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:79)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1549)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2565)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:859)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:321)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:114)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:257)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:383)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:
at weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:166)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:81)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)

Thanks,
Irvinder

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kohlert
Offline
Joined: 2003-06-16
Points: 0

Irvinder,
This is a known bug. I believe that even though this exception is occurring, everything is behaving properly. Can you invoke your webservice? I believe this weeks build will have this bug fixed.

isingh1
Offline
Joined: 2005-09-30
Points: 0

Yes I was able to invoke the webservice when running on the Sun application server but I have to test this on the BEA Weblogic 9.0 server and when I deploy the same service on the weblogic server I get the war file deployment exception due to this error and the WSServletContextListener context is destroyed. Is there any workaround to fix this error on weblogic? Can I get some fix pack for this problem.

Thanks,
Irvinder

kohlert
Offline
Joined: 2003-06-16
Points: 0

I believe the weekly build this week will have the fix.

isingh1
Offline
Joined: 2005-09-30
Points: 0

thanks I will wait for the weekly build for this fix.