-
2. Re:
I'm starting JBoss, then enter in Firefox http://localhost:8080/MySeamProj, after that I receive "The requested resource (/MySeamProj/) is not available." (When creating the project I choose Generic JDBC driver and war option).
Here is the trace from console after JBoss is started:13:44:51,441 INFO [Server] Starting JBoss (MX MicroKernel)... 13:44:51,469 INFO [Server] Release ID: JBoss [EAP] 4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411) 13:44:51,471 INFO [Server] Home Dir: /opt/work/rhdsbeta1/jboss-eap/jboss-as 13:44:51,471 INFO [Server] Home URL: file:/opt/work/rhdsbeta1/jboss-eap/jboss-as/ 13:44:51,473 INFO [Server] Patch URL: null 13:44:51,473 INFO [Server] Server Name: default 13:44:51,473 INFO [Server] Server Home Dir: /opt/work/rhdsbeta1/jboss-eap/jboss-as/server/default 13:44:51,473 INFO [Server] Server Home URL:file:/opt/work/rhdsbeta1/jboss-eap/jboss-as/server/default/ 13:44:51,474 INFO [Server] Server Log Dir:/opt/work/rhdsbeta1/jboss-eap/jboss-as/server/default/log 13:44:51,474 INFO [Server] Server Temp Dir :/opt/work/rhdsbeta1/jboss-eap/jboss-as/server/default/tmp 13:44:51,475 INFO [Server] Root Deployment Filename: jboss-service.xml 13:44:54,059 INFO [ServerInfo] Java version: 1.5.0_12,Sun Microsystems Inc. 13:44:54,061 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_12-b04,Sun Microsystems Inc. 13:44:54,063 INFO [ServerInfo] OS-System: Linux 2.6.18-8.el5xen,i386 13:44:55,467 INFO [Server] Core system initialized 13:45:06,312 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/ 13:45:06,320 INFO [Log4jService$URLWatchTimerTask] Configuring from URL:resource:jboss-log4j.xml 13:45:07,656 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 13:45:07,658 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 13:45:11,244 INFO [TransactionManagerService] Starting recovery manager 13:45:12,422 INFO [TransactionManagerService] Recovery manager started 13:45:12,424 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 13:45:22,648 INFO [EJB3Deployer] Starting java:comp multiplexer 13:45:28,567 INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756) 13:45:35,686 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.5.0_12/jre/lib/i386/client:/usr/java/jdk1.5.0_12/jre/lib/i386:/usr/java/jdk1.5.0_12/jre/../li b/i386:/usr/java/jdk1.5.0_12/jre/lib/i386/client::/usr/java/jdk1.5.0_12/jre/lib/i386::/usr/lib/firefox-1.5.0 .9:/usr/lib/firefox-1.5.0.9 13:45:35,986 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080 13:45:35,990 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009 13:45:35,991 INFO [Catalina] Initialization processed in 876 ms 13:45:35,992 INFO [StandardService] Starting service jboss.web 13:45:36,005 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA 13:45:36,191 INFO [Catalina] Server startup in 199 ms 13:45:36,764 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/ 13:45:38,763 INFO [TomcatDeployer] deploy, ctxPath=/invoker,warUrl=.../deploy/http-invoker.sar/invoker.war/ 13:45:39,453 INFO [TomcatDeployer] deploy, ctxPath=/jbossws,warUrl=.../tmp/deploy/tmp23148jbossws-context-exp.war/ 13:45:40,091 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil,warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 13:45:43,323 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/ 13:45:45,775 INFO [MailService] Mail Service bound to java:/Mail 13:45:46,458 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar 13:45:46,806 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar 13:45:46,912 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar 13:45:47,141 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar 13:45:47,556 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar 13:45:47,721 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar 13:45:47,756 INFO [QuartzResourceAdapter] start quartz!!! 13:45:47,950 INFO [SimpleThreadPool] Job execution threads will use class loader of thread:main 13:45:48,053 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 13:45:48,064 INFO [RAMJobStore] RAMJobStore initialized. 13:45:48,064 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' 13:45:48,065 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 13:45:48,066 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 13:45:48,664 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySeamProjDatasource' to JNDI name 'java:MySeamProjDatasource' 13:45:50,263 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 13:45:51,174 INFO [A] Bound to JNDI name: queue/A 13:45:51,201 INFO [B] Bound to JNDI name: queue/B 13:45:51,205 INFO [C] Bound to JNDI name: queue/C 13:45:51,210 INFO [D] Bound to JNDI name: queue/D 13:45:51,219 INFO [ex] Bound to JNDI name: queue/ex 13:45:51,281 INFO [testTopic] Bound to JNDI name: topic/testTopic 13:45:51,287 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 13:45:51,291 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 13:45:51,336 INFO [testQueue] Bound to JNDI name: queue/testQueue 13:45:51,911 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.18093 13:45:52,012 INFO [DLQ] Bound to JNDI name: queue/DLQ 13:45:52,473 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 13:45:52,629 INFO [TomcatDeployer] deploy, ctxPath=/MySeamProj, warUrl=.../deploy/MySeamProj.war/ 13:45:53,249 WARN [config] Unable to process deployment descriptor for context 'null' 13:45:55,399 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ 13:45:56,404 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 13:45:56,465 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 13:45:56,747 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBPAPP_4_2_0_GA date=200706281411)] Started in 1m:5s:263ms
And this after making Publish:publishing module (/MySeamProj/src/MySeamProj-ds.xml): full, added to server JBoss 4.2 Server (1)(7_28_07_5_42_PM7) loaded in 35807 publishing module (MySeamProj): full, added to server JBoss 4.2 Server (1)(7_28_07_5_42_PM7) publishing module (MySeamProj): incremental, no change to server JBoss 4.2 Server(1)(7_28_07_5_42_PM7) publishing module (MySeamProj): incremental, no change to server JBoss 4.2 Server (1)(7_28_07_5_42_PM7)
One more thing: after the project is created, I right click JBoss server > Add and Remove projects and I see that my project is in the panel "Available projects", not in "Configured projects"? Why? Should I always manually register it under the server? -
3. Re:
It looks like deployment problem for me.
DataSource is bounded.INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySeamProjDatasource' to JNDI name 'java:MySeamProjDatasou
But war is not deployed.13:45:52,629 INFO [TomcatDeployer] deploy, ctxPath=/MySeamProj, warUrl=.../deploy/MySeamProj.war/ 13:45:53,249 WARN [config] Unable to process deployment descriptor for context 'null'
It works fine for me on current version built from SVN. I've just checked several cases:
1. Create project, before JBoss AS started, configure new created project on server instance, then start it. This scenario worked for me.
2. Start JBoss AS, then create project and configure it on running JBoss AS server instance. Several exceptions appear on console, but it works for me also.
Are you using beta1 release or nightly build?