[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5582) Support for server runtime JBossAS 6.0

Juergen Zimmermann (JIRA) jira-events at lists.jboss.org
Wed Jan 13 01:45:31 EST 2010 

    [ https://jira.jboss.org/jira/browse/JBIDE-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12503785#action_12503785 ] 

Juergen Zimmermann commented on JBIDE-5582:
-------------------------------------------

OK, although I cannot create a project related to JBossAS 6, I tried to start an "empty" server. See the stacktrace:

07:39:53,449 INFO  [AbstractJBossASServerBase] Server Configuration:

	JBOSS_HOME URL: file:/C:/Software/jboss-6.0.0.M1/
	Bootstrap: $JBOSS_HOME\server/default/conf/bootstrap.xml
	Common Base: $JBOSS_HOME\common/
	Common Library: $JBOSS_HOME\common/lib/
	Server Name: default
	Server Base: $JBOSS_HOME\server/
	Server Library: $JBOSS_HOME\server/default/lib/
	Server Config: $JBOSS_HOME\server/default/conf/
	Server Home: $JBOSS_HOME\server/default/
	Server Data: $JBOSS_HOME\server/default/data/
	Server Log: $JBOSS_HOME\server/default/log/
	Server Temp: $JBOSS_HOME\server/default/tmp/

07:39:53,460 INFO  [AbstractServer] Starting: JBossAS [6.0.0.M1 (build: SVNTag=JBoss_6_0_0_M1 date=200912040958)]
07:39:53,893 INFO  [AbstractMCServerBase] Starting Microcontainer, Main bootstrapURL=file:/C:/Software/jboss-6.0.0.M1/server/default/conf/bootstrap.xml
07:39:54,443 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
07:39:54,446 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
07:39:54,734 INFO  [CopyMechanism] VFS temp dir: C:\Software\jboss-6.0.0.M1\server\default\tmp
07:39:54,776 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.
07:39:55,599 INFO  [ServerInfo] Java version: 1.7.0-ea,Sun Microsystems Inc.
07:39:55,599 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.7.0-ea-b78)
07:39:55,599 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 17.0-b05,Sun Microsystems Inc.
07:39:55,599 INFO  [ServerInfo] OS-System: Windows Vista 6.0,x86
07:39:55,599 INFO  [ServerInfo] VM arguments: -Dprogram.name=JBossTools: JBoss 6.0.0.M1 Runtime -Xms256m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=C:\Software\jboss-6.0.0.M1\lib\endorsed -Djava.library.path=C:\Software\jboss-6.0.0.M1\bin\native; -Dfile.encoding=Cp1252 
07:39:55,629 INFO  [JMXKernel] Legacy JMX core initialized
07:39:58,392 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
07:39:58,519 INFO  [WebService] Using RMI server codebase: http://localhost:8083/
07:40:02,819 INFO  [AbstractServerConfig] JBoss Web Services - Native Server
07:40:02,819 INFO  [AbstractServerConfig] 3.2.2.GA
07:40:09,296 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl at a84b47[ defaultDomain='null' ]
07:40:18,737 INFO  [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector
07:40:18,937 INFO  [MailService] Mail Service bound to java:/Mail
07:40:21,579 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
07:40:21,579 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
07:40:21,839 INFO  [TransactionManagerService] Initializing recovery manager
07:40:22,048 INFO  [TransactionManagerService] Recovery manager configured
07:40:22,049 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
07:40:22,071 INFO  [TransactionManagerService] Starting transaction recovery manager
07:40:22,727 INFO  [AprLifecycleListener] Loaded Apache Tomcat Native library 1.1.19.
07:40:22,727 INFO  [AprLifecycleListener] APR capabilities: IPv6 [true], sendfile [true], random [true].
07:40:24,481 INFO  [Http11AprProtocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
07:40:24,485 INFO  [AjpAprProtocol] Initializing Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
07:40:24,516 INFO  [StandardService] Starting service jboss.web
07:40:24,520 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.6.GA
07:40:24,583 INFO  [Catalina] Server startup in 97 ms
07:40:24,641 INFO  [TomcatDeployment] deploy, ctxPath=/web-console
07:40:26,152 INFO  [TomcatDeployment] deploy, ctxPath=/juddi
07:40:26,260 INFO  [RegistryServlet] Loading jUDDI configuration.
07:40:26,262 INFO  [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
07:40:26,262 INFO  [RegistryServlet] Initializing jUDDI components.
07:40:26,474 INFO  [TomcatDeployment] deploy, ctxPath=/invoker
07:40:26,665 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Software/jboss-6.0.0.M1/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
07:40:26,677 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Software/jboss-6.0.0.M1/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
07:40:26,686 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Software/jboss-6.0.0.M1/server/default/deploy/jms-ra.rar/META-INF/ra.xml
07:40:26,697 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Software/jboss-6.0.0.M1/server/default/deploy/mail-ra.rar/META-INF/ra.xml
07:40:26,734 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Software/jboss-6.0.0.M1/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
07:40:26,826 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2
07:40:26,852 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
07:40:26,854 INFO  [RAMJobStore] RAMJobStore initialized.
07:40:26,855 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
07:40:26,855 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
07:40:26,855 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
07:40:27,035 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
07:40:29,409 INFO  [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started
07:40:30,340 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
07:40:30,385 INFO  [ConnectionFactory] Connector bisocket://localhost:4457 has leasing enabled, lease period 10000 milliseconds
07:40:30,385 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 4afdc4 started
07:40:30,390 INFO  [ConnectionFactory] Connector bisocket://localhost:4457 has leasing enabled, lease period 10000 milliseconds
07:40:30,390 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at e08787 started
07:40:30,391 INFO  [TopicService] Topic[/topic/kunden] started, fullSize=200000, pageSize=2000, downCacheSize=2000
07:40:30,392 INFO  [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
07:40:30,392 INFO  [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
07:40:30,393 INFO  [ConnectionFactory] Connector bisocket://localhost:4457 has leasing enabled, lease period 10000 milliseconds
07:40:30,393 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 469154 started
07:40:30,396 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
07:40:30,398 INFO  [QueueService] Queue[/queue/marketing] started, fullSize=200000, pageSize=2000, downCacheSize=2000
07:40:30,401 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
07:40:30,604 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console
07:40:34,422 INFO  [TomcatDeployment] deploy, ctxPath=/
07:40:34,560 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws
07:40:34,716 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console
07:40:34,846 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey at 1892c59[domain=default, server=default, name=default]
07:40:34,889 INFO  [Http11AprProtocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
07:40:34,933 INFO  [AjpAprProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
07:40:34,939 INFO  [AbstractServer] JBossAS [6.0.0.M1 (build: SVNTag=JBoss_6_0_0_M1 date=200912040958)] Started in 41s:478ms
07:40:42,460 WARN  [HDScanner] Failed to add deployment: vfszip:/C:/Software/jboss-6.0.0.M1/bin/run.jar/
org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=client/getopt.jar} from run.jar
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)
	at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)
	at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1001)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:437)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:387)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:297)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:347)
	at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:256)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:717)
