January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-52) Add a clean Digest mechanisms implementation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-52?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse resolved ELY-52. --------------------------------- Resolution: Duplicate Issue > Add a clean Digest mechanisms implementation > -------------------------------------------- > > Key: ELY-52 > URL: https://issues.jboss.org/browse/ELY-52 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4047) SLSB with WebService Annotation generates duplicate endpoint when JMS transport used

by Wojciech Oczkowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-4047?page=com.atlassian.jira.plugin.... ] Wojciech Oczkowski commented on WFLY-4047: ------------------------------------------ any chances for help on this? > SLSB with WebService Annotation generates duplicate endpoint when JMS transport used > ------------------------------------------------------------------------------------ > > Key: WFLY-4047 > URL: https://issues.jboss.org/browse/WFLY-4047 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.1.0.Final > Reporter: Wojciech Oczkowski > Assignee: Jason Greene > Attachments: TestWSJMS.zip > > > When deploying Webservice with JMS transport as Stateless Session Bean, 2 endpoint's are published. One is ok JMSDefaultEndpoind and second is HTTPDefaultEndpoint which is treated as JMS endpoind somehow and fails to deploy with exception below. Simple project that reproduces this problem attached (it requires additional Spring libraries for CXF and JMS transport). > 14:03:37,974 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "TestWSJMS-1.0-SNAPSHOT.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_72] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_72] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_72] > Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ? > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371) > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539) > at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67) > at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] > ... 5 more > Caused by: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ? > at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:115) > at org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:119) > at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49) > at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95) > at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:895) > at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131) > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362) > ... 13 more -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4075) Setting "org.jboss.as.jaxrs.enableSpringIntegration" to "true" causes JaxrsSpringProcessor to throw NullPointerException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4075?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4075: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1163646|https://bugzilla.redhat.com/show_bug.cgi?id=1163646] from POST to MODIFIED > Setting "org.jboss.as.jaxrs.enableSpringIntegration" to "true" causes JaxrsSpringProcessor to throw NullPointerException > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4075 > URL: https://issues.jboss.org/browse/WFLY-4075 > Project: WildFly > Issue Type: Bug > Components: REST, VFS > Affects Versions: 9.0.0.Alpha1 > Reporter: Jay Kumar SenSharma > Assignee: Tomas Hofman > Attachments: WFLY-4075_Reproducer_And_Log.zip > > > - When an application containing Spring + Rest Integration is deployed on Wildfly then it causes NullPointerException as following: > {code} > 13:43:19,830 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "RESTfulExample.war" (runtime-name: "RESTfulExample.war") > 13:43:20,313 ERROR [org.wildfly.extension.undertow] (MSC service thread 1-4) Could not find tld /WEB-INF/tld/spring-form.tld > 13:43:20,313 ERROR [org.wildfly.extension.undertow] (MSC service thread 1-4) Could not find tld /WEB-INF/tld/spring.tld > 13:43:20,370 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."RESTfulExample.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."RESTfulExample.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "RESTfulExample.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) [wildfly-server-1.0.0.Alpha8.jar:1.0.0.Alpha8] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:203) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) [wildfly-server-1.0.0.Alpha8.jar:1.0.0.Alpha8] > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:133) > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:199) > ... 6 more > Caused by: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:103) > ... 7 more > 13:43:20,374 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RESTfulExample.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"RESTfulExample.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"RESTfulExample.war\".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"RESTfulExample.war\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3880) Resource Adapters not visible in web console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3880?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3880: ----------------------------------------------- Julian Coleman <jcoleman(a)redhat.com> changed the Status of [bug 1144888|https://bugzilla.redhat.com/show_bug.cgi?id=1144888] from ASSIGNED to MODIFIED > Resource Adapters not visible in web console > --------------------------------------------- > > Key: WFLY-3880 > URL: https://issues.jboss.org/browse/WFLY-3880 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.0.0.Final > Reporter: Van Halbert > Assignee: Heiko Braun > Attachments: Screenshot from 2014-08-26 17_20_50.png > > > In Web Console, in Configuration > Connectors > Resource Adapters, the names of the Resource Adapters (column Archive) are empty. Also, after clicking View> in any of the rows, always the same Connection Definitions are shown (most likely those belonging to the first resource adapter in the list). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-128) Session/MDB Jacc integration

by RH Bugzilla Integration (JIRA)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-121) Support @EJB injection with no parameters

