[JBoss JIRA] (ISPN-6643) CLI - some help commands are not working correctly
by Roman Macor (JIRA)
Roman Macor created ISPN-6643:
---------------------------------
Summary: CLI - some help commands are not working correctly
Key: ISPN-6643
URL: https://issues.jboss.org/browse/ISPN-6643
Project: Infinispan
Issue Type: Bug
Components: CLI
Affects Versions: 9.0.0.Alpha1
Reporter: Roman Macor
Here is a list of help commands that are not working as expected:
- disconnect --help -> doesn't display help, quits CLI
- commit --help
Unexpected command 'commit --help'. Type 'help --commands' for the list of supported commands.
- connect --help -> mentions jboss-cli.sh, should be ispn-cli.sh
- container --help
Unrecognized arguments: [--help]
- version --help -> doesn't display help, instead shows version
- locate --help
Unexpected command 'locate --help'. Type 'help --commands' for the list of supported commands.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6642) java.lang.ClassNotFoundException: javax.transaction.TransactionManager while running config-converter.sh sciprt
by Anna Manukyan (JIRA)
Anna Manukyan created ISPN-6642:
-----------------------------------
Summary: java.lang.ClassNotFoundException: javax.transaction.TransactionManager while running config-converter.sh sciprt
Key: ISPN-6642
URL: https://issues.jboss.org/browse/ISPN-6642
Project: Infinispan
Issue Type: Bug
Reporter: Anna Manukyan
After building the distribution/ module of infinispan and running the {{./config-converter.sh}} command from infinispan-8.3.0.ER5-redhat-1-all/bin/ directory, the following exception is thrown:
{code}
Exception in thread "main" java.lang.NoClassDefFoundError: javax/transaction/TransactionManager
at org.infinispan.configuration.cache.TransactionConfiguration.<clinit>(TransactionConfiguration.java:30)
at org.infinispan.configuration.cache.TransactionConfigurationBuilder.<init>(TransactionConfigurationBuilder.java:37)
at org.infinispan.configuration.cache.ConfigurationBuilder.<init>(ConfigurationBuilder.java:60)
at org.infinispan.configuration.parsing.ConfigurationBuilderHolder.<init>(ConfigurationBuilderHolder.java:26)
at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:114)
at org.infinispan.tools.config.ConfigurationConverter.convert(ConfigurationConverter.java:27)
at org.infinispan.tools.config.ConfigurationConverter.main(ConfigurationConverter.java:56)
Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 7 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6612) Rename internal Hibernate Search directory provider slot
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6612?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6612:
------------------------------------
Description:
We distribute two modules for the hibernate search directory provider: one self contained (with Infinispan deps) to be used together with the Hibernate Search bundled in Wildfly and another for usage with Infinispan query.
Currently both share the same name convention {{for-hibernate-search-x.y}}, that could lead to clashes.
was:
We distribute two modules for the hibernate search directory provider: one self contained to be used together with Wildfly and another for usage with Infinispan query.
Currently both share the same name convention {{for-hibernate-search-x.y}}, that could lead to clashes.
> Rename internal Hibernate Search directory provider slot
> --------------------------------------------------------
>
> Key: ISPN-6612
> URL: https://issues.jboss.org/browse/ISPN-6612
> Project: Infinispan
> Issue Type: Feature Request
> Components: WildFly modules
> Affects Versions: 8.2.1.Final, 9.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> We distribute two modules for the hibernate search directory provider: one self contained (with Infinispan deps) to be used together with the Hibernate Search bundled in Wildfly and another for usage with Infinispan query.
> Currently both share the same name convention {{for-hibernate-search-x.y}}, that could lead to clashes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6612) Rename internal Hibernate Search directory provider slot
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6612?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6612:
------------------------------------
Description:
We distribute two modules for the hibernate search directory provider: one self contained to be used together with Wildfly and another for usage with Infinispan query.
Currently both share the same name convention {{for-hibernate-search-x.y}}, that could lead to clashes.
was:
The currently distributed modules zip contains Hibernate Search engine, that in turn has an optional dependency to {{for-hibernate-search-5.6}} in order to link with the Infinispan Directory Provider, also provided.
Since this slot is also used by Wildfly's internal hibernate search engine that expects a self contained module to provide Infinispan storage for Lucene only, the internal hibernate search engine module should be renamed in order to avoid conflicts.
> Rename internal Hibernate Search directory provider slot
> --------------------------------------------------------
>
> Key: ISPN-6612
> URL: https://issues.jboss.org/browse/ISPN-6612
> Project: Infinispan
> Issue Type: Feature Request
> Components: WildFly modules
> Affects Versions: 8.2.1.Final, 9.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> We distribute two modules for the hibernate search directory provider: one self contained to be used together with Wildfly and another for usage with Infinispan query.
> Currently both share the same name convention {{for-hibernate-search-x.y}}, that could lead to clashes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6612) Rename internal Hibernate Search directory provider slot
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6612?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6612:
------------------------------------
Summary: Rename internal Hibernate Search directory provider slot (was: Rename internal Hibernate Search slot)
> Rename internal Hibernate Search directory provider slot
> --------------------------------------------------------
>
> Key: ISPN-6612
> URL: https://issues.jboss.org/browse/ISPN-6612
> Project: Infinispan
> Issue Type: Feature Request
> Components: WildFly modules
> Affects Versions: 8.2.1.Final, 9.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
>
> The currently distributed modules zip contains Hibernate Search engine, that in turn has an optional dependency to {{for-hibernate-search-5.6}} in order to link with the Infinispan Directory Provider, also provided.
> Since this slot is also used by Wildfly's internal hibernate search engine that expects a self contained module to provide Infinispan storage for Lucene only, the internal hibernate search engine module should be renamed in order to avoid conflicts.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ISPN-6580) Hotrod performance regressions after ISPN-5342 ISPN-6545
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6580?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6580:
----------------------------------
Fix Version/s: 8.2.2.Final
> Hotrod performance regressions after ISPN-5342 ISPN-6545
> --------------------------------------------------------
>
> Key: ISPN-6580
> URL: https://issues.jboss.org/browse/ISPN-6580
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols, Server
> Reporter: Jakub Markos
> Assignee: William Burns
> Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final
>
> Attachments: jfr_recordings.zip, pom.xml, Reproducer.java
>
>
> There were 2 recent regressions in hotrod performance, one between commits dd5501c5e and 628819461 and the second one between 628819461 and db0890270. I didn't look for the exact commits, so the name of the issue might not be 100% exact...
> It is easily reproducable locally with a single server instance, reproducer attached.
> The numbers on my machine:
> ||Build commit||Puts time||Gets time||
> |dd5501c5e|21|74|
> |628819461|26|102|
> |db0890270|48|224|
> The JFR recordings (attached, captured is only the part of the test with gets) for db0890270 show a lot of time is spent in HotRodDecoder#resetNow(), and also the allocation rate goes from 100MB/s for dd5501c5e to over 1GB/s for db0890270. There are no glaring differences between dd5501c5e and 628819461.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months