[JBoss JIRA] (AS7-3404) Assertion error in :reload command
by Stuart Douglas (JIRA)
Stuart Douglas created AS7-3404:
-----------------------------------
Summary: Assertion error in :reload command
Key: AS7-3404
URL: https://issues.jboss.org/browse/AS7-3404
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: Stuart Douglas
Assignee: Brian Stansberry
20:25:39,378 INFO [org.jboss.as] JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" starting
20:25:39,388 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.as.server-controller: org.jboss.msc.service.StartException in service jboss.as.server-controller: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_29]
Caused by: java.lang.AssertionError: profileResourceRegistration is already set
at org.jboss.as.controller.extension.ExtensionRegistry.setProfileResourceRegistration(ExtensionRegistry.java:124) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.ServerControllerModelUtil.initOperations(ServerControllerModelUtil.java:352) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.ServerService.initModel(ServerService.java:296) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractControllerService.start(AbstractControllerService.java:147) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.ServerService.start(ServerService.java:185) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
... 3 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3450) OSGi-WAR fails to deploy
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-3450?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler resolved AS7-3450.
---------------------------------
Labels: jboss-as7 osgi (was: jboss-as7 osgi webapp)
Resolution: Duplicate Issue
Duplicates AS7-2434
> OSGi-WAR fails to deploy
> ------------------------
>
> Key: AS7-3450
> URL: https://issues.jboss.org/browse/AS7-3450
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Rico Neubauer
> Assignee: Thomas Diesler
> Labels: jboss-as7, osgi
> Attachments: OSGiWebApp-0.0.1-SNAPSHOT.war, server.log
>
>
> Trying to deploy a very simple WAR, containing one Servlet as OSGi-bundle on jboss-as-7.1.0.Beta1 fails with error on ClassLoading the servlet.
> osgi-subsystem activation is set to "eager", startlevel to "3".
> Will attach full log and test-WAR, here is an extract from the stacktrace:
> ERROR [org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC] (MSC service thread 1-12) Registration exception. Skipping.: java.lang.ClassNotFoundException: jboss.osgi.webapp.test.JNDIViewServlet from [Module "deployment.jboss.osgi.webapp.test.OSGiWebApp:0.0.1.SNAPSHOT" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:485) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:421) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:155) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:114) [jbosgi-framework-core-1.1.0.jar:]
> at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:415) [jbosgi-framework-core-1.1.0.jar:]
> at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:151) [jbosgi-framework-core-1.1.0.jar:]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3450) OSGi-WAR fails to deploy
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-3450?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler moved JBOSGI-505 to AS7-3450:
--------------------------------------------
Project: Application Server 7 (was: JBoss OSGi)
Key: AS7-3450 (was: JBOSGI-505)
Workflow: GIT Pull Request workflow (was: jira)
Component/s: OSGi
(was: Core Framework)
Security: (was: Public)
Fix Version/s: (was: JBossOSGi 1.0.1)
> OSGi-WAR fails to deploy
> ------------------------
>
> Key: AS7-3450
> URL: https://issues.jboss.org/browse/AS7-3450
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Reporter: Rico Neubauer
> Assignee: Thomas Diesler
> Labels: jboss-as7, osgi, webapp
> Attachments: OSGiWebApp-0.0.1-SNAPSHOT.war, server.log
>
>
> Trying to deploy a very simple WAR, containing one Servlet as OSGi-bundle on jboss-as-7.1.0.Beta1 fails with error on ClassLoading the servlet.
> osgi-subsystem activation is set to "eager", startlevel to "3".
> Will attach full log and test-WAR, here is an extract from the stacktrace:
> ERROR [org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC] (MSC service thread 1-12) Registration exception. Skipping.: java.lang.ClassNotFoundException: jboss.osgi.webapp.test.JNDIViewServlet from [Module "deployment.jboss.osgi.webapp.test.OSGiWebApp:0.0.1.SNAPSHOT" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:485) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:421) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:155) [jboss-modules.jar:1.1.0.CR4]
> at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:114) [jbosgi-framework-core-1.1.0.jar:]
> at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:415) [jbosgi-framework-core-1.1.0.jar:]
> at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:151) [jbosgi-framework-core-1.1.0.jar:]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3449) IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3449?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek moved JBPAPP-7996 to AS7-3449:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-3449 (was: JBPAPP-7996)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.0.CR1b
(was: EAP 6.0.0 DR 5)
Component/s: (was: IPv6 support)
Security: (was: JBoss Internal)
Fix Version/s: (was: EAP 6.0.0 ER 1)
Docs QE Status: (was: NEW)
> IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
> -----------------------------------------------------------------------------
>
> Key: AS7-3449
> URL: https://issues.jboss.org/browse/AS7-3449
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.CR1b
> Environment: Linux
> Reporter: Pavel Janousek
> Priority: Blocker
>
> I unpacked DR5 build ZIP only, didn't touch configuration and try to run as usual:
> {code}
> cd <bin dir of EAP>
> ./standalone.sh
> {code}
> Got this result:
> {code}
> [root@fedora15-vrt1 bin]# ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/pjanouse/tmp/jboss-eap-6.0.0.Alpha2
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:55:46,040 INFO [org.jboss.modules] JBoss Modules version 1.0.3.GA
> 16:55:47,253 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
> 16:55:47,362 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) starting
> 16:55:48,163 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) stopped in 3ms
> 16:55:48,156 ERROR [org.jboss.as.controller.AbstractControllerService] Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:139) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:168) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:197) [jboss-as-server-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:133) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 1 more
> Caused by: java.lang.RuntimeException: Unable to determine a default name based on the local host name
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:188) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:263) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:82) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 4 more
> Caused by: java.net.UnknownHostException: fedora15-vrt1: fedora15-vrt1
> at java.net.InetAddress.getLocalHost(InetAddress.java:1426) [:1.6.0_22]
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:186) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 10 more
> [root@fedora15-vrt1 bin]#
> {code}
> The root of this issue is that *fedora15-vrt1* can't be translated to IPv4 IP address, but only to IPv6 address:
> {code}
> [root@fedora15-vrt1 bin]# ping fedora15-vrt1
> ping: unknown host fedora15-vrt1
> [root@fedora15-vrt1 bin]# ping6 fedora15-vrt1
> PING fedora15-vrt1(vrt1-ip6) 56 data bytes
> 64 bytes from vrt1-ip6: icmp_seq=1 ttl=64 time=0.067 ms
> 64 bytes from vrt1-ip6: icmp_seq=2 ttl=64 time=0.105 ms
> ^C
> --- fedora15-vrt1 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.067/0.086/0.105/0.019 ms
> [root@fedora15-vrt1 bin]#
> {code}
> because I really config /etc/hosts like:
> {code}
> [root@fedora15-vrt1 bin]# cat /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> ::1 localhost6.localdomain6 localhost6
> 10.0.2.15 both
> ::ffff:10.0.2.15 both
> 1:0:0:1::10 vrt1-ip6 fedora15-vrt1
> 1:0:0:1::11 vrt2-ip6
> [root@fedora15-vrt1 bin]#
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3233) socket-binding-group element fails to parse
by dan ginsberg (Created) (JIRA)
socket-binding-group element fails to parse
-------------------------------------------
Key: AS7-3233
URL: https://issues.jboss.org/browse/AS7-3233
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.CR1b
Reporter: dan ginsberg
Assignee: Brian Stansberry
1. Take a domain config that works correctly in 7.1.0-Beta1b and which has a host configuration that includes server elements with port-binding-group such as this:
<!-- server-three avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-binding-group ref="ha-sockets" port-offset="250"/>
2. try to run that config under 7.1.CR1b
expect: servers to start cleanly
find: server fails to parse the port-binding-group
[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[67,13]
[Host Controller] Message: JBAS014789: Unexpected element '{urn:jboss:domain:1.1}socket-binding-group' encountered
[Host Controller] at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseServerContent1_1(HostXml.java:944) [jboss-as-host-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseServer(HostXml.java:845) [jboss-as-host-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.parseServers(HostXml.java:822) [jboss-as-host-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readHostElement_1_1(HostXml.java:389) [jboss-as-host-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:117) [jboss-as-host-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:97) [jboss-as-host-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final.jar:1.0.0.Final]
[Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final.jar:1.0.0.Final]
[Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) [jboss-as-controller-7.1.0.CR1b.jar:7.1.0.CR1b]
[Host Controller] ... 4 more
[Host Controller]
[Host Controller] 15:08:44,587 INFO [org.jboss.as] (MSC service thread 1-8) JBoss AS 7.1.0.CR1b "Flux Capacitor" stopped in 10ms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months