by RH Bugzilla Integration (JIRA)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-493) Automatically index static modules as required

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFCORE-493?page=com.atlassian.jira.plugin... ] Tomasz Adamski reassigned WFCORE-493: ------------------------------------- Assignee: Tomasz Adamski (was: Stuart Douglas) > Automatically index static modules as required > ---------------------------------------------- > > Key: WFCORE-493 > URL: https://issues.jboss.org/browse/WFCORE-493 > Project: WildFly Core > Issue Type: Feature Request > Components: Server > Reporter: Stuart Douglas > Assignee: Tomasz Adamski > > If a static module has an annotation import it should be automatically indexed -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3552) Updated implementation of StrictMaxPool

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3552?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-3552. ---------------------------------- Fix Version/s: 9.0.0.Alpha1 Resolution: Done > Updated implementation of StrictMaxPool > --------------------------------------- > > Key: WFLY-3552 > URL: https://issues.jboss.org/browse/WFLY-3552 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: John O'Hara > Assignee: Jason Greene > Fix For: 9.0.0.Alpha1 > > > To eliminate contention in the EJB StrictMaxPool, can we change the underlying data structure to use ConcurrentLinkedQueue, instead of the LinkedList with synchronization that is in the implementation currently? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3723) setting the local to english in CLI commands on non-english systems does not produce english output

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3723?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3723: ----------------------------------------------- Romain Pelisse <rpelisse(a)redhat.com> changed the Status of [bug 1128132|https://bugzilla.redhat.com/show_bug.cgi?id=1128132] from NEW to POST > setting the local to english in CLI commands on non-english systems does not produce english output > --------------------------------------------------------------------------------------------------- > > Key: WFLY-3723 > URL: https://issues.jboss.org/browse/WFLY-3723 > Project: WildFly > Issue Type: Bug > Components: Localization > Affects Versions: 8.1.0.Final > Environment: Tested on MacOS running in German > Reporter: Tom Fonteyne > Assignee: Romain Pelisse > Priority: Minor > > A German (or french etc...) system must be used to reproduce. > It is likely this is not limited to MacOS, but I do not have a non-english Linux system available > An out of the box install of wildfly/EAP: > Without configuration, the log file is in German as expected. > Using these CLI comands: > :read-operation-description(name=stop-servers,locale=de_DE) -> german > :read-operation-description(name=stop-servers,locale=en_US) -> german > :read-operation-description(name=stop-servers,locale=fr_FR) -> french > So we cannot get the CLI to produce english output > when configuring JAVA_OPTS in domain.conf with: > JAVA_OPTS="$JAVA_OPTS -Duser.language=en -Duser.country=DE -Duser.encoding=utf-8 > The log is now in English -> works as expected; and: > :read-operation-description(name=stop-servers,locale=de_DE) -> german > :read-operation-description(name=stop-servers,locale=en_US) -> english > So it seems we have a bug where the locale set to start the domain takes precedence over the locale set in the CLI command (but only when English is asked) > I presume this is because English is the default locale. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4075) Setting "org.jboss.as.jaxrs.enableSpringIntegration" to "true" causes JaxrsSpringProcessor to throw NullPointerException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4075?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4075: ----------------------------------------------- Tomas Hofman <thofman(a)redhat.com> changed the Status of [bug 1163646|https://bugzilla.redhat.com/show_bug.cgi?id=1163646] from NEW to POST > Setting "org.jboss.as.jaxrs.enableSpringIntegration" to "true" causes JaxrsSpringProcessor to throw NullPointerException > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4075 > URL: https://issues.jboss.org/browse/WFLY-4075 > Project: WildFly > Issue Type: Bug > Components: REST, VFS > Affects Versions: 9.0.0.Alpha1 > Reporter: Jay Kumar SenSharma > Assignee: Tomas Hofman > Attachments: WFLY-4075_Reproducer_And_Log.zip > > > - When an application containing Spring + Rest Integration is deployed on Wildfly then it causes NullPointerException as following: > {code} > 13:43:19,830 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "RESTfulExample.war" (runtime-name: "RESTfulExample.war") > 13:43:20,313 ERROR [org.wildfly.extension.undertow] (MSC service thread 1-4) Could not find tld /WEB-INF/tld/spring-form.tld > 13:43:20,313 ERROR [org.wildfly.extension.undertow] (MSC service thread 1-4) Could not find tld /WEB-INF/tld/spring.tld > 13:43:20,370 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."RESTfulExample.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."RESTfulExample.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "RESTfulExample.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) [wildfly-server-1.0.0.Alpha8.jar:1.0.0.Alpha8] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:203) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) [wildfly-server-1.0.0.Alpha8.jar:1.0.0.Alpha8] > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:133) > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:199) > ... 6 more > Caused by: java.lang.NullPointerException > at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.getResteasySpringVirtualFile(JaxrsSpringProcessor.java:103) > ... 7 more > 13:43:20,374 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RESTfulExample.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"RESTfulExample.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"RESTfulExample.war\".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"RESTfulExample.war\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.NullPointerException > Caused by: java.lang.NullPointerException"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 2015