August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-227) Release JBoss Jakarta JACC 2.0.0.CR2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/JBEE-227?page=com.atlassian.jira.plugin.s... ] Farah Juma updated JBEE-227: ---------------------------- Fix Version/s: jboss-jakarta-jacc-api_spec-2.0.0.CR2 > Release JBoss Jakarta JACC 2.0.0.CR2 > ------------------------------------ > > Key: JBEE-227 > URL: https://issues.jboss.org/browse/JBEE-227 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jacc-api > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: jboss-jakarta-jacc-api_spec-2.0.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4623) Intermittent failures in IdentityOperationsTestCase

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4623?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed reassigned WFCORE-4623: ------------------------------------------ Assignee: Ashley Abdel-Sayed (was: Darran Lofthouse) > Intermittent failures in IdentityOperationsTestCase > --------------------------------------------------- > > Key: WFCORE-4623 > URL: https://issues.jboss.org/browse/WFCORE-4623 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Ashley Abdel-Sayed > Priority: Major > > IdentityOperationsTestCase fails intermittently, producing a set of 21 failures. When this happens the entire job seems to time out. > https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&bui... > The problem seems to involve a server not being able to reach MSC stability during boot and then a lot of problems trying to roll back the boot op. The latter are kind of noise, i.e. the stack trace bit in the snippet below. The key thing is the failure to get MSC stability. > {code} > 17:11:15,658 INFO (main) [org.wildfly.security] <Version.java:55> ELY00001: WildFly Elytron version 1.10.0.CR5 > 17:11:15,878 INFO (main) [org.jboss.msc] <ServiceContainerImpl.java:90> JBoss MSC version 1.4.8.Final > 17:11:15,893 INFO (main) [org.jboss.threads] <Version.java:52> JBoss Threads version 2.3.3.Final > 17:11:16,027 TRACE (main) [org.wildfly.security] <SecurityDomain.java:1056> Building security domain with defaultRealmName Empty. > 17:11:16,037 TRACE (main) [org.wildfly.security] <SecurityDomain.java:708> Role mapping: principal [anonymous] -> decoded roles [] -> realm mapped roles [] -> domain mapped roles [] > 17:11:16,312 TRACE (MSC service thread 1-2) [org.wildfly.extension.elytron] <ProviderDefinitions.java:238> Loaded providers [WildFlyElytron version 1.0] > 17:16:16,313 ERROR (Controller Boot Thread) [org.jboss.as.controller.management-operation] <OperationContextImpl.java:489> WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[("path" => "jboss.server.data.dir")]' > 17:16:21,322 ERROR (Controller Boot Thread) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:1525> WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@b0b65f for operation add at address [ > ("subsystem" => "elytron"), > ("filesystem-realm" => "FileSystemRealm") > ] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException > at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:523) > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1518) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1472) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1455) > at org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1319) > at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:876) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1413) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:495) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4637) Upgrade JBoss / Jakarta JACC to 2.0.0.CR2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4637?page=com.atlassian.jira.plugi... ] Farah Juma updated WFCORE-4637: ------------------------------- Summary: Upgrade JBoss / Jakarta JACC to 2.0.0.CR2 (was: Upgrade JBoss / Jakrata JACC to 2.0.0.CR2) > Upgrade JBoss / Jakarta JACC to 2.0.0.CR2 > ----------------------------------------- > > Key: WFCORE-4637 > URL: https://issues.jboss.org/browse/WFCORE-4637 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 10.0.0.Beta6 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4637) Upgrade JBoss / Jakrata JACC to 2.0.0.CR2

by Farah Juma (Jira)

Farah Juma created WFCORE-4637: ---------------------------------- Summary: Upgrade JBoss / Jakrata JACC to 2.0.0.CR2 Key: WFCORE-4637 URL: https://issues.jboss.org/browse/WFCORE-4637 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 10.0.0.Beta6 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12463) DeploymentRepository.getStartedModules() throws NPE if service stopped.

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12463?page=com.atlassian.jira.plugin... ] Paul Ferraro closed WFLY-12463. ------------------------------- Resolution: Duplicate Issue Silly me. We fixed this already: WFLY-9447 > DeploymentRepository.getStartedModules() throws NPE if service stopped. > ----------------------------------------------------------------------- > > Key: WFLY-12463 > URL: https://issues.jboss.org/browse/WFLY-12463 > Project: WildFly > Issue Type: Bug > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Seen in a remote EJB failover test run during server shutdown: > {noformat} > 2019-08-30 12:41:20,003 ERROR [org.jboss.ejb.client.invocation] (default task-6) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException > at org.jboss.as.ejb3@7.2.3.GA-redhat-00003//org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202) > at org.jboss.as.ejb3@7.2.3.GA-redhat-00003//org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:422) > at org.jboss.as.ejb3@7.2.3.GA-redhat-00003//org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:122) > at org.jboss.ejb-client@4.0.20.Final-redhat-00001-jbeap-17268//org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:465) > at org.jboss.ejb-client@4.0.20.Final-redhat-00001-jbeap-17268//org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:202) > at org.jboss.remoting@5.0.14.Final-jbeap-17268//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting@5.0.14.Final-jbeap-17268//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12463) DeploymentRepository.getStartedModules() throws NPE if service stopped.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12463: ----------------------------------- Summary: DeploymentRepository.getStartedModules() throws NPE if service stopped. Key: WFLY-12463 URL: https://issues.jboss.org/browse/WFLY-12463 Project: WildFly Issue Type: Bug Reporter: Paul Ferraro Assignee: Paul Ferraro Seen in a remote EJB failover test run during server shutdown: {noformat} 2019-08-30 12:41:20,003 ERROR [org.jboss.ejb.client.invocation] (default task-6) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException at org.jboss.as.ejb3@7.2.3.GA-redhat-00003//org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202) at org.jboss.as.ejb3@7.2.3.GA-redhat-00003//org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:422) at org.jboss.as.ejb3@7.2.3.GA-redhat-00003//org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:122) at org.jboss.ejb-client@4.0.20.Final-redhat-00001-jbeap-17268//org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:465) at org.jboss.ejb-client@4.0.20.Final-redhat-00001-jbeap-17268//org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:202) at org.jboss.remoting@5.0.14.Final-jbeap-17268//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) at org.jboss.remoting@5.0.14.Final-jbeap-17268//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.base/java.lang.Thread.run(Thread.java:834) {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-227) Release JBoss Jakarta JACC 2.0.0.CR2

