[
https://issues.jboss.org/browse/TEIID-2132?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2132:
-------------------------------------
I can not find way to pass the server side socket that is created through the AS framework
into Netty for creation of channel. Currently Teiid reads the address and port
information, and passes this information directly to Netty and it creates the necessary
sockets. Lack of use framework to create the socket on AS side contributing to this
issue.
Teiid 8.0 API does not expose boundport in Mbean attribute for
Teiid-JDBC
-------------------------------------------------------------------------
Key: TEIID-2132
URL:
https://issues.jboss.org/browse/TEIID-2132
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.0
Environment: jboss 7, teiid 8, windows 7
Reporter: Akshay Harale
Assignee: Ramesh Reddy
Priority: Minor
Labels: jboss, teiid
Fix For: 8.2
When offset is set for jboss from standalone.xml or standalone.conf.bat file, the bound
port is not displyed in MBean server.
For example,
<socket-binding-group name="standard-sockets"
default-interface="public"
port-offset="${jboss.socket.binding.port-offset:25}">
In above line if I set the value as 25 then that should be added to the default socket
port values and exposed as bound port value in MBean server. But in case of teiid the
"teiid-jdbc" 's boundPort value is not exposed by the jboss.
All other boundPorts values are correctly shown in Mbean, except teiid-jdbc
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira