We are still looking into this - I had a quick question around the way in which
a JBMActivation stops, it looks like you stop delivery and then start a
teardown. As I'm following it when I choose stopDelivery on the MDB it then
requested deactiveEndpoint in the reosource adapter which finally
[quote
]If the message is currently being consumed shouldn't this be waiting for that
transaction? I'm wondering if this is causing the session can not be found when
the in-flight transaction completes?
View the original post :
anonymous wrote :
| If the message is currently being consumed shouldn't this be waiting for
that transaction? I'm wondering if this is causing the session can not be found
when the in-flight transaction completes?
|
You are right.
View the original post :
We have continued to work on this one - and have upgraded to the latest JBoss
5.1.0GA release.
This appears to have resolved the problem with the XA transaction - however we
are using the stopDelivery method on the EJB3 MDB MBean and are getting a
session cannot be found during the
Hi,
I think 'session cannot be found' can happen as I explained. To further verify
my reasoning, you can try to find in the server's server.log if there is
something like:
A problem has been detected with the connection to remote client x,
jmsClientID=. It is possible the
Sorry, actually the second case I supposed (shared connection) is unlikely to
happen. As if it happened, there wouldn't be error messages like you have got.
It should be detected by other clients before reaching that point.
View the original post :
I'm not familiar with this stopDelivery method - I guess this is something
added by the EJB team.
Like Howard says, perhaps it is doing something illegal, but without seeing the
code for it, it would be hard to tell.
View the original post :
Thanks for all the help and insight - I'll jump back over to EJB3 and see if
maybe it is a configuration issue in the deployment or a problem in the EJB3
container (since stopDelivery was only recently added).
Thanks again
P
View the original post :
We are running on a JBoss 5.0.1GA base, though we needed the startDelivery and
stopDelivery methods to exist on the MDB container therefore we upgraded the
EJB 3.0 container to 1.1.4(?).
Judging from the log its a JBoss 1.4.1.GA server, this is just what came with
the server.
|
Hi Phillp,
How many JBoss AS server instances are you running? Is the JBM running in one
instance, and the MDB is running in another? Are they on the same machine or
separate machines? If there are multiple instances, which one do you shut down
first, which one second?
Thanks.
View the
This is just a single JBoss instance, and the only one on the network while we
are testing. The persistence if using Oracle 11g to a database on a second
server.
Thanks again
P
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232505#4232505
Reply to the
ok, this is probably a service shutdown sequence issue between MDB and
Transaction Service. You can ask AS guy for how to make sure the Transaction
Service is shutdown before MDB services.
Or you may not kill the process while there is live transactions.
View the original post :
Regarding the non-serializable error, look at this thread:
http://www.jboss.org/index.html?module=bbop=viewtopict=152893
I'm not sure why you're getting this error though. Maybe some missing
dependency between JCA and JBossMessaging and the shutdown order is not being
respected?
View the
anonymous wrote : I'm not sure why you're getting this error though.
I was referring to this error:
| 2009-05-20 12:30:52,499 ERROR [org.jboss.messaging.util.ExceptionUtil]
(WorkManager(2)-44) Connectio
| nEndpoint[fe-oz919yuf-1-mj809yuf-bruz48-x21o4c5] sendTransaction
Hi Clebert
We have put in the recovery settings into the jbossjta-properties.xml and also
moved it to the top during testing.
It worries me a little that the session isn't found - I could only find
references to that problem occurring in a clustered environment (see
Hi Phillip, please give some details of your application server deployment and
the version of JBM.
The possible reason of the Cannot find session with id is that the session
has been closed before the 'commit' request arrives.
How did you shutdown your application servers? and in what order?
16 matches
Mail list logo
