Feedback
Did this article resolve your question/issue?

   

Article

OpenAccess ServiceHost length limit

Information

 
TitleOpenAccess ServiceHost length limit
URL Nameopenaccess-servicehost-length-limit
Article Number000147721
EnvironmentProduct: OpenAccess SDK
Version: 8.1
OS: All supported platforms
Application: oacla
Question/Problem Description
An error is returned when administering an OpenAccess server on a host with a long name.
Steps to Reproduce- Install the OpenAccess server on a host with a long name, for instance 'mydemo2linux-201908121644-testname-linux-0.aws.mycompany.com'

- Create an OpenAccess service on the machine.
/usr/oaserver81/admin/oacla.sh -nologo -dbg -e /tmp/myodbcserver.log -d /usr/oaserver81/cfg/oadm.ini ServiceCreate MyService OA81_OpenAccessSDKforC

- Any subsequent commands will return an error, for example, this command returns the error below.
/usr/oaserver81/admin/oacla.sh -nologo -dbg -e /tmp/myodbcserver.log -d /usr/oaserver81/cfg/oadm.ini DataSourceCreate MyService MyDSN
Clarifying Information
Error Message[OpenAccess error 267] Internal error. Truncation error in the resource manager.
[OpenAccess error 384] Missing key in configuration file.
[OpenAccess error 6865] Invalid service name MyService.
Defect Number
Enhancement Number
Cause
This is expected behavior.
The ServiceHost name length is limited by the ServiceConnectInfo length.  Both ServiceConnectInfo and ServiceHost have a length limit of 64.  However, ServiceConnectInfo includes the host name value in ServiceHost, so if the ServiceHost name is too long, the size of ServiceConnectInfo exceeds 64 characters.
Resolution
Limit the length of the machine's hostname to allow for its inclusion in the ServiceConnectInfo setting.  The allowed ServiceHost name length is based on the size of ServiceConnectInfo, so the calculation is:

ServiceHost allowed length = 64 - 6 - 1 - size(port number) = 57 - size(port number)

 
Workaround
Contact Technical Support for a workaround.
Notes
Last Modified Date3/24/2020 6:14 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.