July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-459) javassist should also be exported to Hibernate (native) applications

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Carlo de Wolf updated WFLY-459: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8474 (was: https://github.com/jbossas/jboss-as/pull/2766) > javassist should also be exported to Hibernate (native) applications > -------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Labels: downstream_dependency > Fix For: 10.1.0.Final > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1654) Enhancements for set/unset test suite

by Martin Schvarcbacher (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1654?page=com.atlassian.jira.plugi... ] Martin Schvarcbacher updated WFCORE-1654: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1681 > Enhancements for set/unset test suite > ------------------------------------- > > Key: WFCORE-1654 > URL: https://issues.jboss.org/browse/WFCORE-1654 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Martin Schvarcbacher > Assignee: Martin Schvarcbacher > Priority: Minor > > Added tests for jboss-cli ‘set’ and ‘unset’ commands > Use cases: > set variable1=value > set variable2=$variable1 > unset variable1 > set #prints all set variables -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Gytis Trikleris resolved WFLY-6620. ----------------------------------- Resolution: Done Yes sorry. It was resolved by https://github.com/wildfly/wildfly/pull/8817. > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6839) It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-6839: ---------------------------------- Summary: It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml Key: WFLY-6839 URL: https://issues.jboss.org/browse/WFLY-6839 Project: WildFly Issue Type: Bug Components: CLI Reporter: Hynek Švábek Assignee: Alexey Loubyansky In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. {code} <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> ... ... <ValidatingAlias Key="localhost" Value="servercert" /> <ValidatingAlias Key="127.0.0.1" Value="servercert" /> </KeyProvider> {code} But in subsystem configuration I cannot do this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1119) ManagedDatagramSocketBinding throw NPE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1119?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1119: ------------------------------------------------- Enrique Gonzalez Martinez <egonzale(a)redhat.com> changed the Status of [bug 1280235|https://bugzilla.redhat.com/show_bug.cgi?id=1280235] from ASSIGNED to POST > ManagedDatagramSocketBinding throw NPE > -------------------------------------- > > Key: WFCORE-1119 > URL: https://issues.jboss.org/browse/WFCORE-1119 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR8 > Reporter: Stefan Dilk > Assignee: Brian Stansberry > Fix For: 2.0.2.Final > > > i think i have found the same bug as in WFCORE-1033 but in another method. > in the previous bug the bind method was the problem, here i have the same NPE in the close method. there is no null check to registry as in the bind method. > {noformat} > [Server:mgmt-1-prod] 2015-11-10 00:37:15,454 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.jgroups.channel.ee.connector: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee.connector: > java.lang.NullPointerException > [Server:mgmt-1-prod] at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:9 > 6) > [Server:mgmt-1-prod] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > [Server:mgmt-1-prod] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > [Server:mgmt-1-prod] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [Server:mgmt-1-prod] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [Server:mgmt-1-prod] at java.lang.Thread.run(Thread.java:745) > [Server:mgmt-1-prod] Caused by: java.lang.NullPointerException > [Server:mgmt-1-prod] at org.jboss.as.network.ManagedDatagramSocketBinding.close(ManagedDatagramSocketBinding.java:73) > [Server:mgmt-1-prod] at java.net.DatagramSocket.<init>(DatagramSocket.java:245) > [Server:mgmt-1-prod] at org.jboss.as.network.ManagedDatagramSocketBinding.<init>(ManagedDatagramSocketBinding.java:41) > [Server:mgmt-1-prod] at org.jboss.as.network.SocketBindingManagerImpl.createDatagramSocket(SocketBindingManagerImpl.java:87) > [Server:mgmt-1-prod] at org.jboss.as.clustering.jgroups.ManagedSocketFactory.createDatagramSocket(ManagedSocketFactory.java:103) > [Server:mgmt-1-prod] at org.jboss.as.clustering.jgroups.ManagedSocketFactory.createDatagramSocket(ManagedSocketFactory.java:113) > [Server:mgmt-1-prod] at org.jgroups.protocols.UDP.createDatagramSocketWithBindPort(UDP.java:487) > [Server:mgmt-1-prod] at org.jgroups.protocols.UDP.createSockets(UDP.java:361) > [Server:mgmt-1-prod] at org.jgroups.protocols.UDP.start(UDP.java:270) > [Server:mgmt-1-prod] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:965) > [Server:mgmt-1-prod] at org.jgroups.JChannel.startStack(JChannel.java:890) > [Server:mgmt-1-prod] at org.jgroups.JChannel._preConnect(JChannel.java:553) > [Server:mgmt-1-prod] at org.jgroups.JChannel.connect(JChannel.java:288) > [Server:mgmt-1-prod] at org.jgroups.JChannel.connect(JChannel.java:279) > [Server:mgmt-1-prod] at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.start(ChannelConnectorBuilder.java:94) > [Server:mgmt-1-prod] ... 5 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1658) JBEAP-2830 enhancements were not forward ported to upstream

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1658?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1658: ------------------------------------- Description: JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later. I believe there's no problem applying the changes. EAP will use one of the supplements while WildFly will not. was: JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later. I believe there's no problem applying the changes. EAP will use on of the supplements while WildFly will not. > JBEAP-2830 enhancements were not forward ported to upstream > ----------------------------------------------------------- > > Key: WFCORE-1658 > URL: https://issues.jboss.org/browse/WFCORE-1658 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 2.2.0.CR8 > > > JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later. > I believe there's no problem applying the changes. EAP will use one of the supplements while WildFly will not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1658) JBEAP-2830 enhancements were not forward ported to upstream

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1658: ---------------------------------------- Summary: JBEAP-2830 enhancements were not forward ported to upstream Key: WFCORE-1658 URL: https://issues.jboss.org/browse/WFCORE-1658 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 2.2.0.CR8 JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later. I believe there's no problem applying the changes. EAP will use on of the supplements while WildFly will not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6620: ---------------------------------------- [~gytis] Is this done? PR #8817 has an upgrade and a 2nd commit that looks like a typo fix. > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6830) modcluster proxies is not exposed for configuration via admin console

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-6830?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-6830: ---------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > modcluster proxies is not exposed for configuration via admin console > --------------------------------------------------------------------- > > Key: WFLY-6830 > URL: https://issues.jboss.org/browse/WFLY-6830 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Aaron Ogburn > Assignee: Radoslav Husar > Labels: mod_cluster > > The proxies attribute cannot be configured via the console. Just the deprecated proxy-list is still exposed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6636) WELD-001408: Unsatisfied dependencies on hot deploy of app using module-alias as dependency

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6636?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6636: ----------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1338093|https://bugzilla.redhat.com/show_bug.cgi?id=1338093] from POST to ASSIGNED > WELD-001408: Unsatisfied dependencies on hot deploy of app using module-alias as dependency > ------------------------------------------------------------------------------------------- > > Key: WFLY-6636 > URL: https://issues.jboss.org/browse/WFLY-6636 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Tomas Hofman > Attachments: test.ear > > > If a sub deployment uses another sub deployment's module-alias as a dependency, it will deploy successfully, but if hot deployed, it will fail with the error below. Attached reproducer. > {code} > <?xml version="1.0" encoding="UTF-8"?> > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"> > <ear-subdeployments-isolated>true</ear-subdeployments-isolated> > <sub-deployment name="ejb1.jar"> > <module-alias name="deployment.ejb1"/> > </sub-deployment> > <sub-deployment name="ejb2.jar"> > <dependencies> >  >  > <module name="deployment.ejb1" slot="main"/> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > {code} > {code} > 10:43:42,140 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."test.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.ear".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > 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) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type TestEJB1 with qualifiers @Default > at injection point [BackedAnnotatedField] @Inject private test.TestEJB2.test1 > at test.TestEJB2.test1(TestEJB2.java:0) > at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:359) > at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281) > at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134) > at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155) > at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518) > at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68) > at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > 10:43:42,144 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.ear\".WeldStartService: Failed to start service > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type TestEJB1 with qualifiers @Default > at injection point [BackedAnnotatedField] @Inject private test.TestEJB2.test1 > at test.TestEJB2.test1(TestEJB2.java:0) > "}} > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016