August 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1973) Errors on server :reload

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-1973?page=com.atlassian.jira.plugin.... ] Frank Langelage updated WFLY-1973: ---------------------------------- Attachment: server.log > Errors on server :reload > ------------------------ > > Key: WFLY-1973 > URL: https://issues.jboss.org/browse/WFLY-1973 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Beta1 > Reporter: Frank Langelage > Assignee: Jeff Mesnil > Attachments: server.log > > > Having WildFly 8.0.0.Beta1 build from current sources. > After server is online without deployments I executed > $JBOSS_HOME/bin/jboss-cli.sh --connect --command=":reload" > This shows > 22:27:45,605 ERROR [org.jboss.msc.service.fail#startFailed] MSC000001: Failed to start service jboss.messaging.default.jms.pooled-connection-factory.hornetq-ra: org.jboss.msc.service.StartException in service jboss.messaging.default.jms.pooled-connection-factory.hornetq-ra: JBAS011639: Failed to create resource adapter at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:309) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.as.messaging.BinderServiceUtil.installAliasBinderService(BinderServiceUtil.java:72) > at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createJNDIAliases(PooledConnectionFactoryService.java:437) > at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:423) > at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:306) > ... 5 more > See attached server.log. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1973) Errors on server :reload

by Frank Langelage (JIRA)

Frank Langelage created WFLY-1973: ------------------------------------- Summary: Errors on server :reload Key: WFLY-1973 URL: https://issues.jboss.org/browse/WFLY-1973 Project: WildFly Issue Type: Feature Request Components: JMS Affects Versions: 8.0.0.Beta1 Reporter: Frank Langelage Assignee: Jeff Mesnil Having WildFly 8.0.0.Beta1 build from current sources. After server is online without deployments I executed $JBOSS_HOME/bin/jboss-cli.sh --connect --command=":reload" This shows 22:27:45,605 ERROR [org.jboss.msc.service.fail#startFailed] MSC000001: Failed to start service jboss.messaging.default.jms.pooled-connection-factory.hornetq-ra: org.jboss.msc.service.StartException in service jboss.messaging.default.jms.pooled-connection-factory.hornetq-ra: JBAS011639: Failed to create resource adapter at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:309) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:767) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] at org.jboss.as.messaging.BinderServiceUtil.installAliasBinderService(BinderServiceUtil.java:72) at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createJNDIAliases(PooledConnectionFactoryService.java:437) at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:423) at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:306) ... 5 more See attached server.log. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro closed JBXB-194. --------------------------------- Resolution: Won't Fix > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:31 PM: ---------------------------------------------------------------- Learnt that these nodes are actually meant to be there, the issue can be closed. was (Author: fribeiro1): Realized these nodes are actually meant to be there, the issue can be closed. > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:20 PM: ---------------------------------------------------------------- <xs:complexType name="detail"> <xs:sequence> <xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax" /> </xs:complexType> was (Author: fribeiro1): I've confirmed today that the element in question isn't mixed: <xs:complexType name="detail"> <xs:sequence> <xs:any namespace="##any" minOccurs="0" maxOccurs="unbounded" processContents="lax" /> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="lax" /> </xs:complexType> I'll run a new test until tomorrow to try to learn some more. > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:20 PM: ---------------------------------------------------------------- Looking into the schema of SOAP faults to find if these whitespace-only nodes are actually meant to be there. was (Author: fribeiro1): Added a link to the JavaDoc of the Detail class. > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:17 PM: ---------------------------------------------------------------- Clarified in the description that the issue is with whitespace-only nodes. was (Author: fribeiro1): Clarified in the description that it is whitespace nodes. > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:16 PM: ---------------------------------------------------------------- I wouldn't really know at this point, but will investigate. was (Author: fribeiro1): I wouldn't really know at this point, but will look more closely into JBossXB running it outside JBoss Portal to find out. I was told that the setIgnoringElementContentWhitespace method in the javax.xml.parsers.DocumentBuilderFactory class seems to strip the nodes in question, how do these methods compare to it? > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:15 PM: ---------------------------------------------------------------- Realized these nodes are actually meant to be there, the issue can be closed. was (Author: fribeiro1): Found that these whitespaces nodes are actually meant to be there, as documented at http://fernandoribeiro.eti.br/2009/04/24/whitespaces-in-soap-fault-details/, most certainly not an issue with JBossXB at all. You can close the issue. Thanks. > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBXB-194) Support for Ignoring Whitespace-Only Nodes

by Fernando Ribeiro (JIRA)

[ https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s... ] Fernando Ribeiro reopened JBXB-194: ----------------------------------- > Support for Ignoring Whitespace-Only Nodes > ------------------------------------------ > > Key: JBXB-194 > URL: https://issues.jboss.org/browse/JBXB-194 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Affects Versions: JBossXB-1.0.0.SP3 > Reporter: Fernando Ribeiro > > While acessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the whitespace-only nodes described at http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored. > http://java.sun.com/javase/6/docs/api/javax/xml/soap/Detail.html -- 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, 10 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 August 2013