[JBoss JIRA] (ISPN-7856) Do not re-distribute the org.hibernate.search.orm module
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7856?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-7856:
---------------------------------------
[~Seto] sorry for the delay, I missed your comment. Yes, I agree, and many of the internal components have been converted into "feature packs" which means they will now use the {{resource-root} syntax. But while e.g. Hibernate Search already publishes these, Infinispan will only publish them in such format in version 9.3.
> Do not re-distribute the org.hibernate.search.orm module
> --------------------------------------------------------
>
> Key: ISPN-7856
> URL: https://issues.jboss.org/browse/ISPN-7856
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 9.2.0.Final, 9.2.0.CR2
>
>
> Infinispan's build process is currently re-publishing the Hibernate Search modules as it needs to make some changes in their structure.
> However it only needs the {{hibernate-search-engine}} component and some other extensions, it should not re-publish the {{org.hibernate.search.orm}} WildFly module as this is unnecessary and can confuse people about the intended purpose of these modules.
> Side note: do we still need to re-distributed these modules at all? We did some improvements in the build, I wonder if we could avoid this dodgy process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7856) Do not re-distribute the org.hibernate.search.orm module
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7856?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero closed ISPN-7856.
---------------------------------
> Do not re-distribute the org.hibernate.search.orm module
> --------------------------------------------------------
>
> Key: ISPN-7856
> URL: https://issues.jboss.org/browse/ISPN-7856
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 9.2.0.Final, 9.2.0.CR2
>
>
> Infinispan's build process is currently re-publishing the Hibernate Search modules as it needs to make some changes in their structure.
> However it only needs the {{hibernate-search-engine}} component and some other extensions, it should not re-publish the {{org.hibernate.search.orm}} WildFly module as this is unnecessary and can confuse people about the intended purpose of these modules.
> Side note: do we still need to re-distributed these modules at all? We did some improvements in the build, I wonder if we could avoid this dodgy process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7856) Do not re-distribute the org.hibernate.search.orm module
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7856?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero updated ISPN-7856:
----------------------------------
Status: Open (was: New)
> Do not re-distribute the org.hibernate.search.orm module
> --------------------------------------------------------
>
> Key: ISPN-7856
> URL: https://issues.jboss.org/browse/ISPN-7856
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 9.2.0.Final, 9.2.0.CR2
>
>
> Infinispan's build process is currently re-publishing the Hibernate Search modules as it needs to make some changes in their structure.
> However it only needs the {{hibernate-search-engine}} component and some other extensions, it should not re-publish the {{org.hibernate.search.orm}} WildFly module as this is unnecessary and can confuse people about the intended purpose of these modules.
> Side note: do we still need to re-distributed these modules at all? We did some improvements in the build, I wonder if we could avoid this dodgy process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7856) Do not re-distribute the org.hibernate.search.orm module
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7856?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero resolved ISPN-7856.
-----------------------------------
Fix Version/s: 9.2.0.CR2
Resolution: Done
> Do not re-distribute the org.hibernate.search.orm module
> --------------------------------------------------------
>
> Key: ISPN-7856
> URL: https://issues.jboss.org/browse/ISPN-7856
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 9.2.0.Final, 9.2.0.CR2
>
>
> Infinispan's build process is currently re-publishing the Hibernate Search modules as it needs to make some changes in their structure.
> However it only needs the {{hibernate-search-engine}} component and some other extensions, it should not re-publish the {{org.hibernate.search.orm}} WildFly module as this is unnecessary and can confuse people about the intended purpose of these modules.
> Side note: do we still need to re-distributed these modules at all? We did some improvements in the build, I wonder if we could avoid this dodgy process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7856) Do not re-distribute the org.hibernate.search.orm module
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-7856?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero reassigned ISPN-7856:
-------------------------------------
Assignee: Sanne Grinovero (was: Gustavo Fernandes)
> Do not re-distribute the org.hibernate.search.orm module
> --------------------------------------------------------
>
> Key: ISPN-7856
> URL: https://issues.jboss.org/browse/ISPN-7856
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 9.2.0.Final
>
>
> Infinispan's build process is currently re-publishing the Hibernate Search modules as it needs to make some changes in their structure.
> However it only needs the {{hibernate-search-engine}} component and some other extensions, it should not re-publish the {{org.hibernate.search.orm}} WildFly module as this is unnecessary and can confuse people about the intended purpose of these modules.
> Side note: do we still need to re-distributed these modules at all? We did some improvements in the build, I wonder if we could avoid this dodgy process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-7100) IllegalLifecycleStateException: Trying to register a component after stopping
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/ISPN-7100?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed ISPN-7100.
--------------------------------
Assignee: Sebastian Łaskawiec
Resolution: Duplicate Issue
Thanks. Closing as duplicate of ISPN-7488. No need to backport for now.
> IllegalLifecycleStateException: Trying to register a component after stopping
> -----------------------------------------------------------------------------
>
> Key: ISPN-7100
> URL: https://issues.jboss.org/browse/ISPN-7100
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 8.2.4.Final
> Reporter: Radoslav Husar
> Assignee: Sebastian Łaskawiec
> Priority: Minor
> Labels: infinispan_clean_shutdown
>
> Occured on server. Scenarios affected:
> eap-7x-failover-ejb-ejbremote-shutdown-dist-async
> eap-7x-failover-ejb-ejbremote-shutdown-dist-sync
> eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-3owners
> eap-7x-failover-ejb-ejbremote-shutdown-dist-sync-tcpStack
> eap-7x-failover-ejb-ejbremote-shutdown-repl-sync
> eap-7x-failover-ejb-ejbservlet-shutdown-dist-async
> eap-7x-failover-ejb-ejbservlet-shutdown-repl-async
> eap-7x-failover-ejb-ejbservlet-shutdown-repl-sync
> eap-7x-failover-http-session-shutdown-dist-async
> eap-7x-failover-http-session-shutdown-dist-sync
> eap-7x-failover-http-session-shutdown-repl-async-haproxy
> Occurs after "ISPN000082: Stopping the RpcDispatcher for channel ejb" or "WFLYSRV0028: Stopped deployment clusterbench-ee7.ear":
> {code}
> 21:58:55,724 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 91) WFLYCLINF0003: Stopped client-mappings cache from ejb container
> [JBossINF] 21:58:55,726 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-passivating.war) in 259ms
> [JBossINF] 21:58:55,726 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t43) [Context=client-mappings][Scope=dev213]ISPN100003: Finished local rebalance
> [JBossINF] 21:58:55,727 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb
> [JBossINF] 21:58:55,727 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb
> [JBossINF] 21:58:55,734 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-granular.war) in 267ms
> [JBossINF] 21:58:55,735 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: clusterbench-ee7-web-default.war) in 268ms
> [JBossINF] 21:58:55,735 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 269ms
> [JBossINF] 21:58:55,736 WARN [org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler] (remote-thread--p5-t9) ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=client-mappings, type=REBALANCE_CONFIRM, sender=dev215, joinInfo=null, topologyId=29, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=11}: org.infinispan.commons.CacheConfigurationException: Unable to configure component (type: class org.infinispan.topology.CacheTopologyControlCommand, instance CacheTopologyControlCommand{cache=client-mappings, type=REBALANCE_CONFIRM, sender=dev215, joinInfo=null, topologyId=29, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=11})
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:151)
> [JBossINF] at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler$2.run(GlobalInboundInvocationHandler.java:157)
> [JBossINF] at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:199)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at org.jboss.as.clustering.infinispan.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:48)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> [JBossINF] Caused by: org.infinispan.IllegalLifecycleStateException: Trying to register a component after stopping: org.infinispan.topology.LocalTopologyManagerFactory
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:184)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:171)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:167)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.createComponentFactoryInternal(AbstractComponentRegistry.java:348)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.getFactory(AbstractComponentRegistry.java:327)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:293)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:246)
> [JBossINF] at org.infinispan.factories.AbstractComponentRegistry.wireDependencies(AbstractComponentRegistry.java:147)
> [JBossINF] ... 6 more
> {code}
> Server logs:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (ISPN-8535) Rest API redesign
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-8535:
-------------------------------------------
That could work. We could also use a query param called version (see https://apigee.com/about/blog/technology/restful-api-design-tips-versioning).
> Rest API redesign
> -----------------
>
> Key: ISPN-8535
> URL: https://issues.jboss.org/browse/ISPN-8535
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 9.2.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 10.0.0.Final
>
>
> Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references.
> Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples:
> * Create a cache: POST /rest/caches
> * Delete a cache: DELETE /rest/caches/myCache
> * Create a template: POST /rest/templates
> * Delete a template: DELETE /rest/templates/myTemplate
> * Create an entry: POST /rest/caches/myCache/1
> * Create a counter: POST /rest/counters
> * Get a counter value: GET /rest/counters/mycounter
> * Increment a counter: GET /rest/counters/mycounter?action=increment
> * Search a cache: GET /rest/caches/myCache?action=search
> * Create a script: POST /rest/scripts/
> * Get a script source: GET /rest/scritps/myScript
> * Execute a script: GET /rest/scripts/myScript?action=execute¶m1=foo
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months