$50 reward for someone to configure my DimDim

wags
2007-04-14
2013-05-01
  • wags

    wags - 2007-04-14

    I have it installed on a StartLogic VPS running Plesk.

    I have the JRE 6.0 installed. I just installed DimDim 1.6 via the RPM.

    I can start and stop the DimDim server, but it doesn't give me a welcome page when I go to the URL.

    I am not sure if this might be from what looks like a few typos on the installation instructions for configuring DimDim's files via VI. If anyone can show me how to configure it to get it running, I'm willing to send them $50 via PayPal. All of the files should be there. Please feel free to IM if you would like to give it a try.

    Skype:Ben Fremer
    MSN IM: BenFremer@hotmail.com
    Yahoo IM: BenFremer
    AOL IM: BenFremer
    Toll-Free (888)-262-4696

    Thanks,

    Ben Fremer
    Ben@WebAndGraphicSolutions.com
    CEO
    Web & Graphic Solutions
    (888)-262-4696

     
    • wags

      wags - 2007-04-14

      I tried changing the port to 8050 and going to http://64.150.166.154:8050/ ( 64.150.166.154 ) is my IP, and it still didn't work.

      The ./DimDim Status command says "DimDim Conference Server is Running (14317)."

      If anybody knows why I can't access it, that would be great.

      Thanks,

      Ben Fremer
      Ben@WebAndGraphicSolutions.com
      CEO
      Web & Graphic Solutions
      (888)-262-4696

       
      • dimdim_uday

        dimdim_uday - 2007-04-16

        Ben,
        Thank you for using Dimdim.
        Is it possible for you to provide access to your Linux server to me or Rajesh?
        Regards,
        Uday
        uday(at)dimdim.com

         
    • wags

      wags - 2007-04-14

      Here are my configuration files if anybody would care to take a look:

      dimdim.properties

      ##
      ##    WARNING: STRINGS IN THIS FILE ARE USED IN THE INSTALLER AND ELSE WHERE
      ##    AS THEY ARE. ANY CHANGE IN THIS FILE MIGHT REQUIRE CHANGE IN INSTALLER
      ##    AND OR TESTING CODE.
      ##
      ##    The server address and port number
      ##
      dimdim.serverAddress=64.150.166.154
      dimdim.serverPortNumber=8050
      ##
      ##    The webapp name
      ##
      dimdim.webappName=dimdim
      ##
      ##
      ##    This file provides many keys that govern the dimdim conference server
      ##    installation.
      ##
      ##    This is the storage root for storing presentations. The directory will
      ##    contain a directory for each conference, which in turn will contain
      ##    one directory for each presentation.
      ##
      dimdim.presentationStorageRoot=presentations
      ##
      ##    Authentication policy, valid values are: CHECK_EMAIL, CHECK_KEY, NO_CHECK
      ##
      dimdim.authenticationPolicy=NO_CHECK
      ##
      ##    Maximum number of concurrent conferences this server can support.
      ##
      dimdim.maxConcurrentConferences=50
      ##
      ##    Maximum number of total participants for all the concurrent conferences.
      ##
      dimdim.maxTotalParticipants=1000
      ##
      ##    Maximum number of participants, including presenter, for any single conference.
      ##
      dimdim.maxParticipantsPerConference=500
      ##
      ##    Maximum length in minutes, for any single conference.
      ##
      dimdim.maxMeetingLengthMinutes=300
      ##
      ##    This parameter controls the number of objects in a single event as well as
      ##    number of events that are sent to a client in a single poll.
      ##
      dimdim.maxObjectsInOneEvent=25
      ##
      ##    This parameter controls the maximum number of attendees who can be given
      ##    permission to broadcast audio. 0 means no attendee can be enabled to
      ##    transmit audio.
      ##
      dimdim.maxAttendeeAudios=3
      ##
      ##    This is the minimum required download bandwidth for a presenter
      ##
      dimdim.presenterDownloadBandwidthRequired=150
      ##
      ##    This is the minimum required download bandwidth for an attendee.
      ##
      dimdim.attendeeDownloadBandwidthRequired=100
      ##
      ##    This parameter controls if the newly joining attendees should be given the
      ##    mike, i.e. the permission to broadcast audio, if one is available at the
      ##    time. Default is false, meaning that the presenter must specifically assign
      ##    mikes to individual attendees.
      ##
      dimdim.assignMikeOnJoin=false
      ##
      ##    This parameter is the url the presenter and attendee consoles are sent to
      ##    at the end of the meeting. Value / would return the browser to the start
      ##    page of the dimdim server.
      ##
      dimdim.trackbackURL=http://www.dimdim.com
      ##
      ##    File cotainning the list of emails authorized to present conferences.
      ##
      dimdim.presenterEmailsFile=dimdimPresenters.txt
      ##
      ##    File cotainning the list of emails authorized to present conferences.
      ##
      dimdim.dimdimAdminsFile=dimdimAdmins.txt
      ##
      ##    File cotainning the scheduled conferences.
      ##
      dimdim.conferenceSpecsFile=dimdimConferenceSpecs.dmc
      ##
      ##    Key file for the check key authentication policy.
      ##
      dimdim.keyFile=dimdimKey.txt
      ##
      ##    Presenter - Attendee communication message engine threadpool size.
      ##
      dimdim.messageEngineThreadPoolSize=20
      ##
      ##    Email Parameters that can be configured by the user.
      ##
      email.server=mail.webandgraphicsolutions.com
      email.user=ben@webandgraphicsolutions.com
      email.password=//censored
      email.sender=ben@webandgraphicsolutions.com
      email.PORT=25
      email.EMAIL_CC=
      email.EMAIL_BCC=
      ##
      ##
      email.PROTOCOL=smtp
      email.DEBUG_MAIL_SESSION=false
      email.BUFFER_SIZE=2048
      email.EMAIL_SUBJECT = has invited you to a Dimdim web meeting.
      email.EMAIL_FROM_PERSON=DimDim Invitations
      email.EMAIL_FROM=invitations@dimdim.com
      email.EMAIL_REPLY_TO=invitations@dimdim.com
      email.EMAIL_TO=
      email.EMAIL_CHARSET=utf-8
      ##
      ##

      server.xml

      <!--  Example Server Configuration File
        -->
      - <!--
      Note that component elements are nested corresponding to their
           parent-child relationships with each other

        -->
      - <!--
      A "Server" is a singleton element that represents the entire JVM,
           which may contain one or more "Service" instances.  The Server
           listens for a shutdown command on the indicated port.

           Note:  A "Server" is not itself a "Container", so you may not
           define subcomponents such as "Valves" or "Loggers" at this level.

        -->
      - <Server port="8050" shutdown="SHUTDOWN">
      - <!--
      Comment these entries out to disable JMX MBeans support used for the
             administration web application

        -->
        <Listener className="org.apache.catalina.core.AprLifecycleListener" />
        <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
        <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
        <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener" />
      - <!--  Global JNDI resources
        -->
      - <GlobalNamingResources>
      - <!--  Test entry for demonstration purposes
        -->
        <Environment name="simpleValue" type="java.lang.Integer" value="30" />
      - <!--
      Editable user database that can also be used by
               UserDatabaseRealm to authenticate users

        -->
        <Resource name="UserDatabase" auth="Container" type="org.apache.catalina.UserDatabase" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="conf/tomcat-users.xml" />
        </GlobalNamingResources>
      - <!--
      A "Service" is a collection of one or more "Connectors" that share
             a single "Container" (and therefore the web applications visible
             within that Container).  Normally, that Container is an "Engine",
             but this is not required.

             Note:  A "Service" is not itself a "Container", so you may not
             define subcomponents such as "Valves" or "Loggers" at this level.
        

        -->
      - <!--  Define the Tomcat Stand-Alone Service
        -->
      - <Service name="Catalina">
      - <!--
      A "Connector" represents an endpoint by which requests are received
               and responses are returned.  Each Connector passes requests on to the
               associated "Container" (normally an Engine) for processing.

               By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
               You can also enable an SSL HTTP/1.1 Connector on port 8443 by
               following the instructions below and uncommenting the second Connector
               entry.  SSL support requires the following steps (see the SSL Config
               HOWTO in the Tomcat 5 documentation bundle for more detailed
               instructions):
               * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
                 later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
               * Execute:
                   %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
                   $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
                 with a password value of "changeit" for both the certificate and
                 the keystore itself.

               By default, DNS lookups are enabled when a web application calls
               request.getRemoteHost().  This can have an adverse impact on
               performance, so you can disable it by setting the
               "enableLookups" attribute to "false".  When DNS lookups are disabled,
               request.getRemoteHost() will return the String version of the
               IP address of the remote client.
         

        -->
      - <!--  Define a non-SSL HTTP/1.1 Connector on port 8080
        -->
        <Connector port="8050" maxHttpHeaderSize="8192" maxThreads="1500" minSpareThreads="250" maxSpareThreads="750" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
      - <!--
      Note : To disable connection timeouts, set connectionTimeout value
           to 0

        -->
      - <!--
      Note : To use gzip compression you could set the following properties :
         
                     compression="on"
                     compressionMinSize="2048"
                     noCompressionUserAgents="gozilla, traviata"
                     compressableMimeType="text/html,text/xml"
         

        -->
      - <!--  Define a SSL HTTP/1.1 Connector on port 8443
        -->
      - <!--
          <Connector port="8443" maxHttpHeaderSize="8192"
                     maxThreads="1500" minSpareThreads="250" maxSpareThreads="750"
                     enableLookups="false" disableUploadTimeout="true"
                     acceptCount="100" scheme="https" secure="true"
                     clientAuth="false" sslProtocol="TLS" />
         

        -->
      - <!--  Define an AJP 1.3 Connector on port 8009
        -->
        <Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
      - <!--  Define a Proxied HTTP/1.1 Connector on port 8082
        -->
      - <!--  See proxy documentation for more information about using this.
        -->
      - <!--
          <Connector port="8082"
                     maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                     enableLookups="false" acceptCount="100" connectionTimeout="20000"
                     proxyPort="80" disableUploadTimeout="true" />
         

        -->
      - <!--
      An Engine represents the entry point (within Catalina) that processes
               every request.  The Engine implementation for Tomcat stand alone
               analyzes the HTTP headers included with the request, and passes them
               on to the appropriate Host (virtual host).

        -->
      - <!--
      You should set jvmRoute to support load-balancing via AJP ie :
          <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">        
         

        -->
      - <!--  Define the top level container in our container hierarchy
        -->
      - <Engine name="Catalina" defaultHost="localhost">
      - <!--
      The request dumper valve dumps useful debugging information about
                 the request headers and cookies that were received, and the response
                 headers and cookies that were sent, for all requests received by
                 this instance of Tomcat.  If you care only about requests to a
                 particular virtual host, or a particular application, nest this
                 element inside the corresponding <Host> or <Context> entry instead.

                 For a similar mechanism that is portable to all Servlet 2.4
                 containers, check out the "RequestDumperFilter" Filter in the
                 example application (the source for this filter may be found in
                 "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

                 Request dumping is disabled by default.  Uncomment the following
                 element to enable it.

        -->
      - <!--
            <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
           

        -->
      - <!--  Because this Realm is here, an instance will be shared globally
        -->
      - <!--
      This Realm uses the UserDatabase configured in the global JNDI
                 resources under the key "UserDatabase".  Any edits
                 that are performed against this UserDatabase are immediately
                 available for use by the Realm. 

        -->
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase" />
      - <!--
      Comment out the old realm but leave here for now in case we
                 need to go back quickly

        -->
      - <!--
            <Realm className="org.apache.catalina.realm.MemoryRealm" />
           

        -->
      - <!--
      Replace the above Realm with one of the following to get a Realm
                 stored in a database and accessed via JDBC

        -->
      - <!--
            <Realm  className="org.apache.catalina.realm.JDBCRealm"
                   driverName="org.gjt.mm.mysql.Driver"
                connectionURL="jdbc:mysql://localhost/authority"
               connectionName="test" connectionPassword="test"
                    userTable="users" userNameCol="user_name" userCredCol="user_pass"
                userRoleTable="user_roles" roleNameCol="role_name" />
           

        -->
      - <!--
            <Realm  className="org.apache.catalina.realm.JDBCRealm"
                   driverName="oracle.jdbc.driver.OracleDriver"
                connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
               connectionName="scott" connectionPassword="tiger"
                    userTable="users" userNameCol="user_name" userCredCol="user_pass"
                userRoleTable="user_roles" roleNameCol="role_name" />
           

        -->
      - <!--
            <Realm  className="org.apache.catalina.realm.JDBCRealm"
                   driverName="sun.jdbc.odbc.JdbcOdbcDriver"
                connectionURL="jdbc:odbc:CATALINA"
                    userTable="users" userNameCol="user_name" userCredCol="user_pass"
                userRoleTable="user_roles" roleNameCol="role_name" />
           

        -->
      - <!--
      Define the default virtual host
                 Note: XML Schema validation will not work with Xerces 2.2.
            

        -->
      - <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false">
      - <!--
      Defines a cluster for this node,
                   By defining this element, means that every manager will be changed.
                   So when running a cluster, only make sure that you have webapps in there
                   that need to be clustered and remove the other ones.
                   A cluster has the following parameters:

                   className = the fully qualified name of the cluster class

                   clusterName = a descriptive name for your cluster, can be anything

                   mcastAddr = the multicast address, has to be the same for all the nodes

                   mcastPort = the multicast port, has to be the same for all the nodes
                  
                   mcastBindAddress = bind the multicast socket to a specific address
                  
                   mcastTTL = the multicast TTL if you want to limit your broadcast
                  
                   mcastSoTimeout = the multicast readtimeout

                   mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

                   mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

                   tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes

                   tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
                                      in case of multiple ethernet cards.
                                      auto means that address becomes
                                      InetAddress.getLocalHost().getHostAddress()

                   tcpListenPort = the tcp listen port

                   tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
                                        has a wakup bug in java.nio. Set to 0 for no timeout

                   printToScreen = true means that managers will also print to std.out

                   expireSessionsOnShutdown = true means that

                   useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
                                  false means to replicate the session after each request.
                                  false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
                                  <%
                                  HashMap map = (HashMap)session.getAttribute("map");
                                  map.put("key","value");
                                  %>
                   replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
                                     * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
                                     * Synchronous means that the thread that executes the request, is also the
                                     thread the replicates the data to the other nodes, and will not return until all
                                     nodes have received the information.
                                     * Asynchronous means that there is a specific 'sender' thread for each cluster node,
                                     so the request thread will queue the replication request into a "smart" queue,
                                     and then return to the client.
                                     The "smart" queue is a queue where when a session is added to the queue, and the same session
                                     already exists in the queue from a previous request, that session will be replaced
                                     in the queue instead of replicating two requests. This almost never happens, unless there is a
                                     large network delay.
             

        -->
      - <!--
                  When configuring for clustering, you also add in a valve to catch all the requests
                  coming in, at the end of the request, the session may or may not be replicated.
                  A session is replicated if and only if all the conditions are met:
                  1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
                  2. a session exists (has been created)
                  3. the request is not trapped by the "filter" attribute

                  The filter attribute is to filter out requests that could not modify the session,
                  hence we don't replicate the session after the end of this request.
                  The filter is negative, ie, anything you put in the filter, you mean to filter out,
                  ie, no replication will be done on requests that match one of the filters.
                  The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

                  filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
                  ending with .gif and .js are intercepted.
                 
                  The deployer element can be used to deploy apps cluster wide.
                  Currently the deployment only deploys/undeploys to working members in the cluster
                  so no WARs are copied upons startup of a broken node.
                  The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
                  When a new war file is added the war gets deployed to the local instance,
                  and then deployed to the other instances in the cluster.
                  When a war file is deleted from the watchDir the war is undeployed locally
                  and cluster wide
             

        -->
      - <!--
              <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
                       managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                       expireSessionsOnShutdown="false"
                       useDirtyFlag="true"
                       notifyListenersOnReplication="true">

                  <Membership
                      className="org.apache.catalina.cluster.mcast.McastService"
                      mcastAddr="228.0.0.4"
                      mcastPort="45564"
                      mcastFrequency="500"
                      mcastDropTime="3000"/>

                  <Receiver
                      className="org.apache.catalina.cluster.tcp.ReplicationListener"
                      tcpListenAddress="auto"
                      tcpListenPort="4001"
                      tcpSelectorTimeout="100"
                      tcpThreadCount="6"/>

                  <Sender
                      className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                      replicationMode="pooled"
                      ackTimeout="15000"
                      waitForAck="true"/>

                  <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
                         filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
                        
                  <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                            tempDir="/tmp/war-temp/"
                            deployDir="/tmp/war-deploy/"
                            watchDir="/tmp/war-listen/"
                            watchEnabled="false"/>
                           
                  <ClusterListener className="org.apache.catalina.cluster.session.ClusterSessionListener"/>
              </Cluster>
             

        -->
      - <!--
      Normally, users must authenticate themselves to each web app
                   individually.  Uncomment the following entry if you would like
                   a user to be authenticated the first time they encounter a
                   resource protected by a security constraint, and then have that
                   user identity maintained across *all* web applications contained
                   in this virtual host.

        -->
      - <!--
              <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
             

        -->
      - <!--
      Access log processes all requests for this virtual host.  By
                   default, log files are created in the "logs" directory relative to
                   $CATALINA_HOME.  If you wish, you can specify a different
                   directory with the "directory" attribute.  Specify either a relative
                   (to $CATALINA_HOME) or absolute path to the desired directory.
             

        -->
      - <!--
              <Valve className="org.apache.catalina.valves.AccessLogValve"
                       directory="logs"  prefix="localhost_access_log." suffix=".txt"
                       pattern="common" resolveHosts="false"/>
             

        -->
      - <!--
      Access log processes all requests for this virtual host.  By
                   default, log files are created in the "logs" directory relative to
                   $CATALINA_HOME.  If you wish, you can specify a different
                   directory with the "directory" attribute.  Specify either a relative
                   (to $CATALINA_HOME) or absolute path to the desired directory.
                   This access log implementation is optimized for maximum performance,
                   but is hardcoded to support only the "common" and "combined" patterns.
             

        -->
      - <!--
              <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
                       directory="logs"  prefix="localhost_access_log." suffix=".txt"
                       pattern="common" resolveHosts="false"/>
             

        -->
        </Host>
        </Engine>
        </Service>
        </Server>

      wrapper.conf

      #********************************************************************
      # Wrapper Properties
      #********************************************************************
      # Java Application
      wrapper.java.command=/usr/java/jre1.6.0/bin/java

      # Java Main class.  This class must implement the WrapperListener interface
      #  or guarantee that the WrapperManager class is initialized.  Helper
      #  classes are provided to do this for you.  See the Integration section
      #  of the documentation for details.
      wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp

      # Java Classpath (include wrapper.jar)  Add class path elements as
      #  needed starting from 1
      wrapper.java.classpath.1=../common/lib/wrapper.jar
      wrapper.java.classpath.2=../bin/bootstrap.jar
      wrapper.java.classpath.3=../bin/tomcat-juli.jar
      wrapper.java.classpath.4=../common/lib/wrappertest.jar

      # Java Library Path (location of Wrapper.DLL or libwrapper.so)
      wrapper.java.library.path.1=../common/lib

      # Java Additional Parameters

      wrapper.java.additional.1=-Dcatalina.home=..
      wrapper.java.additional.2=-Dcatalina.base=..
      wrapper.java.additional.3=-Djava.endorsed.dirs=../common/endorsed
      wrapper.java.additional.4=-Djava.io.tmpdir=../temp
      wrapper.java.additional.5=-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
      wrapper.java.additional.6=-Djava.util.logging.config.file=logging.properties

      # Initial Java Heap Size (in MB)
      wrapper.java.initmemory=256

      # Maximum Java Heap Size (in MB)
      wrapper.java.maxmemory=1024

      # Application parameters.  Add parameters as needed starting from 1
      wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
      wrapper.app.parameter.2=1
      wrapper.app.parameter.3=start
      wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
      wrapper.app.parameter.5=true
      wrapper.app.parameter.6=1
      wrapper.app.parameter.7=stop

      #********************************************************************
      # Wrapper Logging Properties
      #********************************************************************
      # Format of output for the console.  (See docs for formats)
      wrapper.console.format=PM

      # Log Level for console output.  (See docs for log levels)
      wrapper.console.loglevel=INFO

      # Log file to use for wrapper output logging.
      wrapper.logfile=../logs/wrapper.log

      # Format of output for the log file.  (See docs for formats)
      wrapper.logfile.format=LPTM

      # Log Level for log file output.  (See docs for log levels)
      wrapper.logfile.loglevel=INFO

      # Maximum size that the log file will be allowed to grow to before
      #  the log is rolled. Size is specified in bytes.  The default value
      #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
      #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
      wrapper.logfile.maxsize=0

      # Maximum number of rolled log files which will be allowed before old
      #  files are deleted.  The default value of 0 implies no limit.
      wrapper.logfile.maxfiles=0

      # Log Level for sys/event log output.  (See docs for log levels)
      wrapper.syslog.loglevel=NONE

      #********************************************************************
      # Wrapper Windows Properties
      #********************************************************************
      # Title to use when running as a console
      wrapper.console.title= Dimdim Conference Server

      #********************************************************************
      # Wrapper Windows NT/2000/XP Service Properties
      #********************************************************************
      # WARNING - Do not modify any of these properties when an application
      #  using this configuration file has been installed as a service.
      #  Please uninstall the service before modifying this section.  The
      #  service can then be reinstalled.

      # Name of the service
      wrapper.ntservice.name=testwrapper

      # Display name of the service
      wrapper.ntservice.displayname=Test Wrapper Sample Application

      # Description of the service
      wrapper.ntservice.description=Test Wrapper Sample Application Description

      # Service dependencies.  Add dependencies as needed starting from 1
      wrapper.ntservice.dependency.1=

      # Mode in which the service is installed.  AUTO_START or DEMAND_START
      wrapper.ntservice.starttype=AUTO_START

      # Allow the service to interact with the desktop.
      wrapper.ntservice.interactive=false

      Thanks!

      Ben Fremer 
      Ben@WebAndGraphicSolutions.com 
      CEO 
      Web & Graphic Solutions 
      (888)-262-4696 

       
      • BuckJE

        BuckJE - 2007-05-02

        in your server.xml file you have:

        <Server port="8050" shutdown="SHUTDOWN">

        and in dimdim.prop you have

        dimdim.serverPortNumber=8050

        I do belive this is in confilct, as they are refferring differnet services but you have them on the same port.

        try setting this:

        dimdim.serverPortNumber=8090

        and this in server.xml

        <Connector port="8090" maxHttpHeaderSize="8192" maxThreads="1500" minSpareThreads="250" maxSpareThreads="750" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" /> 

        and leave the
        <Server port="8050" shutdown="SHUTDOWN"> 
        line alone

        start the server..

        then in your browser: 

        www.yourIP.com:8090

         
    • Rajesh Dharmalingam

      Hi Ben,

      Thanks for using Dimdim. Could you please mail me the wrapper.log to rajesh(@)dimdim.com. The configuration looks correct. So, if i could get the wrapper.log, i can update you more on this.

      Regards,
      -Rajesh

       
    • Rajesh Dharmalingam

      Hi Ben,

      I received the wrapper.log from you. From the log, i see that you are using VM ware and the RAM memory is not enough to start the JVM. Could you please increase the RAM memory for the VM and try starting the Dimdim server.

      Please do let me know the updates after the RAM memory of VM ware is increased. If still you face with problems, please do send us the new wrapper.log.

      Regards,
      -Rajesh

       
    • wags

      wags - 2007-04-16

      Where would somebody go about increasing the RAM available to run the JVM? Do I need to call the company hosting it ( Startlogic )?

      Also, how much RAM is needed per instance of each DimDim meeting that is running?

      Thanks,

      Ben

       
    • Rajesh Dharmalingam

      Hi,

      Thanks for the updates. Yes. Could you please check with the hosting company how much RAM is provided for your machine. The minimum requirement for Dimdim regarding RAM is 512MB.

      Once the RAM memory is increase, then try starting the dimdim. If you are still facing problems, please do let us know.

      If you could provide access to your machine, please do send me the access credentials to rajesh(@)dimdim.com

      Regards,
      -Rajesh

       
    • dimdim_uday

      dimdim_uday - 2007-04-17

      Hello Ben,
      You can also try tweaking the Memory allocation from the wrapper.conf.
      Please change the following lines in the wrapper.conf :-

      =====================================
      # Initial Java Heap Size (in MB)
      wrapper.java.initmemory=256

      # Maximum Java Heap Size (in MB)
      wrapper.java.maxmemory=1024
      =====================================
      to read
      =====================================
      # Initial Java Heap Size (in MB)
      wrapper.java.initmemory=128

      # Maximum Java Heap Size (in MB)
      wrapper.java.maxmemory=256
      =====================================
      which will cap the JVM size to a maximum of 256 MB.

      Regards,
      Uday

       
    • wags

      wags - 2007-04-20

      Hi Guys--

      I tried changing the wrapper.conf , and that didn't work.

      Here is access to my server:

      (emailed)

      I was told that the hosting has 1 GB of RAM on it.

      Thanks,

      Ben.

       
    • wags

      wags - 2007-04-23

      It appears to me that the VM can't get enough memory due to it being on VPS -- must I upgrade to a Dedicated server?

      Thanks.

       
      • dimdim_uday

        dimdim_uday - 2007-04-23

        Ben,
        In the past our user community has reported similar cases where they were unable to get the required memory due to VPS. Please go ahead and upgrade to a dedicated server, this should solve the memory problem.

        Regards,
        Uday

         
    • Rajesh Dharmalingam

      Hi Ben,

      Any updates on the issue which you were facing?

      Regards,
      -Rajesh

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks