November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5733) Still open on 9.0.1 Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5733?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-5733: ------------------------------------ Just a point of clarification, we do still do 9.x releases, but they are for high priority fixes at this stage of the lifecycle (security fixes, critical issues affecting a large number of people etc). That said if someone is willing to backport fixes they care about and submit a PR on the 9.x branch, it will be included in the next 9.x release. We don't have one planned atm though (again open on that front). > Still open on 9.0.1 Final > ------------------------- > > Key: WFLY-5733 > URL: https://issues.jboss.org/browse/WFLY-5733 > Project: WildFly > Issue Type: Sub-task > Components: EJB, JMS > Affects Versions: 9.0.1.Final > Reporter: Alberto Persello > Assignee: Darran Lofthouse > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1984) NPE while creating a dynamic FORK channel

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/JGRP-1984?page=com.atlassian.jira.plugin.... ] Ramesh Reddy updated JGRP-1984: ------------------------------- Attachment: RpcForkDispatcherTest.java tcp-shared.xml Files attached > NPE while creating a dynamic FORK channel > ----------------------------------------- > > Key: JGRP-1984 > URL: https://issues.jboss.org/browse/JGRP-1984 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.4 > Reporter: Ramesh Reddy > Assignee: Bela Ban > Fix For: 3.6.7 > > Attachments: RpcForkDispatcherTest.java, tcp-shared.xml > > > I am trying to create a ForkChannel based on the example in docs with code, when FORK protocol not present in the main stack > {code} > channel=new JChannel("tcp.xml")); > channel.connect("RpcDispatcherTestGroup"); > ForkChannel forkChannel = new ForkChannel(channel, "test-rpc", name, true, ProtocolStack.BELOW, FRAG2.class); > forkChannel.connect("test-rpc"); > {code} > this ends with > {code} > Exception in thread "main" java.lang.NullPointerException > at org.jgroups.protocols.FORK.createForkStack(FORK.java:199) > at org.jgroups.fork.ForkChannel.<init>(ForkChannel.java:79) > at org.teiid.systemmodel.RpcDispatcherTest.start(RpcDispatcherTest.java:32) > at org.teiid.systemmodel.RpcDispatcherTest.main(RpcDispatcherTest.java:54 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5733) Still open on 9.0.1 Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5733?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-5733. ------------------------------------ Resolution: Rejected This is already fixed for 10, we don't backport to 9 or provide patches for 9 - looking at the pull requests the changes look small so you could consider backporting yourself or upgrade to 10 once it is available. > Still open on 9.0.1 Final > ------------------------- > > Key: WFLY-5733 > URL: https://issues.jboss.org/browse/WFLY-5733 > Project: WildFly > Issue Type: Sub-task > Components: EJB, JMS > Affects Versions: 9.0.1.Final > Reporter: Alberto Persello > Assignee: Darran Lofthouse > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5733) Still open on 9.0.1 Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-5733?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-5733: -------------------------------------- Assignee: Darran Lofthouse (was: Jason Greene) > Still open on 9.0.1 Final > ------------------------- > > Key: WFLY-5733 > URL: https://issues.jboss.org/browse/WFLY-5733 > Project: WildFly > Issue Type: Sub-task > Components: EJB, JMS > Affects Versions: 9.0.1.Final > Reporter: Alberto Persello > Assignee: Darran Lofthouse > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5733) Still open on 9.0.1 Final

by Alberto Persello (JIRA)

Alberto Persello created WFLY-5733: -------------------------------------- Summary: Still open on 9.0.1 Final Key: WFLY-5733 URL: https://issues.jboss.org/browse/WFLY-5733 Project: WildFly Issue Type: Sub-task Affects Versions: 9.0.1.Final Reporter: Alberto Persello Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3355) MDB fails to deploy on reload

by Alberto Persello (JIRA)

