Title: RE: [JBoss-user] Some J2EE Design Questions
Sorry, connectionless was admittedly a poor choice of words. Typically, that applies to UDP protocols (SNMP, TFTP, and the like).
In most applications of RMI, a client-server RMI connection is not a long-lasting one. By long-lasting, I mean
Title: JBoss XA transaction with WebSphere MQ
1. If EJB Timer (2.1) does not fit the bill for you, an
MBean is a typically a good solution for this problem. Depends on what you mean
by service.
2. Since RMI is a connectionless
protocol (not a persistent connection), there is really no
1. If EJB Timer (2.1) does not fit the bill for you, an MBean is a
typically
a good solution for this problem. Depends on what you mean by service.
What is the status of JBoss implementing EJB 2.1 specs ? The only source of
information I have on this subject is theserverside's matrix, which
Hello Mike,
Could you explain what you mean when you say RMI is a connectionless
protocol (not a persistent connection)
Richard
Finn, Michael wrote:
1. If EJB Timer (2.1) does not fit the bill for you, an MBean is a
typically a good solution for this problem. Depends on what you mean by
Title: RE: [JBoss-user] Some J2EE Design Questions
Pretty sure it's all in cvs head at this point, which means 4.0 (should be in DR1). I don't think there are plans to backport to 3.2 branch, but to be sure, check jboss-dev.
mike
-Original Message-
From: Dan Avram [mailto:[EMAIL
We have attacked this problem in two ways.
One was to use the MBean timer to time out sessions
after a period of inactivity.
The second, more difficult but with some fringe
benefits, was to use heartbeating from the client. We
used JMS heartbeats.
See
