openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "krishnadas.ts" <>
Subject Re: [jira] Created: (OPENJPA-943) How to configure cache synchronization in the case of multiple jvm in same machine
Date Fri, 27 Feb 2009 09:56:54 GMT

hi Pinaki Poddar,

    I changed weblogic cluster messaging from Unicast to MultiCast. Now  It
is working fine with cluster option.Thanks a lot for your response.Anyway
for curiosity i am asking.Is there no option to work kodo with unicast
option.Where i can get a good documentation about tcp configuration for
clustering.i searched a lot of kod and openjpa configuration.only
information i can get is to give like this

      <property name="kodo.RemoteCommitProvider"

But from this i think this is not enough for the case of multiple jvm in
same machine.As far as from my understanding i think in same machine for two
jvm it will try to create two listener in same port(5454).So one of them
will definitly fail.Is there any other parameter to be configured.Or can you
give link of information that says about these think.My application may work
with by setting it to cluster.But i just want to know the concept.i could
not see configuration details for sender and listener port in any
documentation.Only i can see from documentation is the following one.
 The TCP remote commit provider has several options that are defined as host
specifications containing a host name or IP address and an optional port
separated by a colon. For example, the host specification  represents an InetAddress retrieved by invoking
InetAddress.getByName ("")  and a port of 1234.

The TCP provider can be configured by setting the kodo.RemoteCommitProvider
plugin property to contain the appropriate configuration settings. The TCP
provider understands the following properties:


      Port: The TCP port that the provider should listen on for commit
notifications. Defaults to 5636.

      Addresses: A semicolon-separated list of IP addresses to which
notifications should be sent. No default value.

      NumBroadcastThreads: The number of threads to create for the purpose
of transmitting events to peers. You sould increase this value as the number
of concurrent transactions increases. The maximum number of concurrent
transactions is a function of the size of the connection pool. See the the
MaxActive property of kodo.ConnectionFactoryProperties in Section 4.1,
“Using the Kodo DataSource”. Setting a value of 0 will result in behavior
where the thread invoking commit will perform the broadcast directly.
Defaults to 2.

      RecoveryTimeMillis: Amount of time to wait in milliseconds before
attempting to reconnect to a peer of the cluster when connectivity to the
peer is lost. Defaults to 15000.

      MaxIdle: The number of TCP sockets (channels) to keep open to each
peer in the cluster for the transmission of events. Defaults to 2.

      MaxActive: The maximum allowed number of TCP sockets (channels) to
open simultaneously between each peer in the cluster. Defaults to 2. 

To configure a factory to use the TCP provider, your properties might look
like the following:

Example 11.10. TCP Remote Commit Provider Configuration

JPA XML format:

<property name="kodo.RemoteCommitProvider" 

JDO properties format:



So please give me guidance

Thanks and regards
Krishnadasan T S

View this message in context:
Sent from the OpenJPA Developers mailing list archive at

View raw message