-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This thread is so pervasive I'm going to actually install james2.0 in the end... :-) BTW, a short list of answer: - - a Oracle LONG datatype is a sort of VARCHAR2, but can be 2^31 bytes long - - there's a limit of 30K bytes in some tools accessing the db, namely Oracle Forms client server: it comes from the fact that the client have to alloc a buffer, and for unknown reason Forms won't alloc a larger buffer; - - the abovementioned limit is strictly on the tool, not touching the server: java code, C programs & Odbc stuff (included MS Access) may read & write anything up to 2^31 bytes (or the size of the disk, whichever is lower) - - CLOB is twice as large, up to 2^32 bytes (or chars? actually I don't know): more to the point, CLOB has a different internal memory allocation; - - for that reason CLOB is going to supersede LONG: in other word LONG is deprecated; - - according to SUN, CLOB is *TOO* large, in fact somewhere in jdbc lib you may find a: int getPrecision(int nr_column); returning the max dimension on a table column: it works for LONG -> 2^31 <= Integer.MAX_INT it won't for CLOB -> 2^32 > Integer.MAX_INT this causes an exception in the original WorkingDogs Town, which bubbles up to James (1.2.1), which crashes the program. - - this bug is not fixed by sun in any jdk (I don't even know if it is a bug) - - Steps for debugging the installation could be: a/ find out the db schema (ie user); b/ using sqlplus, connect to db & schema; c/ select * from cat; -> in 1.2.1 there should be just a table Message; don't know in 2. d/ desc the table; e/ & select count(*) from table f/ if count(*) is zero, then nobody is able to write to it (the problem is saving the message) g/ if count(*) is greater, then trouble comes when POP tries to read h/ finally, the mapping MAIL_MESSAGES<->DB is (or was?) straightforward one message : one record in the table; if it is still that, then SELECT BODY FROM TABLE should return the info; hope it helps (at least it helps my english) d. - -----Messaggio originale----- Da: John Wang [mailto:[EMAIL PROTECTED]] Inviato: venerd� 18 gennaio 2002 3.26 A: James Users List Oggetto: Re: How to make James work with Oracle database? I still got the problems with James 2 /Oracle 8.1.7. Now I can let the users and james-list use db repository, and also I I changed the Oracle message-body from clob field to long type. When it received the message, it can put into the inbox table, sounds right. The message_body field contains unreadable info. When it retrieves the message, it couldn't shows the info like from, to, subject, the body can't be shown either. I am using latest James2.0a2. The inbox setting is as below: <inboxRepository> <repository destinationURL="db://maildb/inbox/" type="MAIL"> </repository> </inboxRepository> Another question is that since oracle LONG VARCHAR can at most holds 30k characters, therefore it can't hold large message. If that's the case, then it is unuseful to use Oracle as inbox repository. Does that sound right? Thanks, John W - ----- Original Message ----- From: "Danny Angus" <[EMAIL PROTECTED]> To: "James Users List" <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 9:48 AM Subject: RE: How to make James work with Oracle database? > It should be, assuming that .. > a) the table naming is interchangeable, (I think MySQL and SQLserver naming > isn't) > b) any rdbms specific SQL is in the file called sqlresources.xml (in > apps\james\conf, and unpacked after the app has run once) > > James 2+ creates its own tables, so you should'nt need to worry about that > allowing for point b above.. > > If anyone has oracle specific items for sqlresources send them to the list > and we'll add them. > > d. > > >-----Original Message----- > >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > >Sent: 17 January 2002 14:38 > >To: [EMAIL PROTECTED] > >Subject: RE: How to make James work with Oracle database? > > > > > > > >Thanks for the tips. I had hoped that changing from MSQL to 9i > >was going to > >be as easy as changing the JDBC driver. It would appear that's > >not going to > >be the case <sigh>. > > > >Regards, > > Bruce > > > >-----Original Message----- > >From: daniele rizzi [mailto:[EMAIL PROTECTED]] > >Sent: Thursday, January 17, 2002 9:35 AM > >To: James Users List > >Subject: R: How to make James work with Oracle database? > > > > > > > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > > > >Sorry I may only provide with data about James 1.2: in that case you > >had to create a table called "Message" with some fields, and then > >change the DbRepository entry in the config file. > >The Create Table script is not provided, but it's not hard to > >figure out what should be, cooking up the sqlServer/mySql examples. > >There are two caveats: > >- - first you cannot use CLOB but resort to LONG VARCHAR due to a > >bug in Sun > >jdbc > >- - then there are some massaging needed for the schema to run, due > > to some synergy between workingDogs' town and Oracle Jdbc Driver. > > > >Since you are using an upgraded version I'm not boring you with > >the details: > >the interesting point is that in v1.2 ( in 2 also?) the repository is > >screened by a java library, which creates a transparent relationship > >between the objects and the tables, that is james creates the object > >and this library produces the INSERT/UPDATE code needed. > > > >In *that* version there where at least two places to begin debugging: > >- - james itself fills a /log directory; > >- - and workingdogs' town creates a DBxxx.log file containing the details > > of the running connection. > > > >I cannot help more, I've tried once load & run the new james, > >but I've got no way to test IMAP so there is little reason to upgrade > >(I mean I'm not smart enough to judge if Imap works) > > > >bye, > >d.rizzi > > > > > > > > > >- -----Messaggio originale----- > >Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > >Inviato: gioved� 17 gennaio 2002 15.09 > >A: [EMAIL PROTECTED] > >Oggetto: RE: How to make James work with Oracle database? > > > > > > > >I'd be really interested in any James 2.0 / Oracle 9i information that you > >could share. > > > >Thanks, > > Bruce > > > >- -----Original Message----- > >From: daniele rizzi [mailto:[EMAIL PROTECTED]] > >Sent: Thursday, January 17, 2002 2:57 AM > >To: James Users List > >Subject: R: How to make James work with Oracle database? > > > > > > > >- -----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > > > >I've spent boxing day setting up james 1.2 with Oracle 9i, > >but finally it works. Would you state if you are using 1.2 or 2.*? > > > >dany rizzi ([EMAIL PROTECTED]) > > > > > > > >- - -----Messaggio originale----- > >Da: John Wang [mailto:[EMAIL PROTECTED]] > >Inviato: gioved� 17 gennaio 2002 3.46 > >A: [EMAIL PROTECTED] > >Oggetto: How to make James work with Oracle database? > > > > > >I am having problem with using oracle repository, I have created a db > >datasource as below: > > <data-source name="maildb" > > > >class="org.apache.avalon.excalibur.datasource.JdbcDataSource"> > > <driver>oracle.jdbc.driver.OracleDriver</driver> > > <dburl>jdbc:oracle:thin:@JWANG:1521:JWANG</dburl> > > <user>system</user> > > <password>manager</password> > > </data-source> > > > > > >and then I set up the inbox repository, > > <inboxRepository> > > <repository destinationURL="db://maildb/inbox/" > > type="MAIL"> > > </repository> > > </inboxRepository> > > > >and I have also setup the db repository for users and list, > > > >I have created the tables by myself, including inbox,users,lists tables, > > > >I have also put classes12.jar (oracle jdbc driver) into the lib directory, > > > >When I started the james, it hanged there, no error messages, no log coming > >out, the only message I saw is: > > > >"Phoenix 3.1a1-dev" > > > >What is going on? Can anyone help me? > >Thanks very much! > >John W > > > > > > > >- -----BEGIN PGP SIGNATURE----- > >Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> > > > >iQA/AwUBPEaDpnQ0FMcAcek4EQI4rgCgxX/5qKC4eLDcHOENKGVOcR0u7moAoMmO > >Xa5TBrGxHVlC2Cezqxp8qES6 > >=+z7x > >- -----END PGP SIGNATURE----- > > > > > >- -- > >To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > - -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -----BEGIN PGP SIGNATURE----- > Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> > > iQA/AwUBPEbhEHQ0FMcAcek4EQIy7gCbB+/qliuUWFtKctluI/1rZT2aqHgAoMF4 > GoxTtvjmCLZgUxnCsKZ217E/ > =1QsE > -----END PGP SIGNATURE----- > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > - -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBPEfgW3Q0FMcAcek4EQKt/wCgyvtsaweBAy/18OzpdsaUF4g3SRcAn1Fr L7vTE3oDn/0KXG8atk/2tp/0 =h7Uc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
