fyi, we ended up using 4.0.3SP1 with patching jboss-hibernate.jar to use
AFTER_TRANSACTION.
using hibernate from the web layer (self started JTA transaction) with
AFTER_STATEMENT jboss was leaking the actual oracle connections (no resource in
pool exception after a few operations)
using
anonymous wrote : First, not sure how a web service forum is the correct place
for a discussion of Hibernate functionality... But that aside...
|
Sorry, I was searching for this problem and just replied here...
anonymous wrote : 101: define possible running transaction. The integration
anonymous wrote : To what did you set it?
I've changed these two lines:
settings.setProperty(hibernate.connection.agressive_release, false);
| settings.setProperty(hibernate.connection.release_mode,
after_transaction);
But I think when agressive_release is false, release_mode is not
This is an important issue. We also have to patch jboss 4.0.3 by hand to alter
this Hibernate property.
I don't understand how can this be an immutable default: it returns the jdbc
connections to the pool without considering a possible running transaction? I
may not see everything, but it was
Hi,
I'm looking for a solution for the issue above. The most I could do is to set
up the WSMQ and MDB using XA, but never got any message from the queue as
described on the second link below.
What I have found for this issue so far is this:
Sh*t, the most important part of the title just cut off.
So I need and MDB with XA transactions using a WSMQ.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3882107#3882107
Reply to the post :
It was a user bug... :)
Hibernate does use the Thread's classloader first, except when loading it's
properties. So copying the properties to the conf dir solved the issue.
But thanks for the info, it's helped to understand things better!
I owe you a beer, now you only need to visit Hungary
same problem here: two ear's, one calls into the other. salted with the need for ear
scooping.
jboss 3.2.5 siletly ignores the callbyvalue parameter, you need to add it to
org\jboss\metadata\BeanMetaData.java
callByValue = callByValueElt.equalsIgnoreCase (True);
in importJbossXml() at
that the war's should check their own classloaders/scoops and only ask for
the parent when a class is not found. But I will ask it on a different forum.
Thanks in advance,
- 101
PS: sorry for the hijack, will open new topics from now on.
View the original post :
http://www.jboss.org/index.html
filesystem security? maybe the process can not read some jars?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842001#3842001
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842001
=ClassLoadingConfiguration so everyone can lear
from it? Or just answer here and I'll add it.
Thanks in advance,
- 101
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842006#3842006
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode
Fool me, it's FIXED in 3.2.5...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842024#3842024
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3842024
---
This SF.Net email
G, no it's not.
It just loads randomly, as expected after a little thinking.
I tried
class-loading java2ClassLoadingCompliance='false'/
in the war's with no luck.
Oh well...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3842059#3842059
Reply to the
Adrian +1
the only way to keep the productivity and usefulness is to separate the
newbies/careless from the others with user levels/rights/etc... on separation i mean
read-only rights.
i only asked questions here i couldn't answer, sometimes after days of trying!
- 101
a
href=http
Is there a way to access the java: namespace from a timer event? When i make a JNDI
lookup from a method which is called by the timer service, it tries to look up the
name in the global namespace even tough it's a java:/ name.
At least it seems so... is there a limitation i don't know of, or
could be related: when you do a new InitialContext() with localhost as the jndi
provider then it will actually try to connec to the real ip address of the machine
instead of 127.0.0.1.
i'm looking for a solution because if you run.sh --host localhost (to disallow
connections from other hosts)
(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java
17 matches
Mail list logo
