June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4422) Packages with custom classes are not exported properly for HotRod tests in OSGi

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4422?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4422: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2660 > Packages with custom classes are not exported properly for HotRod tests in OSGi > ------------------------------------------------------------------------------- > > Key: ISPN-4422 > URL: https://issues.jboss.org/browse/ISPN-4422 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Martin Gencur > Assignee: Martin Gencur > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4420) Allow configuring keepalive for hotrod connections

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4420?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4420: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2659 > Allow configuring keepalive for hotrod connections > -------------------------------------------------- > > Key: ISPN-4420 > URL: https://issues.jboss.org/browse/ISPN-4420 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > Also consider making the Tcp connections pluggable. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4420) Allow configuring keepalive for hotrod connections

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4420?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4420: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1111221 > Allow configuring keepalive for hotrod connections > -------------------------------------------------- > > Key: ISPN-4420 > URL: https://issues.jboss.org/browse/ISPN-4420 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > Also consider making the Tcp connections pluggable. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4420) Allow configuring keepalive for hotrod connections

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4420?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-4420: -------------------------------- Fix Version/s: 7.0.0.Alpha5 7.0.0.Final > Allow configuring keepalive for hotrod connections > -------------------------------------------------- > > Key: ISPN-4420 > URL: https://issues.jboss.org/browse/ISPN-4420 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > Also consider making the Tcp connections pluggable. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4422) Packages with custom classes are not exported properly for HotRod tests in OSGi

by Martin Gencur (JIRA)

