Messages posted by: maxking

Hi, I have the same problem. I have a Johnson Controls FX40 and set up some analogue temperature BACNet points on the FX40.

The FX40 is attached to a fixed IP address wireless router and I can easy get in there to change the logic or monitor the logic.

I tried to setup a BACNet point using mango and in the Device ID I enter 5667 which is the device ID and in broadcast address I enter in the fixed IP address where I want to connect too.

What do I enter in the port address, at this time its 47808 and as for the wireless fixed IP address router I only port forward, 8080, 3011, 1911, 9973 to the FX40 and that’s all that is needed.

I can enable the device and no warnings or alarms appear, and when i change the port to 8080 or use whois i get "Address already in use: Cannot bind" and i get that on all the above port addresses 8080, 3011, 1911, 9973.

Has anyone got any ideas ?

Thanks apl, I have refered back to my original installation and have deleted all files in the webapps directory and then created a ROOT directory inside the webapps directory and placed all mango files in there and yes if i go to http://localhost:8080 on the server everything is fine and i can log in.

I have the URL pointing to the Tomcat webapps directory on the server (not the root like before).

Now i have other web sites on this server so i use the IIS, so apart from setting up another server is there a solution where i can have IIS and Tomcat on the same server ?

I have now change the port address to 8181 by going to the directory apache-tomact-6.0.20\conf and editing server.xml file to:

<Connector port="8181" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />

I can still log in using http://localhost:8181 and works but no logos and graphics, but still at this time got the problem with doing this from my laptop using a web browser http://213.130.131.19:8181 so it looks like port 8181 is also blocked

So i put it back to the original setting 8080 and took the info from my tomcat msdos startup which is below:

