Bug 841892
| Summary: | ping_on_startup ignored | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Tristan Tarrant <ttarrant> |
| Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED UPSTREAM | QA Contact: | Martin Gencur <mgencur> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0.0 | CC: | jdg-bugs, nobody, oskutka |
| Target Milestone: | ER3 | ||
| Target Release: | 6.0.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In JBoss Data Grid 6.0.0 the HotRod client option infinispan.client.hotrod.ping_on_startup was ignored and the client pinged the servers on start up. This is now resolved and the client's behavior is in accordance with the infinispan.client.hotrod.ping_on_startup option.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:20:20 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: | |
| Embargoed: | |||
|
Description
Tristan Tarrant
2012-07-20 13:49:21 UTC
Michal Linhard <mlinhard> updated the status of jira ISPN-2139 to Reopened Michal Linhard <mlinhard> made a comment on jira ISPN-2139 Hi, I'm just looking at this in 5.1.6.FINAL and the flag infinispan.client.hotrod.ping_on_startup is still ignored - the ping is done regardless of it. I guess it's not a good thing not doing the ping because of the cache name validation at least. Shouldn't we remove the flag infinispan.client.hotrod.ping_on_startup completely ? As of now it's of no use. Before releasing 5.2.0 is good time to do this. Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-2139 to Resolved Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-2139 Since the associated fix versions were released, please avoid reopening the JIRA and simply create a new one with the right affects versions. What is it that you're seeing exactly? I added a test to verify that ping_on_startup disabling worked... When getCache is called the ping is done regardless of ping_on_startup flag. The only effect ping_on_startup has is preventing first ping in TransportObjectFactory.makeObject Radim Vansa <rvansa> updated the status of jira ISPN-2215 to Closed Radim Vansa <rvansa> made a comment on jira ISPN-2215 Verified, in 5.1.7.Final-redhat-1 this is fixed. Radim Vansa <rvansa> made a comment on jira ISPN-2215 Correction, 5.1.7.Final-redhat-0 (JDG 6.0.1.ER3) This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |