Internal Website Search

1-28 of 28 results

listening on a particular IP aside localhost

8888 in configuration file but I wasn't able to add listening ip address such as 192.168.50.56 olyjosh ... . If the server has several different IP addresses then ObjectDB will listen on all of them and specifying specific IP addresses is not supported. Associating a server with IP addresses is of course unrelated to the ObjectDB configuration. support Support

Server User List

that have to be provided when the user connects to the server. The optional ip attribute, if specified, restricts the user to connect to the server only from the specified IP addresses. For instance, "127.0.0.1 ... on which the server is running. Multiple IP addresses can also be specified in a comma separated list and using

Privacy Policy

Data may include information such as Your Device's Internet Protocol address (e.g. IP address), unique ... , the IP address of Your mobile device, Your mobile operating system, the type of mobile Internet

ObjectDB Object Database Features

Client-Server mode (TCP/ IP ). Secure Client-Server mode ( SSL over TCP/ IP ). In process embedded database

Database Server

of TCP/ IP communication between the client and the server it is usually slower than embedded mode ... The TPC/ IP port on which the server listens for new connections is also specified in the Server

Database Connection using JPA

(could be a domain name or an IP address) and listening on the specified port (the default is 6136

ObjectDB is opening too many sockets

(AF_INET6, SOCK_STREAM, IPPROTO_ IP ) = 46494 [pid 26650] 02:48:00.250400 setsockopt(46494 , SOL_IPV6 ... _onoff=0, l_linger=0}, [8]) = 0 [pid 26650] 02:48:00.256978 socket(AF_INET6, SOCK_STREAM, IPPROTO_ IP ... 26650] 02:48:00.269934 socket(AF_INET6, SOCK_STREAM, IPPROTO_ IP ) = 55389 [pid 26650] 02:48:00.274090

The server cannot start in CentOS

all connections? I will try tomorrow. gzdillon Lai Yang The server seems connected, but I set my pc ip to the objectdb.conf, and get the following: Persist failed: Login Error (unauthorized IP address ... (XMLErrorReporter.java:321)   gzdillon Lai Yang Try to remove the ip attribute in

[ODB1] Chapter 8 - ObjectDB Server

these databases from remote machines by TCP/ IP . More details about client server mode vs. embedded database ... to the server only from the specified IP address. For instance, the "127.0.0.1" value ... on which the server process is running. Multiple IP addresses can also be specified in a comma

JSON serialization and __odbHidden members

; "lastActivity":    {        " IP ": "127.0.0.1",     ... ; {        " IP ": "127.0.0.1",        "date ... ;  },    "regActivity":    {        " IP ": "127.0

A distinguished Name for server or explorer is good for maintaining!

, it always outputs this message, regardless changing IP setting: private final static ... by: com.objectdb.o._PersistenceException: Login Error (unauthorized IP address for user 'admin ... .java:16) ... 1 more Caused by: com.objectdb.o.UserException: Login Error (unauthorized IP address

in-memory and on-disk support?

/ IP option but I would like both DB's accessible in-program without the need for TCP/ IP as ... process) mode with no TCP/ IP . Alternatively you can try the more conventional setting of one ordinary

multiple connection using share folder

( ip address or domain name) and port. It is possible in embedded-server mode but it would be easier with client-server mode. Run the ObjectDB Server on one computer. See this manual page . Find the ip ... host and port (see this manual page ). Do not use localhost from other computers but an ip address or

ArrayIndexOutOfBoundsException at com.objectdb.o.ALS.c(ALS.java:89)

.createEntityManager var queryString: java.lang.String = "SELECT res FROM LogEntry res WHERE res.spa = '" + Ip .toString(arp.spa) + "'" // Get LogEntry's with same IP var query: TypedQuery[LogEntry] = em.createQuery

[ODB1] Chapter 1 - About ObjectDB

running on different JVM's communicate with the database server using TCP/ IP . Many client processes ... and faster because no server has to run in the background and no TCP/ IP communication is needed. Adding

Activation error on Schema change

had to activate one more server with Debian - the one with private ip as our development env (23.02

Activation Issue

, it was shutdown the laptop, and move to the office. The activation code isn't tied to IP addresses in any way

Connecting to a remote objectdb server

I am trying to configure my application in a client-server objectdb setup via tcp/ ip . So I first made sure that the remote objectdb server is running using telnet from my local.  $ telnet db.mydomain.com 6136 (worked fine, is able to connect...) My db was configured below: On my application

Composite Index error 328

) { this.lastLogin = lastLogin; } @Basic @Column(name = "last_ ip ") public String getLastIp() { return lastIp

EntityManager creation taking long time

and server on the same machine?  createEntityManager requires a new TCP/ IP connection. Maybe the delay

Many connections possible? and will it makes problem in future?

system) and TCP/ IP ports (when using client-server mode). support Support

connect with server

is my EntityManagerFactory & em is my EntityManager 192.168.0.300 is my server IP   eng.ahmed ahmed Just run

WAN replication ? possible?

these instructions and replace localhost with real IP addresses. You may have to configure routers, Firewall

How to disable use of graphic windows by objectDB

-unknownhostexception support Support One thing, is there any way to specify a ip address

Login Error (bad username 'admin' or password)

. What does happen when you access localhost but using its current IP address? I checked, and both client

[ODB1] Chapter 5 - JDO Connections

is expected to be running on a machine named host (could be domain name or ip address) and listening

Monitoring and Performance counters

for each open connection, see: database name that it is connected to Client username and IP address

ObjectDB 2.7.5

Improved recovery from failure when recovery is enabled with no sync  ( issue #2293 ). 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 #2292 ). Fixed