Home » Search

About listener

131-135 of 135Refresh
Issue
1

Unexpected error when loading all entity instance

a contextDestroyed listener? During the last corruption did you have hot deployments (i.e. in the last day
Issue
1

Query in nested transaction returns detached entity if lazy-loaded

. We worked on enhanced classes. We activated the entity listeners for pre persisted and post persisted
Result
1

ObjectDB version 2.7.5

Version 2.7.5 Improved recovery from failure when recovery is enabled with no sync  (issue #2293, issue #2294). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading (issue #2299). Fixed a bug in restricting server access to a range of IPs (issue
Result
0

[ODB1] Chapter 8 - ObjectDB Server

to listen to To start the server, use the start command: > java com.objectdb.Server start ... when you extract a newer version of the ObjectDB server. The TPC port on which the server is listening for new ... on which the server will be listening for new connections. Usually, it should be set to 6136, which is the default
Result
0

[ODB1] Chapter 5 - JDO Connections

to be running on a machine named host (could be domain name or ip address) and listening ... machine) and listening to the default port (6136): Properties properties = new Properties