About client server

81-90 of 200Refresh
Issue
6

Errors after unexpected server shutdown

After an unexpected server shutdown and restart of our application we have these messages in the log (complete log attached): … [2018-03-26 14:39:30 #1096 store] Request Value: 10:'b61e33d4-8d57-478d-9176-6aa0e2031470' [2018-03-26 14:39:30 #1097 store] *** Attempt to remove a non
Issue
6

500 Internal Server Error on creating a new issue

500 Internal Server Error on creating a new issue
Issue
6

Generating new activation code gives 500 server error

Generating new activation code gives 500 server error
Manual
4

Database Replication and Clustering

, which is managed on an ordinary ObjectDB database server. Any ObjectDB database on any server (but not in ... and only requires running an ObjectDB database server with appropriate  elements in the configuration: <server>          
JDO Doc
4

javax.jdo.PersistenceManagerFactory

with this PersistenceManagerFactory. If not set, assume that the server has the same TimeZone ID as the client. Returns ... that the server has the same TimeZone ID as the client. If incorrectly set, the result of PersistenceManager ... a server to dynamically bind to an instance from this factory associated with the thread's current
Result
3

[ODB1] Chapter 8 - ObjectDB Server

these databases from remote machines by TCP/IP. More details about client server mode vs. embedded database ... support for embedded mode. In order to use client server mode, you have to install the odbse.jar file on both the client and the server machines. This section explains how to run the server
Issue
3

stress test -> com.objectdb.o.InternalException: null

com.objectdb.o.UserException: Mismatch client-server protocol prefix at com.objectdb.o.MSG.d(MSG ... to ObjectDB - (which is still part of your code)) com.objectdb.o.UserException: Mismatch client-server ... . The "Mismatch client-server protocol prefix" is another issue that was reported in the past rarely and we don't
Tutorial
3

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
3

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
Forum
3

Schema Evolution Question

The documentation indicates that " In client-server mode the ObjectDB server must be restarted ... server. Start ObjectDB server. Start new client application with the new schema. I followed these steps in the prescribed order. Stop old client application with the old schema. Stop ObjectDB server