Grails 1.3.7不是以JBoss 7.1开头的 [英] Grails 1.3.7 not starting with JBoss 7.1
本文介绍了Grails 1.3.7不是以JBoss 7.1开头的的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我的公司试图从 JBoss > 4.2.3升级到 JBoss 7.目前我已经安装了本地拷贝 JBoss 7.1，并且试图让我的grails项目在 JBoss上运行 7.1
确切的同样的战争在 JBoss 4.2.3中工作得很好。奇怪的是，没有任何错误。这是来自初创公司的信息：
调用C：\JBoss\jboss-as-7.1.0\ bin\standalone.conf.bat
===================================== ==========================================
JBoss Bootstrap环境
JBOSS_HOME：C：\ JBoss \ jboss-as-7.1.0
JAVA：C：\Java\jdk7\bin\ java
JAVA_OPTS：-XX：+ TieredCompilation -Dprogram.name = standalone.bat -Xms64M -Xmx512M -XX：MaxPermSize = 256M -Dsun.rmi.dgc.cl
ient.gcInterval = 3600000 -Dsun.rmi.dgc.server.gcInterval = 3600000 -Djava.net.preferIPv4Stack = true -Dorg.jboss.resolver.war
ning = true -Djboss.modules.system.pkgs = org.jboss.byteman
========================================== =====================================
15：02：53,200 INFO [org.jboss.modules] JBoss模块版本1.1.0.GA
15：02：53,414 INFO [org.jboss.msc] JBoss MSC版本1.0.2.GA
15：02：53,457 INFO [org.jboss.as] JBAS015899：J Boss AS 7.1.0.Final-SNAPSHOTFlux Capacitor起始
15：02：54,062信息[org.xnio] XNIO版本3.0.0.GA
15：02：54,062信息[org.jboss .as.server] JBAS015888：使用套接字绑定（management-h
ttp）
15：02：54,075创建http管理服务INFO [org.xnio.nio] XNIO NIO实施版本3.0.0。 GA
15：02：54,082信息[org.jboss.remoting] JBoss Remoting版本3.2.0.GA
15：02：54,110信息[org.jboss.as.security] JBAS013101：激活安全子系统
15：02：54,112 INFO [org.jboss.as.clustering.infinispan] JBAS010280：激活Infinispan子系统。
15：02：54,128 INFO [org.jboss.as.logging] JBAS011502：删除引导日志处理程序
15：02：54,133 INFO [org.jboss.as.naming] JBAS011800：激活命名子系统
15：02：54,139 INFO [org.jboss.as.security]（MSC服务线程1-2）JBAS013100：当前PicketBox版本= 4.0.6.final
15：02：54,139 INFO [org。 jboss.as.webservices]（ServerService线程池 - 50）JBAS015537：激活WebServices扩展
sion
15：02：54,145信息[org.jboss.as.configadmin]（ServerService线程池 - 27 ）JBAS016200：激活ConfigAdmin Subsy
主干
15：02：54,156 INFO [服务器服务线程池 - 41] JBAS011940：激活OSGi子系统
15:02 ：54,164 INFO [org.jboss.as.connector]（MSC服务线程1-9）JBAS010408：启动JCA子系统（JBoss IronJacam
ar 1.0.7.Final）
15：02：54,199 INFO [ org.jboss.as.naming]（MSC服务线程1-8）JBAS011802：启动命名服务
15：02：54,201 INFO [org.jboss.as.jaxr]（MSC服务t hread 1-2）绑定JAXR ConnectionFactory：java：jboss / jaxr / Connecti
onFactory
15：02：54,221信息[org.jboss.as.connector.subsystems.datasources]（ServerService线程池 - 28）JBAS010403：部署
ng符合JDBC的驱动程序类org.h2.Driver（版本1.3）
15：02：54,231信息[org.jboss.as.mail.extension]（MSC服务线程1 -16）JBAS015400：绑定邮件会话[java：jboss / ma
il /默认]
15：02：54,254信息[org.jboss.as.connector.subsystems.datasources]（ServerService线程池 - - 28）JBAS010404：部署$ b $ ng不符合JDBC规范的驱动程序类com.mysql.jdbc.Driver（版本5.1）
15：02：55,312 INFO [org.jboss.ws.common.management。 [MSC服务线程1-5] JBoss Web Services - S
CXF服务器4.0.1.GA
15：02：55,416信息[org.jboss.as.remoting]（MSC服务线程1-4）JBAS017100：收听/127.0.0.1:4447
15：02：55,434信息[org.apache.coyote.http11.Http11AprProtocol]（MSC服务线程1-15）启动Coyote H TTP / 1.1 ht
tp - 127.0.0.1-8080
15：02：55,515信息[org.jboss.as.connector.subsystems.datasources]（MSC服务线程1-7）JBAS010400：绑定的数据源
e [java：jboss / datasources / ExampleDS]
15：02：55,521信息[org.jboss.as.connector.subsystems.datasources]（MSC服务线程1-14）JBAS010400：绑定数据源
ce [java：jboss / datasources / MySqlDS]
15：02：55,575 INFO [org.jboss.as.remoting]（MSC服务线程1-4）JBAS017100：在/127.0上收听。 0.1：9999
15：02：55,584信息[org.jboss.as.server.deployment.scanner]（MSC服务线程1-15）JBAS015012：已启动FileSystemDepl
目录C的oymentService：\ JBoss \jboss-as-7.1.0\\standalone\deployments
15：02：55,695 INFO [org.jboss.as.server.deployment]（MSC服务线程1-5）JBAS015876：开始部署 ServerC
onfig.war
15：02：56,941信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-9）JBossOSGi Framework Core -
1.1。 1
15 ：02：56,975错误[org.jboss.as]（MSC服务线程1-12）JBAS015875：JBoss AS 7.1.0.Final-SNAPSHOTFlux Capacitors
在4090ms内触发（带有错误） - 已启动170 （服务失败或缺失依赖项，72项服务为
被动或按需服务）
15：02：57,047信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-10）安装bundle：system.bu
ndle：0.0.0
15：02：57,269信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-10 ）安装bundle：javax.api
：0.0.0
15：02：57,270信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-5）安装bundle：javax .tran
saction.api：0.0.0
15：02：57,270信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-12）安装bundle：jbosgi-re
pository-api：1.0.4
15：02：57,330信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-2）安装包：jboss-as-o
sgi-configadmin：7 .1.0.Final-SNAPSHOT
15：02：57,348信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-3）安装包：jboss-osgi
-logging： 1.0.0
15：02：57,378信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-8）安装bundle：org.apache
.felix.log：1.0 .0
15：02：57,379信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-1）安装bundle：org.apache
.felix.configadmin：1.2。 8
15：02：57,378信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-11）安装包：jbosgi-ht
tp-api：1.0.5
15：02：57,535信息[org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1-6）安装包：osgi.enter
奖励：4.2.0.201003190513
15 ：02：57,931信息[org.jboss.osgi.framework.internal.StartLevelPlugin]（MSC服务线程1-2）启动st
的捆绑包art level：1
15：02：57,936 INFO [org .jboss.osgi.framework.internal.HostBundleState]（MSC servi ce线程1-2）开始捆绑：osgi.ent
erprise：4.2.0.201003190513
15：02：57,941 INFO [org.jboss.osgi.framework.internal.HostBundleState]（MSC service thread 1- 2）开始包：javax.ap
i：0.0.0
15：02：57,952信息[org.jboss.osgi.framework.internal.HostBundleState]（MSC服务线程1-2）Bundle开始： jboss-os
gi-logging：1.0.0
15：02：57,959 INFO [org.jboss.osgi.framework.internal.HostBundleState]（MSC服务线程1-2）Bundle开始：javax。 tr
ansaction.api：0.0.0
15：02：57,964信息[org.jboss.osgi.framework.internal.HostBundleState]（MSC服务线程1-2）Bundle开始：jbosgi-h
ttp-api：1.0.5
15：02：57,967信息[org.jboss.osgi.framework.internal.HostBundleState]（MSC服务线程1-2）开始的包：jbosgi-r
epository-api：1.0.4
15：02：57,984信息[org.jboss.osgi.framework.internal.HostBundleState]（MSC服务线程1-2）Bundle开始：org.apac
he .felix.configadmin：1.2.8
15：02：58,001 INFO [org.jboss.o sgi.framework.internal.HostBundleState]（MSC service thread 1-2）Bundle started：org.apac
he.felix.log：1.0.0
15：02：58,007 INFO [org.jboss。 osgi.framework.internal.HostBundleState]（MSC服务线程1-2）Bundle开始：jboss-as
-osgi-configadmin：7.1.0.Final -SNAPSHOT
15：02：58,013 INFO [org .jboss.osgi.framework.internal.FrameworkActive]（MSC服务线程1-2）OSGi Framework启动
15：02：58,030 INFO [org.jboss.osgi.framework.internal.BundleManager]（MSC服务线程1 -12）安装bundle：ServerCon
fig：0.1.0
15：02：58,071 INFO [org.jboss.as.server]（DeploymentScanner-threads - 2）JBAS018559：部署的ServerConfig.war
15：02：58,568 INFO [org.jboss.osgi.framework.internal.HostBundleState]（MSC service thread 1-14）Bundle started：ServerConfig：0.1.0
================================ ===============================================
我也检查了 JBoss 7 server.log并且没有错误被显示。任何人都可以帮助我解决这个问题吗？
解决方案
Jboss 7试图将应用程序视为OSGI项目而不是普通Web应用。
关键是要么从grails项目的清单中删除osgi，要么在Jboss 7配置中禁用它。我无法知道如何在grails项目的清单中禁用它，因此我从Jboss 7中删除了osgi。
您可以通过打开standalone.xml并找到标记为的子系统来从Jboss 7中删除它。 p>
< subsystem xmlns =urn：jboss：domain：osgi：1.2activation =lazy>
...
...
< / subsystem>
并将其注释掉或将其删除。我发表了评论，Jboss在我重新启动Jboss后自动删除了它。在我做这个之后，我的grails项目被正确加载了。
David
My company is trying to upgrade from JBoss 4.2.3 to JBoss 7. Currently I've setup a local copy of JBoss 7.1 and am trying to get my grails project to work on JBoss 7.1
The exact same war works just fine in JBoss 4.2.3. The weird thing is that there aren't any errors. Here is the info from the startup:
Calling "C:\JBoss\jboss-as-7.1.0\bin\standalone.conf.bat"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\JBoss\jboss-as-7.1.0
JAVA: C:\Java\jdk7\bin\java
JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.cl
ient.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.war
ning=true -Djboss.modules.system.pkgs=org.jboss.byteman
===============================================================================
15:02:53,200 INFO [org.jboss.modules] JBoss Modules version 1.1.0.GA
15:02:53,414 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
15:02:53,457 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" starting
15:02:54,062 INFO [org.xnio] XNIO Version 3.0.0.GA
15:02:54,062 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-h
ttp)
15:02:54,075 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.0.GA
15:02:54,082 INFO [org.jboss.remoting] JBoss Remoting version 3.2.0.GA
15:02:54,110 INFO [org.jboss.as.security] JBAS013101: Activating Security Subsystem
15:02:54,112 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
15:02:54,128 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
15:02:54,133 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
15:02:54,139 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.6.final
15:02:54,139 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Exten
sion
15:02:54,145 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 27) JBAS016200: Activating ConfigAdmin Subsy
stem
15:02:54,156 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 41) JBAS011940: Activating OSGi Subsystem
15:02:54,164 INFO [org.jboss.as.connector] (MSC service thread 1-9) JBAS010408: Starting JCA Subsystem (JBoss IronJacam
ar 1.0.7.Final)
15:02:54,199 INFO [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
15:02:54,201 INFO [org.jboss.as.jaxr] (MSC service thread 1-2) Binding JAXR ConnectionFactory: java:jboss/jaxr/Connecti
onFactory
15:02:54,221 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deployi
ng JDBC-compliant driver class org.h2.Driver (version 1.3)
15:02:54,231 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/ma
il/Default]
15:02:54,254 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010404: Deployi
ng non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
15:02:55,312 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) JBoss Web Services - S
tack CXF Server 4.0.1.GA
15:02:55,416 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:4447
15:02:55,434 INFO [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-15) Starting Coyote HTTP/1.1 on ht
tp--127.0.0.1-8080
15:02:55,515 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data sourc
e [java:jboss/datasources/ExampleDS]
15:02:55,521 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data sour
ce [java:jboss/datasources/MySqlDS]
15:02:55,575 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999
15:02:55,584 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-15) JBAS015012: Started FileSystemDepl
oymentService for directory C:\JBoss\jboss-as-7.1.0\standalone\deployments
15:02:55,695 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "ServerC
onfig.war"
15:02:56,941 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-9) JBossOSGi Framework Core -
1.1.1
15:02:56,975 ERROR [org.jboss.as] (MSC service thread 1-12) JBAS015875: JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" s
tarted (with errors) in 4090ms - Started 170 of 245 services (1 services failed or missing dependencies, 72 services are
passive or on-demand)
15:02:57,047 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-10) Install bundle: system.bu
ndle:0.0.0
15:02:57,269 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-10) Install bundle: javax.api
:0.0.0
15:02:57,270 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-5) Install bundle: javax.tran
saction.api:0.0.0
15:02:57,270 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-12) Install bundle: jbosgi-re
pository-api:1.0.4
15:02:57,330 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: jboss-as-o
sgi-configadmin:7.1.0.Final-SNAPSHOT
15:02:57,348 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-osgi
-logging:1.0.0
15:02:57,378 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-8) Install bundle: org.apache
.felix.log:1.0.0
15:02:57,379 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache
.felix.configadmin:1.2.8
15:02:57,378 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-11) Install bundle: jbosgi-ht
tp-api:1.0.5
15:02:57,535 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-6) Install bundle: osgi.enter
prise:4.2.0.201003190513
15:02:57,931 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-2) Starting bundles for st
art level: 1
15:02:57,936 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: osgi.ent
erprise:4.2.0.201003190513
15:02:57,941 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: javax.ap
i:0.0.0
15:02:57,952 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: jboss-os
gi-logging:1.0.0
15:02:57,959 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: javax.tr
ansaction.api:0.0.0
15:02:57,964 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: jbosgi-h
ttp-api:1.0.5
15:02:57,967 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: jbosgi-r
epository-api:1.0.4
15:02:57,984 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: org.apac
he.felix.configadmin:1.2.8
15:02:58,001 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: org.apac
he.felix.log:1.0.0
15:02:58,007 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-2) Bundle started: jboss-as
-osgi-configadmin:7.1.0.Final-SNAPSHOT
15:02:58,013 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-2) OSGi Framework started
15:02:58,030 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-12) Install bundle: ServerCon
fig:0.1.0
15:02:58,071 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "ServerConfig.war"
15:02:58,568 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-14) Bundle started: ServerConfig:0.1.0
===============================================================================
I also checked the JBoss 7 server.log and no errors were shown. Can anyone help me with this problem?
解决方案
Jboss 7 was trying to treat the application as an OSGI project rather than a regular web application. The key was to either remove osgi from the grails project's manifest or disable it in Jboss 7 configuration. I wasn't able to find out how to disable it on the grails project's manifest so I removed osgi from Jboss 7. You can remove it from Jboss 7 by opening up standalone.xml and finding the subsystem labelled as
<subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
...
...
</subsystem>
and either commenting this out or delete it. I commented mine out and Jboss automatically deleted it for me after I restarted Jboss. Right after I did this my grails project was loaded properly.
David
这篇关于Grails 1.3.7不是以JBoss 7.1开头的的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
查看全文