[ https://issues.jboss.org/browse/WFLY-3355?page=com.atlassian.jira.plugin.... ] Alberto Persello commented on WFLY-3355: ---------------------------------------- is there a patch available for 9.0.1 Final? > MDB fails to deploy on reload > ----------------------------- > > Key: WFLY-3355 > URL: https://issues.jboss.org/browse/WFLY-3355 > Project: WildFly > Issue Type: Bug > Components: EJB, JMS > Affects Versions: 10.0.0.Alpha4 > Environment: Windows 7, 64bit > Reporter: Bart Van Dosselaer > Assignee: Jeff Mesnil > Fix For: 10.0.0.Beta1 > > Attachments: leak-0.0.1-SNAPSHOT.jar > > > When an MDB is deployed and a :reload command is issues, the application server fails to deploy this MDB. > Stacktrace: > {noformat} > 2014-05-14 16:11:22,284 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 57) MSC000001: Failed to start service jboss.deployment.unit."wildfly-helloworld-mdb.war".component.HelloWorldQueueMDB.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-helloworld-mdb.war".component.HelloWorldQueueMDB.START: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) [wildfly-ee-8.1.0.CR2.jar:8.1.0.CR2] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_55] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > Caused by: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:215) > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:186) > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) [wildfly-ee-8.1.0.CR2.jar:8.1.0.CR2] > ... 6 more > Caused by: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down > at org.jboss.jca.core.workmanager.WorkManagerImpl.doFirstChecks(WorkManagerImpl.java:776) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final] > at org.jboss.jca.core.workmanager.WorkManagerImpl.scheduleWork(WorkManagerImpl.java:617) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final] > at org.jboss.jca.core.workmanager.WorkManagerImpl.scheduleWork(WorkManagerImpl.java:602) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final] > at org.hornetq.ra.inflow.HornetQActivation.start(HornetQActivation.java:264) [hornetq-ra-2.4.1.Final.jar:] > at org.hornetq.ra.HornetQResourceAdapter.endpointActivation(HornetQResourceAdapter.java:166) [hornetq-ra-2.4.1.Final.jar:] > at org.jboss.jca.core.rar.EndpointImpl.activate(EndpointImpl.java:191) [ironjacamar-core-impl-1.1.5.Final.jar:1.1.5.Final] > at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.activate(MessageDrivenComponent.java:213) > ... 8 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5732) CLI operation export-journal does not work with custom journal paths

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5732?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-2007 to WFLY-5732: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5732 (was: JBEAP-2007) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: JMS (was: JMS) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.ER1) > CLI operation export-journal does not work with custom journal paths > -------------------------------------------------------------------- > > Key: WFLY-5732 > URL: https://issues.jboss.org/browse/WFLY-5732 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > To reproduce the issue run server in stadalone mode with following properties (or you can use attached standalone-full-ha.xml) > {code} > <bindings-directory path="/var/tmp/journal/bindings"/> > <journal-directory path="/var/tmp/journal/journal"/> > <large-messages-directory path="/var/tmp/journal/largemessages"/> > <paging-directory path="/var/tmp/journal/paging"/> > <jms-queue name="testQueue" entries="jms/queue/testQueue java:jboss/exported/jms/queue/testQueue"/> > {code} > Send some messages into the testQueue with JMSDeliveryMode set to Persistent. > {code} > TextMessage textMessage = context.createTextMessage(content); > textMessage.setJMSDeliveryMode(DeliveryMode.PERSISTENT); > context.createProducer().send(destination, textMessage); > {code} > Run > {code} > ./bin/jboss-cli.sh -c ":reload(admin-only=true)" > ./bin/jboss-cli.sh -c "/subsystem=messaging-activemq/server=default/:export-journal()" > {code} > *Expectation:* Exported file contains sent messages. > *Reality:* Exported file contains no message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-258) Inconsistent 'AuthenticationContext' naming.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-258?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-258: --------------------------------- Priority: Blocker (was: Critical) > Inconsistent 'AuthenticationContext' naming. > -------------------------------------------- > > Key: ELY-258 > URL: https://issues.jboss.org/browse/ELY-258 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta2 > > > Other classes in these packages should also be checked but essentially we have a client and server package, the context in client is AuthenticationContext, the one in server is ServerAuthenticationContext. > If they are ever likely to be both used together then unique names would be advisable, otherwise they could both be 'AuthenticationContext'. > Wait till all engineers are off PTO before working on this one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-258) Inconsistent 'AuthenticationContext' naming.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-258?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-258: ------------------------------------ Assignee: Darran Lofthouse > Inconsistent 'AuthenticationContext' naming. > -------------------------------------------- > > Key: ELY-258 > URL: https://issues.jboss.org/browse/ELY-258 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta2 > > > Other classes in these packages should also be checked but essentially we have a client and server package, the context in client is AuthenticationContext, the one in server is ServerAuthenticationContext. > If they are ever likely to be both used together then unique names would be advisable, otherwise they could both be 'AuthenticationContext'. > Wait till all engineers are off PTO before working on this one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3153) Testing legacy subsystem transformers between different versions of Wildlfy

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3153?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-3153: --------------------------------- Assignee: Tomaz Cerar > Testing legacy subsystem transformers between different versions of Wildlfy > --------------------------------------------------------------------------- > > Key: WFLY-3153 > URL: https://issues.jboss.org/browse/WFLY-3153 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: ehsavoie Hugonnet > Assignee: Tomaz Cerar > > The legacy web subsystem is still evolving. Thus we need to make the legacy web subsystem in WildFly evolve and test the transformers. > But testing the transformation between WildFly 8.0.0.Final and the next version of WildFly fails with the following exception : > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > 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:606) > at org.jboss.as.subsystem.bridge.local.ScopedKernelServicesBootstrap.createChildClassLoaderKernelServices(ScopedKernelServicesBootstrap.java:85) > at org.jboss.as.subsystem.bridge.local.ScopedKernelServicesBootstrap.createKernelServices(ScopedKernelServicesBootstrap.java:53) > at org.jboss.as.subsystem.test.SubsystemTestDelegate$LegacyKernelServiceInitializerImpl.install(SubsystemTestDelegate.java:771) > at org.jboss.as.subsystem.test.SubsystemTestDelegate$LegacyKernelServiceInitializerImpl.access$700(SubsystemTestDelegate.java:644) > at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.build(SubsystemTestDelegate.java:616) > at org.jboss.as.web.test.WebSubsystemTestCase.testTransformation_2_0(WebSubsystemTestCase.java:443) > at org.jboss.as.web.test.WebSubsystemTestCase.testTransformationWildFly8(WebSubsystemTestCase.java:427) > Caused by: java.lang.IllegalArgumentException: JBAS014880: No operation entry called 'add' registered at '[("subsystem" => "web")]' > at org.jboss.as.controller.operations.validation.OperationValidator.throwOrWarnAboutDescriptorProblem(OperationValidator.java:549) > at org.jboss.as.controller.operations.validation.OperationValidator.validateOperation(OperationValidator.java:123) > at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:199) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:289) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) > at java.lang.Thread.run(Thread.java:744) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015