Caused by: java.io.IOException: Child not found client/getopt.jar for DelegatingHandler at 23365286[path=bin/run.jar context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar], available children: [ZipEntryHandler at 12852692[path=bin/run.jar/GetoptDemo.class context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/GetoptDemo.class], ZipEntryHandler at 25321800[path=bin/run.jar/META-INF context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/META-INF], ZipEntryHandler at 12641721[path=bin/run.jar/gnu context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/gnu], ZipEntryHandler at 2747036[path=bin/run.jar/log4j-debug.properties context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/log4j-debug.properties], ZipEntryHandler at 32102416[path=bin/run.jar/log4j-trace.properties context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/log4j-trace.properties], ZipEntryHandler at 23595936[path=bin/run.jar/log4j.properties context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/log4j.properties], ZipEntryHandler at 30620998[path=bin/run.jar/org context=file:/C:/Software/jboss-6.0.0.M1/ real=file:/C:/Software/jboss-6.0.0.M1/bin/run.jar/org]]
	at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:472)
	at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)
	... 17 more

> Support for server runtime JBossAS 6.0
> --------------------------------------
>
>                 Key: JBIDE-5582
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5582
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>            Reporter: Juergen Zimmermann
>            Assignee: Snjezana Peco
>             Fix For: 3.1.0.CR2, 3.2.next
>
>         Attachments: screenshot-missing-JBoss-JARs.jpg, screenshot-New-Server-Runtim-Environment.jpg
>
>
> JBossAS 6.0.0.M1 is available. It can be used in JBossTools via the 5.1 configuration. However, it would be better to have a separate 6.0 configuration option.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbosstools-issues mailing list