Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Could not find coordinator while committing transaction

573 views
Skip to first unread message

Javier Keller

unread,
May 29, 2003, 7:19:10 AM5/29/03
to
Hello,

does anyone know the meaning of the following exception?

javax.transaction.SystemException: Could not contact coordinator at
WL1-2+WL1-2:7003+KK+

No stack trace is available in our log files. We get this exception
when trying to commit a transaction after modifying some data using
container managed persistence with WLS 6.1 sp 3 (the problem is not
necessarily related to container managed persistence, but I didn't
find a better group to post to)

Any ideas will be appreciated

Slava Imeshev

unread,
May 29, 2003, 12:57:27 PM5/29/03
to
Hi Javier,

Could you tell us more about where and when you are
getting this exception? If you see it in the log, could you
post the whole log message?

"Javier Keller" <javier...@pure.de> wrote in message
news:b6d37cf5.03052...@posting.google.com...


Regards,

Slava Imeshev


Tony Lu

unread,
May 29, 2003, 4:42:53 PM5/29/03
to
javier...@pure.de (Javier Keller) wrote in message news:<b6d37cf5.03052...@posting.google.com>...

I have seen this problem as well. it happened when we move our JMS
server to a new machine and the other application servers start to get
this exception, even I modified related setting for JMS server on
these servers. I even did a search for the old host name on those
servers, found nothing.
if you get any progress please let us know.

thanks

Javier Keller

unread,
May 30, 2003, 8:20:53 AM5/30/03
to
> Could you tell us more about where and when you are
> getting this exception? If you see it in the log, could you
> post the whole log message?

The strange thing is that there is no further log message given
indication of the problem. I see the usual log messages of our cmp
beans doing their work. The logic is pretty simple: we are updating
about 400 data records inside a single client transaction using cmp.
Everything works all right, but at the moment of committing we get
this strange message and everything is rolled back... And exactly the
same logic has been working for over one year! So I guess it might be
something with our configuration, as suggested by the other poster,
but what exactly? We use cmp in a clustered environment.

Thanks for your reply,

Javier

Tony Lu

unread,
May 30, 2003, 11:36:21 AM5/30/03
to
I renamed my new server name from MyServer to MainServer, and that
problem goes away.My feeling is that this is network setting related.

Javier Keller

unread,
Jun 5, 2003, 11:09:27 AM6/5/03
to
dol...@hotmail.com (Tony Lu) wrote in message news:<4a973fa8.0305...@posting.google.com>...

I've found out that the names of our servers had been changed in the
config.xml. This seems to be the cause of the mentioned problem about
transactions. Moreover we got some other weird error messages like "Method
create is deployed as TX_MANDATORY, but it was called without a transaction",
even if the client had opened a transaction before creating the ejb...

We don't get these message after having restarted all servers...

Regards,

Javier

0 new messages