[JBoss JIRA] (ISPN-10070) DefaultCacheManager should stop components after start failure
by Dan Berindei (Jira)
Dan Berindei created ISPN-10070:
-----------------------------------
Summary: DefaultCacheManager should stop components after start failure
Key: ISPN-10070
URL: https://issues.jboss.org/browse/ISPN-10070
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.4.10.Final, 10.0.0.Beta2
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 10.0.0.Beta3, 9.4.11.Final
Currently it is impossible to release all the resources allocated during startup if the {{DefaultCacheManager}} instance was created with {{start=true}}. The user has to do something like this:
{code:java}
DefaultCacheManager manager = new DefaultCacheManager(..., false);
try {
manager.start();
} catch (Throwable t) {
manager.stop();
throw t;
}
{code}
Both the constructor and the public {{start()}} method should clean up the started components after a startup failure, so that the user doesn't have to call {{stop()}} explicitly.
Our tests do not currently call {{stop()}} explicitly, so they leak threads and sockets when a manager fails to start (e.g. because something went wrong with the {{CONFIG}} cache).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10067) Server remote store is missing server-name attribute
by Wolf-Dieter Fink (Jira)
Wolf-Dieter Fink created ISPN-10067:
---------------------------------------
Summary: Server remote store is missing server-name attribute
Key: ISPN-10067
URL: https://issues.jboss.org/browse/ISPN-10067
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores, Server
Affects Versions: 10.0.0.Beta2, 9.4.10.Final
Reporter: Wolf-Dieter Fink
Assignee: Tristan Tarrant
Fix For: 10.0.0.Beta3, 9.4.11.Final
When attempting to connect to a server with DIGEST authentication, the client needs to be able to specify the server name, otherwise the following error will happen "javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched URI: hotrod/null; expecting one of: hotrod/myserver"
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months