February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-8869) Infinispan Subsystem Code Cleanup

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8869?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8869: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5782 > Infinispan Subsystem Code Cleanup > --------------------------------- > > Key: ISPN-8869 > URL: https://issues.jboss.org/browse/ISPN-8869 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.0.CR3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > > The infinispan server subsystem has been neglected for a while resulting in old java code, use of various deprecated jboss apis as well as numerous redundant method/variable declarations. While some of the deprecated apis are harder to replace than others, we should replace the ones that are easy wins sooner rather than later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8863) Initial Infinispan subsystem cannot be created via CLI

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8863?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8863: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5782 > Initial Infinispan subsystem cannot be created via CLI > ------------------------------------------------------ > > Key: ISPN-8863 > URL: https://issues.jboss.org/browse/ISPN-8863 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.2.0.CR2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > Attachments: no-ispn.xml > > > If the infinispan server is created with a .xml file that does not contain a {code}<subsystem xmlns="urn:infinispan:server:core:9.2"><cache-container>...</cache-container></subsystem{code} entry, then it's not possible to initialise the subsystem via CLI DMR operations. > Executing {code}/subsystem=datagrid-infinispan:add(){code} results in the following server error: > {code} > 16:46:18,701 INFO [org.jboss.as.clustering.infinispan] (management-handler-thread - 2) Activating Infinispan subsystem. > 16:46:18,705 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "datagrid-infinispan")]): java.lang.IllegalStateException > at org.jboss.as.server.AbstractDeploymentChainStep.execute(AbstractDeploymentChainStep.java:74) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8863) Initial Infinispan subsystem cannot be created via CLI

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8863?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8863: ------------------------------- Fix Version/s: 9.2.0.Final > Initial Infinispan subsystem cannot be created via CLI > ------------------------------------------------------ > > Key: ISPN-8863 > URL: https://issues.jboss.org/browse/ISPN-8863 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.2.0.CR2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.0.Final > > Attachments: no-ispn.xml > > > If the infinispan server is created with a .xml file that does not contain a {code}<subsystem xmlns="urn:infinispan:server:core:9.2"><cache-container>...</cache-container></subsystem{code} entry, then it's not possible to initialise the subsystem via CLI DMR operations. > Executing {code}/subsystem=datagrid-infinispan:add(){code} results in the following server error: > {code} > 16:46:18,701 INFO [org.jboss.as.clustering.infinispan] (management-handler-thread - 2) Activating Infinispan subsystem. > 16:46:18,705 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "datagrid-infinispan")]): java.lang.IllegalStateException > at org.jboss.as.server.AbstractDeploymentChainStep.execute(AbstractDeploymentChainStep.java:74) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8870) Loggers should not inherit from the Core logger

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8870: ------------------------------------- Summary: Loggers should not inherit from the Core logger Key: ISPN-8870 URL: https://issues.jboss.org/browse/ISPN-8870 Project: Infinispan Issue Type: Bug Components: Core Reporter: Tristan Tarrant Assignee: Tristan Tarrant JBoss Logging generates a lot of methods. Using inheritance for the loggers just to reuse one or two methods from the parent logger generates a lot of waste in class metadata. We should drop inheritance and duplicate methods instead -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8869) Infinispan Subsystem Code Cleanup

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-8869: ---------------------------------- Summary: Infinispan Subsystem Code Cleanup Key: ISPN-8869 URL: https://issues.jboss.org/browse/ISPN-8869 Project: Infinispan Issue Type: Enhancement Components: Server Affects Versions: 9.2.0.CR3 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.2.0.Final The infinispan server subsystem has been neglected for a while resulting in old java code, use of various deprecated jboss apis as well as numerous redundant method/variable declarations. While some of the deprecated apis are harder to replace than others, we should replace the ones that are easy wins sooner rather than later. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8868) Expose force unlock with JMX

by Katia Aresti (JIRA)