27-Jan-2010 15:16:47 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\ProgramFiles\Java\jdk1.6.0_18\bin;.;C:\WINNT\Sun\Java\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program iles\Symantec\pcAnywhere\;C:\php;D:\bin\perl.exe;C:\usr\local\wbin;C:\mysql\bin\;
27-Jan-2010 15:16:47 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
27-Jan-2010 15:16:47 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 730 m
27-Jan-2010 15:16:47 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
27-Jan-2010 15:16:47 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.20
27-Jan-2010 15:16:48 org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
27-Jan-2010 15:16:48 org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
27-Jan-2010 15:16:49 org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext INFO 2010-01-27 15:16:49,293 (org.springframework.web.context.ContextLoader.initWebApplicationContext:189) - Root WebApplicationContext: initialization started
INFO 2010-01-27 15:16:49,373 (org.springframework.context.support.AbstractApplicationContext.prepareRefresh:412) - Refreshing org.springframework.web.context.support.XmlWebApplicationContext@b25b9d: display name [Root WebApplicationContext]; startup date [Wed Jan 27 15:16:49 GMT 2010]; root of context hierarchy
INFO 2010-01-27 15:16:49,503 (org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions:323) - Loading XML bean definitions from ServletContext resource [/WEB-INF/applicationContext.xml]
INFO 2010-01-27 15:16:49,594 (org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory:427) - Bean factory for application context [org.springframework.web.context.support.XmlWebApplicationContext@b25b9d]: org.springframework.beans.factory.support.DefaultListableBeanFactory@16925b0
INFO 2010-01-27 15:16:49,784 (org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons:414) - Pre-instantiating singletonsin org.springframework.beans.factory.support.DefaultListableBeanFactory@16925b0: defining beans [CompoundEventsDwr,CustomViewDwr,DataPointDetailsDwr,DataPointE
ditDwr,DataSourceEditDwr,DataSourceListDwr,EmportDwr,EventHandlersDwr,EventsDwr,MailingListsDwr,MiscDwr,PointHierarchyDwr,PointLinksDwr,PublisherEditDwr,PublisherListDwr,ReportsDwr,ScheduledEventsDwr,SystemSettingsDwr,UsersDwr,ViewDwr,WatchListDwr,localeResolver,messageSource]; root of factory hierarchy
INFO 2010-01-27 15:16:50,004 (org.springframework.web.context.ContextLoader.ini tWebApplicationContext:209) - Root WebApplicationContext: initialization completed in 701 ms
INFO 2010-01-27 15:16:50,004 (com.serotonin.mango.MangoContextListener.contextInitialized:73) - Mango context starting
INFO 2010-01-27 15:16:50,425 (com.serotonin.mango.db.DerbyAccess.initializeImpl:69) - Initializing derby connection manager
INFO 2010-01-27 15:16:52,648 (com.serotonin.mango.db.upgrade.DBUpgrade.checkUpgrade:76) - Starting instance with version 1.8.0
INFO 2010-01-27 15:16:53,679 (org.quartz.simpl.SimpleThreadPool.initialize:25 - Job execution threads will use class loader of thread: main
INFO 2010-01-27 15:16:53,720 (org.quartz.core.SchedulerSignalerImpl.<init>:63)- Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
INFO 2010-01-27 15:16:53,720 (org.quartz.core.QuartzScheduler.<init>:215) - Quartz Scheduler v.1.6.3 created.
INFO 2010-01-27 15:16:53,730 (org.quartz.simpl.RAMJobStore.initialize:141) - RAMJobStore initialized.
INFO 2010-01-27 15:16:53,730 (org.quartz.impl.StdSchedulerFactory.instantiate:1224) - Quartz scheduler 'DefaultQuartzScheduler' initialized from default resour
ce file in Quartz package: 'quartz.properties'
INFO 2010-01-27 15:16:53,730 (org.quartz.impl.StdSchedulerFactory.instantiate:122 - Quartz scheduler version: 1.6.3
INFO 2010-01-27 15:16:53,730 (org.quartz.core.QuartzScheduler.start:461) - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
INFO 2010-01-27 15:16:54,350 (com.serotonin.mango.MangoContextListener.contextInitialized:97) - Mango context started
27-Jan-2010 15:16:54 org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'springDispatcher'
INFO 2010-01-27 15:16:54,401 (org.springframework.web.servlet.FrameworkServlet.initServletBean:257) - FrameworkServlet 'springDispatcher': initialization started
INFO 2010-01-27 15:16:54,401 (org.springframework.context.support.AbstractApplicationContext.prepareRefresh:412) - Refreshing org.springframework.web.context.support.XmlWebApplicationContext@f3770c: display name [WebApplicationContext for namespace 'springDispatcher-servlet']; startup date [Wed Jan 27 15:16:54 GMT 2010]; parent: org.springframework.web.context.support.XmlWebApplicationContext@b25b9d
INFO 2010-01-27 15:16:54,401 (org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions:323) - Loading XML bean definitions from ServletContext resource [/WEB-INF/springDispatcher-servlet.xml]
INFO 2010-01-27 15:16:54,441 (org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory:427) - Bean factory for application context [org.springframework.web.context.support.XmlWebApplicationContext@f3770c]: org.springframework.beans.factory.support.DefaultListableBeanFactory@1ad6c98
INFO 2010-01-27 15:16:54,511 (org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons:414) - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1ad6c98: defining beans [viewResolver,defaultMessageCodeResolver,publicUrlMappings,compoundEventsController,dataPointDetailsController,dataPointEditController,dataSourceEditController,dataSourceListController,emportController,eventHandlersController,eventsController,helpController,loginController,logoutController,mobileLoginController,mobileLogoutController,mobileWatchListController,mailingListsController,pointHierarchyController,pointLinksController,publicViewController,publisherEditController,publisherListController,reportChartController,reportsController,scheduledEventsController,sqlController,systemSettingsController,usersController,viewsController,viewEditController,watchListController,webcamLiveFeedController,multipartResolver,commonData]; parent: org.springframework.beans.fory.support.DefaultListableBeanFactory@16925b0INFO 2010-01-27 15:16:55,122 (org.springframework.web.servlet.FrameworkServlet.initServletBean:276) - FrameworkServlet 'springDispatcher': initialization completed in 721 ms
INFO 2010-01-27 15:16:55,132 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - DWR Version 2.0.1 starting.
INFO 2010-01-27 15:16:55,132 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - - Servlet Engine: Apache Tomcat/6.0.20
INFO 2010-01-27 15:16:55,132 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - - Java Version: 1.6.0_18
INFO 2010-01-27 15:16:55,132 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - - Java Vendor: Sun Microsystems Inc.
INFO 2010-01-27 15:16:55,382 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Probably not an issue: org.jdom.Document is not available so the jdom converter will not load. This is only an problem if you wanted to use it.
INFO 2010-01-27 15:16:55,382 (org.directwebremoting.util.CommonsLoggingOutput.info:51) - Probably not an issue: org.jdom.Element is not available so the jdom converter will not load. This is only an problem if you wanted to use it.
27-Jan-2010 15:16:55 org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080
27-Jan-2010 15:16:55 org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009
27-Jan-2010 15:16:55 org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/30 config=null
27-Jan-2010 15:16:55 org.apache.catalina.startup.Catalina start INFO: Server startup in 7947 ms

Problem is i do not know where to go to open ports on a windows 2000 server, which again is a problem.

Any help will be appriciated, and thank you for the advice you have given me so far.

It looks like its the tomcat setup and really nothing to do with mango.

OK, i installed tomcat again and this time pointed to the webapps directory.

So now when i run http://213.130.131.19/index.html i get the Apache Tomcat page.

And when i run http://213.130.131.19/sample/ i get the sample Hello world page

And when i run http://213.130.131.19/mango-1.8.0/ i get the index.jsp page so i am not sure its a fire wall problem.

I followed the Mango document and deleted everything in the webapps directory and made a directory called ROOT and unzipped the mango software in that directory, maybe i was wrong to do this.

So getting there slowley, just don't know why i am seeing the index.jsp and its not running

Hi, i am new to this software and found this site browsing search engines for server software for MODbus.
I have my own server (Microsoft Windows 2000, 5.00.2195, Service Pack 4) in Manchester where I have full access via PCAnywhere and I installed jdk-6u18-windows-i586.exe, apache-tomcat-6.0.20, mango-1.8.0 following the instructions from your web site.

Now when I go to http://localhost:8080 using a firefox web browser on my server everything is fine.

And when I go to http://213.130.131.19:8080 again on my server only, everything is fine, but when I try this from a remote computer I can’t see the page.

Now in Tomcat directory on the server at d:\maxking\geo\apache-tomcat-6.0.20\webapps\ROOT I placed a index.htm test page there and of cause if I type in http://213.130.131.19/ I get the index.htm file, so I know I have this pointing to what I think is the correct folder on the server.

Now I have tried to setup the system so I can remotely look at the mango login, but I don’t know what I am doing wrong, and its very clear to myself that I don’t have a clue

Anyone out there that can help, please.

In the Internet Information Services
Home Directory
Local Path: D:\maxking\geo\apache-tomcat-6.0.20\webapps\ROOT
Script sources access, read, write, directory browsing all ticked.
Application name = default Application
Execute Permissions: Scripts and Executables
Application Protection: Medium (Pooled)
Documents
Enable Default Document is ticked
Web Site Identification
Description: Geo
IP Address: 213.130.131.19
TCP Port: 80