| Summary: | Read timeout when trying to create connection to VDB. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Marek Baluch <mbaluch> |
| Component: | EDS | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.ER2 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2380 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-12 11:58:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Marek Baluch
2010-10-06 12:22:02 UTC
Link: Added: This issue depends TEIID-1291 Couple of things: - you're using the admin port of 31443 for jdbc queries. you should be using the jdbc port, which defaults to 31000 - in ER2, the admin port defaults to using the secure protocol of "mms" - the admin port and the jdbc port use different security domains. so you could eventually have issues if you thought you added the user to the teiid-security-users.properties and tried to use that user id when connecting via the admin port. - as for querying using the admin port, this is an undocumented feature, and there are possible plans to tighten this down so that only admin calls can be made on this port. If you can make the change to use port 31000 and retry, it would be appreciated. It works with the jdbc port. I guess that the use of admin port changed between ER1 and ER2. It was possible to use the admin port on ER1 without problems. From ER1 to ER2 the default secure protocol was changed to mms. So existing test using the mm protocol on the admin port would fail. As for using the admin port for jdbc queries, it's not a documented feature. So please do not setup your test to use the admin port for queries. The engineers are considering enforcing that the admin port not be used for jdbc queries. The use of the jdbc port, as recommended, was successful. As for using undocumented features or future enhancements regarding how the admin and jdbc ports are used, please log an jira specific to the enhancement you would like to see. Thanks for the advice. |