Hi all,
We've recently switched an application from using JBoss 3.0.7 to 3.2.1. In doing so,
the default persistence store for JMS messages has changed from the old File-base one
to a new hypersonic DB-based system
When the system is running, Hypersonic seems to create a log file with an entry
Thanks Julien - I think that explains it.
So if another TX has already locked the bean, then it's not possible to call the
read-only method until the first TX completes? That might well explain what I'm
seeing.
Is there a way to have some methods that don't lock the bean at all? Kind of like
As I understand it, methods marked as read-only on an entity bean shouldn't try and
lock the bean when they are called. So, if I have two instances of an entity bean
(same bean class, different PK), they can call read-only methods on each other at the
same time.
So, can anyone explain why I'm s
Replying to my own post, in case it's ever useful for someone else:
We traced the problem to the jboss user not being able to create new directories
under server/default. The XP box ( of course) had pretty open permisisons, but the
solaris one had been locked down a bit too far. In particular,
Hi all,
I'm trying to get 3.2.1 up and running under solaris, but keep running into naming
exceptions when trying to lookup java:/ConnectionFactory.
"...
Caused by: javax.naming.NameNotFoundException: ConnectionFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java
What OS? On Solaris, there are default housekeeping scripts (kicked off from root's
cron) which clear out files from /tmp and /var/tmp, but leave directory structures
intact.
Might you have something like this running on your box?
Chris
>>> [EMAIL PROTECTED] 07/12/03 07:59pm >>>
Hi all,
I'm
