About client server

101-110 of 200Refresh
JDO Doc
2

javax.jdo.PersistenceManager

Date getServerDate() Get the Date as seen by the server. Get the Date as seen by the server. Clients ... the setting of the server time zone to prepare a Date instance that represents UTC time on the server. Returns: a Date instance corresponding to the UTC Date as seen by the server Since: JDO 2.1
Tutorial
2

Step 7: Run the Spring Web App

a server in your Eclipse - you can run the application now by right clicking the project node (in the [Project Explorer] window), selecting Run As > Run on Server, selecting the Tomcat 6.0 server and clicking Finish. To install a new server check the Manually define a new server radio button (after Run As
Tutorial
2

Step 7: Run the Spring Web App

as a server in your NetBeans - you should be able to run your application now by selecting Run > Run Main Project from the main menu (or F6): You can select the server in the Run category ... . You can stop the Tomcat server and open the database file in ObjectDB Explorer: To enable on the fly
JDO Doc
2

getServerDate()

Method javax.jdo.PersistenceManager Date getServerDate() Get the Date as seen by the server. Clients using this method can order their operations according to a single time source. Implementations use the setting of the server time zone to prepare a Date instance that represents UTC time
JDO Doc
2

getServerTimeZoneID()

Method javax.jdo.PersistenceManagerFactory String getServerTimeZoneID() Gets the TimeZone ID of the server associated with this PersistenceManagerFactory. If not set, assume that the server has the same TimeZone ID as the client. Returns: the TimeZone of the server Since: JDO 2.1 See Also: setServerTimeZoneID(String)
JDO Doc
2

setServerTimeZoneID(timezoneid)

the TimeZone ID of the server associated with this PersistenceManagerFactory. The parameter is a String ... .getAvailableIDs(). If the ServerTimeZoneID is not set, or set to the null String, assume that the server has the same TimeZone ID as the client. If incorrectly set, the result of PersistenceManager
Issue
2

objectdb-2.6.9_06: Extended Persistence Context fails: 'Attempt to begin a new transaction when a transaction is active'

" entity, but this has no consequence for the problems reported.) The client @Singleton @Startup ... due to the transaction not ending * after {@link buildProject} is invoked TWICE from a client like {@link ... .data.ApplicationInfo.start(ApplicationInfo.java:352) at com.sun.enterprise.v3.server
Manual
2

Entity Management Settings

The configuration element specifies front end settings that are relevant on the client side and in embedded mode. The default configuration file contains the following element:
Forum
2

objectdb.conf Information

Hello, Is it possible to get detailed information on objectdb.conf client vs server? We do have an objectdb.conf for our client and one for our server instance. Now there're several questions: - Which config entries are relevant for the client and which one for the server? I.e. what about:
Forum
2

Replication error on slave restart

="$objectdb/ssl/server-kstore" password="pwd" />   <client-truststore path="$objectdb/ssl/client ... I'm trying to enable replication on master server that was running with "recovery" enabled ... slave server: com.objectdb.o.UserException: Failed to synchronize replicated database