dcsimg
Can access application using "http://serverB:8100" but not "http://serverB" (weird log files too)
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   JSPDeveloper_JRunUser
Posted On:   Thursday, June 12, 2003 02:30 PM

We have an application installed on, say, server A. It is accessed using the JRun from server B. User was able to successfully use the application before. It seems like something has changed since no one is able to access the application now using the old URL. JRun has been configured to use IIS. When the user enters the URL, http://serverB/myApp/index.html, he gets a 404 (page not found) error. But when the URL http://serverB:8100/myApp/index.html is used the pages are served and we are able to use the application. Based on this information we are assuming that application is being served if the JRun web server is used but it is not being served when the IIS is used. We have tried re-connecting to the IIS using the con   More>>

We have an application installed on, say, server A. It is accessed using the JRun from server B. User was able to successfully use the application before. It seems like something has changed since no one is able to access the application now using the old URL.



JRun has been configured to use IIS.



When the user enters the URL, http://serverB/myApp/index.html, he gets a 404 (page not found) error. But when the URL http://serverB:8100/myApp/index.html is used the pages are served and we are able to use the application. Based on this information we are assuming that application is being served if the JRun web server is used but it is not being served when the IIS is used. We have tried re-connecting to the IIS using the connector wizard (since we HAVE TO use IIS). Message tells us that configuration has been successfully completed but we are still not able to access the application.



We also looked through the deafult-event logs and found a couple of interesting lines-



06/11 19:11:30 info (JRun) Loading jms

06/11 19:11:30 error (jms) Can not create JNDI initial context: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial



06/11 19:11:30 info (JRun) Loading jndi

06/11 19:11:30 info (JRun) Loading jdbc



06/11 19:11:30 warning (jdbc) Binding exception: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial



[javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial]



javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial



at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:640)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:280)

at javax.naming.InitialContext.bind(InitialContext.java:355)

at allaire.jrun.sql.JdbcBindingService.init(JdbcBindingService.java:98)

at allaire.jrun.ServletService.init(ServletService.java:66)

at allaire.jrun.ServletService.init(ServletService.java:31)

at allaire.jrun.servlet.JRunServletLoader.loadServletInstance(JRunServletLoader.java:203)

at allaire.jrun.servlet.JRunSE.initService(JRunSE.java:892)

at allaire.jrun.servlet.JRunSE.initServices(JRunSE.java:859)

at allaire.jrun.servlet.JvmContext.initServices(JvmContext.java:130)

at allaire.jrun.servlet.JRunSE.init(JRunSE.java:223)

at allaire.jrun.servlet.JvmContext.init(JvmContext.java:69)

at allaire.jrun.ServletService.init(ServletService.java:66)

at allaire.jrun.ServletService.init(ServletService.java:31)

at JRun.main(JRun.java:172)



06/11 19:11:30 info (JRun) (myApp) Initializing JDBC connection pool with 0 connections

06/11 19:11:30 info (JRun) Loading web

06/11 19:11:30 info (web) web listening on *:8100

06/11 19:11:30 info (JRun) Loading mail

06/11 19:11:30 info (JRun) Loading url







We are not sure what is happening. Has someone faced a similar problem ??? Any assistance would be appreciated.

   <<Less

Re: Can access application using "http://serverB:8100" but not "http://serverB" (weird log files too)

Posted By:   AlessandroA_Garbagnati  
Posted On:   Thursday, June 12, 2003 11:31 PM

Hi,

Please, do not post the same question more than once.

Thanks.
About | Sitemap | Contact