June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1534) HAL Console Release 1.5.4

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-1534?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-1534: ------------------------------ Summary: HAL Console Release 1.5.4 (was: HAL 1.0 Milestone 1) > HAL Console Release 1.5.4 > ------------------------- > > Key: WFLY-1534 > URL: https://issues.jboss.org/browse/WFLY-1534 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1534) HAL Console Release 1.5.4

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1534?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1534: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=979355 > HAL Console Release 1.5.4 > ------------------------- > > Key: WFLY-1534 > URL: https://issues.jboss.org/browse/WFLY-1534 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1602) Integrate the picket linke console extension with HAL

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-1602?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-1602: ------------------------------ Parent: WFLY-1474 Issue Type: Sub-task (was: Feature Request) > Integrate the picket linke console extension with HAL > ----------------------------------------------------- > > Key: WFLY-1602 > URL: https://issues.jboss.org/browse/WFLY-1602 > Project: WildFly > Issue Type: Sub-task > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1589) requiredSecret attribute on the AJP connector

by Gilles Bardouillet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1589?page=com.atlassian.jira.plugin.... ] Gilles Bardouillet updated WFLY-1589: ------------------------------------- Attachment: requiredsecret.diff Updating previous patch > requiredSecret attribute on the AJP connector > --------------------------------------------- > > Key: WFLY-1589 > URL: https://issues.jboss.org/browse/WFLY-1589 > Project: WildFly > Issue Type: Feature Request > Components: Web (JBoss Web) > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > Priority: Minor > Attachments: requiredsecret.diff, requiredsecret.diff > > > In JBoss 5 I could set the requiredSecret attribute of the AJP connector. This is no longer possible in JBoss AS 7 and WildFly > This request is to get it implemented similarly to WFLY-254 for tomcatAuthentication -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1602) Integrate the picket linke console extension with HAL

by Heiko Braun (JIRA)

Heiko Braun created WFLY-1602: --------------------------------- Summary: Integrate the picket linke console extension with HAL Key: WFLY-1602 URL: https://issues.jboss.org/browse/WFLY-1602 Project: WildFly Issue Type: Feature Request Components: Web Console Reporter: Heiko Braun Assignee: Harald Pehl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1586) OpenJDK: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-1586?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda commented on WFLY-1586: ----------------------------------------- Checked new bits on F17 64b and WS tests from WF TS are fine now. # java -version java version "1.7.0_25" OpenJDK Runtime Environment (fedora-2.3.10.5.fc17-x86_64) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) f17 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549923 f18 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549917 f19 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549919 f20 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549925 > OpenJDK: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-1586 > URL: https://issues.jboss.org/browse/WFLY-1586 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.0.0.Alpha2 > Environment: java version "1.7.0_25" > OpenJDK Runtime Environment (fedora-2.3.10.3.fc17-x86_64) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc17.x86_64 > Reporter: Carlo de Wolf > Assignee: Rostislav Svoboda > Priority: Blocker > Attachments: org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.txt > > > With the latest update of OpenJDK to 1.7.0.25-2.3.10.3 there is regression w.r.t. WebServices. > Failing tests: > {noformat} > org.jboss.as.test.integration.ws.ejb.ContextHandlerEndpointTestCase > org.jboss.as.test.integration.ws.injection.ejb.basic.EjbEndpointInsideWarTestCase > org.jboss.as.test.integration.ws.injection.ejb.basic.InjectionTestCase > org.jboss.as.test.integration.ws.wsa.TestNoAddressingTestCase > org.jboss.as.test.integration.ws.wsa.TestOptionalAddressingTestCase > org.jboss.as.test.integration.ws.wsa.TestRequiredAddressingTestCase > org.jboss.as.test.integration.ws.wsse.sign.EJBSignTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptMultipleClientsTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.SignEncryptMultipleClientsTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.SignEncryptTestCase > org.jboss.as.test.integration.ws.wsse.sign.SignTestCase > org.jboss.as.test.xts.simple.wsat.client.WSATTestCase > org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase > org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1586) OpenJDK: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-1586?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda edited comment on WFLY-1586 at 6/28/13 4:10 AM: ------------------------------------------------------------------ Checked new bits on F17 64b and WS tests from WF TS are fine now. java version "1.7.0_25" OpenJDK Runtime Environment (fedora-2.3.10.5.fc17-x86_64) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) f17 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549923 f18 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549917 f19 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549919 f20 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549925 was (Author: rsvoboda): Checked new bits on F17 64b and WS tests from WF TS are fine now. # java -version java version "1.7.0_25" OpenJDK Runtime Environment (fedora-2.3.10.5.fc17-x86_64) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) f17 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549923 f18 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549917 f19 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549919 f20 http://koji.fedoraproject.org/koji/taskinfo?taskID=5549925 > OpenJDK: java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-1586 > URL: https://issues.jboss.org/browse/WFLY-1586 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.0.0.Alpha2 > Environment: java version "1.7.0_25" > OpenJDK Runtime Environment (fedora-2.3.10.3.fc17-x86_64) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc17.x86_64 > Reporter: Carlo de Wolf > Assignee: Rostislav Svoboda > Priority: Blocker > Attachments: org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.txt > > > With the latest update of OpenJDK to 1.7.0.25-2.3.10.3 there is regression w.r.t. WebServices. > Failing tests: > {noformat} > org.jboss.as.test.integration.ws.ejb.ContextHandlerEndpointTestCase > org.jboss.as.test.integration.ws.injection.ejb.basic.EjbEndpointInsideWarTestCase > org.jboss.as.test.integration.ws.injection.ejb.basic.InjectionTestCase > org.jboss.as.test.integration.ws.wsa.TestNoAddressingTestCase > org.jboss.as.test.integration.ws.wsa.TestOptionalAddressingTestCase > org.jboss.as.test.integration.ws.wsa.TestRequiredAddressingTestCase > org.jboss.as.test.integration.ws.wsse.sign.EJBSignTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptMultipleClientsTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.SignEncryptMultipleClientsTestCase > org.jboss.as.test.integration.ws.wsse.signencrypt.SignEncryptTestCase > org.jboss.as.test.integration.ws.wsse.sign.SignTestCase > org.jboss.as.test.xts.simple.wsat.client.WSATTestCase > org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase > org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1589) requiredSecret attribute on the AJP connector

