Hi there,
are there restrictions in connection number or something when connecting
to a db2 express c luw through ssl?
i have a strange problem: my db2 server is in the internet and configured
to only accept connections through SSL (port 50001). locally i installed the
server client (v9.5fp2), and cataloged the connection. so if i connect with
the browser to my dev apache, php opens a cataloged connection through the
client and SSL to the server. That works pretty well and fast (limited by
dsl).
For a colleague i reinstalled my setup into a fresh "virtualbox " virtual
machine. this virtualized installation works too, at least mostly. The vm
does NAT for its networking and all vm-installation share the same ssl-key
and certificate (should be changed soon).
what i now experience are connection timeouts when i try to connect to the
db2 server from the vm. even when using db2 cli tool there are timeouts
or periods during that nothing happens and then suddenly db2 cli reports a
successful connection after 2-3 minutes of waiting.
the database is activated on the server to save the startup overhead...
does somebody has some hints what causes these timeouts?
--
MfG, Christian Welzel aka Gawain@Regenbog en
GPG-Key: http://www.camlann.de/key.asc
Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15
are there restrictions in connection number or something when connecting
to a db2 express c luw through ssl?
i have a strange problem: my db2 server is in the internet and configured
to only accept connections through SSL (port 50001). locally i installed the
server client (v9.5fp2), and cataloged the connection. so if i connect with
the browser to my dev apache, php opens a cataloged connection through the
client and SSL to the server. That works pretty well and fast (limited by
dsl).
For a colleague i reinstalled my setup into a fresh "virtualbox " virtual
machine. this virtualized installation works too, at least mostly. The vm
does NAT for its networking and all vm-installation share the same ssl-key
and certificate (should be changed soon).
what i now experience are connection timeouts when i try to connect to the
db2 server from the vm. even when using db2 cli tool there are timeouts
or periods during that nothing happens and then suddenly db2 cli reports a
successful connection after 2-3 minutes of waiting.
the database is activated on the server to save the startup overhead...
does somebody has some hints what causes these timeouts?
--
MfG, Christian Welzel aka Gawain@Regenbog en
GPG-Key: http://www.camlann.de/key.asc
Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15