January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6006) org.jboss.as.security-api module should be deprecated

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6006?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6006: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.0.0.Final) > org.jboss.as.security-api module should be deprecated > ----------------------------------------------------- > > Key: WFLY-6006 > URL: https://issues.jboss.org/browse/WFLY-6006 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.1.0.Final > > > According to Eng, PM and QA inputs in [Module Classification doc|https://mojo.redhat.com/docs/DOC-1053168] there seems to be agreement to change visibility of this module back to deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5964) Update to version 4.1 of the management schema / model

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5964?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5964: ------------------------------- Fix Version/s: 10.1.0.Final (was: 10.0.0.Final) > Update to version 4.1 of the management schema / model > ------------------------------------------------------ > > Key: WFLY-5964 > URL: https://issues.jboss.org/browse/WFLY-5964 > Project: WildFly > Issue Type: Task > Components: Domain Management, Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-97) Trim down the custom model API and align closer with the javax.lang.model API

by James Perkins (JIRA)

James Perkins created LOGTOOL-97: ------------------------------------ Summary: Trim down the custom model API and align closer with the javax.lang.model API Key: LOGTOOL-97 URL: https://issues.jboss.org/browse/LOGTOOL-97 Project: Log Tool Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Fix For: 2.1.0.Alpha1 Using an internal model works in some cases, but makes it harder to keep consistent when adding new annotations as well as validating some rules. If the internal model was able to extend the {{java.lang.model.*}} elements/types new annotations and better validation would be possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1045) kie-ci 6.3.0.Final conflicts with newer versions of Guava

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1045?page=com.atlassian.jira.plugi... ] Petr Široký commented on DROOLS-1045: ------------------------------------- Great! Thanks for confirmation [~abaxter]. > kie-ci 6.3.0.Final conflicts with newer versions of Guava > --------------------------------------------------------- > > Key: DROOLS-1045 > URL: https://issues.jboss.org/browse/DROOLS-1045 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Adam Baxter > Assignee: Petr Široký > Fix For: 6.4.0.Beta1 > > > When using kie-ci with Google's Guava library (v19), we hit the following error: http://stackoverflow.com/questions/32528042/maven-java-lang-illegalaccess... > We solved this by excluding kie-ci's sisu-guice transitive dependency and including the 3.1.7 version released in 2014. > Please update kie-ci's dependencies such that this is no longer an issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1135) Unable to start Wildfly when FIPS is enabled in Domain Mode

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1135?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1135: --------------------------------- Fix Version/s: 2.0.11.Final (was: 2.0.8.Final) > Unable to start Wildfly when FIPS is enabled in Domain Mode > ----------------------------------------------------------- > > Key: WFCORE-1135 > URL: https://issues.jboss.org/browse/WFCORE-1135 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management, Security > Affects Versions: 2.0.1.Final > Reporter: Ryan Emerson > Assignee: Darran Lofthouse > Fix For: 2.0.11.Final > > > Allow FIPS use in Domain mode. This requires additional logic to standalone, due to the connections between controllers and servers. > Resulting stacktrace when attempting to run domain mode with FIPS enabled at the JVM: > 15:47:39,410 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:133) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:server-one] at java.lang.Thread.run(Thread.java:745) > [Server:server-one] Caused by: java.io.IOException: WFLYSRV0117: Unable to initialise a basic SSLContext 'FIPS mode: only SunJSSE TrustManagers may be used' > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.getAcceptingSSLContext(HostControllerConnectionService.java:212) > [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:108) > [Server:server-one] ... 5 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1283) Add version 4.1 of the domain management schema and bump the management model version.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1283?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1283: --------------------------------- Fix Version/s: 2.0.11.Final (was: 2.0.8.Final) > Add version 4.1 of the domain management schema and bump the management model version. > -------------------------------------------------------------------------------------- > > Key: WFCORE-1283 > URL: https://issues.jboss.org/browse/WFCORE-1283 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.11.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1201) Could not upload new deployment

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ] Jason Greene updated WFCORE-1201: --------------------------------- Fix Version/s: 2.0.11.Final (was: 2.0.8.Final) > Could not upload new deployment > ------------------------------- > > Key: WFCORE-1201 > URL: https://issues.jboss.org/browse/WFCORE-1201 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.2.Final > Environment: 2 different machines > Linux Debian Squeeze & Jessie > Oracle Java SE 8 > Reporter: Claudio Weiler > Assignee: Harald Pehl > Fix For: 2.0.11.Final > > > WildFly stop to accept deployments via interface upload with following stacktrace: > ERROR [io.undertow.request] (XNIO-1 task-2) Undertow request failed HttpServerExchange{ POST /management-upload}: java.io.IOException: UT000036: Connection terminated parsing multipart data > at io.undertow.server.handlers.form.MultiPartParserDefinition$MultiPartUploadHandler.parseBlocking(MultiPartParserDefinition.java:203) > at org.jboss.as.domain.http.server.DomainApiGenericOperationHandler.handleRequest(DomainApiGenericOperationHandler.java:104) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68) > at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Same artifact was used before with success, nothing changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1033) Enhance XTS AS7 configuration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-1033?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned WFLY-1033: ----------------------------------- Assignee: Gytis Trikleris > Enhance XTS AS7 configuration > ----------------------------- > > Key: WFLY-1033 > URL: https://issues.jboss.org/browse/WFLY-1033 > Project: WildFly > Issue Type: Enhancement > Components: XTS > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported. > XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations. > The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1033) Enhance XTS AS7 configuration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-1033?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-1033: -------------------------------- Fix Version/s: 11.0.0.Alpha1 > Enhance XTS AS7 configuration > ----------------------------- > > Key: WFLY-1033 > URL: https://issues.jboss.org/browse/WFLY-1033 > Project: WildFly > Issue Type: Enhancement > Components: XTS > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported. > XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations. > The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2387) CDI injection in entity listeners failing

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2387?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-2387: ------------------------------------ I pushed a (work in progress) hack to [https://github.com/scottmarlow/wildfly/tree/orm51] that passes the org.jboss.as.test.integration.ee.injection.support.jpa.EntityListenerInjectionSupportTestCase test case that Tomas Remes provided. This is with the [https://hibernate.atlassian.net/browse/HHH-8706] changes that Steve Ebersole push to the Hibernate master branch. I also tried the [https://hibernate.atlassian.net/browse/HHH-10477] change on the ORM 5.0 branch, with the EntityListenerInjectionSupportTestCase test changed to set persistence unit property "hibernate.delay_cdi_access=true" and that also passed. Additional status updates are in comments on HHH-8706. > CDI injection in entity listeners failing > ----------------------------------------- > > Key: WFLY-2387 > URL: https://issues.jboss.org/browse/WFLY-2387 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Class Loading, JPA / Hibernate > Affects Versions: 8.0.0.Beta1 > Reporter: Emond Papegaaij > Assignee: Scott Marlow > Attachments: TEST-org.jboss.as.test.integration.ee.injection.support.jpa.EntityListenerInjectionSupportTestCase.xml > > > When trying to use CDI injection in JPA entity listeners, deployment fails with the following exception: > {code} > 16:16:37,448 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 15) MSC000001: Failed to start service jboss.persistenceunit."inject-ear.ear#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."inject-ear.ear#primary": java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:169) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25] > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:463) [wildfly-security-manager-1.0.0.Beta3.jar:1.0.0.Beta3] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:178) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75) > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:128) > at org.jboss.weld.Container.instance(Container.java:65) > at org.jboss.weld.manager.BeanManagerImpl.getBeans(BeanManagerImpl.java:563) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:90) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:82) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:71) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory.buildListener(BeanManagerListenerFactory.java:57) > at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.resolveCallbacks(LegacyCallbackProcessor.java:168) > at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.processCallbacksForEntity(LegacyCallbackProcessor.java:71) > at org.hibernate.jpa.event.spi.JpaIntegrator.integrate(JpaIntegrator.java:150) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1837) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:854) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:847) > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:396) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:846) > at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:151) > ... 8 more > {code} > I've created a small showcase of the problem: https://github.com/papegaaij/listener-injection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 January 2016