by Gilles Bardouillet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1589?page=com.atlassian.jira.plugin.... ] Gilles Bardouillet updated WFLY-1589: ------------------------------------- Attachment: requiredsecret.diff Here is a patch. This patch's using a system properties : org.apache.coyote.ajp.DEFAULT_SECRET > requiredSecret attribute on the AJP connector > --------------------------------------------- > > Key: WFLY-1589 > URL: https://issues.jboss.org/browse/WFLY-1589 > Project: WildFly > Issue Type: Feature Request > Components: Web (JBoss Web) > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > Priority: Minor > Attachments: requiredsecret.diff > > > In JBoss 5 I could set the requiredSecret attribute of the AJP connector. This is no longer possible in JBoss AS 7 and WildFly > This request is to get it implemented similarly to WFLY-254 for tomcatAuthentication -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-924) Reduce the log level of optional components failing to start log message (JBAS011006 message id)

by Osamu Nagano (JIRA)

[ https://issues.jboss.org/browse/WFLY-924?page=com.atlassian.jira.plugin.s... ] Osamu Nagano commented on WFLY-924: ----------------------------------- Thank you. It will really save our time;) > Reduce the log level of optional components failing to start log message (JBAS011006 message id) > ------------------------------------------------------------------------------------------------ > > Key: WFLY-924 > URL: https://issues.jboss.org/browse/WFLY-924 > Project: WildFly > Issue Type: Enhancement > Components: EE > Affects Versions: 8.0.0.Alpha2 > Environment: JBoss EAP 6.0 GA, web services subsystem removed, war deployed containing Metro or CXF web services implementation > Reporter: Brad Maxwell > Assignee: jaikiran pai > > It tries to create this class if CXF is packaged in the war: org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > And this stack is logged as a warning: > 11:08:40,879 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.test.war:main" from Service Module Loader > 11:08:40,905 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > If Metro is packaged in the war, it tries to load com.sun.xml.ws.transport.http.servlet.WSAsyncListener and logs a warning with this stack: > 16:48:57,302 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-924) Reduce the log level of optional components failing to start log message (JBAS011006 message id)

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-924?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on WFLY-924: ----------------------------------- Osamu, I discussed this with Stuart and he was of the same opinion as you. i.e. we log a summarized WARN message and log the entire exception stacktrace at DEBUG instead of logging that whole thing at DEBUG. So I've sent a pull request https://github.com/wildfly/wildfly/pull/4714 which takes care of this. > Reduce the log level of optional components failing to start log message (JBAS011006 message id) > ------------------------------------------------------------------------------------------------ > > Key: WFLY-924 > URL: https://issues.jboss.org/browse/WFLY-924 > Project: WildFly > Issue Type: Enhancement > Components: EE > Affects Versions: 8.0.0.Alpha2 > Environment: JBoss EAP 6.0 GA, web services subsystem removed, war deployed containing Metro or CXF web services implementation > Reporter: Brad Maxwell > Assignee: jaikiran pai > > It tries to create this class if CXF is packaged in the war: org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > And this stack is logged as a warning: > 11:08:40,879 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.test.war:main" from Service Module Loader > 11:08:40,905 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > If Metro is packaged in the war, it tries to load com.sun.xml.ws.transport.http.servlet.WSAsyncListener and logs a warning with this stack: > 16:48:57,302 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 June 2013