by Farah Juma (Jira)

Farah Juma created JBEE-227: ------------------------------- Summary: Release JBoss Jakarta JACC 2.0.0.CR2 Key: JBEE-227 URL: https://issues.jboss.org/browse/JBEE-227 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jacc-api Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4150) Support automatically adding / updating credentials in the CredentialStore

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4150?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4150: ---------------------------------- Fix Version/s: (was: 10.0.0.Beta6) > Support automatically adding / updating credentials in the CredentialStore > -------------------------------------------------------------------------- > > Key: WFCORE-4150 > URL: https://issues.jboss.org/browse/WFCORE-4150 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-185) PVC not deleted by deleting WildFlyServer CR

by Martin Choma (Jira)

Martin Choma created WFWIP-185: ---------------------------------- Summary: PVC not deleted by deleting WildFlyServer CR Key: WFWIP-185 URL: https://issues.jboss.org/browse/WFWIP-185 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Choma Assignee: Jeff Mesnil When I delete WildFlyServer CR PVC created by this CR is not deleted as StatefullSet and Pods are . I see Statefull Set and Pod has ownerReferences attribute referencing to parent. ownerReferences List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller. I dont see such attribute specified in PVC {code} # Please edit the object below. Lines beginning with a '#' will be ignored, # and an empty file will abort the edit. If an error occurs while saving this file will be # reopened with the relevant failures. # apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" creationTimestamp: 2019-08-30T13:12:27Z finalizers: - kubernetes.io/pvc-protection labels: app.kubernetes.io/managed-by: wildfly-operator app.kubernetes.io/name: simple-jaxrs-eap72 app.openshift.io/runtime: wildfly name: simple-jaxrs-eap72-volume-simple-jaxrs-eap72-0 namespace: mchoma resourceVersion: "3633284" selfLink: /api/v1/namespaces/mchoma/persistentvolumeclaims/simple-jaxrs-eap72-volume-simple-jaxrs-eap72-0 uid: d0aac389-cb27-11e9-b93c-fa163e9a0fb6 spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Mi volumeName: vol57 status: accessModes: - ReadWriteMany - ReadWriteOnce capacity: storage: 1Gi phase: Bound {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12462) Incompatible conflicting binding Exception and EJB naming

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12462?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12462: ------------------------------------ Forum Reference: https://developer.jboss.org/message/990786 Added a forum link to https://developer.jboss.org/message/990786 > Incompatible conflicting binding Exception and EJB naming > --------------------------------------------------------- > > Key: WFLY-12462 > URL: https://issues.jboss.org/browse/WFLY-12462 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 17.0.1.Final > Environment: MacOS High Sierra > Reporter: Alexey Usharovski > Assignee: Cheng Fang > Priority: Minor > Attachments: server.log.zip, simplewebapp-lesson-6-ejb.zip, war-content.txt.zip > > > Wired exception for very simple EJB with @Remote annotated interface in time of deploy to WildFly 17.0.1.Final > {code:java} > @Stateless > public class UserServiceImpl implements UserServiceRemote { > @Override > public List<UserRepr> getAllUsers() { > return null; > } > } > @Remote > public interface UserServiceRemote { > List<UserRepr> getAllUsers(); > } > {code} > The exception is > {code} > Caused by: java.lang.IllegalArgumentException: WFLYEE0047: Incompatible conflicting binding at java:jboss/exported/simple-webapp/UserServiceImpl!ru.geekbrains.jsf.UserServiceRemote > source: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor$2@6aba1c4b"}, > "WFLYCTL0412: Required services that are not installed:" => [ "jboss.deployment.unit.\"simple-webapp.war\".beanmanager", "jboss.deployment.unit.\"simple-webapp.war\".WeldStartService" ], > "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.deployment.unit.\"simple-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager]", > "jboss.deployment.unit.\"simple-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager, jboss.deployment.unit.\"simple-webapp.war\".WeldStartService]" ] } > {code} > Notice that problem could be resolved by undeploy and Wildfly server restart. May be something wrong with JNDI content? > I've tried to look through the web console but found nothing interesting. > Full application code on GitHub https://github.com/usharik/simplewebapp/tree/lesson-6-ejb -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

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 August 2019