-
1. Re: Store Store (2nd version)
djmalan Jan 25, 2005 12:24 AM (in response to mikezzz)Could you email me your source? I'll commit it to cvs. I'm running windoze so patching is not easy...
Please include your unit tests, I'll add it to the junitee tests for running on jboss.
I've also run into the transaction problem. Any suggestions Andy? -
2. Re: Store Store (2nd version)
mikezzz Jan 25, 2005 2:49 PM (in response to mikezzz)Hi,
I have attached a zip of the src (streamstore-0.2.zip) to the JBoss Mail patchs wiki. This should replace the existing org.jboss.mail.store.* package (move to new package name is pending).
Regards,
Mike
P.S. Don't be surprised if the PostgreSQL fails in JUnitEE. -
3. Re: Store Store (2nd version)
acoliver Jan 27, 2005 1:47 AM (in response to mikezzz)mailstore should have its own transaction seperate from the overall mail. The blob is simply garbage if it doesn't get attached to a real mail object (ala mailboxes/etc). the mail object should POINT to the id of the mailstore rec. The idea is that we collect the data before even caring if we end up with a real message or something we need to reap later somehow.
hey mike don't you have cvs access now? -
4. Re: Store Store (2nd version)
mikezzz Jan 27, 2005 3:16 PM (in response to mikezzz)hey mike don't you have cvs access now?
I'm not sure, I have tried but get any error; "failed to create lock directory for `/cvsroot/jboss/jboss-mail' (/cvsroot/jboss/jboss-mail/#cvs.lock): Permission denied." Can 'cvs login' ok.mailstore should have its own transaction seperate from the overall mail
Cool this makes it easy. The disconnected streams will commit each time the buffer is flushed to disk. The connected streams use a wrapper stream that closes the DB connection whenever the stream is closed. I will include the transaction in the wrapper and commit when the stream is closed. For those implementation that do not require transactions I will not use them.
To support the clean up, I think we will need some sort of delete request queue. An MDB seems the obvious solution? -
5. Re: Store Store (2nd version)
acoliver Feb 1, 2005 3:15 PM (in response to mikezzz)You need to look at the help page on sourceforge. you use cvs over ssh not pserver (thats public cvs non-write only)
the streams part didn't parse.
-Andy -
6. Re: Store Store (2nd version)
mikezzz Feb 12, 2005 9:12 AM (in response to mikezzz)Hi Andy,
I have tried using the cvs client settings from the sourceforge page, but I still get: failed to create lock directory for `/cvsroot/jboss/jboss-mail' (/cvsroot/jboss/jboss-mail/#cvs.lock): Permission denied
Mike. -
7. Re: Store Store (2nd version)
acoliver Feb 15, 2005 12:22 AM (in response to mikezzz)I'm fairly sure you're still using anonymous. vi your working directory CVS/Root -- I bet it has pserver in the begining.
-
8. Re: Store Store (2nd version)
mikezzz Feb 15, 2005 2:54 PM (in response to mikezzz)I tried doing a fresh checkout.
[mike@corona ~]$ echo $CVS_RSH
ssh
[mike@corona ~]$ cvs -z3 -d:ext:mikezzz@cvs.sourceforge.net:/cvsroot/jboss co -P jboss-mail
mikezzz@cvs.sourceforge.net's password:
cvs checkout: warning: cannot write to history file /cvsroot/jboss/CVSROOT/history: Permission denied
cvs checkout: Updating jboss-mail
cvs checkout: failed to create lock directory for `/cvsroot/jboss/jboss-mail' (/cvsroot/jboss/jboss-mail/#cvs.lock): Permission denied
cvs checkout: failed to obtain dir lock in repository `/cvsroot/jboss/jboss-mail'
cvs [checkout aborted]: read lock failed - giving up -
9. Re: Store Store (2nd version)
acoliver Feb 26, 2005 4:16 PM (in response to mikezzz)are you set up yet? I saw that you were supposed to have been.
-
10. Re: Store Store (2nd version)
mikezzz Mar 3, 2005 1:42 AM (in response to mikezzz)Hi Andy,
All set up and working. Should be commiting some stuff at the end of the week.
Mike.