[EJB 3.0] - CMT in Stateless SessionBean (EJB3.0)
by stewchicken
Dear all,
I encounter a roll back problem for my transactions in my stateless session ( implemented under EJB3.0 standard ).
According to below quoted sentence from JAVAEE5.0 Tutorial.
If I didnot explicitly mark transaction for my stateless session's methods
then all those methods are automatically Contain transactin managed , is it correct?
but it seems .the method doesnot roll back successfully when a exception happened inside it. I used JBoss4.0 + Stateless SessinBean (no explicit transacation demarcation used ).
Any hints? Is it a transacatin problem from JBoss or my misunderstanding to
CMT for Stateless Session Bean?
Thanks in advances
Container-Managed Transactions
In an enterprise bean with container-managed transaction demarcation, the EJB container sets the boundaries of the transactions. You can use container-managed transactions with any type of enterprise bean: session, or message-driven. Container-managed transactions simplify development because the enterprise bean code does not explicitly mark the transaction's boundaries. The code does not include statements that begin and end the transaction.
By default if no transaction demarcation is specified enterprise beans use container-managed transaction demarcation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974021#3974021
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974021
19 years, 7 months
[Clustering/JBoss] - Re: Cluster Membership after Network Failure
by dfisher
I downloaded JGroups 2.4 CR2 and replaced the JBoss jgroups jar with the jgroups-all jar.
I now get this Exception when the node-2 joins the Partition:
anonymous wrote :
| 2006-09-25 15:59:59,426 WARN [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] failed unserializing message buffer (msg=[dst: , src: X.X.X.2:7800 (2 headers), size = 304 bytes])
| java.io.StreamCorruptedException: invalid stream header
| at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:737)
| at java.io.ObjectInputStream.(ObjectInputStream.java:253)
| at org.jboss.invocation.MarshalledValueInputStream.(MarshalledValueInpu tStream.java:74)
| at org.jboss.ha.framework.server.HAPartitionImpl.objectFromByteBuffer(HAParti tionImpl.java:144)
| at org.jboss.ha.framework.server.HAPartitionImpl.handle(HAPartitionImpl.java: 967)
| at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java: 623)
| at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java :508)
| at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:331)
| at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher. java:763)
| at org.jgroups.JChannel.up(JChannel.java:1078)
| at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:377)
| at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:393)
| at org.jgroups.stack.Protocol.passUp(Protocol.java:538)
| at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:163)
| at org.jgroups.stack.UpHandler.run(Protocol.java:60)
|
Is there something else I need to do to upgrade JGroups?
Copying the concurrent jar that ships with JGroups caused a whole slew of new exception.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974017#3974017
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974017
19 years, 7 months