Hi Ashish
The ones you refer to below are Shoal properties exposed in GlassFish
not the other way around. (BTW, setting such low values for failure
detection and verification is not recommended and advisable if you are
building a distributed system that needs to be resilient to failures -
settng small timeouts might give you immediate benefit of quick
notifications in a dev setup but in production might expose you to
significant number of false failure notifications for transient network
hiccups or delayed messages)
For more on configurations that can be exposed, see the
ServiceProviderConfigurationKeys Javadoc here :
https://shoal.dev.java.net/nonav/docs/api/com/sun/enterprise/ee/cms/core/ServiceProviderConfigurationKeys.html
Let us know if this answers your question.
--Shreedhar
Ashish Waghmare wrote:
> Hi ,
> For project only using Shoal Framework , but stuck with its
> configuration
> Glassfish provides good configuration . But couldnt map how these
> settings affect Shaol configuration.
> Few of the things in Glassfish can be done in shoal using
>
> configProps.put(ServiceProviderConfigurationKeys.FAILURE_DETECTION_TIMEOUT.toString(),"10");
>
>
> configProps.put(ServiceProviderConfigurationKeys.FAILURE_VERIFICATION_TIMEOUT.toString(),"200");
>
>
> Is there any other mappings available for glassfish properties?
>
>
> Thanks & Regards
> Ashish Waghmare
>
>