Rajesh Chandrakar | 3 Sep 09:30 2004
Picon

[Fedora-users] Servlet Engine and ConnectionPoolNotFoundException!

Dear Professionals,
 
This is Rajesh Chandrakar from India. I am a new user of this group. I started working on fedora after reading the information about it. I read the complete installation procedure given in the website. Accordingly I did the installation procedure in my computer. After doing the procedure step-by-step, system gives some error message when I run the fedora server as follows:
 
 C:\>fedora-start mckoi

Starting Fedora server...

Deploying API-M and API-A...

Starting service Fedora-Server

Apache Tomcat/4.1.0-LE-jdk14

- Processing file c:\fedora-1.2\server\config\deployAPI-A.wsdd

- Problem with servlet engine config file: C:\fedora-1.2\server\tomcat41\webapps

\fedora\/WEB-INF/server-config.wsdd

- <Admin>Done processing</Admin>

- Processing file c:\fedora-1.2\server\config\deploy.wsdd

- <Admin>Done processing</Admin>

Initializing Fedora Server instance...

Got controller 'startup' request from 127.0.0.1

Fedora Version 1.2

Server Host Name: 192.168.1.15

Server Port: 8080

Error starting Fedora server: fedora.server.errors.ModuleInitializationException

: The default connection pool "localMcKoiPool" could not be found. The underlyin

g error was a fedora.server.errors.ConnectionPoolNotFoundExceptionThe message wa

s "Default connection pool not found: localMcKoiPool".

ERROR

Finished.  To stop the server, use fedora-stop.

C:\>
 
 
Please help me where I am doing wrong. It seems to me there are two errors:
 
1) Problem with servlet engine config file: C:\fedora-1.2\server\tomcat41\webapps

\fedora\/WEB-INF/server-config.wsdd

2) Error starting Fedora server: fedora.server.errors.ModuleInitializationException

: The default connection pool "localMcKoiPool" could not be found. The underlyin

g error was a fedora.server.errors.ConnectionPoolNotFoundExceptionThe message wa

s "Default connection pool not found: localMcKoiPool".

thanks in advance. waiting for reply.

with regards,

Rajesh Chandrakar

Scientific & Technical Officer

INFLIBNET Centre, Ahmedabad

Gujarat, India

http://www.inflibnet.ac.in

 

 

 

Ronda A. Grizzle | 3 Sep 15:12 2004

Re: [Fedora-users] Servlet Engine and ConnectionPoolNotFoundException!

Hello Mr. Chandrakar,

Welcome to the fedora users list!

The first error you're seeing (Problem with servlet engine config file: 
C:\fedora-1.2\server\tomcat41\webapps) is caused by a bug in tomcat and 
can safely be ignored.

The second error (fedora.server.errors.ConnectionPoolNotFoundException) is 
caused by Fedora not being able to communicate with the McKoi database.

Some possible reasons for this:
1. You have not run mckoi-init.bat to initialize the mckoi database.
2. The username and password you used when initializing the mckoi database 
do not match the username and password in your fedora.fcfg file. Please 
check this section of your fedora.fcfg to verify:

	<datastore id="localMcKoiPool">
		<comment>McKoi database on localhost running on port 9158</comment>
		<param name="dbUsername" value="fedoraAdmin"/>
		<param name="dbPassword" value="fedoraAdmin"/>
		<param name="jdbcURL" value="jdbc:mckoi://localhost:9158/"/>
		<param name="jdbcDriverClass" value="com.mckoi.JDBCDriver"/>
		<param name="ddlConverter" 
value="fedora.server.utilities.McKoiDDLConverter"/>
		<param name="minPoolSize" value="10"/>
		<param name="maxPoolSize" value="100"/>

The dbUsername and dbPassword values in your config file must match the 
dbUsername and dbPassword you used in setting up your Mckoi db.

If this does not solve your problem, please do let us know.

Best regards,
Ronda
 --
Ronda A. Grizzle
Technical Coordinator, Fedora Project
Digital Library Research & Development
(voice)434-924-3965
(fax)434-924-1431

--On Friday, 03 September, 2004 1:00 PM +0530 Rajesh Chandrakar 
<rajesh@...> wrote:

>
> Dear Professionals,
>
> This is Rajesh Chandrakar from India. I am a new user of this group. I
> started working on fedora after reading the information about it. I read
> the complete installation procedure given in the website. Accordingly I
> did the installation procedure in my computer. After doing the procedure
> step-by-step, system gives some error message when I run the fedora
> server as follows:
>
>  C:\>fedora-start mckoi
>
> Starting Fedora server...
>
> Deploying API-M and API-A...
>
> Starting service Fedora-Server
>
> Apache Tomcat/4.1.0-LE-jdk14
>
> - Processing file c:\fedora-1.2\server\config\deployAPI-A.wsdd
>
> - Problem with servlet engine config file:
> C:\fedora-1.2\server\tomcat41\webapps
>
> \fedora\/WEB-INF/server-config.wsdd
>
> - <Admin>Done processing</Admin>
>
> - Processing file c:\fedora-1.2\server\config\deploy.wsdd
>
> - <Admin>Done processing</Admin>
>
> Initializing Fedora Server instance...
>
> Got controller 'startup' request from 127.0.0.1
>
> Fedora Version 1.2
>
> Server Host Name: 192.168.1.15
>
> Server Port: 8080
>
> Error starting Fedora server:
> fedora.server.errors.ModuleInitializationException
>
> : The default connection pool "localMcKoiPool" could not be found. The
> underlyin
>
> g error was a fedora.server.errors.ConnectionPoolNotFoundExceptionThe
> message wa
>
> s "Default connection pool not found: localMcKoiPool".
>
> ERROR
>
> Finished.  To stop the server, use fedora-stop.
> C:\>
>
>
> Please help me where I am doing wrong. It seems to me there are two
> errors:
>
> 1) Problem with servlet engine config file:
> C:\fedora-1.2\server\tomcat41\webapps
>
> \fedora\/WEB-INF/server-config.wsdd
>
> 2) Error starting Fedora server:
> fedora.server.errors.ModuleInitializationException
>
> : The default connection pool "localMcKoiPool" could not be found. The
> underlyin
>
> g error was a fedora.server.errors.ConnectionPoolNotFoundExceptionThe
> message wa
>
> s "Default connection pool not found: localMcKoiPool".
>
> thanks in advance. waiting for reply.
>
> with regards,
>
> Rajesh Chandrakar
>
> Scientific & Technical Officer
>
> INFLIBNET Centre, Ahmedabad
>
> Gujarat, India
>
> http://www.inflibnet.ac.in
>
>
>
>
>
>

Rajesh Chandrakar | 4 Sep 09:07 2004
Picon

[Fedora-users] Servlet Engine and ConnectionPoolNotFoundException

Dear Mr. Ronda,
 
I deleted the complete installation of fedora server, client and src development. And reinstalled the fedora. As per the instrunction, I did ant serverdist process from c:\fedora-1.2-src directory (FEDORA_DEV directory). Then I initialised the McKoi databsae from C:\ directory by following command:
 
mckoi-init fedoraAdmin fedoraAdmin
 
got message DBInstalled and finished.
 
