[JBoss JIRA] (WFLY-674) NPE in thread "vfs-shutdown"
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-674?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on WFLY-674:
----------------------------------
Fix merged to vfs. we need new release of vfs to be used in WF
> NPE in thread "vfs-shutdown"
> -----------------------------
>
> Key: WFLY-674
> URL: https://issues.jboss.org/browse/WFLY-674
> Project: WildFly
> Issue Type: Bug
> Components: VFS
> Environment: 7.1.0.Alpha1 Jenkins build 1402
> Reporter: Juergen Zimmermann
> Assignee: David Lloyd
> Fix For: 8.0.0.Beta1
>
>
> When I shutdown a standalone server I'm getting a NPE. The shutdown command is:
> jboss-admin.bat --connect command=:shutdown
> Console log:
> ...
> 18:24:55,990 INFO [org.jboss.as.logging] Restored bootstrap log handlers
> 18:24:55,990 INFO [org.jboss.as.jmx.JMXConnectorService] JMX remote connector stopped
> 18:24:56,075 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-as-osgi-configadmin:7.1.0.Alpha1-SNAPSHOT
> 18:24:56,125 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.log:1.0.0
> 18:24:56,230 INFO [org.apache.catalina.core.StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> 18:24:56,286 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.configadmin:1.2.8
> 18:24:56,323 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-osgi-logging:1.0.0
> 18:24:56,330 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
> 18:24:56,331 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
> 18:24:56,368 ERROR [stderr] Exception in thread "vfs-shutdown" java.lang.NullPointerException
> 18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider$DeleteTask.run(TempFileProvider.java:151)
> 18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider.close(TempFileProvider.java:132)
> 18:24:56,368 ERROR [stderr] at org.jboss.osgi.vfs30.VirtualFileAdaptor30$2.run(VirtualFileAdaptor30.java:94)
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-674) NPE in thread "vfs-shutdown"
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-674?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar updated WFLY-674:
-----------------------------
Fix Version/s: 8.0.0.Beta1
(was: Awaiting Volunteers)
> NPE in thread "vfs-shutdown"
> -----------------------------
>
> Key: WFLY-674
> URL: https://issues.jboss.org/browse/WFLY-674
> Project: WildFly
> Issue Type: Bug
> Components: VFS
> Environment: 7.1.0.Alpha1 Jenkins build 1402
> Reporter: Juergen Zimmermann
> Assignee: David Lloyd
> Fix For: 8.0.0.Beta1
>
>
> When I shutdown a standalone server I'm getting a NPE. The shutdown command is:
> jboss-admin.bat --connect command=:shutdown
> Console log:
> ...
> 18:24:55,990 INFO [org.jboss.as.logging] Restored bootstrap log handlers
> 18:24:55,990 INFO [org.jboss.as.jmx.JMXConnectorService] JMX remote connector stopped
> 18:24:56,075 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-as-osgi-configadmin:7.1.0.Alpha1-SNAPSHOT
> 18:24:56,125 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.log:1.0.0
> 18:24:56,230 INFO [org.apache.catalina.core.StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
> 18:24:56,286 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.configadmin:1.2.8
> 18:24:56,323 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-osgi-logging:1.0.0
> 18:24:56,330 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService
> 18:24:56,331 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager
> 18:24:56,368 ERROR [stderr] Exception in thread "vfs-shutdown" java.lang.NullPointerException
> 18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider$DeleteTask.run(TempFileProvider.java:151)
> 18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider.close(TempFileProvider.java:132)
> 18:24:56,368 ERROR [stderr] at org.jboss.osgi.vfs30.VirtualFileAdaptor30$2.run(VirtualFileAdaptor30.java:94)
--
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
10 years, 8 months
[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:
----------------------------------
Issue Type: Bug (was: Feature Request)
> Errors on server :reload
> ------------------------
>
> Key: WFLY-1973
> URL: https://issues.jboss.org/browse/WFLY-1973
> Project: WildFly
> Issue Type: Bug
> 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
10 years, 8 months
[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
10 years, 8 months
[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
10 years, 8 months
[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
10 years, 8 months