You are viewing a plain text version of this content. The canonical link for it is here.

Posted to slide-user@jakarta.apache.org by Raj Kumar <ko...@intalio.com> on 2001/09/06 20:13:29 UTC

Enlist error when using JDBCDescriptor store for Sybase

hi remy,
    I am sybase database with the JDBCDescriptorStore class and i am getting
an enlist error when the slide web application
    starts loading the base data in the Domain.xml file.
    The stores in the Domain.xml file looks this.

          <contentstore name="content"
              classname="slidestore.reference.JDBCContentStore">
                 <parameter
name="driver">com.sybase.jdbc2.jdbc.SybDriver</parameter>
                 <parameter
name="url">sybase:Tds:Rajkumar:2048/repository</parameter>
	         <parameter name="user">sa</parameter>
	         <parameter name="password">liferaj</parameter>
                 <parameter name="jdbcversion">1</parameter>
           </contentstore>

           <nodestore name="data"
classname="slidestore.reference.JDBCDescriptorsStore">
               <parameter
name="driver">com.sybase.jdbc2.jdbc.SybDriver</parameter>
               <parameter
name="url">sybase:Tds:Rajkumar:2048/repository</parameter>
	       <parameter name="user">sa</parameter>
	       <parameter name="password">liferaj</parameter>
               <parameter name="jdbcversion">1</parameter>
           </nodestore>

           <revisiondescriptorsstore>
               <reference store="nodestore" />
	   </revisiondescriptorsstore>

           <lockstore>
               <reference store="nodestore" />
	   </lockstore>

	   <revisiondescriptorstore>
                <reference store="nodestore" />
	   </revisiondescriptorstore>

	   <securitystore>
               <reference store="nodestore" />
	   </securitystore>

The error i get is as follows.

Starting service Tomcat-Standalone
Apache Tomcat/4.0-b5
06 Sep 2001 11:01:01 - org.apache.slide.common.Domain - INFO - Initializing
Doma
in
06 Sep 2001 11:01:01 - org.apache.slide.common.Domain - INFO - Domain
configurat
ion : {Default=Will look for domain.xml in current directory,
org.apache.slide.s
ecurity=false, org.apache.slide.domain=Domain.xml}
06 Sep 2001 11:01:01 - org.apache.slide.common.Domain - INFO - Initializing
name
space : slide
06 Sep 2001 11:01:02 - org.apache.slide.common.Namespace - INFO - Loading
namesp
ace definition
06 Sep 2001 11:01:02 - org.apache.slide.common.Namespace - INFO - Node
store: sl
idestore.reference.JDBCDescriptorsStore
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO - Security
store
 references nodestore
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO - Lock store
sto
re references nodestore
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO - Revision
descr
iptors store references nodestore
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO - Revision
descr
iptor store references nodestore
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO - Content
store:
 slidestore.reference.JDBCContentStore
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO -
Registering St
ore memory of class class org.apache.slide.store.StandardStore with
parameters {
} on scope /
06 Sep 2001 11:01:03 - org.apache.slide.common.Namespace - INFO -
Initializing S
tore memory(org.apache.slide.store.StandardStore)
06 Sep 2001 11:01:05 - org.apache.slide.common.Namespace - INFO - Loading
namesp
ace slide parameters
06 Sep 2001 11:01:05 - org.apache.slide.common.Namespace - INFO - Loading
namesp
ace slide base data
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-1 Flag: 134217728
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-2 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-3 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-4 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-5 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-6 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-7 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-8 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-9 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-10 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-11 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-12 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-13 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-14 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-15 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-16 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-17 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-18 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-19 Flag: 2097152
Enlist error(Transaction 1 in main) = -3
slidestore.reference.JDBCDescriptorsSt
ore@171b26 Branch: main-999799265588-1-20 Flag: 2097152
06 Sep 2001 11:01:17 - org.apache.slide.common.Domain - WARNING -
org.apache.sli
de.common.ServiceAccessException
06 Sep 2001 11:01:17 - org.apache.slide.common.Namespace - INFO - Namespace
base
 configuration was already done before
06 Sep 2001 11:01:17 - org.apache.slide.common.Namespace - INFO - Loading
namesp
ace slide configuration
06 Sep 2001 11:01:17 - org.apache.slide.common.Domain - ERROR -
org.apache.slide
.structure.ObjectNotFoundException: No object found at /actions
Starting service Tomcat-Apache
Apache Tomcat/4.0-b5


I would appreciate any help on this.
      thanks,
      rajkumar


-----Original Message-----
From: Remy Maucherat [mailto:remm@apache.org]
Sent: Tuesday, September 04, 2001 11:15 PM
To: slide-user@jakarta.apache.org
Subject: Re: File quota


> Kiyoko Takanabe wrote:
>
> > Hi, Remy.
> >
> > Thank you for your answer.
> > May I ask about. further details?
> >
> > I want to execute File quota per user.
> > Now, we extend the slide, Contentstore and DiscripterStore.
> >
> > In Slide, userid is not put into Contentstore and DiscripterStore.
> > I want to execute at there.
> > Can I get user's informations individually?
> >
> > Do you have any idea of how to do.
>
> You could extend the server PutMethod to store the "Owner" of the content
in a
> protected property.
> If the content and structure is in the same database you can then write a
> database trigger (or change the content store) to check for the total
size.
> select sum(revisioncontent.xnumber) from revisioncontent, property
> where revisioncontent.uri = property.uri and property.name="owner" and
> property.value="Kiyoko"
>
> A more generic way is to use that ContentInterceptor.preStoreContent but
then
> you have to walk the whole structure and that is slow. In this case you
have to
> keep the total number of bytes used as a property on the user. (You have
the
> SlideToken for the user info). In the preStoreContent you check if there
is
> enough room and put a lock on the user, in the postStoreContent you update
the
> bytes used and unlock user.
> We also have to change the ContentInterceptor and add a preRemoveContent
and
> postRemoveContent to allow you to decrease the used bytes after a remove.
> There is also a small issue, if the client doesn't send a content-length
header
> then you cannot know the content length until after the bytes are written
to the
> store and then you have to revert is the user is over his limit.
> The ContentInterceptor should also be changed to allow it to throw some
> exceptions (or return a status) to indicate the action must stop and to
indicate
> the put operation failed (send an error response to client).

Yes. I was starting to get frustrated by the lack of that possibility. The
problem is: what exception should we allow to throw (ServiceAccessException
? a runtime exception ?). As you mention, a status code could be enough too.
I didn't want to add a new checked exception (there are already enough).

> The second solution has the advantage that you can give each user a
different
> quota size (also a property on user).
> With the first solution this is not that easy because the store doesn't
know the
> identity of the user.

I think there's something missing in the PROPPATCH implementation, since I
don't think it currently prevents modifying the protected properties (bad).

Remy