January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7405) DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7405?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7405: -------------------------------- Status: Open (was: New) > DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors > --------------------------------------------------------------------------------------- > > Key: ISPN-7405 > URL: https://issues.jboss.org/browse/ISPN-7405 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying, Server > Affects Versions: 9.0.0.Beta2 > Reporter: Adrian Nistor > Fix For: 9.0.0.CR1 > > Attachments: error.log > > > Start an infinispan server and run the following CLI command: > ./bin/ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=local:register-proto-schemas(file-names=[myFileWithSyntaxErrors.proto], file-contents=[kaboom])' > since the file has syntax errors it should still be placed in the ___protobuf_metadata cache and a myFileWithSyntaxErrors.proto.errors key should also be created. No exception should be thrown. Currently no key is written in cache and the NPE from the attached log happens. > When registering a proper file without syntax errors this works correctly. > The problem disappears if I disable global state persistence, so the cachestore seems to play a role in this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7405) DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7405?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7405: -------------------------------- Priority: Blocker (was: Major) > DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors > --------------------------------------------------------------------------------------- > > Key: ISPN-7405 > URL: https://issues.jboss.org/browse/ISPN-7405 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying, Server > Affects Versions: 9.0.0.Beta2 > Reporter: Adrian Nistor > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: error.log > > > Start an infinispan server and run the following CLI command: > ./bin/ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=local:register-proto-schemas(file-names=[myFileWithSyntaxErrors.proto], file-contents=[kaboom])' > since the file has syntax errors it should still be placed in the ___protobuf_metadata cache and a myFileWithSyntaxErrors.proto.errors key should also be created. No exception should be thrown. Currently no key is written in cache and the NPE from the attached log happens. > When registering a proper file without syntax errors this works correctly. > The problem disappears if I disable global state persistence, so the cachestore seems to play a role in this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7405) DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7405?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7405: -------------------------------- Attachment: error.log > DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors > --------------------------------------------------------------------------------------- > > Key: ISPN-7405 > URL: https://issues.jboss.org/browse/ISPN-7405 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying, Server > Affects Versions: 9.0.0.Beta2 > Reporter: Adrian Nistor > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: error.log > > > Start an infinispan server and run the following CLI command: > ./bin/ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=local:register-proto-schemas(file-names=[myFileWithSyntaxErrors.proto], file-contents=[kaboom])' > since the file has syntax errors it should still be placed in the ___protobuf_metadata cache and a myFileWithSyntaxErrors.proto.errors key should also be created. No exception should be thrown. Currently no key is written in cache and the NPE from the attached log happens. > When registering a proper file without syntax errors this works correctly. > The problem disappears if I disable global state persistence, so the cachestore seems to play a role in this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7405) DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-7405: ----------------------------------- Summary: DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors Key: ISPN-7405 URL: https://issues.jboss.org/browse/ISPN-7405 Project: Infinispan Issue Type: Bug Components: Remote Querying, Server Affects Versions: 9.0.0.Beta2 Reporter: Adrian Nistor Fix For: 9.0.0.CR1 Start an infinispan server and run the following CLI command: ./bin/ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=local:register-proto-schemas(file-names=[myFileWithSyntaxErrors.proto], file-contents=[kaboom])' since the file has syntax errors it should still be placed in the ___protobuf_metadata cache and a myFileWithSyntaxErrors.proto.errors key should also be created. No exception should be thrown. Currently no key is written in cache and the NPE from the attached log happens. When registering a proper file without syntax errors this works correctly. The problem disappears if I disable global state persistence, so the cachestore seems to play a role in this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-7228: ------------------------------------- Did you look in the server log? Does it fail with NPE? In that case it is a different new issue I just found today which is probably due to putAll being broken when your cache has a cachestore, which is exactly the case of the protobuf metadata cache. If you see the NPE try temporarily removing the <global-state/> element from the cache-container in your server's xml config to get rid of the cachestore and the error. And test the new DMR ops again. > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1266) Add more integration tests with Arquillian

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1266?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1266. --------------------------------- Resolution: Out of Date > Add more integration tests with Arquillian > ------------------------------------------ > > Key: ISPN-1266 > URL: https://issues.jboss.org/browse/ISPN-1266 > Project: Infinispan > Issue Type: Task > Components: CDI Integration > Reporter: Kevin Pollet > Assignee: Kevin Pollet > Priority: Minor > > This extension should be tested with: > * Open Web Beans > * JBoss AS7 > * GlassFish -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5824) Migration tool for configuration for both library mode and server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5824?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-5824. --------------------------------- Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Migration tool for configuration for both library mode and server > ----------------------------------------------------------------- > > Key: ISPN-5824 > URL: https://issues.jboss.org/browse/ISPN-5824 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Pedro Zapata > Assignee: Tristan Tarrant > Labels: jdg7 > Fix For: 9.0.0.Alpha2 > > > Regarding Configuration, the big changes: Library mode and Client-server mode have same configurations. Any infinispan.xml in Library will need to be changed substantially. We will need to write a migrator tool from old Library xml to Library xml. JDG Server will be able to read existing Server infinispan.xml and change it to latest version (upon any action on the Management model). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3186) Update HotRod server documentation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3186?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-3186. --------------------------------- Fix Version/s: 7.0.0.Final Assignee: Tristan Tarrant Resolution: Done > Update HotRod server documentation > ---------------------------------- > > Key: ISPN-3186 > URL: https://issues.jboss.org/browse/ISPN-3186 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Thomas Fromm > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.0.0.Final > > > following pages are obsolete or need linked hint for current ISPN versions: > https://docs.jboss.org/author/display/ISPN/Using+Hot+Rod+Server > https://docs.jboss.org/author/display/ISPN/Server+Command+Line+Options -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5823) Send Infinispan events to Hawkular

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5823?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5823: ---------------------------------- Priority: Minor (was: Major) > Send Infinispan events to Hawkular > ---------------------------------- > > Key: ISPN-5823 > URL: https://issues.jboss.org/browse/ISPN-5823 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Pedro Zapata > Priority: Minor > Labels: jdg7 > > Create integration to optionally log Infinispan events to Hawkular -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2082) JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2082?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2082: ------------------------------------- Assignee: Ryan Emerson > JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes > -------------------------------------------------------------------------- > > Key: ISPN-2082 > URL: https://issues.jboss.org/browse/ISPN-2082 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.1.5.FINAL > Environment: OS X 10.7.4, JDK 1.7.0u4 > Reporter: Ryan Scharer > Assignee: Ryan Emerson > > I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything works fine. If the value is greater, the cache store fails with ORA-24816. This occurs because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore implementation and write my own insert/update SQL in storeLockSafe(). This works fine, but obviously isn't ideal from an upgrade point of view. Simply overriding storeLockSafe() isn't an option due to all the private fields. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017