My last post is not quite complete.
UserTransactions are of course also use in Beans with BMT. However, the
UserTransaction object is the object that you have to use to start, commit and
rollback your transactions. The EJBContext holds the state for an EJB (CMT and
BMT) and is managed by the App
hehe, agreed. This actually the first time since 6 months that I am looking in
to this forum again. I normally don't bother to look here anymore, because of
the attitude of some "officials".
Sad that things haven't changed.
View the original post :
http://www.jboss.org/index.html?module=bb&op=
and deleting the messages is only fighting a symptom anyway. Those messages should
never appear in the database because they were already delivered before the database
comes online again and there are no durable subscribers.
View the original post :
http://www.jboss.org/index.html?module=bb&op=
We know that, but unfortunately you decided to switch from tomcat 4.x to tomcat 5
which makes 3.2.4/5 a new major release and not a minor release or patch.
The customer would have to start their whole test cycle again, which would move the
live date to next year, which would cost us more than $
a quick update on this issue.
According to our investigations the problem was the result of probably two bugs in
Jboss.
If the database is not available and the cache limit is reached, the messages are not
deleted from the cache after delivery (you can see the the counter going up in the JMX
c
just to clarify, when I am saying "professional support teams" I am not talking about
the JBoss support or IONA in specific. I was just making a generalised statement based
on almost 20 years of experience with support teams from almost every major software
company.
No offense...
Btw, when I a
The IONA support was engaged by the PROJECT team after I started the thread. I am
responsible for the PRODUCT development and try to get answers from whereever I can.
The guaranteed answers from official support teams are often enough "sorry, we don't
know". I have more trust in the community th
Adrian,
thanks for your response. I am aware of the temp message in that version. But this is
not original problem in my opinion. I configured a DurableSubscriber for the Topic to
keep all the messages in the table. The system is definitely not using temporary
topics. It seems that these messag
Getting a little bit confused. My previous post was not right, I think.
The destination for the entries in the JMS table is something like
TOPIC.ErrorTopic.ID:3.-2147483648
This syntax with the ID is used for temporary topics, right?
So, next guess:
For some reason on the customer site the topic
My comment about the messages being sent to a temporary topic is actually not true. I
mis-interpreted the "T" in the TXOP column. It only means they are inserted by the
message cache, right?
I still do not know how JBossMQ works when the database is down. I would expect to get
an exception imme
We had some weird phenomenons at a customer site that we are unable to explain. I am
actually not sure if anyone can explain that. I can already see adrian asking me what
drugs I am taking :)
The customer is currently running acceptance tests for our product which will take
about 2 months.
Our
Any updates on the release date for JBoss 4. The roadmap says Q2. We are now at the
end of May, so you should be able to give a more exact date for the release.
There are no plans to implement the EJB 2.1 timer objects in JBoss 3.2.x, right?
View the original post :
http://www.jboss.org/index.ht
12 matches
Mail list logo
