Re: 3.0.0 on Linux
Hi Garry, You missed my point. I've been trying to get help on building 3.3.0 for over a week with no response (see my long list of posts). Since I can't get anyone to respond to my 3.3.0 build problem, I had to look for an alternative. I currently have a 3.0.0 beta 5 install that has worked for years on a Windows server. My only alternative until I get my 3.3.0 build problems resolved is to move that v3b5 to Linux since my windows server is going away. I have added custom code. So I can't just download the binaries. I would love to move to 3.3.0. But until I can figure out my build problems and/or get someone to respond to my questions, this is my only choice. Now my current ancient v3b5 that worked on Windows fails on Linux with OpenJPA issues (see prev post). I realize this is a completely volunteer forum. But I'm dying here. I've got to get some version of james running on my AWS Linux box. Can someone please find time to help? I'll take help on my 3.0.0 b5 OpenJPA issue and/or my 3.3.0 Eclipse build problems... just SOMETHING. Thx Jerry On 9/8/2019 2:31 AM, Garry Hurley wrote: 3.0.0 is kinda old. In fact, IIRC, it never made it out of Beta stage. 3.3.0 works and is stable, so unless you have some reason to use an older version, you should consider updating. Sent from my iPhone On Sep 8, 2019, at 12:07 AM, Jerry Malcolm wrote: I'm still waiting and hoping somebody can please explain why I can't build 3.3.0 on Eclipse. (See my other thread). But I'm on a deadline. My windows server is going away soon and I HAVE to get a mail solution onto AWS. (ANYBODY?? PLEASE HELP!) So in meantime, plan-B is to copy my current ancient v3b5 installation off of my Windows server to my AWS Linux instance. Since James is 100% java (good ol' "write once -- run anywhere"..., right?) I figured I could just copy the entire James installation folder and fix a couple of backslashes in file paths in config files, and it should run perfectly. Wrong-o. I literally copied the folder precisely, and changed to run.sh instead of run.bat. After a few expected startup messages, I get a bunch of OpenJPA warnings, followed by a bunch of errors telling me foreign keys are missing from my database, etc. (See log excerpt below). I went back to the running Windows instance. There is no reference anywhere in the Windows James log to jpa. Since the conf and lib folders are identical (as far as I can tell) between these two instances, I'm baffled. Why is OpenJPA getting upset with the Linux install and not the Windows install. My first thought was something with case-sensitive file names. But I can't find any of those situations. I'm not familiar with OpenJPA configuration. So these errors mean nothing to me. What did I do wrong? (BTW... both instances point to the same db... so I know the database is not corrupt). Can anybody help with this problem (or better... help me with the 3.3.0 Eclipse disaster... I don't want to remain on v3b5 forever). Thx. Log entries: INFO 02:35:01,219 | james.dnsservice | Adding autodiscovered search path ec2.internal. INFO 02:35:01,220 | james.dnsservice | DNS Server is: 172.31.0.2 INFO 02:35:01,226 | james.dnsservice | Registered cache, resolver and search paths as DNSJava defaults 185 James INFO [main] openjpa.Runtime - Starting OpenJPA 2.2.1 215 James INFO [main] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.MySQLDictionary". 630 James WARN [main] openjpa.MetaData - The class "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the openjpa.MetaDataFactory configuration property could not be loaded by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. 631 James WARN [main] openjpa.MetaData - The class "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed in the openjpa.MetaDataFactory configuration property could not be loaded by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. 723 James INFO [main] openjpa.MetaData - The class "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the openjpa.MetaDataFactory configuration property could not be loaded by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. 723 James INFO [main] openjpa.MetaData - The class "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed in the openjpa.MetaDataFactory configuration property could not be loaded by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. 735 James INFO [main] openjpa.MetaData - The class "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the openjpa.MetaDataFactory configuration property could not be loaded by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. 735 James INFO [main] openjpa.MetaData - The class "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed in the openjpa.MetaDataFactory configuration property could not be
Re: 3.0.0 on Linux
3.0.0 is kinda old. In fact, IIRC, it never made it out of Beta stage. 3.3.0 works and is stable, so unless you have some reason to use an older version, you should consider updating. Sent from my iPhone > On Sep 8, 2019, at 12:07 AM, Jerry Malcolm wrote: > > I'm still waiting and hoping somebody can please explain why I can't build > 3.3.0 on Eclipse. (See my other thread). But I'm on a deadline. My windows > server is going away soon and I HAVE to get a mail solution onto AWS. > (ANYBODY?? PLEASE HELP!) > > So in meantime, plan-B is to copy my current ancient v3b5 installation off of > my Windows server to my AWS Linux instance. Since James is 100% java (good > ol' "write once -- run anywhere"..., right?) I figured I could just copy the > entire James installation folder and fix a couple of backslashes in file > paths in config files, and it should run perfectly. Wrong-o. I literally > copied the folder precisely, and changed to run.sh instead of run.bat. After > a few expected startup messages, I get a bunch of OpenJPA warnings, followed > by a bunch of errors telling me foreign keys are missing from my database, > etc. (See log excerpt below). I went back to the running Windows instance. > There is no reference anywhere in the Windows James log to jpa. Since the > conf and lib folders are identical (as far as I can tell) between these two > instances, I'm baffled. Why is OpenJPA getting upset with the Linux install > and not the Windows install. My first thought was something with > case-sensitive file names. But I can't find any of those situations. I'm not > familiar with OpenJPA configuration. So these errors mean nothing to me. > What did I do wrong? (BTW... both instances point to the same db... so I know > the database is not corrupt). > > Can anybody help with this problem (or better... help me with the 3.3.0 > Eclipse disaster... I don't want to remain on v3b5 forever). > > Thx. > > Log entries: > > INFO 02:35:01,219 | james.dnsservice | Adding autodiscovered search path > ec2.internal. > INFO 02:35:01,220 | james.dnsservice | DNS Server is: 172.31.0.2 > INFO 02:35:01,226 | james.dnsservice | Registered cache, resolver and search > paths as DNSJava defaults > 185 James INFO [main] openjpa.Runtime - Starting OpenJPA 2.2.1 > 215 James INFO [main] openjpa.jdbc.JDBC - Using dictionary class > "org.apache.openjpa.jdbc.sql.MySQLDictionary". > 630 James WARN [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 631 James WARN [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed > in the openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 723 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 723 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed > in the openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 735 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 735 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed > in the openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 740 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 740 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed > in the openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > 746 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > . > > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'domainlist': Initialization