Katia Aresti created ISPN-8868: ---------------------------------- Summary: Expose force unlock with JMX Key: ISPN-8868 URL: https://issues.jboss.org/browse/ISPN-8868 Project: Infinispan Issue Type: Enhancement Components: Clustered Locks Reporter: Katia Aresti Assignee: Katia Aresti Expose a way with JMX to force the release of a lock -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8798) ByteString places too strict a constraint on cache name length

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8798?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-8798: --------------------------------------- Infinispan now has a limitation on 255 bytes for cache names. I think it is up to 2LC code to implement this. [~galder.zamarreno], can you look into this ? > ByteString places too strict a constraint on cache name length > -------------------------------------------------------------- > > Key: ISPN-8798 > URL: https://issues.jboss.org/browse/ISPN-8798 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.5.Final, 9.2.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 9.2.0.CR3, 9.1.6.Final > > > The hibernate 2nd level cache code can easily generate cache names that exceed the byte length restriction enforced by ByteString. Cache names are generated using the fully qualified class name of the entity, which are user defined, and in the case of WildFly, also includes the deployment name, which can be particularly long for EARs. > At the very least, we should use an unsigned byte which doubles the allowed size. Why not also consider using https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... to marshal/unmarshal the size of the byte[] containing the name? At worst, this costs an extra byte, but solves the size problem for even sizes larger than 255. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8798) ByteString places too strict a constraint on cache name length

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/ISPN-8798?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on ISPN-8798: ------------------------------------ Hi [~NadirX], mostly I'd like to track the jira for the work, whatever the implementation solution will be, if there is a jira. This impacts application compatibility, so I'd really like a short term solution. Thanks! :) > ByteString places too strict a constraint on cache name length > -------------------------------------------------------------- > > Key: ISPN-8798 > URL: https://issues.jboss.org/browse/ISPN-8798 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.5.Final, 9.2.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 9.2.0.CR3, 9.1.6.Final > > > The hibernate 2nd level cache code can easily generate cache names that exceed the byte length restriction enforced by ByteString. Cache names are generated using the fully qualified class name of the entity, which are user defined, and in the case of WildFly, also includes the deployment name, which can be particularly long for EARs. > At the very least, we should use an unsigned byte which doubles the allowed size. Why not also consider using https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... to marshal/unmarshal the size of the byte[] containing the name? At worst, this costs an extra byte, but solves the size problem for even sizes larger than 255. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8867) REST server fails to convert between text formats and octet-stream

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8867: --------------------------------------- Summary: REST server fails to convert between text formats and octet-stream Key: ISPN-8867 URL: https://issues.jboss.org/browse/ISPN-8867 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Using the default cache with no MediaType configuration: The following request returns error 500: {noformat} curl -v -u user:pass -XPUT -H "Content-type: application/xml" -d "<root>element</root>" http://localhost:8080/rest/default/1 {noformat} The following request succeds: {noformat} curl -v -u user:pass -XPUT -H "Content-type: application/json" -d '{ "name": "test"}' http://localhost:8080/rest/default/2 {noformat} But when reading it back it returns "[B@26197e2f" instead of the inserted document. {noformat} curl -v -u user:pass -H "Content-type: text/plain" http://localhost:8080/rest/default/2 {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8867) REST server fails to convert between text formats and octet-stream

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8867?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8867: ------------------------------------ Affects Version/s: 9.2.0.CR3 > REST server fails to convert between text formats and octet-stream > ------------------------------------------------------------------ > > Key: ISPN-8867 > URL: https://issues.jboss.org/browse/ISPN-8867 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.2.0.CR3 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Using the default cache with no MediaType configuration: > The following request returns error 500: > {noformat} > curl -v -u user:pass -XPUT -H "Content-type: application/xml" -d "<root>element</root>" http://localhost:8080/rest/default/1 > {noformat} > The following request succeds: > {noformat} > curl -v -u user:pass -XPUT -H "Content-type: application/json" -d '{ "name": "test"}' http://localhost:8080/rest/default/2 > {noformat} > But when reading it back it returns "[B@26197e2f" instead of the inserted document. > {noformat} > curl -v -u user:pass -H "Content-type: text/plain" http://localhost:8080/rest/default/2 > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018