[JBoss JIRA] (ISPN-10461) Server creates sslcontext even without an identity
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10461?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10461:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Server creates sslcontext even without an identity
> --------------------------------------------------
>
> Key: ISPN-10461
> URL: https://issues.jboss.org/browse/ISPN-10461
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.Beta5
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> If the server has a security realm without a server identity, the server instantiates a SSLContext and configures the endpoints to use it. This makes unencrypted access impossible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10462) Drop the infinispan-cloud module and merge config files to core
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10462?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10462:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Drop the infinispan-cloud module and merge config files to core
> ---------------------------------------------------------------
>
> Key: ISPN-10462
> URL: https://issues.jboss.org/browse/ISPN-10462
> Project: Infinispan
> Issue Type: Task
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> The infinispan-cloud module contains three configuration files which can be merged to core.
> Such configurations have optional dependencies on specific jgroups modules. These should be called out in the configuration comments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10463) Server uses disabled features
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10463?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10463:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Server uses disabled features
> -----------------------------
>
> Key: ISPN-10463
> URL: https://issues.jboss.org/browse/ISPN-10463
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 10.0.0.Beta4, 9.4.15.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.CR1, 9.4.17.Final
>
>
> Some Infinispan features are disabled in the product, e.g. data segmentation.
> This is done with a file META-INF/infinispan-features.properties added by the productization script in infinispan-commons:
> org.infinispan.feature.data-segmentation=false
> The properties file is read and the feature is disabled in library mode, but somehow the server doesn't find the properties file and the feature is enabled.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10465) Duplicate Jgroups stack causes erroneous warning
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10465?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10465:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Duplicate Jgroups stack causes erroneous warning
> ------------------------------------------------
>
> Key: ISPN-10465
> URL: https://issues.jboss.org/browse/ISPN-10465
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 10.0.0.Beta5
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> If a {{<stack-file ../>}} is specified with the same name as an existing stack, then the resulting error message indicates that the stack file cannot be found instead of relaying that a duplicate stack exists.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10483) Running tests from IDE throws @AutoProtoschemaBuilder fatal exception
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10483?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10483:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Running tests from IDE throws @AutoProtoschemaBuilder fatal exception
> ---------------------------------------------------------------------
>
> Key: ISPN-10483
> URL: https://issues.jboss.org/browse/ISPN-10483
> Project: Infinispan
> Issue Type: Bug
> Reporter: Gustavo Fernandes
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> Happens 95% of the time when trying to run a test from the REST module on Intellij, for example {{org.infinispan.rest.Http2Test}}:
> {noformat}
> Error:java: @AutoProtoSchemaBuilder processor threw a fatal exception: java.lang.RuntimeException: Type not found : long
> at org.infinispan.protostream.annotations.impl.processor.types.MirrorClassFactory$MirrorClass.isAssignableTo(MirrorClassFactory.java:541)
> at org.infinispan.protostream.annotations.impl.ProtoMessageTypeMetadata.scanMemberAnnotations(ProtoMessageTypeMetadata.java:212)
> at org.infinispan.protostream.annotations.impl.BaseProtoSchemaGenerator.generateAndRegister(BaseProtoSchemaGenerator.java:116)
> at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processClass(AutoProtoSchemaBuilderAnnotationProcessor.java:287)
> at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processElement(AutoProtoSchemaBuilderAnnotationProcessor.java:218)
> at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processDependencies(AutoProtoSchemaBuilderAnnotationProcessor.java:344)
> at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processClass(AutoProtoSchemaBuilderAnnotationProcessor.java:279)
> at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processElement(AutoProtoSchemaBuilderAnnotationProcessor.java:218)
> at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.process(AutoProtoSchemaBuilderAnnotationProcessor.java:171)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
> at com.sun.tools.javac.main.Main.compile(Main.java:523)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
> at org.jetbrains.jps.javac.JavacMain.compile(JavacMain.java:195)
> at org.jetbrains.jps.incremental.java.JavaBuilder.compileJava(JavaBuilder.java:460)
> at org.jetbrains.jps.incremental.java.JavaBuilder.compile(JavaBuilder.java:330)
> at org.jetbrains.jps.incremental.java.JavaBuilder.doBuild(JavaBuilder.java:255)
> at org.jetbrains.jps.incremental.java.JavaBuilder.build(JavaBuilder.java:213)
> at org.jetbrains.jps.incremental.IncProjectBuilder.runModuleLevelBuilders(IncProjectBuilder.java:1324)
> at org.jetbrains.jps.incremental.IncProjectBuilder.runBuildersForChunk(IncProjectBuilder.java:1004)
> at org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:1071)
> at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:965)
> at org.jetbrains.jps.incremental.IncProjectBuilder.buildChunks(IncProjectBuilder.java:794)
> at org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:376)
> at org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:178)
> at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:139)
> at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:288)
> at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:121)
> at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:228)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10487) HTTP/2 POST: Request Entity Too Large
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10487?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10487:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> HTTP/2 POST: Request Entity Too Large
> -------------------------------------
>
> Key: ISPN-10487
> URL: https://issues.jboss.org/browse/ISPN-10487
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: http2
> Fix For: 10.0.0.CR2
>
>
> Start server-ng and create a cache named 'default':
> {noformat}
> curl -v -XPOST -d '{"distributed-cache":{"mode": "SYNC"}}' -H "Content-type: application/json" http://localhost:11222/rest/v2/caches/default
> {noformat}
> Try to put an entry using HTTP/2
> {noformat}
> curl -v -XPOST -d '1' -H "Content-type: application/json" http://localhost:11222/rest/v2/caches/default/1 --http2
> {noformat}
> Error 413 is received:
> {noformat}
> * Trying ::1:11222...
> * TCP_NODELAY set
> * connect to ::1 port 11222 failed: Connection refused
> * Trying 127.0.0.1:11222...
> * TCP_NODELAY set
> * Connected to localhost (127.0.0.1) port 11222 (#0)
> > POST /rest/v2/caches/default/1 HTTP/1.1
> > Host: localhost:11222
> > User-Agent: curl/7.65.3
> > Accept: */*
> > Connection: Upgrade, HTTP2-Settings
> > Upgrade: h2c
> > HTTP2-Settings: AAMAAABkAARAAAAAAAIAAAAA
> > Content-type: application/json
> > Content-Length: 1
> >
> * upload completely sent off: 1 out of 1 bytes
> * Mark bundle as not supporting multiuse
> < HTTP/1.1 413 Request Entity Too Large
> < content-length: 0
> <
> * Connection #0 to host localhost left intact
> {noformat}
> The same command line without http/2 succeeds
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10413) os-maven-plugin not setting `os.detected.classifier` property on partial maven builds
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10413?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10413:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> os-maven-plugin not setting `os.detected.classifier` property on partial maven builds
> -------------------------------------------------------------------------------------
>
> Key: ISPN-10413
> URL: https://issues.jboss.org/browse/ISPN-10413
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> When executing {{mvn clean install -am -pl core}} the commons module will fail because the property {{os.detected.classifier}} is not set by the {{os-maven-plugin}} resulting in a NPE being thrown by the {{proto-schema-compatibility}} maven plugin.
> {code:java}
> [ERROR] Failed to execute goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check (default) on project infinispan-commons: Execution default of goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check failed.: NullPointerException -> [Help 1]
> {code}
> The solution is to add the following to the parent pom:
> {code:java}
> <extensions>
> <extension>
> <groupId>kr.motd.maven</groupId>
> <artifactId>os-maven-plugin</artifactId>
> </extension>
> </extensions>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (ISPN-10414) Remove AtomicObjectFactory
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10414?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10414:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34)
> Remove AtomicObjectFactory
> --------------------------
>
> Key: ISPN-10414
> URL: https://issues.jboss.org/browse/ISPN-10414
> Project: Infinispan
> Issue Type: Task
> Components: API
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> The AtomicObjectFactory has not been actively developed since it's inception in ISPN-3695 and is not documented in the user guide. We should remove this module.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months