Console
[color=red]11:54:31,406 INFO [Server] Starting JBoss (MX MicroKernel)…
11:54:31,406 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
11:54:31,406 INFO [Server] Home Dir: D:\Servers\prod\jboss-producao
11:54:31,421 INFO [Server] Home URL: file:/D:/Servers/prod/jboss-producao/
11:54:31,421 INFO [Server] Patch URL: null
11:54:31,421 INFO [Server] Server Name: default
11:54:31,421 INFO [Server] Server Home Dir: D:\Servers\prod\jboss-producao\server\default
11:54:31,421 INFO [Server] Server Home URL: file:/D:/Servers/prod/jboss-producao/server/default/
11:54:31,421 INFO [Server] Server Log Dir: D:\Servers\prod\jboss-producao\server\default\log
11:54:31,421 INFO [Server] Server Temp Dir: D:\Servers\prod\jboss-producao\server\default\tmp
11:54:31,421 INFO [Server] Root Deployment Filename: jboss-service.xml
11:54:31,734 INFO [ServerInfo] Java version: 1.5.0_17,Sun Microsystems Inc.
11:54:31,734 INFO [ServerInfo] Java VM: Java HotSpot™ Client VM 1.5.0_17-b04,Sun Microsystems Inc.
11:54:31,734 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
11:54:33,875 INFO [Server] Core system initialized
11:54:36,046 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
11:54:36,062 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml[/color]
Estou tentando iniciar o jboss sozinho (sem nenhum projeto) pelo eclipse mas ele chega somente até ai…
Aumentei o timeout para 300 (5 min) mas mesmo assim o servidor não passa desse ponto.
Eu tentei apagar o .metadata…
Tentei mudar de workspace…
E tentei usar o jboss 5.1…
Console jboss 5.1
[color=red]
12:06:41,796 INFO [ServerImpl] Starting JBoss (Microcontainer)…
12:06:41,796 INFO [ServerImpl] Release ID: JBoss [The Oracle] <a href="http://5.1.0.GA">5.1.0.GA</a> (build: SVNTag=JBoss_5_1_0_GA date=200905221053)
12:06:41,796 INFO [ServerImpl] Bootstrap URL: null
12:06:41,796 INFO [ServerImpl] Home Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>
12:06:41,796 INFO [ServerImpl] Home URL: file:/D:/Servers/default/jboss-5.1.0.GA/
12:06:41,796 INFO [ServerImpl] Library URL: file:/D:/Servers/default/jboss-5.1.0.GA/lib/
12:06:41,796 INFO [ServerImpl] Patch URL: null
12:06:41,796 INFO [ServerImpl] Common Base URL: file:/D:/Servers/default/jboss-5.1.0.GA/common/
12:06:41,796 INFO [ServerImpl] Common Library URL: file:/D:/Servers/default/jboss-5.1.0.GA/common/lib/
12:06:41,796 INFO [ServerImpl] Server Name: default
12:06:41,796 INFO [ServerImpl] Server Base Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server
12:06:41,796 INFO [ServerImpl] Server Base URL: file:/D:/Servers/default/jboss-5.1.0.GA/server/
12:06:41,796 INFO [ServerImpl] Server Config URL: file:/D:/Servers/default/jboss-5.1.0.GA/server/default/conf/
12:06:41,796 INFO [ServerImpl] Server Home Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default
12:06:41,796 INFO [ServerImpl] Server Home URL: file:/D:/Servers/default/jboss-5.1.0.GA/server/default/
12:06:41,796 INFO [ServerImpl] Server Data Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default\data
12:06:41,796 INFO [ServerImpl] Server Library URL: file:/D:/Servers/default/jboss-5.1.0.GA/server/default/lib/
12:06:41,796 INFO [ServerImpl] Server Log Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default\log
12:06:41,796 INFO [ServerImpl] Server Native Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default\tmp\native
12:06:41,796 INFO [ServerImpl] Server Temp Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default\tmp
12:06:41,796 INFO [ServerImpl] Server Temp Deploy Dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default\tmp\deploy
12:06:42,515 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/D:/Servers/default/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
12:06:43,296 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
12:06:43,296 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
12:06:43,609 INFO [CopyMechanism] VFS temp dir: D:\Servers\default\<a href="http://jboss-5.1.0.GA">jboss-5.1.0.GA</a>\server\default\tmp
12:06:43,625 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
12:06:44,859 INFO [ServerInfo] Java version: 1.5.0_17,Sun Microsystems Inc.
12:06:44,859 INFO [ServerInfo] Java Runtime: Java™ 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
12:06:44,859 INFO [ServerInfo] Java VM: Java HotSpot™ Client VM 1.5.0_17-b04,Sun Microsystems Inc.
12:06:44,859 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
12:06:44,859 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dfile.encoding=Cp1252
12:06:44,890 INFO [JMXKernel] Legacy JMX core initialized
12:06:46,937 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@25b64d[domain=default, server=default, name=default]
12:06:48,875 INFO [WebService] Using RMI server codebase: <a href="http://127.0.0.1:8083/">http://127.0.0.1:8083/</a>
12:06:55,781 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
12:06:55,781 INFO [NativeServerConfig] <a href="http://3.1.2.GA">3.1.2.GA</a>
12:06:56,546 INFO [AttributeCallbackItem] Owner callback not implemented.
12:06:58,093 INFO [LogNotificationListener] Adding notification listener for logging mbean “jboss.system:service=Logging,type=Log4jService” to server org.jboss.mx.server.MBeanServerImpl@1742dfe[ defaultDomain=‘jboss’ ]
12:07:11,390 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15190305{vfsfile:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
12:07:11,390 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15190305{vfsfile:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
12:07:11,390 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15190305{vfsfile:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
12:07:11,390 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15190305{vfsfile:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
12:07:15,062 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
12:07:15,218 INFO [MailService] Mail Service bound to java:/Mail
12:07:17,906 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
12:07:17,921 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
12:07:18,078 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
12:07:18,156 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
12:07:18,156 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
12:07:18,578 INFO [TransactionManagerService] Initializing recovery manager
12:07:18,765 INFO [TransactionManagerService] Recovery manager configured
12:07:18,765 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
12:07:18,812 INFO [TransactionManagerService] Starting transaction recovery manager
12:07:20,171 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\Arquivos de programas\Java\jre1.5.0_17\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:/Arquivos de programas/Java/jre1.5.0_17/bin/client;D:/Arquivos de programas/Java/jre1.5.0_17/bin;D:\Arquivos de programas\Windows Resource Kits\Tools;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\SysinternalsSuite;D:\eclipse;C:\WINDOWS\system32\WindowsPowerShell\v1.0;D:\Arquivos de programas\TortoiseSVN\bin;C:\Arquivos de programas\Microsoft SQL Server\100\Tools\Binn;C:\Arquivos de programas\Microsoft SQL Server\100\DTS\Binn;C:\Arquivos de programas\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE;C:\Arquivos de programas\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies;D:\Arquivos de programas\apache-maven-2.1.0\bin;
12:07:20,250 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
12:07:20,250 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:07:20,281 INFO [StandardService] Starting service <a href="http://jboss.web">jboss.web</a>
12:07:20,281 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA
12:07:20,359 INFO [Catalina] Server startup in 100 ms
12:07:20,375 INFO [TomcatDeployment] deploy, ctxPath=/invoker
12:07:21,078 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
12:07:21,140 INFO [TomcatDeployment] deploy, ctxPath=/web-console
12:07:21,734 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
12:07:21,750 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
12:07:21,781 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
12:07:21,812 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
12:07:21,828 INFO [RARDeployment] Required license terms exist, view vfszip:/D:/Servers/default/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
12:07:21,968 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
12:07:22,000 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
12:07:22,000 INFO [RAMJobStore] RAMJobStore initialized.
12:07:22,000 INFO [StdSchedulerFactory] Quartz scheduler ‘DefaultQuartzScheduler’ initialized from default resource file in Quartz package: 'quartz.properties’
12:07:22,000 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
12:07:22,000 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
12:07:23,671 INFO [ConnectionFactoryBindingService] Bound ConnectionManager ‘jboss.jca:service=DataSourceBinding,name=DefaultDS’ to JNDI name 'java:DefaultDS’
12:07:24,234 INFO [ServerPeer] JBoss Messaging <a href="http://1.4.3.GA">1.4.3.GA</a> server [0] started
12:07:24,453 INFO [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will <em>not</em> support failover
12:07:24,453 INFO [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will <em>not</em> support load balancing
12:07:24,546 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
12:07:24,546 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@f394a2 started
12:07:24,546 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
12:07:24,546 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1ed05dd started
12:07:24,562 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
12:07:24,562 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@14c78e3 started
12:07:24,578 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:07:24,578 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
12:07:24,718 INFO [ConnectionFactoryBindingService] Bound ConnectionManager ‘jboss.jca:service=ConnectionFactoryBinding,name=JmsXA’ to JNDI name 'java:JmsXA’
12:07:25,218 INFO [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar
12:07:25,234 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
12:07:25,234 INFO [JBossASKernel] with dependencies:
12:07:25,234 INFO [JBossASKernel] and demands:
12:07:25,234 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
12:07:25,234 INFO [JBossASKernel] and supplies:
12:07:25,234 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
12:07:25,234 INFO [JBossASKernel] jndi:SecureManagementView/remote
12:07:25,234 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.ManagementView
12:07:25,234 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar
12:07:25,234 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
12:07:25,234 INFO [JBossASKernel] with dependencies:
12:07:25,234 INFO [JBossASKernel] and demands:
12:07:25,234 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
12:07:25,234 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
12:07:25,234 INFO [JBossASKernel] and supplies:
12:07:25,234 INFO [JBossASKernel] jndi:SecureProfileService/remote
12:07:25,234 INFO [JBossASKernel] jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
12:07:25,234 INFO [JBossASKernel] Class:org.jboss.profileservice.spi.ProfileService
12:07:25,234 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar
12:07:25,234 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
12:07:25,234 INFO [JBossASKernel] with dependencies:
12:07:25,234 INFO [JBossASKernel] and demands:
12:07:25,234 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
12:07:25,234 INFO [JBossASKernel] and supplies:
12:07:25,234 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager
12:07:25,234 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote
12:07:25,234 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
12:07:25,234 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar
12:07:25,234 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData@dfb412{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
12:07:25,234 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData@120e7e1{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
12:07:25,234 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData@f34ef{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
12:07:25,390 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
12:07:25,406 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
12:07:25,484 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureManagementView/remote - EJB3.x Default Remote Business Interface
SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface
12:07:25,593 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
12:07:25,593 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
12:07:25,625 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureProfileService/remote - EJB3.x Default Remote Business Interface
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
12:07:25,703 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
12:07:25,703 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager
12:07:25,718 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface
12:07:25,890 INFO [TomcatDeployment] deploy, ctxPath=/admin-console
12:07:26,046 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console’
12:07:30,765 INFO [TomcatDeployment] deploy, ctxPath=/
12:07:30,859 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
12:07:30,953 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
12:07:30,984 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
12:07:31,015 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 49s:203ms
[/color]
O jboss 5.1 chegou ate aqui… mas no final deu na mesma.
Alguém já teve algum problema parecido? Qualquer experiência com alguma coisa semelhante já me ajudaria por que eu não tenho idéia do que possa estar provocando esse problema.
Em adendo:
Estou usando o jdk 1.5 update 7 e o jre jdk 1.5 update 7.
