Btw, i remember now i already pinged openjpa ml with this.
The answer was that it was possible that a resolved bug was the cause,
and they said to upgrade.
We did that, and I felt less often in that pitfall.
So there is hope :)
Tks,
Eric
On 23/11/2010 10:50, Raju Bitter wrote:
Thanks a lot, Eric. That makes sense. I'll keep an eye on that.
On Tue, Nov 23, 2010 at 9:12 AM, Eric Charles<[email protected]> wrote:
Hi,
I already had normal start and freeze when adding a user for example via
telnet.
This happened when I changed stuff in the jpa implementations, and probably
the change gave problems.
I came to the conclusion that openjpa was the cause of the freeze and not
james' code.
Probably this is the same in your situation.
I will monitor this issue with the new openjpa releases, and ping the
openjpa mailing list about that if needed.
Tks,
Eric
On 23/11/2010 01:10, Raju Bitter wrote:
There was one situation which was a little bit difficult to understand
for me. My MySQL instance was bound to my server's IP address instead
of 127.0.0.1. But in the database.properties I used "localhost" within
the database.url.
With the default setup (not using JPA for domains), when I launched
James I didn't see any exception or error message. But when I used the
remote admin shell through telnet, the session froze as soon as I
started adding users. Of course the reason was mis-configuration on my
side, but it took me some time to find the reason for that.
What exactly does happen in that case? Why don't I see an exception
when I try to add a user in that situation?
- Raju
On Thu, Nov 4, 2010 at 10:10 AM, Raju Bitter
<[email protected]> wrote:
Yes, everything is working now. Thanks again!
On Thu, Nov 4, 2010 at 7:37 AM, Eric Charles<[email protected]> wrote:
Hi Raju,
So everything is working fine now?
You didn't get any exception before simply because james didn't try to
access the database (it access it for mail delivery or for admin
functions
for example).
Tks,
Eric
On 3/11/2010 18:55, Raju Bitter wrote:
Thanks, Eric. I activated JPADomainList, and now I get a JPA exception
in my wrapper.log file:
org.apache.openjpa.util.UserException: A connection could not be
obtained for driver class "null" and URL "null".
Checking my database.properties I saw that I mispelled the database
name. The only strange thing was that I didn't see any exception until
making the change to the domainlist.xml.
Thanks,
Raju
On Wed, Nov 3, 2010 at 4:09 PM, Eric Charles<[email protected]> wrote:
Hi Raju,
See bottom of http://openjpa.apache.org/integration.html to have
explanation
of the openjpa.Runtim message. You don't have to worry about it
(message
is
also there with derby).
fyi, the mysql jdbc driver can be dropped in ./conf/lib.
Is there something that doesn't work ? Have you got exceptions with
mysql
?
You can type help in the remote administrator (username = root / pwd =
root)
and invoke the command you want, typically "adduser" to begin.
We still need to update the config of the web site.
On my side, I like to enable virtual hosting in mailserver.xml, and
set
JPADomainList in domainlist.xml so I can adddomain, adduser,...
Tks,
Eric
On 3/11/2010 16:02, Raju Bitter wrote:
Hi all,
I'm using 3.0 M1 with MySQL as my database. I can launch James - just
see this warning:
46 James WARN [main] openjpa.Runtime - An error occurred while
registering a ClassTransformer with PersistenceUnitInfo: name
'James',
root URL [file:/opt/james-3.0-M1/conf/]. The error has been consumed.
To see it, set your openjpa.Runtime log level to TRACE. Load-time
class transformation will not be available.
Everything seems to work fine. I can connect to the admin console
through telnet, but as soon as I start adding users, execute
"countusers" - probably anything accessing the database - the admin
console doesn't show me any output and doesn't execute any commands.
The jame-server log file shows these entries:
INFO 15:52:04,914 | james.remotemanager | Login for root successful
users org.apache.james.user.jpa.jpausersreposit...@1bb60ad
29564 James INFO [New I/O server worker #4-1] openjpa.Runtime -
Starting OpenJPA 2.0.1
29664 James INFO [New I/O server worker #4-1] openjpa.jdbc.JDBC -
Using dictionary class "org.apache.openjpa.jdbc.sql.MySQLDictionary".
I'm using the following database properties:
# Use derby as default
database.driverClassName=com.mysql.jdbc.Driver
database.url=jdbc:mysql://localhost/james
database.username=jamesuser
database.password=*********
CLASSPATH_PREFIX
# Add every needed extra jar to this
CLASSPATH_PREFIX=../lib/mysql-connector-java-5.1.13-bin.jar
Software versions:
Ubuntu 8.04
mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486)
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
When I use the default Derby database, everything works fine.
What should I do next? Thanks,
Raju
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
