[Red Hat JIRA] (ISPN-12592) Improve error message when XML element is removed
by Dan Berindei (Jira)
Dan Berindei created ISPN-12592:
-----------------------------------
Summary: Improve error message when XML element is removed
Key: ISPN-12592
URL: https://issues.redhat.com/browse/ISPN-12592
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Core
Affects Versions: 12.0.0.Dev07
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 12.0.0.CR1
When an element is removed from the XML configuration schema, configurations using the old XML namespace trigger a warning that the element is deprecated, including the name of the replacement element.
Configurations files with no namespace declarations are assumed to be using the latest schema and don't trigger the warning, instead they trigger a generic `Unexpected element 'X' encountered` exception.
Assuming the latest schema is the right thing to do, but we need to improve the error message for upgraders.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[Red Hat JIRA] (ISPN-12592) Improve error message when XML element is removed
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12592?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12592:
--------------------------------
Status: Open (was: New)
> Improve error message when XML element is removed
> -------------------------------------------------
>
> Key: ISPN-12592
> URL: https://issues.redhat.com/browse/ISPN-12592
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Core
> Affects Versions: 12.0.0.Dev07
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.CR1
>
>
> When an element is removed from the XML configuration schema, configurations using the old XML namespace trigger a warning that the element is deprecated, including the name of the replacement element.
> Configurations files with no namespace declarations are assumed to be using the latest schema and don't trigger the warning, instead they trigger a generic `Unexpected element 'X' encountered` exception.
> Assuming the latest schema is the right thing to do, but we need to improve the error message for upgraders.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[Red Hat JIRA] (ISPN-12591) In-place rolling upgrades
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-12591:
--------------------------------------
Summary: In-place rolling upgrades
Key: ISPN-12591
URL: https://issues.redhat.com/browse/ISPN-12591
Project: Infinispan
Issue Type: Task
Components: Core
Reporter: Tristan Tarrant
Fix For: 14.0.0.Final
Requirements:
* Upgrade from one version of Infinispan/JGroups to another
* Use at most one additional node during the process
* Continuous operativity during the process. Performance degradation is acceptable.
* Work during a Kubernetes Rolling Update
* No data loss should occur
Ref: https://github.com/jgroups-extras/RollingUpgrades
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[Red Hat JIRA] (ISPN-4397) HR server is not able to connect to KDC server
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-4397?page=com.atlassian.jira.plugin... ]
Tristan Tarrant closed ISPN-4397.
---------------------------------
Resolution: Out of Date
> HR server is not able to connect to KDC server
> ----------------------------------------------
>
> Key: ISPN-4397
> URL: https://issues.redhat.com/browse/ISPN-4397
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
> Priority: Major
>
> After upgrade to WildFly 8.1 (commit [2eb84c2824d82530e508b2063409b1d22225772d|https://github.com/infinispan/in...]), HotRod server endpoint is not able to connect to KDC server (when kerberos sasl server-context-name name is specified) and startup teh the HR server fails with
> {noformat}
> Caused by: javax.security.auth.login.LoginException: Cannot locate KDC
> at com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:763) [rt.jar:1.7.0_45]
> at com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584) [rt.jar:1.7.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) [rt.jar:1.7.0_45]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.login(LoginContext.java:594) [rt.jar:1.7.0_45]
> at org.infinispan.server.endpoint.subsystem.ProtocolServerService.getServerSubject(ProtocolServerService.java:235)
> at org.infinispan.server.endpoint.subsystem.ProtocolServerService.start(ProtocolServerService.java:126)
> ... 5 more
> Caused by: KrbException: Cannot locate KDC
> at sun.security.krb5.Config.getKDCList(Config.java:1236) [rt.jar:1.7.0_45]
> at sun.security.krb5.KdcComm.send(KdcComm.java:210) [rt.jar:1.7.0_45]
> at sun.security.krb5.KdcComm.send(KdcComm.java:191) [rt.jar:1.7.0_45]
> at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:319) [rt.jar:1.7.0_45]
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:364) [rt.jar:1.7.0_45]
> at com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735) [rt.jar:1.7.0_45]
> ... 19 more
> Caused by: KrbException: Generic error (description in e-text) (60) - Unable to locate KDC for realm INFINISPAN.ORG
> at sun.security.krb5.Config.getKDCFromDNS(Config.java:1333) [rt.jar:1.7.0_45]
> at sun.security.krb5.Config.getKDCList(Config.java:1209) [rt.jar:1.7.0_45]
> ... 24 more
> {noformat}
> In this case KDC run on port 6088 and it's very likely (more in-depth investigation is needed), that krb client used by server ignores path to krb setup (env. var {{java.security.krb5.conf}}) and tried to connect to port 88. This seems to be a bug in WildFly 8.1.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[Red Hat JIRA] (ISPN-4397) HR server is not able to connect to KDC server
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-4397?page=com.atlassian.jira.plugin... ]
Tristan Tarrant reassigned ISPN-4397:
-------------------------------------
Assignee: Tristan Tarrant
> HR server is not able to connect to KDC server
> ----------------------------------------------
>
> Key: ISPN-4397
> URL: https://issues.redhat.com/browse/ISPN-4397
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
> Priority: Major
>
> After upgrade to WildFly 8.1 (commit [2eb84c2824d82530e508b2063409b1d22225772d|https://github.com/infinispan/in...]), HotRod server endpoint is not able to connect to KDC server (when kerberos sasl server-context-name name is specified) and startup teh the HR server fails with
> {noformat}
> Caused by: javax.security.auth.login.LoginException: Cannot locate KDC
> at com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:763) [rt.jar:1.7.0_45]
> at com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:584) [rt.jar:1.7.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) [rt.jar:1.7.0_45]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:695) [rt.jar:1.7.0_45]
> at javax.security.auth.login.LoginContext.login(LoginContext.java:594) [rt.jar:1.7.0_45]
> at org.infinispan.server.endpoint.subsystem.ProtocolServerService.getServerSubject(ProtocolServerService.java:235)
> at org.infinispan.server.endpoint.subsystem.ProtocolServerService.start(ProtocolServerService.java:126)
> ... 5 more
> Caused by: KrbException: Cannot locate KDC
> at sun.security.krb5.Config.getKDCList(Config.java:1236) [rt.jar:1.7.0_45]
> at sun.security.krb5.KdcComm.send(KdcComm.java:210) [rt.jar:1.7.0_45]
> at sun.security.krb5.KdcComm.send(KdcComm.java:191) [rt.jar:1.7.0_45]
> at sun.security.krb5.KrbAsReqBuilder.send(KrbAsReqBuilder.java:319) [rt.jar:1.7.0_45]
> at sun.security.krb5.KrbAsReqBuilder.action(KrbAsReqBuilder.java:364) [rt.jar:1.7.0_45]
> at com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:735) [rt.jar:1.7.0_45]
> ... 19 more
> Caused by: KrbException: Generic error (description in e-text) (60) - Unable to locate KDC for realm INFINISPAN.ORG
> at sun.security.krb5.Config.getKDCFromDNS(Config.java:1333) [rt.jar:1.7.0_45]
> at sun.security.krb5.Config.getKDCList(Config.java:1209) [rt.jar:1.7.0_45]
> ... 24 more
> {noformat}
> In this case KDC run on port 6088 and it's very likely (more in-depth investigation is needed), that krb client used by server ignores path to krb setup (env. var {{java.security.krb5.conf}}) and tried to connect to port 88. This seems to be a bug in WildFly 8.1.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months
[Red Hat JIRA] (ISPN-9054) Upgrade to Aesh 1.0
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-9054?page=com.atlassian.jira.plugin... ]
Tristan Tarrant closed ISPN-9054.
---------------------------------
Resolution: Out of Date
> Upgrade to Aesh 1.0
> -------------------
>
> Key: ISPN-9054
> URL: https://issues.redhat.com/browse/ISPN-9054
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: CLI
> Reporter: Ryan Emerson
> Priority: Major
>
> Aesh 1.0 has been released, and is currently used by Wildfly 12.x. 1.0 has several differences to Aesh 0.66.x, most notably the introduction of the aesh-readline project and the removal of AeshConsoleCallback. The upgrade is non-trivial, however due to some of the new features provided by Aesh 1.x, it could greatly reduce the amount of code required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 3 months