Martin Gencur created ISPN-4422: ----------------------------------- Summary: Packages with custom classes are not exported properly for HotRod tests in OSGi Key: ISPN-4422 URL: https://issues.jboss.org/browse/ISPN-4422 Project: Infinispan Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite - Server Affects Versions: 7.0.0.Alpha4 Reporter: Martin Gencur Assignee: Mircea Markus -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4422) Packages with custom classes are not exported properly for HotRod tests in OSGi

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4422?page=com.atlassian.jira.plugin.... ] Martin Gencur reassigned ISPN-4422: ----------------------------------- Assignee: Martin Gencur (was: Mircea Markus) > Packages with custom classes are not exported properly for HotRod tests in OSGi > ------------------------------------------------------------------------------- > > Key: ISPN-4422 > URL: https://issues.jboss.org/browse/ISPN-4422 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Martin Gencur > Assignee: Martin Gencur > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-800) Infinispan inside OSGI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on ISPN-800: ---------------------------------------------- Ion Savin <isavin(a)redhat.com> changed the Status of [bug 1111201|https://bugzilla.redhat.com/show_bug.cgi?id=1111201] from ASSIGNED to POST > Infinispan inside OSGI > ---------------------- > > Key: ISPN-800 > URL: https://issues.jboss.org/browse/ISPN-800 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Luca Stancapiano > Assignee: Ion Savin > > We need to import infinispan inside a OSGI repository. Tests are made with Felix. > I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan > I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. > Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) > Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: > jboss transaction api 1.0.1.GA > We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) > jgroups 2.10.1.GA > (it's a osgi bundle since the 3.x version) > river 1.2.3.GA > (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) > marshalling-api 1.2.3.GA > (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) > jboss logging spi 2.0.5.GA > (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version. Fixed in the 3.x version) > rhq plugin annotations 1.4.0.B01 > (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) > i18nlog 1.0.9 > (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) > log4j 1.2.16 > (that's ok...it is a osgi bundle ;)) > jcip-annotations 1.0 > (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) > We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: > 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. > 2 - it does not fail due to the dependency that is not really essential. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-800) Infinispan inside OSGI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on ISPN-800: ---------------------------------------------- Ion Savin <isavin(a)redhat.com> changed the Status of [bug 1111201|https://bugzilla.redhat.com/show_bug.cgi?id=1111201] from NEW to ASSIGNED > Infinispan inside OSGI > ---------------------- > > Key: ISPN-800 > URL: https://issues.jboss.org/browse/ISPN-800 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Luca Stancapiano > Assignee: Ion Savin > > We need to import infinispan inside a OSGI repository. Tests are made with Felix. > I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan > I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. > Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) > Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: > jboss transaction api 1.0.1.GA > We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) > jgroups 2.10.1.GA > (it's a osgi bundle since the 3.x version) > river 1.2.3.GA > (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) > marshalling-api 1.2.3.GA > (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) > jboss logging spi 2.0.5.GA > (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version. Fixed in the 3.x version) > rhq plugin annotations 1.4.0.B01 > (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) > i18nlog 1.0.9 > (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) > log4j 1.2.16 > (that's ok...it is a osgi bundle ;)) > jcip-annotations 1.0 > (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) > We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: > 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. > 2 - it does not fail due to the dependency that is not really essential. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-800) Infinispan inside OSGI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-800?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated ISPN-800: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1095200, https://bugzilla.redhat.com/show_bug.cgi?id=1111201 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1095200) > Infinispan inside OSGI > ---------------------- > > Key: ISPN-800 > URL: https://issues.jboss.org/browse/ISPN-800 > Project: Infinispan > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Luca Stancapiano > Assignee: Ion Savin > > We need to import infinispan inside a OSGI repository. Tests are made with Felix. > I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan > I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. > Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) > Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: > jboss transaction api 1.0.1.GA > We patched it. There is a new OSGI version here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... ) > jgroups 2.10.1.GA > (it's a osgi bundle since the 3.x version) > river 1.2.3.GA > (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/river/pom.xml ) > marshalling-api 1.2.3.GA > (opened an issue for marshalling 1.4.0 in JBMAR-118 and https://github.com/flashboss/jboss-marshalling/blob/master/api/pom.xml ) > jboss logging spi 2.0.5.GA > (added a jira issue in JBLOGGING-51 . It could be fixed in the 2.2.0.CR2 version. Fixed in the 3.x version) > rhq plugin annotations 1.4.0.B01 > (opened a feature request in https://bugzilla.redhat.com/show_bug.cgi?id=657754 ) > i18nlog 1.0.9 > (sent a patch in https://sourceforge.net/projects/i18nlog . It could become a OSGI bundle in the 1.0.10 version. Waiting for a response. Fixed in 1.15) > log4j 1.2.16 > (that's ok...it is a osgi bundle ;)) > jcip-annotations 1.0 > (I sent a patch via email to brian(a)briangoetz.com and a post in http://tembrel.blogspot.com. Sent the patch in concurrency-interest(a)cs.oswego.edu too. They responded to me. There is a OSGI version with a different artifact name. I changed the dependency in the pom.xml of the parent project) > We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: > 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. > 2 - it does not fail due to the dependency that is not really essential. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4421) Migration from jboss-as to wildfly arquillian-container-managed broke RollingUpgrades tests

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4421?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-4421: ------------------------------------- I suppose one of the servers, probably the older one, will have to be started via other means than Arquillian (e.g. antrun plugin or cargo). The other problem is that Infinispan Arquillian Container (it is used to collect jmx stats) now communicates with the server over http-remoting-jmx. I can investigate whether ispn-arq can be configured to use different protocols for different versions of server. Or we can try to not use ispn-arq for this test. > Migration from jboss-as to wildfly arquillian-container-managed broke RollingUpgrades tests > ------------------------------------------------------------------------------------------- > > Key: ISPN-4421 > URL: https://issues.jboss.org/browse/ISPN-4421 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Labels: test_suite, testsuite_stability > > Server was rebased to Wildfly. > For Arquillian, jboss-as-arquillian-container-managed was changed to wildfly-arquillian-container-managed in order to reflect respective changes. > The problem for Rolling Upgrade tests ( -Psuite.rolling.upgrades ) is that there are used also old server instances in those tests. > Due to new changes in infinispan-arquillian-container old Infinispan servers are not properly managed during their startup phase. > Observation: > Switching port to 10099 (wildfly is using 10090 for mgmt ops) does not help. Strange message is continuously showing until timeout: > 13:41:57,691 ERROR [org.jboss.remoting.remote.connection] (Remoting "node1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Received an invalid message length of 1195725856 > "Experiment" with setting up <property name="managementProtocol">remoting-jmx</property> for OLD server in arquillian.xml didn't help either, however, ERROR message ^ disappeared. > But the server can't start properly, better to say, it starts, but Arquillian is not able to handle it properly and communicate: > testHotRodRollingUpgradesDiffVersions(org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT) Time elapsed: 60.389 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container > at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:204) > at org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112) > at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255) > at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:93) > at org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.testHotRodRollingUpgradesDiffVersions(HotRodRollingUpgradesIT.java:68) > It looks like we need to somehow create a "bridge" or "switch" which will allow operations for both old and new servers in one test. > Or maybe I'm missing something important. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2014