-
1. Re: move from glassfish to jboss as 7
nickarls Aug 21, 2012 6:16 AM (in response to ryannewbie)Ryan Li wrote:
hello everyone,
I am new to jboss 7. I got many questions moving from glassfish v3.1.2 to AS 7.
why I wanna move is that when I first start jboss, the startup time is lightning fast and it seems jboss is commercially more popular.
it worths the effort to move myself from glassfish to jboss even I am still learning JEE.
here are my questions:
1. how to configure datasource in the web console? I googled a bit. it seems that the answer is the hard code XML. ( correct me if I am wrong! but I don't see a button to add a datasource in web console localhost:9990/console )
2. could you name me a good jboss 7 book to start with for configuration?
3. does jboss 7 include Richfaces? I didn't find a jar's name containing *rich* in JBOSS_HOME and its sub dirs.
4. does jboss use EclipseLink? if not, should I change the persistence.xml to suit the provider?
5. last question. I added two projects to jboss runtime in Eclipse. both don't run. I can understand the one with datasource configured for glassfish. Yet, the other one is a pure jsf, the error code is 404 (resource is not available). It's enabled in web console.
Thanks very much reading my post or even give me an answer!
Ryan
1. Check the "profile" (not runtime) tab in the upper-hand corner
2. Not that many written yet, Check out "JBoss AS 7 Configuration, Deployment and Administration"
3. It's an application lib deployed with the application, not a part of the AS. Check the RF docs for more info
4. It uses Hibernate as the default provider, not sure what the status of using EclipseLink is currently
5. Paste the full stack trace
-
2. Re: move from glassfish to jboss as 7
ryannewbie Aug 21, 2012 6:40 AM (in response to nickarls)for question 5, could you show me the path of getting the stack trace in web console?
server.log
22:49:53,605 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
22:49:53,672 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
22:49:59,577 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
22:50:07,469 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
22:50:09,818 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
22:50:11,241 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
22:50:13,252 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
22:50:24,031 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
22:50:24,058 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
22:50:24,058 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
22:50:25,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:50:25,370 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
22:50:25,373 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 51237ms - Started 133 of 208 services (74 services are passive or on-demand)
22:54:56,984 INFO [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011942: Stopping OSGi Framework
22:55:13,669 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
22:55:13,767 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
22:55:14,453 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
22:55:14,459 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
22:55:14,998 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
22:55:15,103 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:55:15,250 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
22:55:15,273 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:4447
22:55:15,275 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
22:55:15,620 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
22:55:15,624 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 12618ms - Started 133 of 208 services (74 services are passive or on-demand)
22:55:23,697 INFO [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011942: Stopping OSGi Framework
22:55:23,724 WARN [org.jboss.remoting.remote] (Remoting "frank-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
22:55:23,725 WARN [org.jboss.remoting.remote] (Remoting "frank-pc:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
22:56:27,989 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
22:56:28,018 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
22:56:28,121 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
22:56:28,170 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
22:56:28,211 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:4447
22:56:28,509 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:56:28,705 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
22:56:28,706 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 5834ms - Started 133 of 208 services (74 services are passive or on-demand)
23:02:08,414 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) JBoss Web Services - Stack CXF Server 4.0.2.GA
23:02:08,708 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
23:02:08,832 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
23:02:08,877 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
23:02:08,918 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999
23:02:09,275 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:02:09,400 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
23:02:09,401 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 5675ms - Started 133 of 208 services (74 services are passive or on-demand)
23:06:07,315 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) JBossOSGi Framework Core - 1.1.8.Final
23:06:07,548 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: system.bundle:0.0.0
23:06:08,186 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: jboss-osgi-logging:1.0.0
23:06:08,212 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: org.apache.felix.log:1.0.0
23:06:08,233 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jbosgi-http-api:1.0.5
23:06:08,241 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-1) Install bundle: org.apache.felix.configadmin:1.2.8
23:06:08,293 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: jboss-as-osgi-configadmin:7.1.1.Final
23:06:08,304 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-2) Install bundle: javax.transaction.api:0.0.0
23:06:08,651 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-4) Install bundle: osgi.enterprise:4.2.0.201003190513
23:06:08,908 INFO [org.jboss.osgi.framework.internal.StartLevelPlugin] (MSC service thread 1-4) Starting bundles for start level: 1
23:06:08,916 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jbosgi-http-api:1.0.5
23:06:08,919 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: osgi.enterprise:4.2.0.201003190513
23:06:08,948 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-as-osgi-configadmin:7.1.1.Final
23:06:08,961 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: jboss-osgi-logging:1.0.0
23:06:09,002 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.log:1.0.0
23:06:09,005 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: javax.transaction.api:0.0.0
23:06:09,048 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-4) Bundle started: org.apache.felix.configadmin:1.2.8
23:06:09,053 INFO [org.jboss.osgi.framework.internal.FrameworkActive] (MSC service thread 1-4) OSGi Framework started
23:06:40,128 INFO [org.jboss.as.repository] (HttpManagementService-threads - 9) JBAS014900: Content added at location C:\jboss-as-7.1.1.Final\standalone\data\content\25\43b79ab039f621191eb6404b97ab27fa48cb1a\content
23:07:13,142 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "BookWeb.war"
23:07:13,906 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011401: Read persistence.xml for chapter10PU
23:07:13,984 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.module.service."deployment.BookWeb.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.BookWeb.war".main: Failed to load module: deployment.BookWeb.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
Caused by: org.jboss.modules.ModuleNotFoundException: Module org.eclipse.persistence:main is not found in local module loader @21d392b9 (roots: C:\jboss-as-7.1.1.Final\modules)
at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
at org.jboss.modules.Module.addPaths(Module.java:841)
at org.jboss.modules.Module.link(Module.java:1181)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
23:07:14,217 INFO [org.jboss.as.server] (HttpManagementService-threads - 9) JBAS015870: Deploy of deployment "BookWeb.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.BookWeb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.BookWeb.war\".main: Failed to load module: deployment.BookWeb.war:main"}}
23:07:14,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BookWeb.war in 18ms
23:07:14,254 INFO [org.jboss.as.controller] (HttpManagementService-threads - 9) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.module.service."deployment.BookWeb.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.BookWeb.war".main: Failed to load module: deployment.BookWeb.war:main
23:15:37,750 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
23:15:37,806 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
23:15:38,408 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
23:15:39,100 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA
23:15:39,400 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
23:15:39,514 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
23:15:39,780 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
23:15:39,859 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
23:15:39,906 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found planets.war in deployment directory. To trigger deployment create a file called planets.war.dodeploy
23:15:39,912 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found BookWeb.war in deployment directory. To trigger deployment create a file called BookWeb.war.dodeploy
23:15:39,954 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
23:15:39,961 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447
23:15:40,117 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
23:15:40,263 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) Operation ("add") failed - address: ([("deployment" => "BookWeb.war")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"BookWeb.war\")]"
23:15:40,265 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014803: Duplicate resource [(\"deployment\" => \"BookWeb.war\")]"}}
23:15:40,269 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) undefined
23:15:40,719 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
23:15:40,720 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 9524ms - Started 133 of 208 services (74 services are passive or on-demand)
23:19:45,417 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found planets.war in deployment directory. To trigger deployment create a file called planets.war.dodeploy
23:19:45,482 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "planets.war"
23:19:46,271 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment planets.war
23:19:46,609 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: planets.war
23:19:46,773 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
23:19:46,876 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment planets.war
23:19:47,930 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/planets'
23:19:50,306 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-3) Hibernate Validator 4.2.0.Final
23:19:50,723 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Monitoring jndi:/default-host/planets/WEB-INF/faces-config.xml for modifications
23:19:50,788 WARNING [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) JSF1025: [/planets] Context initialization parameter 'facelets.LIBRARIES' is deprecated. The option will still be configured, but please use 'javax.faces.FACELETS_LIBRARIES' in the future.
23:19:50,790 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) JSF1019: [/planets] Configuration option 'javax.faces.FACELETS_LIBRARIES' RESET to '/WEB-INF/corejsf.taglib.xml'
23:19:50,829 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /planets
23:19:51,050 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "planets.war"
23:22:21,200 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment planets.war
23:22:21,217 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment planets.war in 39ms
23:22:21,220 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "planets.war"
23:22:21,280 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment planets.war
23:22:21,303 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: planets.war
23:22:21,319 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment planets.war
23:22:21,451 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/planets'
23:22:21,561 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Monitoring jndi:/default-host/planets/WEB-INF/faces-config.xml for modifications
23:22:21,572 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /planets
23:22:21,693 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "planets.war" with deployment "planets.war"
16:16:22,949 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
16:16:22,972 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:16:23,105 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
16:16:23,130 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:16:23,158 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
16:16:23,603 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
16:16:24,475 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
16:16:26,903 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:16:27,617 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
16:16:29,019 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:16:29,195 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
16:16:31,114 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
16:16:32,222 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7.1.1.Final\standalone\deployments
16:16:32,233 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
16:16:32,235 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
16:16:32,246 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found planets.war in deployment directory. To trigger deployment create a file called planets.war.dodeploy
16:16:32,755 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:16:33,123 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "planets.war"
16:16:33,993 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment planets.war
16:16:34,275 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: planets.war
16:16:34,414 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.5 (AS71)
16:16:34,511 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment planets.war
16:16:35,779 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/planets'
16:16:37,241 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-1) Hibernate Validator 4.2.0.Final
16:16:37,609 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Monitoring jndi:/default-host/planets/WEB-INF/faces-config.xml for modifications
16:16:37,748 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /planets
16:16:37,768 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:16:37,777 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 25512ms - Started 190 of 267 services (76 services are passive or on-demand)
16:16:37,931 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "planets.war"
-
3. Re: move from glassfish to jboss as 7
nickarls Aug 21, 2012 6:59 AM (in response to ryannewbie)1 of 1 people found this helpfulNot sure how to get it in the Web Console. I usually look at the server log file
"Module org.eclipse.persistence:main is not found in local module loader"
is probably from the EclipseLink reference.
Do you have multiple deployments with the same name ("JBAS014803: Duplicate resource") or is this a side effect from the eclipselink classloading failure, I wonder?
-
4. Re: move from glassfish to jboss as 7
avneesh Aug 21, 2012 7:02 AM (in response to nickarls)Is there any one here who can help me for this issue I am having.
https://community.jboss.org/thread/203791
Thanks..
-
5. Re: move from glassfish to jboss as 7
smarlow Aug 21, 2012 8:33 AM (in response to ryannewbie)1 of 1 people found this helpfulIt sounds like your application's persistence.xml is configured to use EclipseLink. Some discussion of how others have setup EclipseLink is described here.
If you comment out the <provider> element in the persistence.xml, the Hibernate persistence provider will be used. Here is a link to an example persistence.xml that is ready to work with Hibernate.