You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-users@xml.apache.org by Øyvind Vestavik <Oy...@idi.ntnu.no> on 2002/03/12 20:14:45 UTC
Startup problems. No error message description
I try to start up xindice, but can't seem to understand what is going
wrong. If someone has an idea as to what causes this... :-)
Im using jdk1.3:
[fadm@fenris]java -version
java version "1.3.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02)
Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode)
(what does mixes mode mean?)
And have added the following to my local profile:
if [ -e "/usr/flocal/etc/fenris_profile" ]; then
source /usr/flocal/etc/fenris_profile
export JAVA_HOME=/usr/flocal/opt/jdk1.3
export XINDICE_HOME=/usr/flocal/opt/xindice
export PATH=.:/usr/flocal/opt/jdk1.3/bin:/usr/flocal/opt/jdk1.3:/usr/flocal/opt/xindice/bin/:$PATH
export CLASSPATH=/usr/flocal/opt/xindice/java/lib/openorb-1.2.0.jar:$CLASSPATH
fi
This is the entire response I get when starting xindice
[fadm@fenris]/usr/flocal/opt/xindice: start
Xindice Loader
==============
Environment
-----------
XINDICE_HOME = /usr/flocal/opt/xindice
CLASSPATH =
/usr/flocal/opt/xindice/java/lib/xmldb.jar:/usr/flocal/opt/xindice/java/lib/xmldb-xupdate.jar:
/usr/flocal/opt/xindice/java/lib/xmldb-sdk.jar:/usr/flocal/opt/xindice/java/lib/xml-apis-1.0.jar:
/usr/flocal/opt/xindice/java/lib/xindice.jar:/usr/flocal/opt/xindice/java/lib/xerces-1.4.3.jar:
/usr/flocal/opt/xindice/java/lib/xalan-2.0.1.jar:/usr/flocal/opt/xindice/java/lib/openorb_tools-1.2.0.jar:
/usr/flocal/opt/xindice/java/lib/openorb-1.2.0.jar:/usr/flocal/opt/xindice/java/lib/infozone-tools.jar:
/usr/flocal/opt/xindice/java/lib/examples.jar:/usr/flocal/opt/xindice/java/lib/ant-1.4.1.jar:
/usr/flocal/opt/xindice/classgen:/usr/flocal/opt/xindice/config:/usr/flocal/opt/xindice/java/lib/openorb-1.2.0.jar:
/usr/flocal/opt/vbroker/lib/migration.jar:/usr/flocal/opt/vbroker/lib/vbdev.jar:/usr/flocal/opt/vbroker/lib/vbjdev.jar:
/usr/flocal/opt/vbroker/lib/vbjorb.jar:/usr/flocal/opt/oracle/8.1.6./jdbc/lib/classes12.zip:
/usr/flocal/opt/oracle/8.1.6./jdbc/lib/jndi.zip:/usr/flocal/opt/oracle/8.1.6./jdbc/lib/jta.zip:
/usr/flocal/opt/oracle/8.1.6./jdbc/lib/nls_charset12.zip:/usr/flocal/opt/versant/jvi/2.4.0/lib/jvi2.4.0-jdk1.1.jar:
/usr/flocal/opt/versant/jvi/2.4.0/lib/jgl3.0.0.jar:/usr/flocal/opt/versant/jvi/2.4.0/lib/oromatcher1.1.jar:
/usr/flocal/opt/versant/jvi/2.4.0/lib/jtaxa0.9.jar:.:/usr/flocal/opt/hs/hcj/handle.jar:
Starting Xindice
----------------
Xindice 1.0rc2 (Pepper)
Database: 'db' initializing
Script: 'GET' added to script storage
Service: 'db' started
ERROR: Could not start service 'HTTPServer'
Service: 'APIService' started
FATAL ERROR: Service manager could not be started
[fadm@fenris]/usr/flocal/opt/xindice:
Øyvind Vestavik
Øvre Møllenberggt 44b
7014 Trondheim
oyvindve@idi.ntnu.no
41422911
Re: Startup problems. No error message description
Posted by "Mark J. Stang" <ma...@earthlink.net>.
Are you running on a Corporate Sun type box?
Mark
Øyvind Vestavik wrote:
> First of all:
> Thank you Mark for your effort to help me.
> I really appreciate it.
>
> After two days i finally found that my problems getting Xindice
> started had nothing to do with any environement variables as I had
> thought. It had to do with
> the fact that the servers http service is running om rel. low portnumber.
> These are (at least on the machine I'm working on) reserved for processes
> running as root. I don't have access to root. When the http service
> couldn't start, the API service couldn't start either.
>
> By simply changing the port number of the http service in the
> XINDICE_HOME/config/system.xml I managed to get the server up and running
> in no time :-)
>
> In case someone run into the same problem..
>
> Øyvind
>
> Øyvind Vestavik
> Øvre Møllenberggt 44b
> 7014 Trondheim
> oyvindve@idi.ntnu.no
> 41422911
Re: Startup problems. No error message description
Posted by "Mark J. Stang" <ma...@earthlink.net>.
My error, it is 1023. And now that you mention it, services have a list of
ports and an english translation. It is used by netstat to "translate" the
names.
Mark
Kimbro Staken wrote:
> On Wednesday, March 13, 2002, at 10:51 AM, Mark J. Stang wrote:
>
> > Kimbro/Tom/et. al.,
> > Øyvind brings up a pretty good point, the default port number is below the
> > reserved
> > number of 5000. If I remember correctly, all ports below 5000 are known
> > as
> > "Well Known Ports" and are supposed to be reserved. I think XmlBlaster
> > recently
> > requested that their particular port be reserved for them.
>
> Well known ports are 1023 and below. You can reserve other ports but IANA
> doesn't really control anything above 1023 and most apps don't bother with
> registering. In reality we should be using an alt-http port but we
> explicitly avoided that because it is so easy to conflict with another
> process. i.e. 8080 is the default for Tomcat and a bunch of other things
> and 8008 isn't much better.
>
> > By reserving ports and adding them to the services file, we eliminate the
> > possibility
> > that the OS would "give away" our port. *nix platforms grab unassigned
> > ports
>
> Are you sure the services file is used for this purpose?
>
> > whenever someone needs a port. It does this by starting at the ones
> > above
> > the
> > reserved ports and then keeps on going. Eventually, it rotates back and
> > starts all
> > over. Windows on the other hand just starts at the begining every time
> > and
> > keeps
> > reusing ports.
> >
> > Anyway, the port that xindice uses is usually reserved for root access
> > only
> > on some
>
> It's ports 1023 and below that are reserved for root access.
>
> > machines. So, we probably should a default that is above the reserved
> > limit. Or
> > maybe provide a better message? I don't know, what does everyone else
> > think?
> >
> > Mark
> >
> > Øyvind Vestavik wrote:
> >
> >> First of all:
> >> Thank you Mark for your effort to help me.
> >> I really appreciate it.
> >>
> >> After two days i finally found that my problems getting Xindice
> >> started had nothing to do with any environement variables as I had
> >> thought. It had to do with
> >> the fact that the servers http service is running om rel. low portnumber.
> >> These are (at least on the machine I'm working on) reserved for processes
> >> running as root. I don't have access to root. When the http service
> >> couldn't start, the API service couldn't start either.
> >>
> >> By simply changing the port number of the http service in the
> >> XINDICE_HOME/config/system.xml I managed to get the server up and running
> >> in no time :-)
> >>
> >> In case someone run into the same problem..
> >>
> >> Øyvind
> >>
> >> Øyvind Vestavik
> >> Øvre Møllenberggt 44b
> >> 7014 Trondheim
> >> oyvindve@idi.ntnu.no
> >> 41422911
> >
> >
> Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
> Apache Xindice native XML database http://xml.apache.org/xindice
> XML:DB Initiative http://www.xmldb.org
> Senior Technologist (Your company name here)
Re: Startup problems. No error message description
Posted by Kimbro Staken <ks...@xmldatabases.org>.
On Wednesday, March 13, 2002, at 10:51 AM, Mark J. Stang wrote:
> Kimbro/Tom/et. al.,
> Øyvind brings up a pretty good point, the default port number is below the
> reserved
> number of 5000. If I remember correctly, all ports below 5000 are known
> as
> "Well Known Ports" and are supposed to be reserved. I think XmlBlaster
> recently
> requested that their particular port be reserved for them.
Well known ports are 1023 and below. You can reserve other ports but IANA
doesn't really control anything above 1023 and most apps don't bother with
registering. In reality we should be using an alt-http port but we
explicitly avoided that because it is so easy to conflict with another
process. i.e. 8080 is the default for Tomcat and a bunch of other things
and 8008 isn't much better.
> By reserving ports and adding them to the services file, we eliminate the
> possibility
> that the OS would "give away" our port. *nix platforms grab unassigned
> ports
Are you sure the services file is used for this purpose?
> whenever someone needs a port. It does this by starting at the ones
> above
> the
> reserved ports and then keeps on going. Eventually, it rotates back and
> starts all
> over. Windows on the other hand just starts at the begining every time
> and
> keeps
> reusing ports.
>
> Anyway, the port that xindice uses is usually reserved for root access
> only
> on some
It's ports 1023 and below that are reserved for root access.
> machines. So, we probably should a default that is above the reserved
> limit. Or
> maybe provide a better message? I don't know, what does everyone else
> think?
>
> Mark
>
> Øyvind Vestavik wrote:
>
>> First of all:
>> Thank you Mark for your effort to help me.
>> I really appreciate it.
>>
>> After two days i finally found that my problems getting Xindice
>> started had nothing to do with any environement variables as I had
>> thought. It had to do with
>> the fact that the servers http service is running om rel. low portnumber.
>> These are (at least on the machine I'm working on) reserved for processes
>> running as root. I don't have access to root. When the http service
>> couldn't start, the API service couldn't start either.
>>
>> By simply changing the port number of the http service in the
>> XINDICE_HOME/config/system.xml I managed to get the server up and running
>> in no time :-)
>>
>> In case someone run into the same problem..
>>
>> Øyvind
>>
>> Øyvind Vestavik
>> Øvre Møllenberggt 44b
>> 7014 Trondheim
>> oyvindve@idi.ntnu.no
>> 41422911
>
>
Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
Senior Technologist (Your company name here)
Re: changing port. Complications
Posted by Kimbro Staken <ks...@xmldatabases.org>.
On Wednesday, March 13, 2002, at 12:11 PM, Øyvind Vestavik wrote:
>
> Maybe I missed this in the docs but here is the response i get when trying
> to use the commandline tools:
>
> ERROR : A connection to the Database instance 'db' could not be created.
> Error: http://localhost:4080/db_bootstrap.ior
If you change the server port you have to tell the client to use the new
port on each request.
>
> I guess this has to do with the fact that I changed the port for the http
> service. Is there any more entries I have to change than the one in
> system.xml or is this "hardcoded" into the server code??
> It would be better if it was read from the system.xml in each case??
Changing system.xml affects the server, the client doesn't look at that
file and shouldn't since you can't assume they're running on the same
machine. Changing the port on the client just involves parameters on the
command line. i.e. -c with a full URI.
> Øyvind
>
> Øyvind Vestavik
> Øvre Møllenberggt 44b
> 7014 Trondheim
> oyvindve@idi.ntnu.no
> 41422911
>
>
>
>
Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
Senior Technologist (Your company name here)
changing port. Complications
Posted by Øyvind Vestavik <Oy...@idi.ntnu.no>.
Maybe I missed this in the docs but here is the response i get when trying
to use the commandline tools:
ERROR : A connection to the Database instance 'db' could not be created.
Error: http://localhost:4080/db_bootstrap.ior
I guess this has to do with the fact that I changed the port for the http
service. Is there any more entries I have to change than the one in
system.xml or is this "hardcoded" into the server code??
It would be better if it was read from the system.xml in each case??
Øyvind
Øyvind Vestavik
Øvre Møllenberggt 44b
7014 Trondheim
oyvindve@idi.ntnu.no
41422911
Re: Startup problems. No error message description
Posted by Kimbro Staken <ks...@xmldatabases.org>.
On Wednesday, March 13, 2002, at 10:51 AM, Mark J. Stang wrote:
> Kimbro/Tom/et. al.,
> Øyvind brings up a pretty good point, the default port number is below the
> reserved
> number of 5000. If I remember correctly, all ports below 5000 are known
> as
> "Well Known Ports" and are supposed to be reserved. I think XmlBlaster
> recently
> requested that their particular port be reserved for them.
Well known ports are 1023 and below. You can reserve other ports but IANA
doesn't really control anything above 1023 and most apps don't bother with
registering. In reality we should be using an alt-http port but we
explicitly avoided that because it is so easy to conflict with another
process. i.e. 8080 is the default for Tomcat and a bunch of other things
and 8008 isn't much better.
> By reserving ports and adding them to the services file, we eliminate the
> possibility
> that the OS would "give away" our port. *nix platforms grab unassigned
> ports
Are you sure the services file is used for this purpose?
> whenever someone needs a port. It does this by starting at the ones
> above
> the
> reserved ports and then keeps on going. Eventually, it rotates back and
> starts all
> over. Windows on the other hand just starts at the begining every time
> and
> keeps
> reusing ports.
>
> Anyway, the port that xindice uses is usually reserved for root access
> only
> on some
It's ports 1023 and below that are reserved for root access.
> machines. So, we probably should a default that is above the reserved
> limit. Or
> maybe provide a better message? I don't know, what does everyone else
> think?
>
> Mark
>
> Øyvind Vestavik wrote:
>
>> First of all:
>> Thank you Mark for your effort to help me.
>> I really appreciate it.
>>
>> After two days i finally found that my problems getting Xindice
>> started had nothing to do with any environement variables as I had
>> thought. It had to do with
>> the fact that the servers http service is running om rel. low portnumber.
>> These are (at least on the machine I'm working on) reserved for processes
>> running as root. I don't have access to root. When the http service
>> couldn't start, the API service couldn't start either.
>>
>> By simply changing the port number of the http service in the
>> XINDICE_HOME/config/system.xml I managed to get the server up and running
>> in no time :-)
>>
>> In case someone run into the same problem..
>>
>> Øyvind
>>
>> Øyvind Vestavik
>> Øvre Møllenberggt 44b
>> 7014 Trondheim
>> oyvindve@idi.ntnu.no
>> 41422911
>
>
Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
Senior Technologist (Your company name here)
Re: Startup problems. No error message description
Posted by "Mark J. Stang" <ma...@earthlink.net>.
Kimbro/Tom/et. al.,
Øyvind brings up a pretty good point, the default port number is below the
reserved
number of 5000. If I remember correctly, all ports below 5000 are known as
"Well Known Ports" and are supposed to be reserved. I think XmlBlaster
recently
requested that their particular port be reserved for them.
By reserving ports and adding them to the services file, we eliminate the
possibility
that the OS would "give away" our port. *nix platforms grab unassigned
ports
whenever someone needs a port. It does this by starting at the ones above
the
reserved ports and then keeps on going. Eventually, it rotates back and
starts all
over. Windows on the other hand just starts at the begining every time and
keeps
reusing ports.
Anyway, the port that xindice uses is usually reserved for root access only
on some
machines. So, we probably should a default that is above the reserved
limit. Or
maybe provide a better message? I don't know, what does everyone else
think?
Mark
Øyvind Vestavik wrote:
> First of all:
> Thank you Mark for your effort to help me.
> I really appreciate it.
>
> After two days i finally found that my problems getting Xindice
> started had nothing to do with any environement variables as I had
> thought. It had to do with
> the fact that the servers http service is running om rel. low portnumber.
> These are (at least on the machine I'm working on) reserved for processes
> running as root. I don't have access to root. When the http service
> couldn't start, the API service couldn't start either.
>
> By simply changing the port number of the http service in the
> XINDICE_HOME/config/system.xml I managed to get the server up and running
> in no time :-)
>
> In case someone run into the same problem..
>
> Øyvind
>
> Øyvind Vestavik
> Øvre Møllenberggt 44b
> 7014 Trondheim
> oyvindve@idi.ntnu.no
> 41422911
Re: Startup problems. No error message description
Posted by "Mark J. Stang" <ma...@earthlink.net>.
Kimbro/Tom/et. al.,
Øyvind brings up a pretty good point, the default port number is below the
reserved
number of 5000. If I remember correctly, all ports below 5000 are known as
"Well Known Ports" and are supposed to be reserved. I think XmlBlaster
recently
requested that their particular port be reserved for them.
By reserving ports and adding them to the services file, we eliminate the
possibility
that the OS would "give away" our port. *nix platforms grab unassigned
ports
whenever someone needs a port. It does this by starting at the ones above
the
reserved ports and then keeps on going. Eventually, it rotates back and
starts all
over. Windows on the other hand just starts at the begining every time and
keeps
reusing ports.
Anyway, the port that xindice uses is usually reserved for root access only
on some
machines. So, we probably should a default that is above the reserved
limit. Or
maybe provide a better message? I don't know, what does everyone else
think?
Mark
Øyvind Vestavik wrote:
> First of all:
> Thank you Mark for your effort to help me.
> I really appreciate it.
>
> After two days i finally found that my problems getting Xindice
> started had nothing to do with any environement variables as I had
> thought. It had to do with
> the fact that the servers http service is running om rel. low portnumber.
> These are (at least on the machine I'm working on) reserved for processes
> running as root. I don't have access to root. When the http service
> couldn't start, the API service couldn't start either.
>
> By simply changing the port number of the http service in the
> XINDICE_HOME/config/system.xml I managed to get the server up and running
> in no time :-)
>
> In case someone run into the same problem..
>
> Øyvind
>
> Øyvind Vestavik
> Øvre Møllenberggt 44b
> 7014 Trondheim
> oyvindve@idi.ntnu.no
> 41422911
Re: Startup problems. No error message description
Posted by Øyvind Vestavik <Oy...@idi.ntnu.no>.
I'm using solaris 2,6 on a sun sparc box.
I don't know if the port use is restricted by the os or by the
administrator, as he's away on a conference..
PS Thanks for the clarificatin on the commandline tools beeing a client
and not a part of the server. When the hours get longer and longer.. :-)
Øyvind Vestavik
Øvre Møllenberggt 44b
7014 Trondheim
oyvindve@idi.ntnu.no
41422911
On Wed, 13 Mar 2002, Kimbro Staken wrote:
>
> On Wednesday, March 13, 2002, at 10:29 AM, Øyvind Vestavik wrote:
>
> >
> > First of all:
> > Thank you Mark for your effort to help me.
> > I really appreciate it.
> >
> > After two days i finally found that my problems getting Xindice
> > started had nothing to do with any environement variables as I had
> > thought. It had to do with
> > the fact that the servers http service is running om rel. low portnumber.
> > These are (at least on the machine I'm working on) reserved for processes
> > running as root. I don't have access to root. When the http service
> > couldn't start, the API service couldn't start either.
>
> What OS are you using that requires root for ports above 1023?
>
> >
> > By simply changing the port number of the http service in the
> > XINDICE_HOME/config/system.xml I managed to get the server up and running
> > in no time :-)
> >
> > In case someone run into the same problem..
> >
> > Øyvind
> >
> > Øyvind Vestavik
> > Øvre Møllenberggt 44b
> > 7014 Trondheim
> > oyvindve@idi.ntnu.no
> > 41422911
> >
> >
> >
> Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
> Apache Xindice native XML database http://xml.apache.org/xindice
> XML:DB Initiative http://www.xmldb.org
> Senior Technologist (Your company name here)
>
Re: Startup problems. No error message description
Posted by Kimbro Staken <ks...@xmldatabases.org>.
On Wednesday, March 13, 2002, at 10:29 AM, Øyvind Vestavik wrote:
>
> First of all:
> Thank you Mark for your effort to help me.
> I really appreciate it.
>
> After two days i finally found that my problems getting Xindice
> started had nothing to do with any environement variables as I had
> thought. It had to do with
> the fact that the servers http service is running om rel. low portnumber.
> These are (at least on the machine I'm working on) reserved for processes
> running as root. I don't have access to root. When the http service
> couldn't start, the API service couldn't start either.
What OS are you using that requires root for ports above 1023?
>
> By simply changing the port number of the http service in the
> XINDICE_HOME/config/system.xml I managed to get the server up and running
> in no time :-)
>
> In case someone run into the same problem..
>
> Øyvind
>
> Øyvind Vestavik
> Øvre Møllenberggt 44b
> 7014 Trondheim
> oyvindve@idi.ntnu.no
> 41422911
>
>
>
Kimbro Staken - http://www.kstaken.org - http://www.xmldatabases.org
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
Senior Technologist (Your company name here)
Re: Startup problems. No error message description
Posted by Øyvind Vestavik <Oy...@idi.ntnu.no>.
First of all:
Thank you Mark for your effort to help me.
I really appreciate it.
After two days i finally found that my problems getting Xindice
started had nothing to do with any environement variables as I had
thought. It had to do with
the fact that the servers http service is running om rel. low portnumber.
These are (at least on the machine I'm working on) reserved for processes
running as root. I don't have access to root. When the http service
couldn't start, the API service couldn't start either.
By simply changing the port number of the http service in the
XINDICE_HOME/config/system.xml I managed to get the server up and running
in no time :-)
In case someone run into the same problem..
Øyvind
Øyvind Vestavik
Øvre Møllenberggt 44b
7014 Trondheim
oyvindve@idi.ntnu.no
41422911
Re: Startup problems. No error message description
Posted by "Mark J. Stang" <ma...@earthlink.net>.
Øyvind,
Why are you adding the openorb-1.2.0.jar to the classpath? In
the start script, Xindice builds its' own classpath. You shouldn't have
to add anything. You might want to echo $CLASSPATH to see what
values are there. In the start script you can also echo it there to see
if you have anything "strange" in front of the Xindice jars. Also,
is your JDK "fresh"? What I mean by that is that could someone,
or even you have added any jars to the jre/lib/ext? Xindice
only requires a 1.3 clean version of Java and its own jars.
Anything else that is added to the classpath can break it.
This includes other Jars in the classpath before Xindices' or
other jars that are included in the jre libs.
Try to isolate it from everything else, get it to startup and run
and then add back in the rest of your environment.
I have it running on Linux Redhat 7.2, Mac OSX(1 laptop, 1 dual processor, 1 desktop),
Windows NT and Windows 2000. So it is possible to get it to run.
What OS are you trying to run it on?
HTH,
Mark
Øyvind Vestavik wrote:
> I try to start up xindice, but can't seem to understand what is going
> wrong. If someone has an idea as to what causes this... :-)
>
> Im using jdk1.3:
> [fadm@fenris]java -version
> java version "1.3.1_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02)
> Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode)
> (what does mixes mode mean?)
>
> And have added the following to my local profile:
> if [ -e "/usr/flocal/etc/fenris_profile" ]; then
> source /usr/flocal/etc/fenris_profile
> export JAVA_HOME=/usr/flocal/opt/jdk1.3
> export XINDICE_HOME=/usr/flocal/opt/xindice
> export PATH=.:/usr/flocal/opt/jdk1.3/bin:/usr/flocal/opt/jdk1.3:/usr/flocal/opt/xindice/bin/:$PATH
> export CLASSPATH=/usr/flocal/opt/xindice/java/lib/openorb-1.2.0.jar:$CLASSPATH
> fi
>
> This is the entire response I get when starting xindice
>
> [fadm@fenris]/usr/flocal/opt/xindice: start
> Xindice Loader
> ==============
>
> Environment
> -----------
> XINDICE_HOME = /usr/flocal/opt/xindice
> CLASSPATH =
> /usr/flocal/opt/xindice/java/lib/xmldb.jar:/usr/flocal/opt/xindice/java/lib/xmldb-xupdate.jar:
> /usr/flocal/opt/xindice/java/lib/xmldb-sdk.jar:/usr/flocal/opt/xindice/java/lib/xml-apis-1.0.jar:
> /usr/flocal/opt/xindice/java/lib/xindice.jar:/usr/flocal/opt/xindice/java/lib/xerces-1.4.3.jar:
> /usr/flocal/opt/xindice/java/lib/xalan-2.0.1.jar:/usr/flocal/opt/xindice/java/lib/openorb_tools-1.2.0.jar:
> /usr/flocal/opt/xindice/java/lib/openorb-1.2.0.jar:/usr/flocal/opt/xindice/java/lib/infozone-tools.jar:
> /usr/flocal/opt/xindice/java/lib/examples.jar:/usr/flocal/opt/xindice/java/lib/ant-1.4.1.jar:
> /usr/flocal/opt/xindice/classgen:/usr/flocal/opt/xindice/config:/usr/flocal/opt/xindice/java/lib/openorb-1.2.0.jar:
> /usr/flocal/opt/vbroker/lib/migration.jar:/usr/flocal/opt/vbroker/lib/vbdev.jar:/usr/flocal/opt/vbroker/lib/vbjdev.jar:
> /usr/flocal/opt/vbroker/lib/vbjorb.jar:/usr/flocal/opt/oracle/8.1.6./jdbc/lib/classes12.zip:
> /usr/flocal/opt/oracle/8.1.6./jdbc/lib/jndi.zip:/usr/flocal/opt/oracle/8.1.6./jdbc/lib/jta.zip:
> /usr/flocal/opt/oracle/8.1.6./jdbc/lib/nls_charset12.zip:/usr/flocal/opt/versant/jvi/2.4.0/lib/jvi2.4.0-jdk1.1.jar:
> /usr/flocal/opt/versant/jvi/2.4.0/lib/jgl3.0.0.jar:/usr/flocal/opt/versant/jvi/2.4.0/lib/oromatcher1.1.jar:
> /usr/flocal/opt/versant/jvi/2.4.0/lib/jtaxa0.9.jar:.:/usr/flocal/opt/hs/hcj/handle.jar:
>
> Starting Xindice
> ----------------
>
> Xindice 1.0rc2 (Pepper)
>
> Database: 'db' initializing
> Script: 'GET' added to script storage
> Service: 'db' started
> ERROR: Could not start service 'HTTPServer'
> Service: 'APIService' started
> FATAL ERROR: Service manager could not be started
> [fadm@fenris]/usr/flocal/opt/xindice:
>
> Øyvind Vestavik
> Øvre Møllenberggt 44b
> 7014 Trondheim
> oyvindve@idi.ntnu.no
> 41422911