April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-91) [QE] - JMAN4-153 - Install the in-process agent via zip into a zip installed EAP 6 installation

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-91?page=com.atlassian.jira.plu... ] Prachi Yadav commented on HAWKULARQE-91: ---------------------------------------- Bugzilla created: https://bugzilla.redhat.com/show_bug.cgi?id=1445768 > [QE] - JMAN4-153 - Install the in-process agent via zip into a zip installed EAP 6 installation > ----------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-91 > URL: https://issues.jboss.org/browse/HAWKULARQE-91 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > Labels: mm-integration-hawkular-qe > > See [JMAN4-153|https://issues.jboss.org/browse/JMAN4-153] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-91) [QE] - JMAN4-153 - Install the in-process agent via zip into a zip installed EAP 6 installation

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-91?page=com.atlassian.jira.plu... ] Prachi Yadav commented on HAWKULARQE-91: ---------------------------------------- Unable to monitor EAP 6in domain mode. > [QE] - JMAN4-153 - Install the in-process agent via zip into a zip installed EAP 6 installation > ----------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-91 > URL: https://issues.jboss.org/browse/HAWKULARQE-91 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > Labels: mm-integration-hawkular-qe > > See [JMAN4-153|https://issues.jboss.org/browse/JMAN4-153] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1102) Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1102?page=com.atlassian.jira.plugin.s... ] David Lloyd updated ELY-1102: ----------------------------- Fix Version/s: 1.1.0.Beta39 (was: 1.1.0.Beta38) > Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol > --------------------------------------------------------------------------------------------- > > Key: ELY-1102 > URL: https://issues.jboss.org/browse/ELY-1102 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta39 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2691) Elytron modifiable realms should show existing identities in subsystem

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2691?page=com.atlassian.jira.plugi... ] Ondrej Kotek commented on WFCORE-2691: -------------------------------------- There are other similar Elytron resources, e.g. {{/subsystem=elytron/*-key-store=x/alias=aliasFromExternalSource}}. [~brian.stansberry], do I understand it well that this is a design issue and other blocker Jira issues should be created for such resources? > Elytron modifiable realms should show existing identities in subsystem > ---------------------------------------------------------------------- > > Key: WFCORE-2691 > URL: https://issues.jboss.org/browse/WFCORE-2691 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta15 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Labels: filesystem-realm, security-realm > > Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in: > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"elytron\"), > (\"filesystem-realm\" => \"realm\"), > (\"identity\" => \"user\") > ]' not found", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add > { > "outcome" => "failed", > "failure-description" => "WFLYELY01000: Identity with name [user] already exists.", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1102) Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol

by David Lloyd (JIRA)

David Lloyd created ELY-1102: -------------------------------- Summary: Provide accessors in AuthenticationContextConfigurationClient to read the configured protocol Key: ELY-1102 URL: https://issues.jboss.org/browse/ELY-1102 Project: WildFly Elytron Issue Type: Enhancement Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.1.0.Beta38 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1124) Unble to provision errors when creating KieContainor from KieServices in the Vert.X verticle

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1124?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1124: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Unble to provision errors when creating KieContainor from KieServices in the Vert.X verticle > -------------------------------------------------------------------------------------------- > > Key: DROOLS-1124 > URL: https://issues.jboss.org/browse/DROOLS-1124 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.4.0.CR2 > Environment: OS: MacOX and 10.10.5 > Vert.X: 3.2.1 > Reporter: xiaodong wang > Assignee: Mario Fusco > > WARN Sisu - Error injecting: org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > com.google.inject.ProvisionException: Unable to provision, see the following errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was bound. > while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > 1 error > at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1018) > at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1044) > at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48) > at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) > at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:54) > at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70) > at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:113) > at org.eclipse.sisu.bean.BeanScheduler$Activator.onProvision(BeanScheduler.java:176) > at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:122) > at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68) > at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68) > at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:46) > at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) > at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1066) > at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) > at com.google.inject.Scopes$1$1.get(Scopes.java:59) > at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) > at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1009) > at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1059) > at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1005) > at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:82) > at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:249) > at org.kie.scanner.embedder.PlexusComponentProvider.lookup(PlexusComponentProvider.java:42) > at org.kie.scanner.embedder.MavenEmbedder.buildMavenExecutionRequest(MavenEmbedder.java:119) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:90) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:81) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:75) > at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:42) > at org.kie.scanner.embedder.MavenProjectLoader.loadMavenProject(MavenProjectLoader.java:96) > at org.kie.scanner.Aether.<init>(Aether.java:62) > at org.kie.scanner.Aether.getAether(Aether.java:74) > at org.kie.scanner.MavenRepository.getMavenRepository(MavenRepository.java:80) > at org.kie.scanner.ArtifactResolver.<init>(ArtifactResolver.java:53) > at org.kie.scanner.KieRepositoryScannerImpl.getArtifactResolver(KieRepositoryScannerImpl.java:102) > at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:119) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:130) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:116) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:93) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:115) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:111) > at com.cyngn.soothsayer.application.Server.init(Server.java:83) > at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$163(DeploymentManager.java:427) > at io.vertx.core.impl.ContextImpl.lambda$wrapTask$18(ContextImpl.java:335) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) > at java.lang.Thread.run(Thread.java:745) > 14:22:39.388 [vert.x-eventloop-thread-1] ERROR o.kie.scanner.embedder.MavenEmbedder - Unable to build MavenEmbedder > org.codehaus.plexus.component.repository.exception.ComponentLookupException: com.google.inject.ProvisionException: Unable to provision, see the following errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was bound. > while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] (via modules: org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule) > at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] (via modules: org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule) > while locating org.apache.maven.execution.MavenExecutionRequestPopulator > 1 error > role: org.apache.maven.execution.MavenExecutionRequestPopulator > roleHint: > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255) > at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:249) > at org.kie.scanner.embedder.PlexusComponentProvider.lookup(PlexusComponentProvider.java:42) > at org.kie.scanner.embedder.MavenEmbedder.buildMavenExecutionRequest(MavenEmbedder.java:119) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:90) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:81) > at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:75) > at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:42) > at org.kie.scanner.embedder.MavenProjectLoader.loadMavenProject(MavenProjectLoader.java:96) > at org.kie.scanner.Aether.<init>(Aether.java:62) > at org.kie.scanner.Aether.getAether(Aether.java:74) > at org.kie.scanner.MavenRepository.getMavenRepository(MavenRepository.java:80) > at org.kie.scanner.ArtifactResolver.<init>(ArtifactResolver.java:53) > at org.kie.scanner.KieRepositoryScannerImpl.getArtifactResolver(KieRepositoryScannerImpl.java:102) > at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:119) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:130) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:116) > at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:93) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:115) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:111) > at com.cyngn.soothsayer.application.Server.init(Server.java:83) > at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$163(DeploymentManager.java:427) > at io.vertx.core.impl.ContextImpl.lambda$wrapTask$18(ContextImpl.java:335) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-91) [QE] - JMAN4-153 - Install the in-process agent via zip into a zip installed EAP 6 installation

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-91?page=com.atlassian.jira.plu... ] Prachi Yadav commented on HAWKULARQE-91: ---------------------------------------- Manual Test case created and executed: - https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... - https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > [QE] - JMAN4-153 - Install the in-process agent via zip into a zip installed EAP 6 installation > ----------------------------------------------------------------------------------------------- > > Key: HAWKULARQE-91 > URL: https://issues.jboss.org/browse/HAWKULARQE-91 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > Labels: mm-integration-hawkular-qe > > See [JMAN4-153|https://issues.jboss.org/browse/JMAN4-153] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2691) Elytron modifiable realms should show existing identities in subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2691?page=com.atlassian.jira.plugi... ] Jan Kalina edited comment on WFCORE-2691 at 4/26/17 8:40 AM: ------------------------------------------------------------- Communicated in mailinglist: Best solution will be *removing identity resouces and using realm operations for access to identities instead*. For example: {code} /subsystem=elytron/ldap-realm=ldapRealm:read-identity(name=ldapUser) /subsystem=elytron/ldap-realm=ldapRealm:add-identity(name=ldapUser,foo=bar,xyz=true) {code} was (Author: honza889): Communicated in mailinglist: Best solution will be *removing identity resouces and using realm operations for access to identities instead*. > Elytron modifiable realms should show existing identities in subsystem > ---------------------------------------------------------------------- > > Key: WFCORE-2691 > URL: https://issues.jboss.org/browse/WFCORE-2691 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta15 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Labels: filesystem-realm, security-realm > > Elytron {{filesystem-realm}} should load existing identities from file system. The steps to reproduce results in: > {noformat} > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:read-identity > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"elytron\"), > (\"filesystem-realm\" => \"realm\"), > (\"identity\" => \"user\") > ]' not found", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=elytron/filesystem-realm=realm/identity=user:add > { > "outcome" => "failed", > "failure-description" => "WFLYELY01000: Identity with name [user] already exists.", > "rolled-back" => true > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2722) Elytron subsystem - Missing OTP support in set-password operation on identity in filesystem-realm

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2722?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-2722: ------------------------------------ Assignee: Yeray Borges (was: Darran Lofthouse) > Elytron subsystem - Missing OTP support in set-password operation on identity in filesystem-realm > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-2722 > URL: https://issues.jboss.org/browse/WFCORE-2722 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Yeray Borges > Priority: Critical > > The set-password operation on identities in filesystem-realm doesn't support OTP credentials. So identity with OneTimePassword can't be created in the filesystem-realm (Elytron subsystem). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5

by Kay J (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ] Kay J commented on DROOLS-1537: ------------------------------- So I have to use the same kBase instead of creating a new one? Why's that? The marshalling is meant to be a backup for recovery or for role back to old version. If I have to reuse the old kBase this isn't possible, as the kBase will not always be available, e.g. when I restart my application and want to unmarshall the session from a file or database. > Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5 > ---------------------------------------------------------------------------------------- > > Key: DROOLS-1537 > URL: https://issues.jboss.org/browse/DROOLS-1537 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Reporter: Kay J > Assignee: Mario Fusco > Attachments: RestoreReproducer.java > > > Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78 > Hello Drools users, > I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic. > I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017