November 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5978) Unused scripts in EAP bin directory

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-5978?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink edited comment on ISPN-5978 at 11/24/15 10:50 AM: ------------------------------------------------------------------- You might remove run.sh and run.bat as well. This scripts are only needed because of compatibility for older EAP. until EAP6 the server was started by run.* so the script just note the user to use standalone or domain. For Infinispan-Server this is not needed was (Author: wdfink): You might remove run.sh and run.bat as well. This scripts are only needed because of compatibility for older EAP. until EAP6 the server was started by run.* so the script just note the user to use standalone or domain. For JDG this is not needed > Unused scripts in EAP bin directory > ----------------------------------- > > Key: ISPN-5978 > URL: https://issues.jboss.org/browse/ISPN-5978 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Beta1 > Reporter: Vaclav Dedik > Assignee: Vaclav Dedik > Fix For: 8.1.0.Final > > > There are these unecessary scripts in the EAP bin directory: > appclient.sh > jboss-cli.sh > wsconsume.sh > wsprovide.sh > appclient.sh, wsconsume.sh and wsprovide.sh are already removed from upstream. jboss-cli.sh is still present. > See bugzilla: > https://bugzilla.redhat.com/show_bug.cgi?id=1198413 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5980) Upgrade Scala to 2.11.7

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5980?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5980: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.1.0.Beta2 Resolution: Done > Upgrade Scala to 2.11.7 > ----------------------- > > Key: ISPN-5980 > URL: https://issues.jboss.org/browse/ISPN-5980 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process > Affects Versions: 8.1.0.Beta1 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Fix For: 8.1.0.Beta2, 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5897) Enhance filter_failed_tests.sh to support compressed logs

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5897?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5897: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Enhance filter_failed_tests.sh to support compressed logs > --------------------------------------------------------- > > Key: ISPN-5897 > URL: https://issues.jboss.org/browse/ISPN-5897 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 8.1.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Final, 8.1.0.Beta1 > > > Currently the trace build uses a lot of disk space. Using `CompressedFileAppender` should reduce the size of the logs considerably, but we still want to save only the logs of the failed tests in the build artifacts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5897) Enhance filter_failed_tests.sh to support compressed logs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5897?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5897: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/3791, https://github.com/infinispan/infinispan/pull/3846 (was: https://github.com/infinispan/infinispan/pull/3791) > Enhance filter_failed_tests.sh to support compressed logs > --------------------------------------------------------- > > Key: ISPN-5897 > URL: https://issues.jboss.org/browse/ISPN-5897 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 8.1.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Currently the trace build uses a lot of disk space. Using `CompressedFileAppender` should reduce the size of the logs considerably, but we still want to save only the logs of the failed tests in the build artifacts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5897) Enhance filter_failed_tests.sh to support compressed logs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5897?page=com.atlassian.jira.plugin.... ] Dan Berindei reopened ISPN-5897: -------------------------------- > Enhance filter_failed_tests.sh to support compressed logs > --------------------------------------------------------- > > Key: ISPN-5897 > URL: https://issues.jboss.org/browse/ISPN-5897 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 8.1.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Currently the trace build uses a lot of disk space. Using `CompressedFileAppender` should reduce the size of the logs considerably, but we still want to save only the logs of the failed tests in the build artifacts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5982) Custom audit logger is ignored in server mode

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-5982?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-5982: --------------------------------------- After digging into it little bit, there's no audit logger setup at all, even default one it not used. > Custom audit logger is ignored in server mode > --------------------------------------------- > > Key: ISPN-5982 > URL: https://issues.jboss.org/browse/ISPN-5982 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Vojtech Juranek > > When custom audit logger is configured for cache container in server mode (e.g. sniplet bellow), it's ignored and default logger is still used > {noformat} > <authorization audit-logger="org.infinispan.server.test.security.log.TestAuditLogger"> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5985) Add tests for listeners matching the requirements of ClientEvents.addClientQueryListener

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5985: ----------------------------------- Summary: Add tests for listeners matching the requirements of ClientEvents.addClientQueryListener Key: ISPN-5985 URL: https://issues.jboss.org/browse/ISPN-5985 Project: Infinispan Issue Type: Task Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.1.0.Beta2, 8.0.2.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5983) Cannot connect via JMX to servers managed in domain mode

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-5983?page=com.atlassian.jira.plugin.... ] Jiří Holuša commented on ISPN-5983: ----------------------------------- Yes, I thought so. Therefore I will update the PR according to Ladislav's comments and it could be done, thanks. > Cannot connect via JMX to servers managed in domain mode > -------------------------------------------------------- > > Key: ISPN-5983 > URL: https://issues.jboss.org/browse/ISPN-5983 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Servers, Server > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Jiří Holuša > > I was trying to connect remotely to Infinispan servers run in domain mode. I was following instructions that worked for me with Wildfly 10 (e.g. at https://goldmann.pl/blog/2013/04/16/jmx-connections-to-jboss-as/ ), but that didn't work with Infinispan servers. There is no documentation about how to do this and since it's not working the WildFly way, I mark this issue as bug. > After investigation, we (many thanks to [~lthon]) found out that it doesn't work with ISPN server, because WildFly uses http upgrade for this purpose via http-connector. The connector (by default commented in the domain.xml) requires undertow subsystem to work, however, ISPN server doesn't have it. > There are two possible solutions: > * add the undertow subsystem. The modules/ directory already has the jars, therefore it's only needed to add following to domain.xml and than you can connect to the server via JMX URL service:jmx:remote+http://localhost:8080. However, I wouldn't prefer this solution. > {code} > <subsystem xmlns="urn:jboss:domain:undertow:3.0"> > <buffer-cache name="default"/> > <server name="default-server"> > <http-listener name="default" socket-binding="http"/> > <host name="default-host" alias="localhost"/> > </server> > <servlet-container name="default"/> > </subsystem> > {code} > * second solution is to create remoting endpoint just the way it was before in JBoss AS 7, therefore add following to the domain.xml and then connect via JMX URL: service:jmx:remote://localhost:4447. This solution should be preferred IMHO. > {code} > <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/> > {code} > {code} > <socket-binding name="remoting" port="4447"/> > {code} > I will soon issue a PR with the solution number 2 and appropriate update of documentation. Of course, these options should be disabled by default, by I think it would be nice to have them commented in the domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5983) Cannot connect via JMX to servers managed in domain mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5983?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-5983: --------------------------------------- We don't want the undertow subsystem, as our protocol handlers use Netty and we don't support deployment of servlets and such. > Cannot connect via JMX to servers managed in domain mode > -------------------------------------------------------- > > Key: ISPN-5983 > URL: https://issues.jboss.org/browse/ISPN-5983 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Servers, Server > Affects Versions: 8.1.0.Beta1 > Reporter: Jiří Holuša > Assignee: Jiří Holuša > > I was trying to connect remotely to Infinispan servers run in domain mode. I was following instructions that worked for me with Wildfly 10 (e.g. at https://goldmann.pl/blog/2013/04/16/jmx-connections-to-jboss-as/ ), but that didn't work with Infinispan servers. There is no documentation about how to do this and since it's not working the WildFly way, I mark this issue as bug. > After investigation, we (many thanks to [~lthon]) found out that it doesn't work with ISPN server, because WildFly uses http upgrade for this purpose via http-connector. The connector (by default commented in the domain.xml) requires undertow subsystem to work, however, ISPN server doesn't have it. > There are two possible solutions: > * add the undertow subsystem. The modules/ directory already has the jars, therefore it's only needed to add following to domain.xml and than you can connect to the server via JMX URL service:jmx:remote+http://localhost:8080. However, I wouldn't prefer this solution. > {code} > <subsystem xmlns="urn:jboss:domain:undertow:3.0"> > <buffer-cache name="default"/> > <server name="default-server"> > <http-listener name="default" socket-binding="http"/> > <host name="default-host" alias="localhost"/> > </server> > <servlet-container name="default"/> > </subsystem> > {code} > * second solution is to create remoting endpoint just the way it was before in JBoss AS 7, therefore add following to the domain.xml and then connect via JMX URL: service:jmx:remote://localhost:4447. This solution should be preferred IMHO. > {code} > <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/> > {code} > {code} > <socket-binding name="remoting" port="4447"/> > {code} > I will soon issue a PR with the solution number 2 and appropriate update of documentation. Of course, these options should be disabled by default, by I think it would be nice to have them commented in the domain.xml. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5984) Use Message.setFlag(short) to avoid creating a temporary array

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5984?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5984: ------------------------------- Status: Open (was: New) > Use Message.setFlag(short) to avoid creating a temporary array > -------------------------------------------------------------- > > Key: ISPN-5984 > URL: https://issues.jboss.org/browse/ISPN-5984 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: performance > Fix For: 8.1.0.Beta2 > > > {{Message.setFlag(Message.Flag...)}} creates a temporary array on each invocation, and {{Message.setFlag(short)}} avoids it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2015