Now I modified the fedora.fcfg, you may please look at it as follows
<?xml version="1.0" encoding="UTF-8"?>
<server xmlns="http://www.fedora.info/definitions/1/0/config/" xmlns:fedora-config="http://www.fedora.info/definitions/1/0/config/" class="fedora.server.BasicServer">
 <param name="repositoryName" value="Fedora Repository 1"/>
 <comment>Defines a human readable name for the Fedora server; default is Fedora Repository.</comment>
 <param name="adminEmailList" value="rajesh <at> inflibnet.ac.in"/>
 <comment>Defines one or more email addresses for server administrators; list is space delimited.</comment>
 <param name="adminPassword" value="fedoraAdmin"/>
 <comment>Defines the password for the Fedora server; default is fedoraAdmin.</comment>
 <param name="log_max_size" value="5242880"/>
 <comment>Defines the threshold at which a new log file is generated based on the size of the current log file in bytes; default is 5242880 bytes.</comment>
 <param name="log_max_days" value="7"/>
 <comment>Defines the threshold at which a new log file is generated based on number of days since the server was started in days; default is 7 days.</comment>
 <param name="log_dir" value="logs"/>
 <comment>Defines the directory in which the Fedora logs will be written; default is logs.</comment>
 <param name="log_level" value="finest"/>
 <comment>Defines the level of logging desired;default is finest; possible levels include:
  - config
   denotes logging indicating what occurred during the server's (or a module's) configuration phase.
  - fine
   denotes logging indicating basic information about a request to the server (like hostname, operation name, and success or failure). 
  - finer
   denotes logging indicating detailed information about a request to the server (like the full request, full response, and timing information).
  - finest (deafult)
   denotes logging indicating method entry/exit or extremely verbose information intended to aid in debugging.
  - info
   denotes logging indicating that something relatively uncommon and interesting happened, like server or module startup or shutdown, or a periodic job.
  - warning
   denotes logging indicating that an undesired (but non-fatal) condition occured.
  - severe
   denotes logging indicating that the server is inoperable or unable to start.
 </comment>
 <param name="log_flush_threshold" value="1"/>
 <comment>Defines the flush threshold for logging in number of records; default is one log record.</comment>
 <param name="path_algorithm" value="fedora.server.storage.lowlevel.TimestampPathAlgorithm"/>
 <comment>Defines the java class used to determine the path algorithm for LowLevelStorage;
  default is fedora.server.storage.lowlevel.TimestampPathAlgorithm.
 </comment>
 <param name="file_system" value="fedora.server.storage.lowlevel.GenericFileSystem"/>
 <comment>Defines the java class that determines the type of implementation for LowLevelStorage;
  default is fedora.server.storage.lowlevel.GenericFileSystem.
 </comment>
 <param name="registry" value="fedora.server.storage.lowlevel.DBPathRegistry"/>
 <comment>Defines the java class used to determine the path registry for LowLevelStorage;
  default is fedora.server.storage.lowlevel.DBPathRegistry.
 </comment>
 <param name="backslash_is_escape" value="yes" oraclevalue="no"/>
 <comment>Defines whether the backing database (which include registry tables) the backslash character
  to be the escape character (token beginning an escape sequence).  This is needed to correctly
  store and retrieve filepaths from the registry tables, if running under Windows/DOS.
 </comment>
 <param name="object_store_base" value="C:\fedora1_2_objects"/>
 <comment>Defines the root directory for the internal storage of Fedora objects.
  This value should be adjusted based on your installation environment;
  default assumes a Windows installation of C:\fedora1_2_objects.
 </comment>
 <param name="temp_store_base" value="C:\fedora1_2_temp"/>
 <comment>Defines the root directory for Fedora temporary storage.
  This value should be adjusted based on your installation environment;
  default assumes a Windows installation of C:\fedora1_2_temp.
 </comment>
 <param name="datastream_store_base" value="C:\fedora1_2_datastreams"/>
 <comment>Defines the root directory for the internal storage of Managed Content datastreams.
  This value should be adjusted based on your installation environment;
  default assumes a Windows installation of C:\fedora1_2_datastreams.
 </comment>
 <param name="debug" value="false"/>
 <comment>A boolean toggle used to turn off/on internal debugging in the code.</comment>
 <param name="datastreamExpirationLimit" value="300"/>
 <comment>
  Controls the size of the datastream mediation hash by removing entries outside the specified threshold.
  The value is specified in seconds.
  Note this value must be greater than the limit specified for the datastreamMediationLimit.
 </comment>
 <param name="datastreamMediationLimit" value="5000"/>
 <comment>
  Determines the time interval in which external mechanisms must respond to requests by the Fedora server.
   The value is specified in milliseconds. 
  The value specified should be set high enough to allow for an average response time from any single external mechanisms.
  Note this value must be less than the limit specified for the datastreamExpirationLimit.
 </comment>
 <param name="fedoraServerPort" value="8080"/>
 <comment>Defines the port number on which the Fedora server runs; default is 8080.</comment>
 <param name="fedoraShutdownPort" value="8005"/>
 <comment>Defines the port number used to shutdown the Fedora sever; default is 8005.</comment>
 <param name="fedoraRedirectPort" value="8443"/>
 <comment>Defines the redirect port of the Fedora sever; default is 8443.</comment>
 <param name="fedoraServerHost" value="192.168.1.15"/>
 <comment>Defines the host name for the Fedora server, as seen from the outside world.</comment>
 <module role="fedora.server.storage.DOManager" class="fedora.server.storage.DefaultDOManager">
  <comment>
        Description:
          The interface to the storage subsystem.  This provides
          context-appropriate DOReaders and DOWriters for reflecting on and
          writing to the objects stored in the repository.  It also
          provides methods for reflecting on the contents of the repository
          as a whole.  This implementation uses DefinitiveDOReader/Writer
          for an "application" of "apim" and a FastDOReader/Writer
          for an "application" of "apia" (from the Context).  Other
          context-specific logic TBD.
        Parameters:
        - pidNamespace (required)
          This is the namespace id for pids of newly-created objects.
          This should be unique for a repository.
          It can be from 1 to 17 characters, and may only contain
          A-Z, a-z, 0-9, and '-' (dash).
        - retainPIDs [default="demo test"]
          Namespaces of PIDs to retain during the ingest process.
          When an object is ingested, Fedora normally allocates a unique PID
          within pidNamespace for it regardless of what the object says its
          PID is.  This option provides a way to override that behavior on
          a per-pid-namespace basis.  If specified, this should be a
          space-delimited list of pid namespaces that will be accepted in the
          object as-is.
        - storagePool [default=default provided by the ConnectionPoolManager]
          The named connection pool from which read/write
          database connections are to be provided for the storage
          subsystem (see the ConnectionPoolManager module)
        - storageFormat (required)
          The format in which internal serializations of digital objects
          are to be written.  There must exist a correspondingly
          named serializer-deserializer pair in the DOTranslator module.
        - storageCharacterEncoding [default=UTF-8]
          If the serialization format is text-based,
          this is the character encoding that should be used.</comment>
        - exportFormat (required)
          The format in which external serializations of digital objects
          are to be written.  There must exist a correspondingly
          named serializer-deserializer pair in the DOTranslator module.
  <param name="pidNamespace" value="111"/>
  <param name="retainPIDs" value="demo test changeme"/>
  <param name="storagePool" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
  <param name="storageFormat" value="metslikefedora1"/>
  <param name="exportFormat" value="metslikefedora1export"/>
  <param name="storageCharacterEncoding" value="UTF-8"/>
 </module>
 <module role="fedora.server.management.Management" class="fedora.server.management.DefaultManagement">
  <comment>
        Description:
          The management subsystem.
          This implements the methods necessary to fulfill API-M
          requests without regard to:
            - how the service is exposed
            - how bytestreams and java types might be marshalled/demarshalled
              over the wire
            - how the storage subsystem is implemented.
        Parameters:
            - allowHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must match for any Management request to be accepted.
              If this is not specified, all requests will be accepted unless
              the remote address matches a deny pattern.
            - denyHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must not match for any Management request to be accepted.
              If this is not specified, request acceptance is governed
              solely by the allowHosts parameter.
        </comment>
  <param name="allowHosts" value="192.168.1.1-192.168.1.255"/>
 </module>
 <module role="fedora.server.access.Access" class="fedora.server.access.DefaultAccess">
  <comment>
        Description:
          The access subsystem.
          This implements the methods necessary to fulfill API-A
          requests without regard to:
            - how the service is exposed
            - how bytestreams and java types might be marshalled/demarshalled
              over the wire
            - how the storage subsystem is implemented.
        Parameters:
            - allowHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must match for any Management request to be accepted.
              If this is not specified, all requests will be accepted unless
              the remote address matches a deny pattern.
            - denyHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must not match for any Management request to be accepted.
              If this is not specified, request acceptance is governed
              solely by the allowHosts parameter.
            - doMediateDatastreams (required)
              A boolean switch indicating whether Datastream Mediation is activated or not.
              Datastream Mediation provides additional repository security by not exposing
              the actual physical location of Referenced Content datastreams to external
              mechanisms(services). Instead of exposing the actual physical location of
              Referenced Content datastreams , Datastream Mediation functions as a proxy
              requiring all external services to communicate through the Fedora server to
              resolve the location of Referenced Content datastreams. For Datastream
              Mediation to function, the Fedora server must be internet accessible on its
              designated port by any potential external service. This requirement can be
              difficult to satisfy if the Fedora server is located behind a firewall and
              you do not have ready access to the firewall's configuration to enable the
              required access. If the Fedora server is behind a firewall and you have no
              access to the firewall's configuration, you can disable Datastream Mediation
              which will allow external services to access Referenced Content datastreams
              using their actual physical locations. Managed Content and XMLMetadata
              datastreams are stored internally in the Fedora repository and can only be
              accessed through the Fedora server so disabling Datastream Mediation has no
              effect on these types of datastreams. Disabling Datastream Mediation exposes
              the physical location of Referenced Content datastream to external services
              which can result in unintended access to the raw datastreams by surreptitious
              external mechanisms. It is recommended that Datastream Mediation be disabled
              only for testing or cases where this security issue is not a concern. The
              default value of doMediateDatastreams is true.
            </comment>
  <param name="doMediateDatastreams" value="false"/>
 </module>
 <module role="fedora.server.access.DynamicAccess" class="fedora.server.access.DynamicAccessModule">
  <comment>
        Description:
          The dynamic behavior module for the access subsystem.
          This implements the methods necessary to fulfill API-A
          requests without regard to:
             - dynamically associating a default behavior definition and mechanism with objects
           - (Future) dynamically associating other behavior definitions and mechanisms with objects
           - running disseminations of dynamic behaviors
        Parameters:
            - fedora-system:1
              The interface that defines the methods of the bootstrap
              disseminator.  These methods are "built-in" to the Fedora
              system, and are dynamically associated with every
              behavior definition and behavior mechanism object.
            - fedora-system:2
              The class that implements the methods of the bootstrap
              disseminator.  These method implementations are "built-in"
              to the Fedora system, and are dynamically associated with
              every behavior definition and behavior mechanism object. 
              This class can be though of as implementing
              an "internal service" whereas other disseminators use
              external services (described by WSDL) to do their work.
            - fedora-system:3
              The interface that defines the methods of the default
              disseminator.  These methods are "built-in" to the Fedora
              system, and are dynamically associated with every object.
            - fedora-system:4
              The class that implements the methods of the default
              disseminator.  These method implementations are "built-in"
              to the Fedora system, and are dynamically associated with
              every object.  This class can be though of as implementing
              an "internal service" whereas other disseminators use
              external services (described by WSDL) to do their work.
            </comment>
  <param name="fedora-system:1" value="fedora.server.access.internalservices.Bootstrap"/>
  <param name="fedora-system:2" value="fedora.server.access.internalservices.BootstrapImpl"/>
  <param name="fedora-system:3" value="fedora.server.access.internalservices.DefaultBehavior"/>
  <param name="fedora-system:4" value="fedora.server.access.internalservices.DefaultBehaviorImpl"/>
 </module>
 <module role="fedora.server.search.FieldSearch" class="fedora.server.search.FieldSearchSQLModule">
  <comment>
        Description:
          Supports the API-A simpleSearch and advancedSearch methods.
        Parameters:
          - maxResults (required, must be > 0)
            The maximum number of records to return as the result of a search.
            Even if a client requests more results at a time, this is the
            cutoff value.
          - maxSecondsPerSession (required, must be > 0)
            The maximum number of seconds that the server guarantees subsequent
            search results may be obtained.  This is only used in cases where
            the number of results is greater than maxResults (as specified
            by the server [above] or the client [in the search request])
          - connectionPool (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=ConnectionPoolManager's default)
            The connectionPool providing the connection to the database to
            be used.
         Warning:
            When setting these values, keep in mind that while a session
            is not timed out (maxSecondsPerSession seconds haven't elapsed,
            and not all results have been requested), a connection from the
            pool is tied up.  Therefore, the connectionPool should be at least
            of size n, large enough to accomodate n simultaneous search
            sessions.  The longer maxSecondsPerSession is, the more chance
            you have of tying up all available connections from the pool.
            Therefore, keep maxSecondsPerSession fairly low, but still
            reasonable for an automated program or user to serially get
            a long list of results, and make sure you have a connectionPool
            large enough to accomodate your users.
        </comment>
  <param name="maxResults" value="100"/>
  <param name="maxSecondsPerSession" value="100"/>
  <param name="connectionPool" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
 </module>
 <module role="fedora.oai.OAIProvider" class="fedora.server.oai.FedoraOAIProviderModule">
  <comment>
        Description:
          Exposes the repository for OAI harvesters.</comment>
        Parameters:
          - repositoryName (required)
            The name of the repository, to be given to OAI harvesters.
          - repositoryDomainName (required)
            The domain name of the repository, which helps to uniquely identify
   items from the repository in OAI-PMH requests.  This should just
   be the domain name of the organization that exposes the objects.
   More information on the OAI identifier syntax can be found at
   http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm
          - adminEmails (required)
            One or more space-separated email addresses, to be given to OAI harvesters.
          - friends (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
            A space-separated list of URLs to known OAI provider baseURLs.
            This is OAI's provider discovery enabler.  Harvesters can use these to crawl OAI providers.
          - maxRecords (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
            The maximum number of results to return at a time for ListRecords requests.
          - maxHeaders (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
            The maximum number of results to return at a time for ListIdentifiers requests.
  <param name="repositoryName" value="INFLIBNET Digital Repository System"/>
  <param name="repositoryDomainName" value="rajesh.lo"/>
  <param name="adminEmails" value="rajesh <at> inflibnet.ac.in"/>
  <param name="friends" value="http://arXiv.org/oai2 http://memory.loc.gov/cgi-bin/oai2_0"/>
  <param name="maxRecords" value="100"/>
  <param name="maxHeaders" value="100"/>
 </module>
 <module role="fedora.server.storage.translation.DOTranslator" class="fedora.server.storage.translation.DOTranslatorModule">
  <comment>Supports translation from DigitalObject to a stream of
        some format, and vice-versa.  The parameters below specify
        serializer/deserializer classes to be used for a given format.
        Those classes must implement the DOSerializer/DODeserializer
        interfaces.
        </comment>
  <param name="serializer_metslikefedora1" value="fedora.server.storage.translation.METSLikeDOSerializer"/>
  <param name="deserializer_metslikefedora1" value="fedora.server.storage.translation.METSLikeDODeserializer"/>
  <param name="serializer_metslikefedora1export" value="fedora.server.storage.translation.METSLikeExportDOSerializer"/>
  <param name="deserializer_metslikefedora1export" value="fedora.server.storage.translation.METSLikeDODeserializer"/>
 </module>
 <module role="fedora.server.management.PIDGenerator" class="fedora.server.management.BasicPIDGenerator">
  <comment>The pid generator.</comment>
  <param name="pidgen_log_dir" value="pidgen"/>
 </module>
 <module role="fedora.server.storage.replication.DOReplicator" class="fedora.server.storage.replication.DefaultDOReplicator">
  <comment>Supports synching data from definitive storage with
        dissemination db.</comment>
 </module>
 <module role="fedora.server.storage.ConnectionPoolManager" class="fedora.server.storage.ConnectionPoolManagerImpl">
  <comment>This module facilitates obtaining ConnectionPools</comment>
  <param name="defaultPoolName" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
  <param name="poolNames" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
 </module>
 <module role="fedora.server.validation.DOValidator" class="fedora.server.validation.DOValidatorModule">
  <comment>
  Description: 
  Supports validation of digital objects, including XML Schema validation (to METS schema),
  Schematron validation (to Fedora Rules schema written in Schematron language), and (in future) other programatic validation
  including referential integrity checking of existence and availability of distributed data and/or services.
   Parameters:
    - tempDir  (required):  this is a directory that the validation module can use as a work space, as when it must
    write a temporary file.
    - xmlSchema: this is local path for the Fedora-METS XML schema used to do XML schema validation of digital objects
    - schematronPreprocessor:  this is the local path to the "skeleton" style sheet for schematron processing
    - schematronSchema:  this is the local path to the Fedora Schematron Schema used to do Fedora-specific validation of digital objects.
    This schema expresses integrity rules which are not covered by the Fedora-METS XML schema.
        </comment>
  <param name="tempDir" value="work"/>
  <param name="xmlSchema" value="xsd/mets-fedora-ext.xsd"/>
  <param name="schematronPreprocessor" value="schematron/preprocessor.xslt"/>
  <param name="schematronSchema" value="schematron/fedoraRulesExt.xml"/>
 </module>
 <module role="fedora.server.storage.ExternalContentManager" class="fedora.server.storage.DefaultExternalContentManager">
  <comment>This module facilitates obtaining external content via HTTP
                Parameters:
                - userAgent (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=Fedora): How to identify the
                  Fedora server in HTTP requests.  This defaults to something
                  reasonable, but if you want to provide more information
                  (such as an admin email address) in the User-Agent HTTP
                  request header, put it here.
                </comment>
 </module>
 <module role="fedora.server.utilities.ThreadMonitor" class="fedora.server.utilities.ThreadMonitorModule">
  <comment>Prints basic information about the running threads to the
            log periodically for diagnostic purposes.
 
            Parameters:
             - active (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=no): whether to activate this module.  "yes" or "true" activates it.
             - pollInterval (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=10000): how many milliseconds to wait between each polling.
            </comment>
  <param name="active" value="false"/>
  <param name="pollInterval" value="5000"/>
 </module>
 <datastore id="localMySQLPool">
  <comment>MySQL database on localhost with db name of fedora12</comment>
  <param name="dbUsername" value="fedoraAdmin"/>
  <param name="dbPassword" value="fedoraAdmin"/>
  <param name="jdbcURL" value="jdbc:mysql://localhost/fedora12?useUnicode=true&amp;characterEncoding=UTF-8"/>
  <param name="jdbcDriverClass" value="org.gjt.mm.mysql.Driver"/>
  <param name="ddlConverter" value="fedora.server.utilities.MySQLDDLConverter"/>
  <param name="minPoolSize" value="10"/>
  <param name="maxPoolSize" value="100"/>
 </datastore>
 <datastore id="localMcKoiPool">
  <comment>McKoi database on localhost running on port 9158</comment>
  <param name="dbUsername" value="fedoraAdmin"/>
  <param name="dbPassword" value="fedoraAdmin"/>
  <param name="jdbcURL" value="jdbc:mckoi://192.168.1.15:9158/"/>
  <param name="jdbcDriverClass" value="com.mckoi.JDBCDriver"/>
  <param name="ddlConverter" value="fedora.server.utilities.McKoiDDLConverter"/>
  <param name="minPoolSize" value="10"/>
  <param name="maxPoolSize" value="100"/>
 </datastore>
 <datastore id="localOracle9iPool">
  <comment>Oracle9i database on localhost with SID=fedora12</comment>
  <param name="dbUsername" value="fedoraAdmin"/>
  <param name="dbPassword" value="fedoraAdmin"/>
  <param name="jdbcURL" value="jdbc:oracle:thin: <at> localhost:1521:fedora12"/>
  <param name="jdbcDriverClass" value="oracle.jdbc.driver.OracleDriver"/>
  <param name="ddlConverter" value="fedora.server.utilities.OracleDDLConverter"/>
  <param name="minPoolSize" value="10"/>
  <param name="maxPoolSize" value="100"/>
 </datastore>
</server>
still I got same problem Servlet engine and ConnectionPoolNotFoundException. Please guide.
 
Whe I stop the fedora server. It gets stop. but when I go to stop the McKoi database it gets me following error:
 
java.sql.SQLException: Connection refused: Connect
at com.mckoi.database.jdbc.TCPStreamDatabaseInterface.ConnectToDatabase: Unknown Source
at com.mckoi.database.jdbc.MDriver.Connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.mckoi.runtime.McKoiDBMain.doShutDown(Unknown Source)
at com.mckoi.runtime.McKoiDBMain.main(Unknown Source)
 
Finished.
 
For your kind information. I am using Windows 2000 Advanced Server with ServicePack 1.
 
regards,
Rajesh
 
 
 
 
 
 
 
Rajesh Chandrakar | 8 Sep 14:08 2004
Picon

[Fedora-users] Re: Servlet Engine and ConnectionPoolNotFoundException

Dear Ronda,
 
I tried to use the MySQL version 5.0 database instead of McKoi. The same error, I am getting. Will you please help me, what problem it is? I am very much interested to implement FEDORA Repository in my Centre. For your kind information, I am using:
 
Microsoft Windows 2000 Advance Server
I upgraded the server pack with 4
Java Version 1.4.2
Fedora Version 1.2
My SQL Version 5.0
 
Please guide me.
 
Rajesh
 
----- Original Message -----
Sent: Saturday, September 04, 2004 12:37 PM
Subject: Servlet Engine and ConnectionPoolNotFoundException

Dear Mr. Ronda,
 
I deleted the complete installation of fedora server, client and src development. And reinstalled the fedora. As per the instrunction, I did ant serverdist process from c:\fedora-1.2-src directory (FEDORA_DEV directory). Then I initialised the McKoi databsae from C:\ directory by following command:
 
mckoi-init fedoraAdmin fedoraAdmin
 
got message DBInstalled and finished.
 
Now I modified the fedora.fcfg, you may please look at it as follows
<?xml version="1.0" encoding="UTF-8"?>
<server xmlns="http://www.fedora.info/definitions/1/0/config/" xmlns:fedora-config="http://www.fedora.info/definitions/1/0/config/" class="fedora.server.BasicServer">
 <param name="repositoryName" value="Fedora Repository 1"/>
 <comment>Defines a human readable name for the Fedora server; default is Fedora Repository.</comment>
 <param name="adminEmailList" value="rajesh <at> inflibnet.ac.in"/>
 <comment>Defines one or more email addresses for server administrators; list is space delimited.</comment>
 <param name="adminPassword" value="fedoraAdmin"/>
 <comment>Defines the password for the Fedora server; default is fedoraAdmin.</comment>
 <param name="log_max_size" value="5242880"/>
 <comment>Defines the threshold at which a new log file is generated based on the size of the current log file in bytes; default is 5242880 bytes.</comment>
 <param name="log_max_days" value="7"/>
 <comment>Defines the threshold at which a new log file is generated based on number of days since the server was started in days; default is 7 days.</comment>
 <param name="log_dir" value="logs"/>
 <comment>Defines the directory in which the Fedora logs will be written; default is logs.</comment>
 <param name="log_level" value="finest"/>
 <comment>Defines the level of logging desired;default is finest; possible levels include:
  - config
   denotes logging indicating what occurred during the server's (or a module's) configuration phase.
  - fine
   denotes logging indicating basic information about a request to the server (like hostname, operation name, and success or failure). 
  - finer
   denotes logging indicating detailed information about a request to the server (like the full request, full response, and timing information).
  - finest (deafult)
   denotes logging indicating method entry/exit or extremely verbose information intended to aid in debugging.
  - info
   denotes logging indicating that something relatively uncommon and interesting happened, like server or module startup or shutdown, or a periodic job.
  - warning
   denotes logging indicating that an undesired (but non-fatal) condition occured.
  - severe
   denotes logging indicating that the server is inoperable or unable to start.
 </comment>
 <param name="log_flush_threshold" value="1"/>
 <comment>Defines the flush threshold for logging in number of records; default is one log record.</comment>
 <param name="path_algorithm" value="fedora.server.storage.lowlevel.TimestampPathAlgorithm"/>
 <comment>Defines the java class used to determine the path algorithm for LowLevelStorage;
  default is fedora.server.storage.lowlevel.TimestampPathAlgorithm.
 </comment>
 <param name="file_system" value="fedora.server.storage.lowlevel.GenericFileSystem"/>
 <comment>Defines the java class that determines the type of implementation for LowLevelStorage;
  default is fedora.server.storage.lowlevel.GenericFileSystem.
 </comment>
 <param name="registry" value="fedora.server.storage.lowlevel.DBPathRegistry"/>
 <comment>Defines the java class used to determine the path registry for LowLevelStorage;
  default is fedora.server.storage.lowlevel.DBPathRegistry.
 </comment>
 <param name="backslash_is_escape" value="yes" oraclevalue="no"/>
 <comment>Defines whether the backing database (which include registry tables) the backslash character
  to be the escape character (token beginning an escape sequence).  This is needed to correctly
  store and retrieve filepaths from the registry tables, if running under Windows/DOS.
 </comment>
 <param name="object_store_base" value="C:\fedora1_2_objects"/>
 <comment>Defines the root directory for the internal storage of Fedora objects.
  This value should be adjusted based on your installation environment;
  default assumes a Windows installation of C:\fedora1_2_objects.
 </comment>
 <param name="temp_store_base" value="C:\fedora1_2_temp"/>
 <comment>Defines the root directory for Fedora temporary storage.
  This value should be adjusted based on your installation environment;
  default assumes a Windows installation of C:\fedora1_2_temp.
 </comment>
 <param name="datastream_store_base" value="C:\fedora1_2_datastreams"/>
 <comment>Defines the root directory for the internal storage of Managed Content datastreams.
  This value should be adjusted based on your installation environment;
  default assumes a Windows installation of C:\fedora1_2_datastreams.
 </comment>
 <param name="debug" value="false"/>
 <comment>A boolean toggle used to turn off/on internal debugging in the code.</comment>
 <param name="datastreamExpirationLimit" value="300"/>
 <comment>
  Controls the size of the datastream mediation hash by removing entries outside the specified threshold.
  The value is specified in seconds.
  Note this value must be greater than the limit specified for the datastreamMediationLimit.
 </comment>
 <param name="datastreamMediationLimit" value="5000"/>
 <comment>
  Determines the time interval in which external mechanisms must respond to requests by the Fedora server.
   The value is specified in milliseconds. 
  The value specified should be set high enough to allow for an average response time from any single external mechanisms.
  Note this value must be less than the limit specified for the datastreamExpirationLimit.
 </comment>
 <param name="fedoraServerPort" value="8080"/>
 <comment>Defines the port number on which the Fedora server runs; default is 8080.</comment>
 <param name="fedoraShutdownPort" value="8005"/>
 <comment>Defines the port number used to shutdown the Fedora sever; default is 8005.</comment>
 <param name="fedoraRedirectPort" value="8443"/>
 <comment>Defines the redirect port of the Fedora sever; default is 8443.</comment>
 <param name="fedoraServerHost" value="192.168.1.15"/>
 <comment>Defines the host name for the Fedora server, as seen from the outside world.</comment>
 <module role="fedora.server.storage.DOManager" class="fedora.server.storage.DefaultDOManager">
  <comment>
        Description:
          The interface to the storage subsystem.  This provides
          context-appropriate DOReaders and DOWriters for reflecting on and
          writing to the objects stored in the repository.  It also
          provides methods for reflecting on the contents of the repository
          as a whole.  This implementation uses DefinitiveDOReader/Writer
          for an "application" of "apim" and a FastDOReader/Writer
          for an "application" of "apia" (from the Context).  Other
          context-specific logic TBD.
        Parameters:
        - pidNamespace (required)
          This is the namespace id for pids of newly-created objects.
          This should be unique for a repository.
          It can be from 1 to 17 characters, and may only contain
          A-Z, a-z, 0-9, and '-' (dash).
        - retainPIDs [default="demo test"]
          Namespaces of PIDs to retain during the ingest process.
          When an object is ingested, Fedora normally allocates a unique PID
          within pidNamespace for it regardless of what the object says its
          PID is.  This option provides a way to override that behavior on
          a per-pid-namespace basis.  If specified, this should be a
          space-delimited list of pid namespaces that will be accepted in the
          object as-is.
        - storagePool [default=default provided by the ConnectionPoolManager]
          The named connection pool from which read/write
          database connections are to be provided for the storage
          subsystem (see the ConnectionPoolManager module)
        - storageFormat (required)
          The format in which internal serializations of digital objects
          are to be written.  There must exist a correspondingly
          named serializer-deserializer pair in the DOTranslator module.
        - storageCharacterEncoding [default=UTF-8]
          If the serialization format is text-based,
          this is the character encoding that should be used.</comment>
        - exportFormat (required)
          The format in which external serializations of digital objects
          are to be written.  There must exist a correspondingly
          named serializer-deserializer pair in the DOTranslator module.
  <param name="pidNamespace" value="111"/>
  <param name="retainPIDs" value="demo test changeme"/>
  <param name="storagePool" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
  <param name="storageFormat" value="metslikefedora1"/>
  <param name="exportFormat" value="metslikefedora1export"/>
  <param name="storageCharacterEncoding" value="UTF-8"/>
 </module>
 <module role="fedora.server.management.Management" class="fedora.server.management.DefaultManagement">
  <comment>
        Description:
          The management subsystem.
          This implements the methods necessary to fulfill API-M
          requests without regard to:
            - how the service is exposed
            - how bytestreams and java types might be marshalled/demarshalled
              over the wire
            - how the storage subsystem is implemented.
        Parameters:
            - allowHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must match for any Management request to be accepted.
              If this is not specified, all requests will be accepted unless
              the remote address matches a deny pattern.
            - denyHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must not match for any Management request to be accepted.
              If this is not specified, request acceptance is governed
              solely by the allowHosts parameter.
        </comment>
  <param name="allowHosts" value="192.168.1.1-192.168.1.255"/>
 </module>
 <module role="fedora.server.access.Access" class="fedora.server.access.DefaultAccess">
  <comment>
        Description:
          The access subsystem.
          This implements the methods necessary to fulfill API-A
          requests without regard to:
            - how the service is exposed
            - how bytestreams and java types might be marshalled/demarshalled
              over the wire
            - how the storage subsystem is implemented.
        Parameters:
            - allowHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must match for any Management request to be accepted.
              If this is not specified, all requests will be accepted unless
              the remote address matches a deny pattern.
            - denyHosts (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
              A comma-separated list of IP ranges that the client's address
              is compared to. If this is specified, the remote address
              must not match for any Management request to be accepted.
              If this is not specified, request acceptance is governed
              solely by the allowHosts parameter.
            - doMediateDatastreams (required)
              A boolean switch indicating whether Datastream Mediation is activated or not.
              Datastream Mediation provides additional repository security by not exposing
              the actual physical location of Referenced Content datastreams to external
              mechanisms(services). Instead of exposing the actual physical location of
              Referenced Content datastreams , Datastream Mediation functions as a proxy
              requiring all external services to communicate through the Fedora server to
              resolve the location of Referenced Content datastreams. For Datastream
              Mediation to function, the Fedora server must be internet accessible on its
              designated port by any potential external service. This requirement can be
              difficult to satisfy if the Fedora server is located behind a firewall and
              you do not have ready access to the firewall's configuration to enable the
              required access. If the Fedora server is behind a firewall and you have no
              access to the firewall's configuration, you can disable Datastream Mediation
              which will allow external services to access Referenced Content datastreams
              using their actual physical locations. Managed Content and XMLMetadata
              datastreams are stored internally in the Fedora repository and can only be
              accessed through the Fedora server so disabling Datastream Mediation has no
              effect on these types of datastreams. Disabling Datastream Mediation exposes
              the physical location of Referenced Content datastream to external services
              which can result in unintended access to the raw datastreams by surreptitious
              external mechanisms. It is recommended that Datastream Mediation be disabled
              only for testing or cases where this security issue is not a concern. The
              default value of doMediateDatastreams is true.
            </comment>
  <param name="doMediateDatastreams" value="false"/>
 </module>
 <module role="fedora.server.access.DynamicAccess" class="fedora.server.access.DynamicAccessModule">
  <comment>
        Description:
          The dynamic behavior module for the access subsystem.
          This implements the methods necessary to fulfill API-A
          requests without regard to:
             - dynamically associating a default behavior definition and mechanism with objects
           - (Future) dynamically associating other behavior definitions and mechanisms with objects
           - running disseminations of dynamic behaviors
        Parameters:
            - fedora-system:1
              The interface that defines the methods of the bootstrap
              disseminator.  These methods are "built-in" to the Fedora
              system, and are dynamically associated with every
              behavior definition and behavior mechanism object.
            - fedora-system:2
              The class that implements the methods of the bootstrap
              disseminator.  These method implementations are "built-in"
              to the Fedora system, and are dynamically associated with
              every behavior definition and behavior mechanism object. 
              This class can be though of as implementing
              an "internal service" whereas other disseminators use
              external services (described by WSDL) to do their work.
            - fedora-system:3
              The interface that defines the methods of the default
              disseminator.  These methods are "built-in" to the Fedora
              system, and are dynamically associated with every object.
            - fedora-system:4
              The class that implements the methods of the default
              disseminator.  These method implementations are "built-in"
              to the Fedora system, and are dynamically associated with
              every object.  This class can be though of as implementing
              an "internal service" whereas other disseminators use
              external services (described by WSDL) to do their work.
            </comment>
  <param name="fedora-system:1" value="fedora.server.access.internalservices.Bootstrap"/>
  <param name="fedora-system:2" value="fedora.server.access.internalservices.BootstrapImpl"/>
  <param name="fedora-system:3" value="fedora.server.access.internalservices.DefaultBehavior"/>
  <param name="fedora-system:4" value="fedora.server.access.internalservices.DefaultBehaviorImpl"/>
 </module>
 <module role="fedora.server.search.FieldSearch" class="fedora.server.search.FieldSearchSQLModule">
  <comment>
        Description:
          Supports the API-A simpleSearch and advancedSearch methods.
        Parameters:
          - maxResults (required, must be > 0)
            The maximum number of records to return as the result of a search.
            Even if a client requests more results at a time, this is the
            cutoff value.
          - maxSecondsPerSession (required, must be > 0)
            The maximum number of seconds that the server guarantees subsequent
            search results may be obtained.  This is only used in cases where
            the number of results is greater than maxResults (as specified
            by the server [above] or the client [in the search request])
          - connectionPool (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=ConnectionPoolManager's default)
            The connectionPool providing the connection to the database to
            be used.
         Warning:
            When setting these values, keep in mind that while a session
            is not timed out (maxSecondsPerSession seconds haven't elapsed,
            and not all results have been requested), a connection from the
            pool is tied up.  Therefore, the connectionPool should be at least
            of size n, large enough to accomodate n simultaneous search
            sessions.  The longer maxSecondsPerSession is, the more chance
            you have of tying up all available connections from the pool.
            Therefore, keep maxSecondsPerSession fairly low, but still
            reasonable for an automated program or user to serially get
            a long list of results, and make sure you have a connectionPool
            large enough to accomodate your users.
        </comment>
  <param name="maxResults" value="100"/>
  <param name="maxSecondsPerSession" value="100"/>
  <param name="connectionPool" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
 </module>
 <module role="fedora.oai.OAIProvider" class="fedora.server.oai.FedoraOAIProviderModule">
  <comment>
        Description:
          Exposes the repository for OAI harvesters.</comment>
        Parameters:
          - repositoryName (required)
            The name of the repository, to be given to OAI harvesters.
          - repositoryDomainName (required)
            The domain name of the repository, which helps to uniquely identify
   items from the repository in OAI-PMH requests.  This should just
   be the domain name of the organization that exposes the objects.
   More information on the OAI identifier syntax can be found at
   http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm
          - adminEmails (required)
            One or more space-separated email addresses, to be given to OAI harvesters.
          - friends (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string)
            A space-separated list of URLs to known OAI provider baseURLs.
            This is OAI's provider discovery enabler.  Harvesters can use these to crawl OAI providers.
          - maxRecords (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
            The maximum number of results to return at a time for ListRecords requests.
          - maxHeaders (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
            The maximum number of results to return at a time for ListIdentifiers requests.
  <param name="repositoryName" value="INFLIBNET Digital Repository System"/>
  <param name="repositoryDomainName" value="rajesh.lo"/>
  <param name="adminEmails" value="rajesh <at> inflibnet.ac.in"/>
  <param name="friends" value="http://arXiv.org/oai2 http://memory.loc.gov/cgi-bin/oai2_0"/>
  <param name="maxRecords" value="100"/>
  <param name="maxHeaders" value="100"/>
 </module>
 <module role="fedora.server.storage.translation.DOTranslator" class="fedora.server.storage.translation.DOTranslatorModule">
  <comment>Supports translation from DigitalObject to a stream of
        some format, and vice-versa.  The parameters below specify
        serializer/deserializer classes to be used for a given format.
        Those classes must implement the DOSerializer/DODeserializer
        interfaces.
        </comment>
  <param name="serializer_metslikefedora1" value="fedora.server.storage.translation.METSLikeDOSerializer"/>
  <param name="deserializer_metslikefedora1" value="fedora.server.storage.translation.METSLikeDODeserializer"/>
  <param name="serializer_metslikefedora1export" value="fedora.server.storage.translation.METSLikeExportDOSerializer"/>
  <param name="deserializer_metslikefedora1export" value="fedora.server.storage.translation.METSLikeDODeserializer"/>
 </module>
 <module role="fedora.server.management.PIDGenerator" class="fedora.server.management.BasicPIDGenerator">
  <comment>The pid generator.</comment>
  <param name="pidgen_log_dir" value="pidgen"/>
 </module>
 <module role="fedora.server.storage.replication.DOReplicator" class="fedora.server.storage.replication.DefaultDOReplicator">
  <comment>Supports synching data from definitive storage with
        dissemination db.</comment>
 </module>
 <module role="fedora.server.storage.ConnectionPoolManager" class="fedora.server.storage.ConnectionPoolManagerImpl">
  <comment>This module facilitates obtaining ConnectionPools</comment>
  <param name="defaultPoolName" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
  <param name="poolNames" value="localMySQLPool" mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
 </module>
 <module role="fedora.server.validation.DOValidator" class="fedora.server.validation.DOValidatorModule">
  <comment>
  Description: 
  Supports validation of digital objects, including XML Schema validation (to METS schema),
  Schematron validation (to Fedora Rules schema written in Schematron language), and (in future) other programatic validation
  including referential integrity checking of existence and availability of distributed data and/or services.
   Parameters:
    - tempDir  (required):  this is a directory that the validation module can use as a work space, as when it must
    write a temporary file.
    - xmlSchema: this is local path for the Fedora-METS XML schema used to do XML schema validation of digital objects
    - schematronPreprocessor:  this is the local path to the "skeleton" style sheet for schematron processing
    - schematronSchema:  this is the local path to the Fedora Schematron Schema used to do Fedora-specific validation of digital objects.
    This schema expresses integrity rules which are not covered by the Fedora-METS XML schema.
        </comment>
  <param name="tempDir" value="work"/>
  <param name="xmlSchema" value="xsd/mets-fedora-ext.xsd"/>
  <param name="schematronPreprocessor" value="schematron/preprocessor.xslt"/>
  <param name="schematronSchema" value="schematron/fedoraRulesExt.xml"/>
 </module>
 <module role="fedora.server.storage.ExternalContentManager" class="fedora.server.storage.DefaultExternalContentManager">
  <comment>This module facilitates obtaining external content via HTTP
                Parameters:
                - userAgent (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=Fedora): How to identify the
                  Fedora server in HTTP requests.  This defaults to something
                  reasonable, but if you want to provide more information
                  (such as an admin email address) in the User-Agent HTTP
                  request header, put it here.
                </comment>
 </module>
 <module role="fedora.server.utilities.ThreadMonitor" class="fedora.server.utilities.ThreadMonitorModule">
  <comment>Prints basic information about the running threads to the
            log periodically for diagnostic purposes.
 
            Parameters:
             - active (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=no): whether to activate this module.  "yes" or "true" activates it.
             - pollInterval (optional...to make unspecified, comment out or delete the whole param line as opposed to using an empty string, default=10000): how many milliseconds to wait between each polling.
            </comment>
  <param name="active" value="false"/>
  <param name="pollInterval" value="5000"/>
 </module>
 <datastore id="localMySQLPool">
  <comment>MySQL database on localhost with db name of fedora12</comment>
  <param name="dbUsername" value="fedoraAdmin"/>
  <param name="dbPassword" value="fedoraAdmin"/>
  <param name="jdbcURL" value="jdbc:mysql://localhost/fedora12?useUnicode=true&amp;characterEncoding=UTF-8"/>
  <param name="jdbcDriverClass" value="org.gjt.mm.mysql.Driver"/>
  <param name="ddlConverter" value="fedora.server.utilities.MySQLDDLConverter"/>
  <param name="minPoolSize" value="10"/>
  <param name="maxPoolSize" value="100"/>
 </datastore>
 <datastore id="localMcKoiPool">
  <comment>McKoi database on localhost running on port 9158</comment>
  <param name="dbUsername" value="fedoraAdmin"/>
  <param name="dbPassword" value="fedoraAdmin"/>
  <param name="jdbcURL" value="jdbc:mckoi://192.168.1.15:9158/"/>
  <param name="jdbcDriverClass" value="com.mckoi.JDBCDriver"/>
  <param name="ddlConverter" value="fedora.server.utilities.McKoiDDLConverter"/>
  <param name="minPoolSize" value="10"/>
  <param name="maxPoolSize" value="100"/>
 </datastore>
 <datastore id="localOracle9iPool">
  <comment>Oracle9i database on localhost with SID=fedora12</comment>
  <param name="dbUsername" value="fedoraAdmin"/>
  <param name="dbPassword" value="fedoraAdmin"/>
  <param name="jdbcURL" value="jdbc:oracle:thin: <at> localhost:1521:fedora12"/>
  <param name="jdbcDriverClass" value="oracle.jdbc.driver.OracleDriver"/>
  <param name="ddlConverter" value="fedora.server.utilities.OracleDDLConverter"/>
  <param name="minPoolSize" value="10"/>
  <param name="maxPoolSize" value="100"/>
 </datastore>
</server>
still I got same problem Servlet engine and ConnectionPoolNotFoundException. Please guide.
 
Whe I stop the fedora server. It gets stop. but when I go to stop the McKoi database it gets me following error:
 
java.sql.SQLException: Connection refused: Connect
at com.mckoi.database.jdbc.TCPStreamDatabaseInterface.ConnectToDatabase: Unknown Source
at com.mckoi.database.jdbc.MDriver.Connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.mckoi.runtime.McKoiDBMain.doShutDown(Unknown Source)
at com.mckoi.runtime.McKoiDBMain.main(Unknown Source)
 
Finished.
 
For your kind information. I am using Windows 2000 Advanced Server with ServicePack 1.
 
regards,
Rajesh
 
 
 
 
 
 
 
Ronda A. Grizzle | 8 Sep 17:33 2004

Re: [Fedora-users] Re: Servlet Engine and ConnectionPoolNotFoundException

Hello Rajesh,

I have been consulting with the developers on your problems getting Fedora 
up and running. Thank you for including your system information.

Since mysql 5.0 is an alpha release and has not been tested with the 
Fedora software, we suggest using a 4.0.x release, which are stable.

The version of mysql that is packaged with Fedora 1.2 is a 3.23.x release, 
and the jdbc driver included with the software is suitable for that 
release. In order to upgrade to a 4.0.x version, you will need to change 
out the jdbc driver per the instructions found here: 
<http://www.fedora.info/wiki/bin/view/Fedora/MySQLVersion4>.

With regard to your mckoi question: there is no way that I know of to 
retrieve the username and password that you used to initialize mckoi. I 
would suggest that you stop the mckoi database with mckoi-stop, delete the 
mckoi094/data directory and its contents, and reinitialize the database 
with mckoi-init, remembering if you use a dbusername and db password that 
is different from the default to change the username/password in the jdbc 
driver section to match those used to initialize the database.

Please let me know of any further problems that you have getting started 
with Fedora.

Best regards,
Ronda

--On Wednesday, 08 September, 2004 5:38 PM +0530 Rajesh Chandrakar 
<rajesh@...> wrote:

>
> Dear Ronda,
>
> I tried to use the MySQL version 5.0 database instead of McKoi. The same
> error, I am getting. Will you please help me, what problem it is? I am
> very much interested to implement FEDORA Repository in my Centre. For
> your kind information, I am using:
>
> Microsoft Windows 2000 Advance Server
> I upgraded the server pack with 4
> Java Version 1.4.2
> Fedora Version 1.2
> My SQL Version 5.0
>
> Please guide me.
>
> Rajesh
>
>
>
> ----- Original Message -----
> From: Rajesh Chandrakar
> To: fedora-users@...
> Sent: Saturday, September 04, 2004 12:37 PM
> Subject: Servlet Engine and ConnectionPoolNotFoundException
>
>
> Dear Mr. Ronda,
>
> I deleted the complete installation of fedora server, client and src
> development. And reinstalled the fedora. As per the instrunction, I did
> ant serverdist process from c:\fedora-1.2-src directory (FEDORA_DEV
> directory). Then I initialised the McKoi databsae from C:\ directory by
> following command:
>
> mckoi-init fedoraAdmin fedoraAdmin
>
> got message DBInstalled and finished.
>
> Now I modified the fedora.fcfg, you may please look at it as follows
> <?xml version="1.0" encoding="UTF-8"?>
> <server xmlns="http://www.fedora.info/definitions/1/0/config/"
> xmlns:fedora-config="http://www.fedora.info/definitions/1/0/config/"
> class="fedora.server.BasicServer">
>  <param name="repositoryName" value="Fedora Repository 1"/>
>  <comment>Defines a human readable name for the Fedora server; default
> is Fedora Repository.</comment>
>  <param name="adminEmailList" value="rajesh@..."/>
>  <comment>Defines one or more email addresses for server administrators;
> list is space delimited.</comment>
>  <param name="adminPassword" value="fedoraAdmin"/>
>  <comment>Defines the password for the Fedora server; default is
> fedoraAdmin.</comment>
>  <param name="log_max_size" value="5242880"/>
>  <comment>Defines the threshold at which a new log file is generated
> based on the size of the current log file in bytes; default is 5242880
> bytes.</comment>
>  <param name="log_max_days" value="7"/>
>  <comment>Defines the threshold at which a new log file is generated
> based on number of days since the server was started in days; default is
> 7 days.</comment>
>  <param name="log_dir" value="logs"/>
>  <comment>Defines the directory in which the Fedora logs will be
> written; default is logs.</comment>
>  <param name="log_level" value="finest"/>
>  <comment>Defines the level of logging desired;default is finest;
> possible levels include:
>   - config
>    denotes logging indicating what occurred during the server's (or a
> module's) configuration phase.
>   - fine
>    denotes logging indicating basic information about a request to the
> server (like hostname, operation name, and success or failure).
>   - finer
>    denotes logging indicating detailed information about a request to
> the server (like the full request, full response, and timing
> information).
>   - finest (deafult)
>    denotes logging indicating method entry/exit or extremely verbose
> information intended to aid in debugging.
>   - info
>    denotes logging indicating that something relatively uncommon and
> interesting happened, like server or module startup or shutdown, or a
> periodic job.
>   - warning
>    denotes logging indicating that an undesired (but non-fatal)
> condition occurred.
>   - severe
>    denotes logging indicating that the server is inoperable or unable to
> start.
>  </comment>
>  <param name="log_flush_threshold" value="1"/>
>  <comment>Defines the flush threshold for logging in number of records;
> default is one log record.</comment>
>  <param name="path_algorithm"
> value="fedora.server.storage.lowlevel.TimestampPathAlgorithm"/>
>  <comment>Defines the java class used to determine the path algorithm
> for LowLevelStorage;
>   default is fedora.server.storage.lowlevel.TimestampPathAlgorithm.
>  </comment>
>  <param name="file_system"
> value="fedora.server.storage.lowlevel.GenericFileSystem"/>
>  <comment>Defines the java class that determines the type of
> implementation for LowLevelStorage;
>   default is fedora.server.storage.lowlevel.GenericFileSystem.
>  </comment>
>  <param name="registry"
> value="fedora.server.storage.lowlevel.DBPathRegistry"/>
>  <comment>Defines the java class used to determine the path registry for
> LowLevelStorage;
>   default is fedora.server.storage.lowlevel.DBPathRegistry.
>  </comment>
>  <param name="backslash_is_escape" value="yes" oraclevalue="no"/>
>  <comment>Defines whether the backing database (which include registry
> tables) the backslash character
>   to be the escape character (token beginning an escape sequence).  This
> is needed to correctly
>   store and retrieve filepaths from the registry tables, if running
> under Windows/DOS.
>  </comment>
>  <param name="object_store_base" value="C:\fedora1_2_objects"/>
>  <comment>Defines the root directory for the internal storage of Fedora
> objects.
>   This value should be adjusted based on your installation environment;
>   default assumes a Windows installation of C:\fedora1_2_objects.
>  </comment>
>  <param name="temp_store_base" value="C:\fedora1_2_temp"/>
>  <comment>Defines the root directory for Fedora temporary storage.
>   This value should be adjusted based on your installation environment;
>   default assumes a Windows installation of C:\fedora1_2_temp.
>  </comment>
>  <param name="datastream_store_base" value="C:\fedora1_2_datastreams"/>
>  <comment>Defines the root directory for the internal storage of Managed
> Content datastreams.
>   This value should be adjusted based on your installation environment;
>   default assumes a Windows installation of C:\fedora1_2_datastreams.
>  </comment>
>  <param name="debug" value="false"/>
>  <comment>A boolean toggle used to turn off/on internal debugging in the
> code.</comment>
>  <param name="datastreamExpirationLimit" value="300"/>
>  <comment>
>   Controls the size of the datastream mediation hash by removing entries
> outside the specified threshold.
>   The value is specified in seconds.
>   Note this value must be greater than the limit specified for the
> datastreamMediationLimit.
>  </comment>
>  <param name="datastreamMediationLimit" value="5000"/>
>  <comment>
>   Determines the time interval in which external mechanisms must respond
> to requests by the Fedora server.
>    The value is specified in milliseconds.
>   The value specified should be set high enough to allow for an average
> response time from any single external mechanisms.
>   Note this value must be less than the limit specified for the
> datastreamExpirationLimit.
>  </comment>
>  <param name="fedoraServerPort" value="8080"/>
>  <comment>Defines the port number on which the Fedora server runs;
> default is 8080.</comment>
>  <param name="fedoraShutdownPort" value="8005"/>
>  <comment>Defines the port number used to shutdown the Fedora sever;
> default is 8005.</comment>
>  <param name="fedoraRedirectPort" value="8443"/>
>  <comment>Defines the redirect port of the Fedora sever; default is
> 8443.</comment>
>  <param name="fedoraServerHost" value="192.168.1.15"/>
>  <comment>Defines the host name for the Fedora server, as seen from the
> outside world.</comment>
>  <module role="fedora.server.storage.DOManager"
> class="fedora.server.storage.DefaultDOManager">
>   <comment>
>         Description:
>           The interface to the storage subsystem.  This provides
>           context-appropriate DOReaders and DOWriters for reflecting on
> and
>           writing to the objects stored in the repository.  It also
>           provides methods for reflecting on the contents of the
> repository
>           as a whole.  This implementation uses DefinitiveDOReader/Writer
>           for an "application" of "apim" and a FastDOReader/Writer
>           for an "application" of "apia" (from the Context).  Other
>           context-specific logic TBD.
>         Parameters:
>         - pidNamespace (required)
>           This is the namespace id for pids of newly-created objects.
>           This should be unique for a repository.
>           It can be from 1 to 17 characters, and may only contain
>           A-Z, a-z, 0-9, and '-' (dash).
>         - retainPIDs [default="demo test"]
>           Namespaces of PIDs to retain during the ingest process.
>           When an object is ingested, Fedora normally allocates a unique
> PID
>           within pidNamespace for it regardless of what the object says
> its
>           PID is.  This option provides a way to override that behavior
> on
>           a per-pid-namespace basis.  If specified, this should be a
>           space-delimited list of pid namespaces that will be accepted
> in the
>           object as-is.
>         - storagePool [default=default provided by the
> ConnectionPoolManager]
>           The named connection pool from which read/write
>           database connections are to be provided for the storage
>           subsystem (see the ConnectionPoolManager module)
>         - storageFormat (required)
>           The format in which internal serializations of digital objects
>           are to be written.  There must exist a correspondingly
>           named serializer-deserializer pair in the DOTranslator module.
>         - storageCharacterEncoding [default=UTF-8]
>           If the serialization format is text-based,
>           this is the character encoding that should be used.</comment>
>         - exportFormat (required)
>           The format in which external serializations of digital objects
>           are to be written.  There must exist a correspondingly
>           named serializer-deserializer pair in the DOTranslator module.
>   <param name="pidNamespace" value="111"/>
>   <param name="retainPIDs" value="demo test changeme"/>
>   <param name="storagePool" value="localMySQLPool"
> mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
>   <param name="storageFormat" value="metslikefedora1"/>
>   <param name="exportFormat" value="metslikefedora1export"/>
>   <param name="storageCharacterEncoding" value="UTF-8"/>
>  </module>
>  <module role="fedora.server.management.Management"
> class="fedora.server.management.DefaultManagement">
>   <comment>
>         Description:
>           The management subsystem.
>           This implements the methods necessary to fulfill API-M
>           requests without regard to:
>             - how the service is exposed
>             - how bytestreams and java types might be
> marshalled/demarshalled
>               over the wire
>             - how the storage subsystem is implemented.
>         Parameters:
>             - allowHosts (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string)
>               A comma-separated list of IP ranges that the client's
> address
>               is compared to. If this is specified, the remote address
>               must match for any Management request to be accepted.
>               If this is not specified, all requests will be accepted
> unless
>               the remote address matches a deny pattern.
>             - denyHosts (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string)
>               A comma-separated list of IP ranges that the client's
> address
>               is compared to. If this is specified, the remote address
>               must not match for any Management request to be accepted.
>               If this is not specified, request acceptance is governed
>               solely by the allowHosts parameter.
>         </comment>
>   <param name="allowHosts" value="192.168.1.1-192.168.1.255"/>
>  </module>
>  <module role="fedora.server.access.Access"
> class="fedora.server.access.DefaultAccess">
>   <comment>
>         Description:
>           The access subsystem.
>           This implements the methods necessary to fulfill API-A
>           requests without regard to:
>             - how the service is exposed
>             - how bytestreams and java types might be
> marshalled/demarshalled
>               over the wire
>             - how the storage subsystem is implemented.
>         Parameters:
>             - allowHosts (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string)
>               A comma-separated list of IP ranges that the client's
> address
>               is compared to. If this is specified, the remote address
>               must match for any Management request to be accepted.
>               If this is not specified, all requests will be accepted
> unless
>               the remote address matches a deny pattern.
>             - denyHosts (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string)
>               A comma-separated list of IP ranges that the client's
> address
>               is compared to. If this is specified, the remote address
>               must not match for any Management request to be accepted.
>               If this is not specified, request acceptance is governed
>               solely by the allowHosts parameter.
>             - doMediateDatastreams (required)
>               A boolean switch indicating whether Datastream Mediation
> is activated or not.
>               Datastream Mediation provides additional repository
> security by not exposing
>               the actual physical location of Referenced Content
> datastreams to external
>               mechanisms(services). Instead of exposing the actual
> physical location of
>               Referenced Content datastreams , Datastream Mediation
> functions as a proxy
>               requiring all external services to communicate through the
> Fedora server to
>               resolve the location of Referenced Content datastreams.
> For Datastream
>               Mediation to function, the Fedora server must be internet
> accessible on its
>               designated port by any potential external service. This
> requirement can be
>               difficult to satisfy if the Fedora server is located
> behind a firewall and
>               you do not have ready access to the firewall's
> configuration to enable the
>               required access. If the Fedora server is behind a firewall
> and you have no
>               access to the firewall's configuration, you can disable
> Datastream Mediation
>               which will allow external services to access Referenced
> Content datastreams
>               using their actual physical locations. Managed Content and
> XMLMetadata
>               datastreams are stored internally in the Fedora repository
> and can only be
>               accessed through the Fedora server so disabling Datastream
> Mediation has no
>               effect on these types of datastreams. Disabling Datastream
> Mediation exposes
>               the physical location of Referenced Content datastream to
> external services
>               which can result in unintended access to the raw
> datastreams by surreptitious
>               external mechanisms. It is recommended that Datastream
> Mediation be disabled
>               only for testing or cases where this security issue is not
> a concern. The
>               default value of doMediateDatastreams is true.
>             </comment>
>   <param name="doMediateDatastreams" value="false"/>
>  </module>
>  <module role="fedora.server.access.DynamicAccess"
> class="fedora.server.access.DynamicAccessModule">
>   <comment>
>         Description:
>           The dynamic behavior module for the access subsystem.
>           This implements the methods necessary to fulfill API-A
>           requests without regard to:
>              - dynamically associating a default behavior definition and
> mechanism with objects
>            - (Future) dynamically associating other behavior definitions
> and mechanisms with objects
>            - running disseminations of dynamic behaviors
>         Parameters:
>             - fedora-system:1
>               The interface that defines the methods of the bootstrap
>               disseminator.  These methods are "built-in" to the Fedora
>               system, and are dynamically associated with every
>               behavior definition and behavior mechanism object.
>             - fedora-system:2
>               The class that implements the methods of the bootstrap
>               disseminator.  These method implementations are "built-in"
>               to the Fedora system, and are dynamically associated with
>               every behavior definition and behavior mechanism object.
>               This class can be though of as implementing
>               an "internal service" whereas other disseminators use
>               external services (described by WSDL) to do their work.
>             - fedora-system:3
>               The interface that defines the methods of the default
>               disseminator.  These methods are "built-in" to the Fedora
>               system, and are dynamically associated with every object.
>             - fedora-system:4
>               The class that implements the methods of the default
>               disseminator.  These method implementations are "built-in"
>               to the Fedora system, and are dynamically associated with
>               every object.  This class can be though of as implementing
>               an "internal service" whereas other disseminators use
>               external services (described by WSDL) to do their work.
>             </comment>
>   <param name="fedora-system:1"
> value="fedora.server.access.internalservices.Bootstrap"/>
>   <param name="fedora-system:2"
> value="fedora.server.access.internalservices.BootstrapImpl"/>
>   <param name="fedora-system:3"
> value="fedora.server.access.internalservices.DefaultBehavior"/>
>   <param name="fedora-system:4"
> value="fedora.server.access.internalservices.DefaultBehaviorImpl"/>
>  </module>
>  <module role="fedora.server.search.FieldSearch"
> class="fedora.server.search.FieldSearchSQLModule">
>   <comment>
>         Description:
>           Supports the API-A simpleSearch and advancedSearch methods.
>         Parameters:
>           - maxResults (required, must be > 0)
>             The maximum number of records to return as the result of a
> search.
>             Even if a client requests more results at a time, this is the
>             cutoff value.
>           - maxSecondsPerSession (required, must be > 0)
>             The maximum number of seconds that the server guarantees
> subsequent
>             search results may be obtained.  This is only used in cases
> where
>             the number of results is greater than maxResults (as
> specified
>             by the server [above] or the client [in the search request])
>           - connectionPool (optional...to make unspecified, comment out
> or delete the whole param line as opposed to using an empty string,
> default=ConnectionPoolManager's default)
>             The connectionPool providing the connection to the database
> to
>             be used.
>          Warning:
>             When setting these values, keep in mind that while a session
>             is not timed out (maxSecondsPerSession seconds haven't
> elapsed,
>             and not all results have been requested), a connection from
> the
>             pool is tied up.  Therefore, the connectionPool should be at
> least
>             of size n, large enough to accomodate n simultaneous search
>             sessions.  The longer maxSecondsPerSession is, the more
> chance
>             you have of tying up all available connections from the pool.
>             Therefore, keep maxSecondsPerSession fairly low, but still
>             reasonable for an automated program or user to serially get
>             a long list of results, and make sure you have a
> connectionPool
>             large enough to accomodate your users.
>         </comment>
>   <param name="maxResults" value="100"/>
>   <param name="maxSecondsPerSession" value="100"/>
>   <param name="connectionPool" value="localMySQLPool"
> mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
>  </module>
>  <module role="fedora.oai.OAIProvider"
> class="fedora.server.oai.FedoraOAIProviderModule">
>   <comment>
>         Description:
>           Exposes the repository for OAI harvesters.</comment>
>         Parameters:
>           - repositoryName (required)
>             The name of the repository, to be given to OAI harvesters.
>           - repositoryDomainName (required)
>             The domain name of the repository, which helps to uniquely
> identify
>    items from the repository in OAI-PMH requests.  This should just
>    be the domain name of the organization that exposes the objects.
>    More information on the OAI identifier syntax can be found at
>    http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm
>           - adminEmails (required)
>             One or more space-separated email addresses, to be given to
> OAI harvesters.
>           - friends (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string)
>             A space-separated list of URLs to known OAI provider
> baseURLs.
>             This is OAI's provider discovery enabler.  Harvesters can
> use these to crawl OAI providers.
>           - maxRecords (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string,
> default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
>             The maximum number of results to return at a time for
> ListRecords requests.
>           - maxHeaders (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string,
> default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
>             The maximum number of results to return at a time for
> ListIdentifiers requests.
>   <param name="repositoryName" value="INFLIBNET Digital Repository
> System"/>
>   <param name="repositoryDomainName" value="rajesh.lo"/>
>   <param name="adminEmails" value="rajesh@..."/>
>   <param name="friends" value="http://arXiv.org/oai2
> http://memory.loc.gov/cgi-bin/oai2_0"/>
>   <param name="maxRecords" value="100"/>
>   <param name="maxHeaders" value="100"/>
>  </module>
>  <module role="fedora.server.storage.translation.DOTranslator"
> class="fedora.server.storage.translation.DOTranslatorModule">
>   <comment>Supports translation from DigitalObject to a stream of
>         some format, and vice-versa.  The parameters below specify
>         serializer/deserializer classes to be used for a given format.
>         Those classes must implement the DOSerializer/DODeserializer
>         interfaces.
>         </comment>
>   <param name="serializer_metslikefedora1"
> value="fedora.server.storage.translation.METSLikeDOSerializer"/>
>   <param name="deserializer_metslikefedora1"
> value="fedora.server.storage.translation.METSLikeDODeserializer"/>
>   <param name="serializer_metslikefedora1export"
> value="fedora.server.storage.translation.METSLikeExportDOSerializer"/>
>   <param name="deserializer_metslikefedora1export"
> value="fedora.server.storage.translation.METSLikeDODeserializer"/>
>  </module>
>  <module role="fedora.server.management.PIDGenerator"
> class="fedora.server.management.BasicPIDGenerator">
>   <comment>The pid generator.</comment>
>   <param name="pidgen_log_dir" value="pidgen"/>
>  </module>
>  <module role="fedora.server.storage.replication.DOReplicator"
> class="fedora.server.storage.replication.DefaultDOReplicator">
>   <comment>Supports synching data from definitive storage with
>         dissemination db.</comment>
>  </module>
>  <module role="fedora.server.storage.ConnectionPoolManager"
> class="fedora.server.storage.ConnectionPoolManagerImpl">
>   <comment>This module facilitates obtaining ConnectionPools</comment>
>   <param name="defaultPoolName" value="localMySQLPool"
> mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
>   <param name="poolNames" value="localMySQLPool"
> mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
>  </module>
>  <module role="fedora.server.validation.DOValidator"
> class="fedora.server.validation.DOValidatorModule">
>   <comment>
>   Description:
>   Supports validation of digital objects, including XML Schema
> validation (to METS schema),
>   Schematron validation (to Fedora Rules schema written in Schematron
> language), and (in future) other programatic validation
>   including referential integrity checking of existence and availability
> of distributed data and/or services.
>    Parameters:
>     - tempDir  (required):  this is a directory that the validation
> module can use as a work space, as when it must
>     write a temporary file.
>     - xmlSchema: this is local path for the Fedora-METS XML schema used
> to do XML schema validation of digital objects
>     - schematronPreprocessor:  this is the local path to the "skeleton"
> style sheet for schematron processing
>     - schematronSchema:  this is the local path to the Fedora Schematron
> Schema used to do Fedora-specific validation of digital objects.
>     This schema expresses integrity rules which are not covered by the
> Fedora-METS XML schema.
>         </comment>
>   <param name="tempDir" value="work"/>
>   <param name="xmlSchema" value="xsd/mets-fedora-ext.xsd"/>
>   <param name="schematronPreprocessor"
> value="schematron/preprocessor.xslt"/>
>   <param name="schematronSchema" value="schematron/fedoraRulesExt.xml"/>
>  </module>
>  <module role="fedora.server.storage.ExternalContentManager"
> class="fedora.server.storage.DefaultExternalContentManager">
>   <comment>This module facilitates obtaining external content via HTTP
>                 Parameters:
>                 - userAgent (optional...to make unspecified, comment out
> or delete the whole param line as opposed to using an empty string,
> default=Fedora): How to identify the
>                   Fedora server in HTTP requests.  This defaults to
> something
>                   reasonable, but if you want to provide more information
>                   (such as an admin email address) in the User-Agent HTTP
>                   request header, put it here.
>                 </comment>
>  </module>
>  <module role="fedora.server.utilities.ThreadMonitor"
> class="fedora.server.utilities.ThreadMonitorModule">
>   <comment>Prints basic information about the running threads to the
>             log periodically for diagnostic purposes.
>
>             Parameters:
>              - active (optional...to make unspecified, comment out or
> delete the whole param line as opposed to using an empty string,
> default=no): whether to activate this module.  "yes" or "true" activates
> it.
>              - pollInterval (optional...to make unspecified, comment out
> or delete the whole param line as opposed to using an empty string,
> default=10000): how many milliseconds to wait between each polling.
>             </comment>
>   <param name="active" value="false"/>
>   <param name="pollInterval" value="5000"/>
>  </module>
>  <datastore id="localMySQLPool">
>   <comment>MySQL database on localhost with db name of fedora12</comment>
>   <param name="dbUsername" value="fedoraAdmin"/>
>   <param name="dbPassword" value="fedoraAdmin"/>
>   <param name="jdbcURL"
> value="jdbc:mysql://localhost/fedora12?useUnicode=true&amp;characterEnco
> ding=UTF-8"/>
>   <param name="jdbcDriverClass" value="org.gjt.mm.mysql.Driver"/>
>   <param name="ddlConverter"
> value="fedora.server.utilities.MySQLDDLConverter"/>
>   <param name="minPoolSize" value="10"/>
>   <param name="maxPoolSize" value="100"/>
>  </datastore>
>  <datastore id="localMcKoiPool">
>   <comment>McKoi database on localhost running on port 9158</comment>
>   <param name="dbUsername" value="fedoraAdmin"/>
>   <param name="dbPassword" value="fedoraAdmin"/>
>   <param name="jdbcURL" value="jdbc:mckoi://192.168.1.15:9158/"/>
>   <param name="jdbcDriverClass" value="com.mckoi.JDBCDriver"/>
>   <param name="ddlConverter"
> value="fedora.server.utilities.McKoiDDLConverter"/>
>   <param name="minPoolSize" value="10"/>
>   <param name="maxPoolSize" value="100"/>
>  </datastore>
>  <datastore id="localOracle9iPool">
>   <comment>Oracle9i database on localhost with SID=fedora12</comment>
>   <param name="dbUsername" value="fedoraAdmin"/>
>   <param name="dbPassword" value="fedoraAdmin"/>
>   <param name="jdbcURL"
> value="jdbc:oracle:thin: <at> localhost:1521:fedora12"/>
>   <param name="jdbcDriverClass" value="oracle.jdbc.driver.OracleDriver"/>
>   <param name="ddlConverter"
> value="fedora.server.utilities.OracleDDLConverter"/>
>   <param name="minPoolSize" value="10"/>
>   <param name="maxPoolSize" value="100"/>
>  </datastore>
> </server>
>
> still I got same problem Servlet engine and
> ConnectionPoolNotFoundException. Please guide.
>
> Whe I stop the fedora server. It gets stop. but when I go to stop the
> McKoi database it gets me following error:
>
> java.sql.SQLException: Connection refused: Connect
> at com.mckoi.database.jdbc.TCPStreamDatabaseInterface.ConnectToDatabase:
> Unknown Source
> at com.mckoi.database.jdbc.MDriver.Connect(Unknown Source)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at java.sql.DriverManager.getConnection(Unknown Source)
> at com.mckoi.runtime.McKoiDBMain.doShutDown(Unknown Source)
> at com.mckoi.runtime.McKoiDBMain.main(Unknown Source)
>
> Finished.
>
> For your kind information. I am using Windows 2000 Advanced Server with
> ServicePack 1.
>
> regards,
> Rajesh
>
>
>
>
>
>
>
>

 --
Ronda A. Grizzle
Technical Coordinator, Fedora Project
Digital Library Research & Development
(voice)434-924-3965
(fax)434-924-1431

Rajesh Chandrakar | 9 Sep 06:57 2004
Picon

Re: [Fedora-users] Re: Servlet Engine and ConnectionPoolNotFoundException

Dear Ronda,

Thanks for reply.

----- Original Message -----
From: "Ronda A. Grizzle" <rag9b@...>
To: "Rajesh Chandrakar" <rajesh@...>;
<fedora-users@...>
Sent: Wednesday, September 08, 2004 9:03 PM
Subject: Re: [Fedora-users] Re: Servlet Engine and
ConnectionPoolNotFoundException

> Hello Rajesh,
>
> I have been consulting with the developers on your problems getting Fedora
> up and running. Thank you for including your system information.

I am thankful to you for addressing my problem to the developer.

> Since mysql 5.0 is an alpha release and has not been tested with the
> Fedora software, we suggest using a 4.0.x release, which are stable.

I will try with the MySQL 4.0.x release.

> The version of mysql that is packaged with Fedora 1.2 is a 3.23.x release,
> and the jdbc driver included with the software is suitable for that
> release. In order to upgrade to a 4.0.x version, you will need to change
> out the jdbc driver per the instructions found here:
> <http://www.fedora.info/wiki/bin/view/Fedora/MySQLVersion4>.

I modified accordingly in source and distribution directory after
downloading the concerned driver from the mysql website. Still same problem
I am getting.

> With regard to your mckoi question: there is no way that I know of to
> retrieve the username and password that you used to initialize mckoi. I
> would suggest that you stop the mckoi database with mckoi-stop, delete the
> mckoi094/data directory and its contents, and reinitialize the database
> with mckoi-init, remembering if you use a dbusername and db password that
> is different from the default to change the username/password in the jdbc
> driver section to match those used to initialize the database.

I deleted the mckoi data directory and reinitialized it with the default
login and password (i.e. fedoraAdmin). Still same problem persist. This I
did after upgrading the service pack with version 4. One more time I will
try this for sake of myself.

with profound regards,
Rajesh

> Please let me know of any further problems that you have getting started
> with Fedora.
>
> Best regards,
> Ronda
>
> --On Wednesday, 08 September, 2004 5:38 PM +0530 Rajesh Chandrakar
> <rajesh@...> wrote:
>
> >
> > Dear Ronda,
> >
> > I tried to use the MySQL version 5.0 database instead of McKoi. The same
> > error, I am getting. Will you please help me, what problem it is? I am
> > very much interested to implement FEDORA Repository in my Centre. For
> > your kind information, I am using:
> >
> > Microsoft Windows 2000 Advance Server
> > I upgraded the server pack with 4
> > Java Version 1.4.2
> > Fedora Version 1.2
> > My SQL Version 5.0
> >
> > Please guide me.
> >
> > Rajesh
> >
> >
> >
> > ----- Original Message -----
> > From: Rajesh Chandrakar
> > To: fedora-users@...
> > Sent: Saturday, September 04, 2004 12:37 PM
> > Subject: Servlet Engine and ConnectionPoolNotFoundException
> >
> >
> > Dear Mr. Ronda,
> >
> > I deleted the complete installation of fedora server, client and src
> > development. And reinstalled the fedora. As per the instrunction, I did
> > ant serverdist process from c:\fedora-1.2-src directory (FEDORA_DEV
> > directory). Then I initialised the McKoi databsae from C:\ directory by
> > following command:
> >
> > mckoi-init fedoraAdmin fedoraAdmin
> >
> > got message DBInstalled and finished.
> >
> > Now I modified the fedora.fcfg, you may please look at it as follows
> > <?xml version="1.0" encoding="UTF-8"?>
> > <server xmlns="http://www.fedora.info/definitions/1/0/config/"
> > xmlns:fedora-config="http://www.fedora.info/definitions/1/0/config/"
> > class="fedora.server.BasicServer">
> >  <param name="repositoryName" value="Fedora Repository 1"/>
> >  <comment>Defines a human readable name for the Fedora server; default
> > is Fedora Repository.</comment>
> >  <param name="adminEmailList" value="rajesh@..."/>
> >  <comment>Defines one or more email addresses for server administrators;
> > list is space delimited.</comment>
> >  <param name="adminPassword" value="fedoraAdmin"/>
> >  <comment>Defines the password for the Fedora server; default is
> > fedoraAdmin.</comment>
> >  <param name="log_max_size" value="5242880"/>
> >  <comment>Defines the threshold at which a new log file is generated
> > based on the size of the current log file in bytes; default is 5242880
> > bytes.</comment>
> >  <param name="log_max_days" value="7"/>
> >  <comment>Defines the threshold at which a new log file is generated
> > based on number of days since the server was started in days; default is
> > 7 days.</comment>
> >  <param name="log_dir" value="logs"/>
> >  <comment>Defines the directory in which the Fedora logs will be
> > written; default is logs.</comment>
> >  <param name="log_level" value="finest"/>
> >  <comment>Defines the level of logging desired;default is finest;
> > possible levels include:
> >   - config
> >    denotes logging indicating what occurred during the server's (or a
> > module's) configuration phase.
> >   - fine
> >    denotes logging indicating basic information about a request to the
> > server (like hostname, operation name, and success or failure).
> >   - finer
> >    denotes logging indicating detailed information about a request to
> > the server (like the full request, full response, and timing
> > information).
> >   - finest (deafult)
> >    denotes logging indicating method entry/exit or extremely verbose
> > information intended to aid in debugging.
> >   - info
> >    denotes logging indicating that something relatively uncommon and
> > interesting happened, like server or module startup or shutdown, or a
> > periodic job.
> >   - warning
> >    denotes logging indicating that an undesired (but non-fatal)
> > condition occurred.
> >   - severe
> >    denotes logging indicating that the server is inoperable or unable to
> > start.
> >  </comment>
> >  <param name="log_flush_threshold" value="1"/>
> >  <comment>Defines the flush threshold for logging in number of records;
> > default is one log record.</comment>
> >  <param name="path_algorithm"
> > value="fedora.server.storage.lowlevel.TimestampPathAlgorithm"/>
> >  <comment>Defines the java class used to determine the path algorithm
> > for LowLevelStorage;
> >   default is fedora.server.storage.lowlevel.TimestampPathAlgorithm.
> >  </comment>
> >  <param name="file_system"
> > value="fedora.server.storage.lowlevel.GenericFileSystem"/>
> >  <comment>Defines the java class that determines the type of
> > implementation for LowLevelStorage;
> >   default is fedora.server.storage.lowlevel.GenericFileSystem.
> >  </comment>
> >  <param name="registry"
> > value="fedora.server.storage.lowlevel.DBPathRegistry"/>
> >  <comment>Defines the java class used to determine the path registry for
> > LowLevelStorage;
> >   default is fedora.server.storage.lowlevel.DBPathRegistry.
> >  </comment>
> >  <param name="backslash_is_escape" value="yes" oraclevalue="no"/>
> >  <comment>Defines whether the backing database (which include registry
> > tables) the backslash character
> >   to be the escape character (token beginning an escape sequence).  This
> > is needed to correctly
> >   store and retrieve filepaths from the registry tables, if running
> > under Windows/DOS.
> >  </comment>
> >  <param name="object_store_base" value="C:\fedora1_2_objects"/>
> >  <comment>Defines the root directory for the internal storage of Fedora
> > objects.
> >   This value should be adjusted based on your installation environment;
> >   default assumes a Windows installation of C:\fedora1_2_objects.
> >  </comment>
> >  <param name="temp_store_base" value="C:\fedora1_2_temp"/>
> >  <comment>Defines the root directory for Fedora temporary storage.
> >   This value should be adjusted based on your installation environment;
> >   default assumes a Windows installation of C:\fedora1_2_temp.
> >  </comment>
> >  <param name="datastream_store_base" value="C:\fedora1_2_datastreams"/>
> >  <comment>Defines the root directory for the internal storage of Managed
> > Content datastreams.
> >   This value should be adjusted based on your installation environment;
> >   default assumes a Windows installation of C:\fedora1_2_datastreams.
> >  </comment>
> >  <param name="debug" value="false"/>
> >  <comment>A boolean toggle used to turn off/on internal debugging in the
> > code.</comment>
> >  <param name="datastreamExpirationLimit" value="300"/>
> >  <comment>
> >   Controls the size of the datastream mediation hash by removing entries
> > outside the specified threshold.
> >   The value is specified in seconds.
> >   Note this value must be greater than the limit specified for the
> > datastreamMediationLimit.
> >  </comment>
> >  <param name="datastreamMediationLimit" value="5000"/>
> >  <comment>
> >   Determines the time interval in which external mechanisms must respond
> > to requests by the Fedora server.
> >    The value is specified in milliseconds.
> >   The value specified should be set high enough to allow for an average
> > response time from any single external mechanisms.
> >   Note this value must be less than the limit specified for the
> > datastreamExpirationLimit.
> >  </comment>
> >  <param name="fedoraServerPort" value="8080"/>
> >  <comment>Defines the port number on which the Fedora server runs;
> > default is 8080.</comment>
> >  <param name="fedoraShutdownPort" value="8005"/>
> >  <comment>Defines the port number used to shutdown the Fedora sever;
> > default is 8005.</comment>
> >  <param name="fedoraRedirectPort" value="8443"/>
> >  <comment>Defines the redirect port of the Fedora sever; default is
> > 8443.</comment>
> >  <param name="fedoraServerHost" value="192.168.1.15"/>
> >  <comment>Defines the host name for the Fedora server, as seen from the
> > outside world.</comment>
> >  <module role="fedora.server.storage.DOManager"
> > class="fedora.server.storage.DefaultDOManager">
> >   <comment>
> >         Description:
> >           The interface to the storage subsystem.  This provides
> >           context-appropriate DOReaders and DOWriters for reflecting on
> > and
> >           writing to the objects stored in the repository.  It also
> >           provides methods for reflecting on the contents of the
> > repository
> >           as a whole.  This implementation uses
DefinitiveDOReader/Writer
> >           for an "application" of "apim" and a FastDOReader/Writer
> >           for an "application" of "apia" (from the Context).  Other
> >           context-specific logic TBD.
> >         Parameters:
> >         - pidNamespace (required)
> >           This is the namespace id for pids of newly-created objects.
> >           This should be unique for a repository.
> >           It can be from 1 to 17 characters, and may only contain
> >           A-Z, a-z, 0-9, and '-' (dash).
> >         - retainPIDs [default="demo test"]
> >           Namespaces of PIDs to retain during the ingest process.
> >           When an object is ingested, Fedora normally allocates a unique
> > PID
> >           within pidNamespace for it regardless of what the object says
> > its
> >           PID is.  This option provides a way to override that behavior
> > on
> >           a per-pid-namespace basis.  If specified, this should be a
> >           space-delimited list of pid namespaces that will be accepted
> > in the
> >           object as-is.
> >         - storagePool [default=default provided by the
> > ConnectionPoolManager]
> >           The named connection pool from which read/write
> >           database connections are to be provided for the storage
> >           subsystem (see the ConnectionPoolManager module)
> >         - storageFormat (required)
> >           The format in which internal serializations of digital objects
> >           are to be written.  There must exist a correspondingly
> >           named serializer-deserializer pair in the DOTranslator module.
> >         - storageCharacterEncoding [default=UTF-8]
> >           If the serialization format is text-based,
> >           this is the character encoding that should be used.</comment>
> >         - exportFormat (required)
> >           The format in which external serializations of digital objects
> >           are to be written.  There must exist a correspondingly
> >           named serializer-deserializer pair in the DOTranslator module.
> >   <param name="pidNamespace" value="111"/>
> >   <param name="retainPIDs" value="demo test changeme"/>
> >   <param name="storagePool" value="localMySQLPool"
> > mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
> >   <param name="storageFormat" value="metslikefedora1"/>
> >   <param name="exportFormat" value="metslikefedora1export"/>
> >   <param name="storageCharacterEncoding" value="UTF-8"/>
> >  </module>
> >  <module role="fedora.server.management.Management"
> > class="fedora.server.management.DefaultManagement">
> >   <comment>
> >         Description:
> >           The management subsystem.
> >           This implements the methods necessary to fulfill API-M
> >           requests without regard to:
> >             - how the service is exposed
> >             - how bytestreams and java types might be
> > marshalled/demarshalled
> >               over the wire
> >             - how the storage subsystem is implemented.
> >         Parameters:
> >             - allowHosts (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string)
> >               A comma-separated list of IP ranges that the client's
> > address
> >               is compared to. If this is specified, the remote address
> >               must match for any Management request to be accepted.
> >               If this is not specified, all requests will be accepted
> > unless
> >               the remote address matches a deny pattern.
> >             - denyHosts (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string)
> >               A comma-separated list of IP ranges that the client's
> > address
> >               is compared to. If this is specified, the remote address
> >               must not match for any Management request to be accepted.
> >               If this is not specified, request acceptance is governed
> >               solely by the allowHosts parameter.
> >         </comment>
> >   <param name="allowHosts" value="192.168.1.1-192.168.1.255"/>
> >  </module>
> >  <module role="fedora.server.access.Access"
> > class="fedora.server.access.DefaultAccess">
> >   <comment>
> >         Description:
> >           The access subsystem.
> >           This implements the methods necessary to fulfill API-A
> >           requests without regard to:
> >             - how the service is exposed
> >             - how bytestreams and java types might be
> > marshalled/demarshalled
> >               over the wire
> >             - how the storage subsystem is implemented.
> >         Parameters:
> >             - allowHosts (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string)
> >               A comma-separated list of IP ranges that the client's
> > address
> >               is compared to. If this is specified, the remote address
> >               must match for any Management request to be accepted.
> >               If this is not specified, all requests will be accepted
> > unless
> >               the remote address matches a deny pattern.
> >             - denyHosts (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string)
> >               A comma-separated list of IP ranges that the client's
> > address
> >               is compared to. If this is specified, the remote address
> >               must not match for any Management request to be accepted.
> >               If this is not specified, request acceptance is governed
> >               solely by the allowHosts parameter.
> >             - doMediateDatastreams (required)
> >               A boolean switch indicating whether Datastream Mediation
> > is activated or not.
> >               Datastream Mediation provides additional repository
> > security by not exposing
> >               the actual physical location of Referenced Content
> > datastreams to external
> >               mechanisms(services). Instead of exposing the actual
> > physical location of
> >               Referenced Content datastreams , Datastream Mediation
> > functions as a proxy
> >               requiring all external services to communicate through the
> > Fedora server to
> >               resolve the location of Referenced Content datastreams.
> > For Datastream
> >               Mediation to function, the Fedora server must be internet
> > accessible on its
> >               designated port by any potential external service. This
> > requirement can be
> >               difficult to satisfy if the Fedora server is located
> > behind a firewall and
> >               you do not have ready access to the firewall's
> > configuration to enable the
> >               required access. If the Fedora server is behind a firewall
> > and you have no
> >               access to the firewall's configuration, you can disable
> > Datastream Mediation
> >               which will allow external services to access Referenced
> > Content datastreams
> >               using their actual physical locations. Managed Content and
> > XMLMetadata
> >               datastreams are stored internally in the Fedora repository
> > and can only be
> >               accessed through the Fedora server so disabling Datastream
> > Mediation has no
> >               effect on these types of datastreams. Disabling Datastream
> > Mediation exposes
> >               the physical location of Referenced Content datastream to
> > external services
> >               which can result in unintended access to the raw
> > datastreams by surreptitious
> >               external mechanisms. It is recommended that Datastream
> > Mediation be disabled
> >               only for testing or cases where this security issue is not
> > a concern. The
> >               default value of doMediateDatastreams is true.
> >             </comment>
> >   <param name="doMediateDatastreams" value="false"/>
> >  </module>
> >  <module role="fedora.server.access.DynamicAccess"
> > class="fedora.server.access.DynamicAccessModule">
> >   <comment>
> >         Description:
> >           The dynamic behavior module for the access subsystem.
> >           This implements the methods necessary to fulfill API-A
> >           requests without regard to:
> >              - dynamically associating a default behavior definition and
> > mechanism with objects
> >            - (Future) dynamically associating other behavior definitions
> > and mechanisms with objects
> >            - running disseminations of dynamic behaviors
> >         Parameters:
> >             - fedora-system:1
> >               The interface that defines the methods of the bootstrap
> >               disseminator.  These methods are "built-in" to the Fedora
> >               system, and are dynamically associated with every
> >               behavior definition and behavior mechanism object.
> >             - fedora-system:2
> >               The class that implements the methods of the bootstrap
> >               disseminator.  These method implementations are "built-in"
> >               to the Fedora system, and are dynamically associated with
> >               every behavior definition and behavior mechanism object.
> >               This class can be though of as implementing
> >               an "internal service" whereas other disseminators use
> >               external services (described by WSDL) to do their work.
> >             - fedora-system:3
> >               The interface that defines the methods of the default
> >               disseminator.  These methods are "built-in" to the Fedora
> >               system, and are dynamically associated with every object.
> >             - fedora-system:4
> >               The class that implements the methods of the default
> >               disseminator.  These method implementations are "built-in"
> >               to the Fedora system, and are dynamically associated with
> >               every object.  This class can be though of as implementing
> >               an "internal service" whereas other disseminators use
> >               external services (described by WSDL) to do their work.
> >             </comment>
> >   <param name="fedora-system:1"
> > value="fedora.server.access.internalservices.Bootstrap"/>
> >   <param name="fedora-system:2"
> > value="fedora.server.access.internalservices.BootstrapImpl"/>
> >   <param name="fedora-system:3"
> > value="fedora.server.access.internalservices.DefaultBehavior"/>
> >   <param name="fedora-system:4"
> > value="fedora.server.access.internalservices.DefaultBehaviorImpl"/>
> >  </module>
> >  <module role="fedora.server.search.FieldSearch"
> > class="fedora.server.search.FieldSearchSQLModule">
> >   <comment>
> >         Description:
> >           Supports the API-A simpleSearch and advancedSearch methods.
> >         Parameters:
> >           - maxResults (required, must be > 0)
> >             The maximum number of records to return as the result of a
> > search.
> >             Even if a client requests more results at a time, this is
the
> >             cutoff value.
> >           - maxSecondsPerSession (required, must be > 0)
> >             The maximum number of seconds that the server guarantees
> > subsequent
> >             search results may be obtained.  This is only used in cases
> > where
> >             the number of results is greater than maxResults (as
> > specified
> >             by the server [above] or the client [in the search request])
> >           - connectionPool (optional...to make unspecified, comment out
> > or delete the whole param line as opposed to using an empty string,
> > default=ConnectionPoolManager's default)
> >             The connectionPool providing the connection to the database
> > to
> >             be used.
> >          Warning:
> >             When setting these values, keep in mind that while a session
> >             is not timed out (maxSecondsPerSession seconds haven't
> > elapsed,
> >             and not all results have been requested), a connection from
> > the
> >             pool is tied up.  Therefore, the connectionPool should be at
> > least
> >             of size n, large enough to accomodate n simultaneous search
> >             sessions.  The longer maxSecondsPerSession is, the more
> > chance
> >             you have of tying up all available connections from the
pool.
> >             Therefore, keep maxSecondsPerSession fairly low, but still
> >             reasonable for an automated program or user to serially get
> >             a long list of results, and make sure you have a
> > connectionPool
> >             large enough to accomodate your users.
> >         </comment>
> >   <param name="maxResults" value="100"/>
> >   <param name="maxSecondsPerSession" value="100"/>
> >   <param name="connectionPool" value="localMySQLPool"
> > mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
> >  </module>
> >  <module role="fedora.oai.OAIProvider"
> > class="fedora.server.oai.FedoraOAIProviderModule">
> >   <comment>
> >         Description:
> >           Exposes the repository for OAI harvesters.</comment>
> >         Parameters:
> >           - repositoryName (required)
> >             The name of the repository, to be given to OAI harvesters.
> >           - repositoryDomainName (required)
> >             The domain name of the repository, which helps to uniquely
> > identify
> >    items from the repository in OAI-PMH requests.  This should just
> >    be the domain name of the organization that exposes the objects.
> >    More information on the OAI identifier syntax can be found at
> >    http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm
> >           - adminEmails (required)
> >             One or more space-separated email addresses, to be given to
> > OAI harvesters.
> >           - friends (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string)
> >             A space-separated list of URLs to known OAI provider
> > baseURLs.
> >             This is OAI's provider discovery enabler.  Harvesters can
> > use these to crawl OAI providers.
> >           - maxRecords (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string,
> > default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
> >             The maximum number of results to return at a time for
> > ListRecords requests.
> >           - maxHeaders (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string,
> > default=FieldSearch:maxResults, imposed maximum=FieldSearch:maxResults)
> >             The maximum number of results to return at a time for
> > ListIdentifiers requests.
> >   <param name="repositoryName" value="INFLIBNET Digital Repository
> > System"/>
> >   <param name="repositoryDomainName" value="rajesh.lo"/>
> >   <param name="adminEmails" value="rajesh@..."/>
> >   <param name="friends" value="http://arXiv.org/oai2
> > http://memory.loc.gov/cgi-bin/oai2_0"/>
> >   <param name="maxRecords" value="100"/>
> >   <param name="maxHeaders" value="100"/>
> >  </module>
> >  <module role="fedora.server.storage.translation.DOTranslator"
> > class="fedora.server.storage.translation.DOTranslatorModule">
> >   <comment>Supports translation from DigitalObject to a stream of
> >         some format, and vice-versa.  The parameters below specify
> >         serializer/deserializer classes to be used for a given format.
> >         Those classes must implement the DOSerializer/DODeserializer
> >         interfaces.
> >         </comment>
> >   <param name="serializer_metslikefedora1"
> > value="fedora.server.storage.translation.METSLikeDOSerializer"/>
> >   <param name="deserializer_metslikefedora1"
> > value="fedora.server.storage.translation.METSLikeDODeserializer"/>
> >   <param name="serializer_metslikefedora1export"
> > value="fedora.server.storage.translation.METSLikeExportDOSerializer"/>
> >   <param name="deserializer_metslikefedora1export"
> > value="fedora.server.storage.translation.METSLikeDODeserializer"/>
> >  </module>
> >  <module role="fedora.server.management.PIDGenerator"
> > class="fedora.server.management.BasicPIDGenerator">
> >   <comment>The pid generator.</comment>
> >   <param name="pidgen_log_dir" value="pidgen"/>
> >  </module>
> >  <module role="fedora.server.storage.replication.DOReplicator"
> > class="fedora.server.storage.replication.DefaultDOReplicator">
> >   <comment>Supports synching data from definitive storage with
> >         dissemination db.</comment>
> >  </module>
> >  <module role="fedora.server.storage.ConnectionPoolManager"
> > class="fedora.server.storage.ConnectionPoolManagerImpl">
> >   <comment>This module facilitates obtaining ConnectionPools</comment>
> >   <param name="defaultPoolName" value="localMySQLPool"
> > mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
> >   <param name="poolNames" value="localMySQLPool"
> > mckoivalue="localMcKoiPool" oraclevalue="localOracle9iPool"/>
> >  </module>
> >  <module role="fedora.server.validation.DOValidator"
> > class="fedora.server.validation.DOValidatorModule">
> >   <comment>
> >   Description:
> >   Supports validation of digital objects, including XML Schema
> > validation (to METS schema),
> >   Schematron validation (to Fedora Rules schema written in Schematron
> > language), and (in future) other programatic validation
> >   including referential integrity checking of existence and availability
> > of distributed data and/or services.
> >    Parameters:
> >     - tempDir  (required):  this is a directory that the validation
> > module can use as a work space, as when it must
> >     write a temporary file.
> >     - xmlSchema: this is local path for the Fedora-METS XML schema used
> > to do XML schema validation of digital objects
> >     - schematronPreprocessor:  this is the local path to the "skeleton"
> > style sheet for schematron processing
> >     - schematronSchema:  this is the local path to the Fedora Schematron
> > Schema used to do Fedora-specific validation of digital objects.
> >     This schema expresses integrity rules which are not covered by the
> > Fedora-METS XML schema.
> >         </comment>
> >   <param name="tempDir" value="work"/>
> >   <param name="xmlSchema" value="xsd/mets-fedora-ext.xsd"/>
> >   <param name="schematronPreprocessor"
> > value="schematron/preprocessor.xslt"/>
> >   <param name="schematronSchema" value="schematron/fedoraRulesExt.xml"/>
> >  </module>
> >  <module role="fedora.server.storage.ExternalContentManager"
> > class="fedora.server.storage.DefaultExternalContentManager">
> >   <comment>This module facilitates obtaining external content via HTTP
> >                 Parameters:
> >                 - userAgent (optional...to make unspecified, comment out
> > or delete the whole param line as opposed to using an empty string,
> > default=Fedora): How to identify the
> >                   Fedora server in HTTP requests.  This defaults to
> > something
> >                   reasonable, but if you want to provide more
information
> >                   (such as an admin email address) in the User-Agent
HTTP
> >                   request header, put it here.
> >                 </comment>
> >  </module>
> >  <module role="fedora.server.utilities.ThreadMonitor"
> > class="fedora.server.utilities.ThreadMonitorModule">
> >   <comment>Prints basic information about the running threads to the
> >             log periodically for diagnostic purposes.
> >
> >             Parameters:
> >              - active (optional...to make unspecified, comment out or
> > delete the whole param line as opposed to using an empty string,
> > default=no): whether to activate this module.  "yes" or "true" activates
> > it.
> >              - pollInterval (optional...to make unspecified, comment out
> > or delete the whole param line as opposed to using an empty string,
> > default=10000): how many milliseconds to wait between each polling.
> >             </comment>
> >   <param name="active" value="false"/>
> >   <param name="pollInterval" value="5000"/>
> >  </module>
> >  <datastore id="localMySQLPool">
> >   <comment>MySQL database on localhost with db name of
fedora12</comment>
> >   <param name="dbUsername" value="fedoraAdmin"/>
> >   <param name="dbPassword" value="fedoraAdmin"/>
> >   <param name="jdbcURL"
> > value="jdbc:mysql://localhost/fedora12?useUnicode=true&amp;characterEnco
> > ding=UTF-8"/>
> >   <param name="jdbcDriverClass" value="org.gjt.mm.mysql.Driver"/>
> >   <param name="ddlConverter"
> > value="fedora.server.utilities.MySQLDDLConverter"/>
> >   <param name="minPoolSize" value="10"/>
> >   <param name="maxPoolSize" value="100"/>
> >  </datastore>
> >  <datastore id="localMcKoiPool">
> >   <comment>McKoi database on localhost running on port 9158</comment>
> >   <param name="dbUsername" value="fedoraAdmin"/>
> >   <param name="dbPassword" value="fedoraAdmin"/>
> >   <param name="jdbcURL" value="jdbc:mckoi://192.168.1.15:9158/"/>
> >   <param name="jdbcDriverClass" value="com.mckoi.JDBCDriver"/>
> >   <param name="ddlConverter"
> > value="fedora.server.utilities.McKoiDDLConverter"/>
> >   <param name="minPoolSize" value="10"/>
> >   <param name="maxPoolSize" value="100"/>
> >  </datastore>
> >  <datastore id="localOracle9iPool">
> >   <comment>Oracle9i database on localhost with SID=fedora12</comment>
> >   <param name="dbUsername" value="fedoraAdmin"/>
> >   <param name="dbPassword" value="fedoraAdmin"/>
> >   <param name="jdbcURL"
> > value="jdbc:oracle:thin: <at> localhost:1521:fedora12"/>
> >   <param name="jdbcDriverClass"
value="oracle.jdbc.driver.OracleDriver"/>
> >   <param name="ddlConverter"
> > value="fedora.server.utilities.OracleDDLConverter"/>
> >   <param name="minPoolSize" value="10"/>
> >   <param name="maxPoolSize" value="100"/>
> >  </datastore>
> > </server>
> >
> > still I got same problem Servlet engine and
> > ConnectionPoolNotFoundException. Please guide.
> >
> > Whe I stop the fedora server. It gets stop. but when I go to stop the
> > McKoi database it gets me following error:
> >
> > java.sql.SQLException: Connection refused: Connect
> > at com.mckoi.database.jdbc.TCPStreamDatabaseInterface.ConnectToDatabase:
> > Unknown Source
> > at com.mckoi.database.jdbc.MDriver.Connect(Unknown Source)
> > at java.sql.DriverManager.getConnection(Unknown Source)
> > at java.sql.DriverManager.getConnection(Unknown Source)
> > at com.mckoi.runtime.McKoiDBMain.doShutDown(Unknown Source)
> > at com.mckoi.runtime.McKoiDBMain.main(Unknown Source)
> >
> > Finished.
> >
> > For your kind information. I am using Windows 2000 Advanced Server with
> > ServicePack 1.
> >
> > regards,
> > Rajesh
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>  --
> Ronda A. Grizzle
> Technical Coordinator, Fedora Project
> Digital Library Research & Development
> (voice)434-924-3965
> (fax)434-924-1431

jpb | 9 Sep 22:29 2004

[Fedora-users] [PATCH] New "economic" information management mechanism implemented in fedora-1.2.1

Hello,
   Thank you for your hard work on Fedora!
   I include with this email a patch implementing (in monstrously ugly
fashion :) what I believe is a new idea in information management.  The
patch implements three new methods in the Fedora-API-M: certifyIngest,
exchangeCertificate, and verifyCertificate.  certifyIngest is a method
that returns, in addition to the PID that ingestObject returns, a
series of tokens in XML format representing the submitted information.
   The point of the certifyIngest method is to provide submitters with
scarce tokens of ownership, which can be traded in economic processes
to establish the value of the underlying information.  In effect, this
makes every certified document into its own currency system.  This, I
believe, will also make it possible to apply mechanisms from financial
engineering to the management of information.  That's the idea,
anyway... this is a first step toward that goal.
   The exchangeCertificate method allows holders of the tokens (or
"information currency units") to exchange those tokens to ensure that
they are the only holder after a trade. The verifyCertificate method
takes an XML document providing the digest value of a secret
certification information value, and responds with a "valid" or
"invalid" response.
   The value of the certificates is (will be :) highly dependent on the
stability and security of the issuing system, and other factors as
well, but virtually all of the matters related to their issuance, to
say nothing of their use, remain to be addressed.
   Any response besides the expected resounding yawn will be welcomed! :)
   Thanks again for your hard work!

   J. Patrick Bedell
   jpb@...

P.S.: The patch applies cleanly to last night's Fedora-1.2.1, available at
http://www.fedora.info/nightlydist... I haven't tested the release
version, though.  Go into the unzipped fedora-1.2.1-src directory and use
"patch -p1 < patch-fedora-ic-1.2.1".  Good luck, and please feel free to
contact me if you would like any help or have any suggestions!

P.P.S.:  There is also a servlet implementing a getSeriesInfo method for
the  (modified) Fedora-API-M-Lite REST interface.

Here are examples of the information currency series and verifycert
documents:

<ics>
<ic>
<sid>http://www.openteaching.com:8080/fedora/mgmt/getSeriesInfo?seriesID=ef2d7126384a00bdcfa885a27c743f8d338860d5</sid>
<sig>aec2a52ba30172ee57490433e7ec44065dace773f9b3f780a382df2dbb3f15276185b92045b61c0e72ee5f76fddc6b4806abeca60ad9407f8ccebbabbbfaac7642cdc542f9ed236a66f377d9bada8482073423e950cba2bf024470ee2a035a1d756c2ac610d9ab2f2f9de5e57ebcd3bd8a6aade435deb9e897515ba829378111</sig>
</ic>
<ic>
<sig>d6863dd54a80330998698d322a72b5ccdd4288cd7510a1d1336f60471040e92705da8c9a6888c66149b3bd15f03cf03300d4ea0f1435da9100e824eed44b506fb87f30a2acb89da25dd42d63a405c9628fad51254d3c6413dffe9f2af9944f3d53c571a5d7b5d9ab99125da0237e0e596857e12027f9615d57b446ce31a1d306</sig>
</sig>
<sid>http://www.openteaching.com:8080/fedora/mgmt/getSeriesInfo?seriesID=ef2d7126384a00bdcfa885a27c743f8d338860d5
</sid>
</ic>
</ics>

<verifycert>
<sid>http://www.openteaching.com:8080/fedora/mgmt/getSeriesInfo?seriesID=ef2d7126384a00bdcfa885a27c743f8d338860d5
</sid>
<digest>226e7b26c652a0259f414d6563ddea6eb39d8f19
</digest>
</verifycert>

Attachment (patch-fedora-ic-1.2.1): application/octet-stream, 0 bytes
jpb | 9 Sep 22:48 2004

[Fedora-users] Re: [PATCH] New "economic" information management mechanism implemented in fedora-1.2.1

   It appears that the patch was not included correctly with the first
email.  The patch should be correctly included this time... sorry for
the mistake!

   J. Patrick Bedell
   jpb@...

> Hello,
>    Thank you for your hard work on Fedora!
>    I include with this email a patch implementing (in monstrously ugly
> fashion :) what I believe is a new idea in information management.
...
Attachment (patch-fedora-ic-1.2.1): application/octet-stream, 66 KiB
Rajesh Chandrakar | 15 Sep 15:15 2004
Picon

[Fedora-users] what next?

Dear Ronda,
 
Now, I could able to install the fedora 1.2 with MySql 4.0. And is working fine. I could able to get the webaddress like http://rajesh:8080/fedora/describe/  and search pages. After ingesting the fedora-ingest-demo, I am able to browse the fedora demo.
 
But I am bit confussed about how to ingest the articles on the fedora. As I went through the fedora-admin and I could able to get the application window on screen. But, I am not able to get the exact step to go ahead with ingesting the digital full text articles basically I have the PDF files which I would like put on it. Please guide. I tried to look at the documents availabl on web, I couldn't understand exacately. It would be better if you can tell me the steps, how to go about it.
 
thanking you in advance.
 
with regards,
rajesh
 
 
Jürgen Zauner | 16 Sep 10:50 2004
Picon

[Fedora-users] Media Asset Management with Fedora

Hello!

The features of fedore look very impressive and interesting. The
installation of Fedora has been very easy.
So, we have decided to use Fedora for media asset management project.
One of our application requirements
is to search for a specific media type like (audio, video, image or
document) and to restrict the search on
several selected categories like "nature", "animals", "mountains",
"austria", "upper-austria" (which would be
for example a subcategory of "austria").
The problem is that i have not yet figured out a way to do this with Fedora.
Maybe someone can give me some "how-to"-tips.

Best regards,
Juergen Zauner


Gmane