On Mon, 2010-04-19 at 10:16 -0400, Ramesh Reddy wrote:
On Mon, 2010-04-19 at 10:24 -0400, Ken Johnson wrote:
> So by default, the server will not be able to accept remote JDBC
> connections? I see the security benefits of this behavior but also
> end-user inconvenience.
Yes, I agree that this is little inconvenience to the users out of the
box. The primary driving factors were
2) Align the host resolution to be similar to the JBoss AS, so that
users are not given two different choices in configuring the bind
The logic changed *if* the host name resolves "localhost" (mostly
developer machines), however like in any typical shared server
environment would have their host name specified, so they will resolve
to proper LAN address that will be reachable by the known name.
> Does the hostname or IP specified with -b have
> to match *exactly* with the hostname string in the JDBC URL used by
> client applications? Or will it work as long as it resolves down to
> same IP address (I assume the latter but just checking)?
If they resolve to same IP that would be enough. If the sever is started
with "0.0.0.0" then any resolved IP on that machine will be fine. Also,
note that user could still provide the host name/ip in the Teiid
configuration to override the default behavior.
> Also, how will this impact Teiid firewall configuration and dynamic
> environments like Amazon EC2 where internal and external addresses
I do not know. Do these offer IP forwarding services may be?
This primarily deals with issues in the past regarding clustering.
Basically, in the past, a client would make a JDBC connection to the
server and ask for a resource list. The server would create a list of
resources which contains the host name and TCP port number for the
services. The server would use the "host name" property configured at
installation time. So, if I were to install the server and say its host
name was myteiidhost.com
then even when a client would connect using a
host name of public.myteiidhost.com
the server would return a resource
list which only included host names of myteiidhost.com
. If this host
name was not resolvable by the client, the connection would fail mid-way
through. The firewall property was introduced to account for this. If
the firewall property was defined to include a value of
then the resource list would be rewritten to use
the host name the client used rather then the host name used at server
Is this still an issue? Does Teiid server create a resource list that
contains host names/ports?
Middleware Support Engineering Group
Global Support Services
Red Hat, Inc.
1.866.LINUX70 (+1.314.336.2990) xt 81-62909
Looking to carve out IT costs?