[JBoss JIRA] (JBIDE-14027) Remote EAP 5 fails to start correctly
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14027?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-14027.
---------------------------------
> Remote EAP 5 fails to start correctly
> -------------------------------------
>
> Key: JBIDE-14027
> URL: https://issues.jboss.org/browse/JBIDE-14027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Environment: JBDS 7.0.0.Alpha2 B135
> EAP 5.1.2/5.2.0
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta1
>
> Attachments: JBIDE-14027.jmxfail.txt
>
>
> When I set up a remote EAP 5 server and start it, it first starts normally:
> {code}
> 2013-04-15 15:09:51,863 INFO [org.jboss.web.WebService] (main) Using RMI server codebase: http://MARVIN.BRQ.REDHAT.COM:8083/
> 2013-04-15 15:09:56,801 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) JBoss Web Services - Stack Native Core
> 2013-04-15 15:09:56,802 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) 3.1.2.SP11
> 2013-04-15 15:09:58,404 INFO [org.jboss.logbridge.LogNotificationListener] (main) Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@5aacc14[ defaultDomain='jboss' ]
> 2013-04-15 15:10:05,967 INFO [org.jboss.mail.MailService] (main) Mail Service bound to java:/Mail
> 2013-04-15 15:10:07,097 WARN [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (main) 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.
> 2013-04-15 15:10:08,507 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP12) - JBoss Inc.
> 2013-04-15 15:10:08,508 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Setting up property manager MBean and JMX layer
> 2013-04-15 15:10:08,850 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Initializing recovery manager
> 2013-04-15 15:10:09,163 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Recovery manager configured
> 2013-04-15 15:10:09,163 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Binding TransactionManager JNDI Reference
> 2013-04-15 15:10:09,194 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Starting transaction recovery manager
> 2013-04-15 15:10:09,627 INFO [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/bin/native
> 2013-04-15 15:10:09,698 INFO [org.apache.coyote.http11.Http11Protocol] (main) Initializing Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:09,700 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Initializing Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:09,742 INFO [org.apache.catalina.core.StandardService] (main) Starting service jboss.web
> 2013-04-15 15:10:09,752 INFO [org.apache.catalina.core.StandardEngine] (main) Starting Servlet Engine: JBoss Web/2.1.12.GA-patch-01
> 2013-04-15 15:10:09,859 INFO [org.apache.catalina.startup.Catalina] (main) Server startup in 158 ms
> 2013-04-15 15:10:09,900 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jbossws
> 2013-04-15 15:10:10,511 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/invoker
> 2013-04-15 15:10:10,555 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/web-console
> 2013-04-15 15:10:10,987 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,002 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,011 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/jms-ra.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,024 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/mail-ra.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,045 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,130 INFO [org.quartz.simpl.SimpleThreadPool] (main) Job execution threads will use class loader of thread: main
> 2013-04-15 15:10:11,155 INFO [org.quartz.core.QuartzScheduler] (main) Quartz Scheduler v.1.5.2 created.
> 2013-04-15 15:10:11,158 INFO [org.quartz.simpl.RAMJobStore] (main) RAMJobStore initialized.
> 2013-04-15 15:10:11,159 INFO [org.quartz.impl.StdSchedulerFactory] (main) Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
> 2013-04-15 15:10:11,159 INFO [org.quartz.impl.StdSchedulerFactory] (main) Quartz scheduler version: 1.5.2
> 2013-04-15 15:10:11,161 INFO [org.quartz.core.QuartzScheduler] (main) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> 2013-04-15 15:10:11,738 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
> 2013-04-15 15:10:12,161 INFO [org.jboss.jms.server.ServerPeer] (main) JBoss Messaging 1.4.8.SP5 server [0] started
> 2013-04-15 15:10:12,283 INFO [org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
> 2013-04-15 15:10:12,348 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://MARVIN.BRQ.REDHAT.COM:4457 has leasing enabled, lease period 10000 milliseconds
> 2013-04-15 15:10:12,348 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@a4dbd0f started
> 2013-04-15 15:10:12,351 INFO [org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
> 2013-04-15 15:10:12,352 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main) 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
> 2013-04-15 15:10:12,352 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main) 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
> 2013-04-15 15:10:12,354 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://MARVIN.BRQ.REDHAT.COM:4457 has leasing enabled, lease period 10000 milliseconds
> 2013-04-15 15:10:12,354 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@606fdb4b started
> 2013-04-15 15:10:12,355 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://MARVIN.BRQ.REDHAT.COM:4457 has leasing enabled, lease period 10000 milliseconds
> 2013-04-15 15:10:12,355 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@74bdaaa started
> 2013-04-15 15:10:12,473 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
> 2013-04-15 15:10:12,670 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/admin-console
> 2013-04-15 15:10:13,118 INFO [javax.enterprise.resource.webcontainer.jsf.config] (main) Initializing Mojarra (1.2_13-b01-FCS) for context '/admin-console'
> 2013-04-15 15:10:16,703 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/
> 2013-04-15 15:10:16,757 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jmx-console
> 2013-04-15 15:10:16,862 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Loading profile: ProfileKey@684640e6[domain=default, server=default, name=default]
> 2013-04-15 15:10:16,900 INFO [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:16,984 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:17,010 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.2 (build: SVNTag=JBPAPP_5_1_2 date=201111102209)] Started in 34s:709ms
> {code}
> But a few seconds after that strange things happen:
> {code}
> 2013-04-15 15:10:22,087 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/jmx-console
> 2013-04-15 15:10:22,118 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/
> 2013-04-15 15:10:22,143 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/admin-console
> 2013-04-15 15:10:22,245 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (HDScanner) Unbound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' from JNDI name 'java:JmsXA'
> 2013-04-15 15:10:22,261 INFO [org.jboss.jms.server.destination.QueueService] (HDScanner) Queue[/queue/ExpiryQueue] stopped
> 2013-04-15 15:10:22,262 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (HDScanner) org.jboss.jms.server.connectionfactory.ConnectionFactory@a4dbd0f undeployed
> 2013-04-15 15:10:22,263 INFO [org.jboss.jms.server.destination.QueueService] (HDScanner) Queue[/queue/DLQ] stopped
> 2013-04-15 15:10:22,263 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (HDScanner) org.jboss.jms.server.connectionfactory.ConnectionFactory@74bdaaa undeployed
> 2013-04-15 15:10:22,264 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (HDScanner) org.jboss.jms.server.connectionfactory.ConnectionFactory@606fdb4b undeployed
> 2013-04-15 15:10:22,294 INFO [org.jboss.jms.server.ServerPeer] (HDScanner) JMS ServerPeer[0] stopped
> 2013-04-15 15:10:22,300 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (HDScanner) Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' from JNDI name 'java:DefaultDS'
> 2013-04-15 15:10:22,694 INFO [org.jboss.jdbc.HypersonicDatabase] (HDScanner) Database standalone closed clean
> 2013-04-15 15:10:22,704 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
> 2013-04-15 15:10:22,704 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
> 2013-04-15 15:10:22,706 INFO [org.quartz.simpl.SimpleThreadPool] (HDScanner) There are still 35 worker threads active. See javadoc runInThread(Runnable) for a possible explanation
> 2013-04-15 15:10:22,706 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
> 2013-04-15 15:10:22,745 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/jbossws
> 2013-04-15 15:10:22,751 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/invoker
> 2013-04-15 15:10:22,756 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/web-console
> 2013-04-15 15:10:22,766 INFO [org.apache.coyote.http11.Http11Protocol] (HDScanner) Pausing Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:22,767 INFO [org.apache.coyote.http11.Http11Protocol] (HDScanner) Stopping Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:22,769 INFO [org.apache.coyote.ajp.AjpProtocol] (HDScanner) Pausing Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:22,770 INFO [org.apache.coyote.ajp.AjpProtocol] (HDScanner) Stopping Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:22,777 INFO [org.apache.catalina.core.StandardService] (HDScanner) Stopping service jboss.web
> 2013-04-15 15:10:22,809 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) Stopping transaction recovery manager
> 2013-04-15 15:10:22,812 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) Destroying TransactionManagerService
> 2013-04-15 15:10:24,588 INFO [org.jboss.mail.MailService] (HDScanner) Mail service 'java:/Mail' removed from JNDI
> 2013-04-15 15:10:28,975 INFO [org.jboss.mail.MailService] (HDScanner) Mail Service bound to java:/Mail
> 2013-04-15 15:10:29,495 WARN [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (HDScanner) 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.
> 2013-04-15 15:10:30,814 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP12) - JBoss Inc.
> 2013-04-15 15:10:30,821 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) Setting up property manager MBean and JMX layer
> 2013-04-15 15:10:30,844 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Create: name=TransactionManager state=Configured
> com.arjuna.common.util.exceptions.ManagementPluginException: com.arjuna.common.util.exceptions.ManagementPluginException: Failed to register mbeans: javax.management.InstanceAlreadyExistsException: com.arjuna.ats.properties:module=arjuna already registered.
> at com.arjuna.common.internal.util.propertyservice.PropertyManagerImpl.addManagementPlugin(PropertyManagerImpl.java:496)
> at com.arjuna.ats.jbossatx.jta.TransactionManagerService.create(TransactionManagerService.java:193)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243)
> at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
> at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:125)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:52)
> at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> 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$201(ScheduledThreadPoolExecutor.java:165)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-14027) Remote EAP 5 fails to start correctly
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14027?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-14027:
----------------------------------
Fix Version/s: (was: 4.2.0.Beta3)
This JIRA was already verified as fixed in JBoss Tools 4.1.0.Beta1. Thus I will remove 4.2 from the fix version and close this again.
This particular JIRA was only about remote servers and the cause was that the JMX call for new deployment URL was called even for remote servers which was an error.
What Axel saw is described in JBIDE-17668.
> Remote EAP 5 fails to start correctly
> -------------------------------------
>
> Key: JBIDE-14027
> URL: https://issues.jboss.org/browse/JBIDE-14027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Environment: JBDS 7.0.0.Alpha2 B135
> EAP 5.1.2/5.2.0
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta1
>
> Attachments: JBIDE-14027.jmxfail.txt
>
>
> When I set up a remote EAP 5 server and start it, it first starts normally:
> {code}
> 2013-04-15 15:09:51,863 INFO [org.jboss.web.WebService] (main) Using RMI server codebase: http://MARVIN.BRQ.REDHAT.COM:8083/
> 2013-04-15 15:09:56,801 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) JBoss Web Services - Stack Native Core
> 2013-04-15 15:09:56,802 INFO [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) 3.1.2.SP11
> 2013-04-15 15:09:58,404 INFO [org.jboss.logbridge.LogNotificationListener] (main) Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@5aacc14[ defaultDomain='jboss' ]
> 2013-04-15 15:10:05,967 INFO [org.jboss.mail.MailService] (main) Mail Service bound to java:/Mail
> 2013-04-15 15:10:07,097 WARN [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (main) 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.
> 2013-04-15 15:10:08,507 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP12) - JBoss Inc.
> 2013-04-15 15:10:08,508 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Setting up property manager MBean and JMX layer
> 2013-04-15 15:10:08,850 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Initializing recovery manager
> 2013-04-15 15:10:09,163 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Recovery manager configured
> 2013-04-15 15:10:09,163 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Binding TransactionManager JNDI Reference
> 2013-04-15 15:10:09,194 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Starting transaction recovery manager
> 2013-04-15 15:10:09,627 INFO [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/bin/native
> 2013-04-15 15:10:09,698 INFO [org.apache.coyote.http11.Http11Protocol] (main) Initializing Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:09,700 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Initializing Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:09,742 INFO [org.apache.catalina.core.StandardService] (main) Starting service jboss.web
> 2013-04-15 15:10:09,752 INFO [org.apache.catalina.core.StandardEngine] (main) Starting Servlet Engine: JBoss Web/2.1.12.GA-patch-01
> 2013-04-15 15:10:09,859 INFO [org.apache.catalina.startup.Catalina] (main) Server startup in 158 ms
> 2013-04-15 15:10:09,900 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jbossws
> 2013-04-15 15:10:10,511 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/invoker
> 2013-04-15 15:10:10,555 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/web-console
> 2013-04-15 15:10:10,987 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,002 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,011 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/jms-ra.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,024 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/mail-ra.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,045 INFO [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/home/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
> 2013-04-15 15:10:11,130 INFO [org.quartz.simpl.SimpleThreadPool] (main) Job execution threads will use class loader of thread: main
> 2013-04-15 15:10:11,155 INFO [org.quartz.core.QuartzScheduler] (main) Quartz Scheduler v.1.5.2 created.
> 2013-04-15 15:10:11,158 INFO [org.quartz.simpl.RAMJobStore] (main) RAMJobStore initialized.
> 2013-04-15 15:10:11,159 INFO [org.quartz.impl.StdSchedulerFactory] (main) Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
> 2013-04-15 15:10:11,159 INFO [org.quartz.impl.StdSchedulerFactory] (main) Quartz scheduler version: 1.5.2
> 2013-04-15 15:10:11,161 INFO [org.quartz.core.QuartzScheduler] (main) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> 2013-04-15 15:10:11,738 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
> 2013-04-15 15:10:12,161 INFO [org.jboss.jms.server.ServerPeer] (main) JBoss Messaging 1.4.8.SP5 server [0] started
> 2013-04-15 15:10:12,283 INFO [org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
> 2013-04-15 15:10:12,348 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://MARVIN.BRQ.REDHAT.COM:4457 has leasing enabled, lease period 10000 milliseconds
> 2013-04-15 15:10:12,348 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@a4dbd0f started
> 2013-04-15 15:10:12,351 INFO [org.jboss.jms.server.destination.QueueService] (main) Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
> 2013-04-15 15:10:12,352 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main) 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
> 2013-04-15 15:10:12,352 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper] (main) 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
> 2013-04-15 15:10:12,354 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://MARVIN.BRQ.REDHAT.COM:4457 has leasing enabled, lease period 10000 milliseconds
> 2013-04-15 15:10:12,354 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@606fdb4b started
> 2013-04-15 15:10:12,355 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) Connector bisocket://MARVIN.BRQ.REDHAT.COM:4457 has leasing enabled, lease period 10000 milliseconds
> 2013-04-15 15:10:12,355 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (main) org.jboss.jms.server.connectionfactory.ConnectionFactory@74bdaaa started
> 2013-04-15 15:10:12,473 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
> 2013-04-15 15:10:12,670 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/admin-console
> 2013-04-15 15:10:13,118 INFO [javax.enterprise.resource.webcontainer.jsf.config] (main) Initializing Mojarra (1.2_13-b01-FCS) for context '/admin-console'
> 2013-04-15 15:10:16,703 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/
> 2013-04-15 15:10:16,757 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jmx-console
> 2013-04-15 15:10:16,862 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Loading profile: ProfileKey@684640e6[domain=default, server=default, name=default]
> 2013-04-15 15:10:16,900 INFO [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:16,984 INFO [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:17,010 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.2 (build: SVNTag=JBPAPP_5_1_2 date=201111102209)] Started in 34s:709ms
> {code}
> But a few seconds after that strange things happen:
> {code}
> 2013-04-15 15:10:22,087 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/jmx-console
> 2013-04-15 15:10:22,118 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/
> 2013-04-15 15:10:22,143 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/admin-console
> 2013-04-15 15:10:22,245 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (HDScanner) Unbound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' from JNDI name 'java:JmsXA'
> 2013-04-15 15:10:22,261 INFO [org.jboss.jms.server.destination.QueueService] (HDScanner) Queue[/queue/ExpiryQueue] stopped
> 2013-04-15 15:10:22,262 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (HDScanner) org.jboss.jms.server.connectionfactory.ConnectionFactory@a4dbd0f undeployed
> 2013-04-15 15:10:22,263 INFO [org.jboss.jms.server.destination.QueueService] (HDScanner) Queue[/queue/DLQ] stopped
> 2013-04-15 15:10:22,263 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (HDScanner) org.jboss.jms.server.connectionfactory.ConnectionFactory@74bdaaa undeployed
> 2013-04-15 15:10:22,264 INFO [org.jboss.jms.server.connectionfactory.ConnectionFactory] (HDScanner) org.jboss.jms.server.connectionfactory.ConnectionFactory@606fdb4b undeployed
> 2013-04-15 15:10:22,294 INFO [org.jboss.jms.server.ServerPeer] (HDScanner) JMS ServerPeer[0] stopped
> 2013-04-15 15:10:22,300 INFO [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (HDScanner) Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' from JNDI name 'java:DefaultDS'
> 2013-04-15 15:10:22,694 INFO [org.jboss.jdbc.HypersonicDatabase] (HDScanner) Database standalone closed clean
> 2013-04-15 15:10:22,704 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
> 2013-04-15 15:10:22,704 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
> 2013-04-15 15:10:22,706 INFO [org.quartz.simpl.SimpleThreadPool] (HDScanner) There are still 35 worker threads active. See javadoc runInThread(Runnable) for a possible explanation
> 2013-04-15 15:10:22,706 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
> 2013-04-15 15:10:22,745 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/jbossws
> 2013-04-15 15:10:22,751 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/invoker
> 2013-04-15 15:10:22,756 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/web-console
> 2013-04-15 15:10:22,766 INFO [org.apache.coyote.http11.Http11Protocol] (HDScanner) Pausing Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:22,767 INFO [org.apache.coyote.http11.Http11Protocol] (HDScanner) Stopping Coyote HTTP/1.1 on http-marvin.brq.redhat.com%2F10.34.26.31-8080
> 2013-04-15 15:10:22,769 INFO [org.apache.coyote.ajp.AjpProtocol] (HDScanner) Pausing Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:22,770 INFO [org.apache.coyote.ajp.AjpProtocol] (HDScanner) Stopping Coyote AJP/1.3 on ajp-marvin.brq.redhat.com%2F10.34.26.31-8009
> 2013-04-15 15:10:22,777 INFO [org.apache.catalina.core.StandardService] (HDScanner) Stopping service jboss.web
> 2013-04-15 15:10:22,809 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) Stopping transaction recovery manager
> 2013-04-15 15:10:22,812 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) Destroying TransactionManagerService
> 2013-04-15 15:10:24,588 INFO [org.jboss.mail.MailService] (HDScanner) Mail service 'java:/Mail' removed from JNDI
> 2013-04-15 15:10:28,975 INFO [org.jboss.mail.MailService] (HDScanner) Mail Service bound to java:/Mail
> 2013-04-15 15:10:29,495 WARN [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (HDScanner) 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.
> 2013-04-15 15:10:30,814 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP12) - JBoss Inc.
> 2013-04-15 15:10:30,821 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (HDScanner) Setting up property manager MBean and JMX layer
> 2013-04-15 15:10:30,844 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Create: name=TransactionManager state=Configured
> com.arjuna.common.util.exceptions.ManagementPluginException: com.arjuna.common.util.exceptions.ManagementPluginException: Failed to register mbeans: javax.management.InstanceAlreadyExistsException: com.arjuna.ats.properties:module=arjuna already registered.
> at com.arjuna.common.internal.util.propertyservice.PropertyManagerImpl.addManagementPlugin(PropertyManagerImpl.java:496)
> at com.arjuna.ats.jbossatx.jta.TransactionManagerService.create(TransactionManagerService.java:193)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243)
> at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
> at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:125)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:52)
> at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> 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$201(ScheduledThreadPoolExecutor.java:165)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17745) NPE while editing ParamConverterProvider
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17745?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-17745:
------------------------------------
Assignee: Xavier Coulon
> NPE while editing ParamConverterProvider
> ----------------------------------------
>
> Key: JBIDE-17745
> URL: https://issues.jboss.org/browse/JBIDE-17745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140702-0157-B560
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> This issues happened while I was editing ParamConverterProvider but I was not able to reproduce this issue any more.
> {code}
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.addMarker(JaxrsMetamodelValidator.java:624)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validatePathParamAnnotation(JaxrsResourceMethodValidatorDelegate.java:414)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validateNoUnboundPathParamAnnotationValues(JaxrsResourceMethodValidatorDelegate.java:316)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:94)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:81)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:61)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:494)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:433)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17745) NPE while editing ParamConverterProvider
by Radoslav Rábara (JIRA)
Radoslav Rábara created JBIDE-17745:
---------------------------------------
Summary: NPE while editing ParamConverterProvider
Key: JBIDE-17745
URL: https://issues.jboss.org/browse/JBIDE-17745
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Beta3
Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140702-0157-B560
Reporter: Radoslav Rábara
Fix For: 4.2.0.Beta3
This issues happened while I was editing ParamConverterProvider but I was not able to reproduce this issue any more.
{code}
org.jboss.tools.common.validation.JBTValidationException
at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
Caused by: java.lang.NullPointerException
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.addMarker(JaxrsMetamodelValidator.java:624)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validatePathParamAnnotation(JaxrsResourceMethodValidatorDelegate.java:414)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validateNoUnboundPathParamAnnotationValues(JaxrsResourceMethodValidatorDelegate.java:316)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:94)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:1)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:81)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:61)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:1)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:494)
at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:433)
at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
... 4 more
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17212:
--------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Beta3)
> Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17212
> URL: https://issues.jboss.org/browse/JBIDE-17212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case.
> From JBIDE-7515:
> {quote}
> I left the shutdown script empty.
> You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't.
> In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1".
> {quote}
> The shutdown should default to process kill even if the shutdown script is empty.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17212:
-------------------------------------
Pushing to maintenance. As far as I can tell, this is working as expected.
> Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17212
> URL: https://issues.jboss.org/browse/JBIDE-17212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case.
> From JBIDE-7515:
> {quote}
> I left the shutdown script empty.
> You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't.
> In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1".
> {quote}
> The shutdown should default to process kill even if the shutdown script is empty.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17573) Download Runtimes window lacks properties when opened
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17573?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17573:
-------------------------------------
I made a commit which attempts to clear the selection after creating everything. I'm not sure if it will work. One thing I noticed is that even when I clear the selection, another 'selection event' is registered, and I can't find the cause. It seems to be some default behavior taken during the open. Really confused about it.
I guess we'll see if this works =/
[~mmalina] please test after a build of base.
> Download Runtimes window lacks properties when opened
> -----------------------------------------------------
>
> Key: JBIDE-17573
> URL: https://issues.jboss.org/browse/JBIDE-17573
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a B121
> OS X
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.0.Beta3
>
> Attachments: runtime-details.png
>
>
> When I open the Download Runtimes dialog, the first item is automatically selected (currently GateIn Portal 3.6.0), but the information box in the lower part of the window does not display Project URL and Download URL:
> !runtime-details.png!
> Once you change the selection to something else (and then even back to the first item), the properties are displayed alright.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBIDE-17744) IndexOutOfBound exception
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-17744:
-------------------------------------
Summary: IndexOutOfBound exception
Key: JBIDE-17744
URL: https://issues.jboss.org/browse/JBIDE-17744
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Beta2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.Beta3
{code}
Java Model Exception: Java Model Status [Index out of bounds]
at org.eclipse.jdt.internal.core.Openable.codeSelect(Openable.java:158)
at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:377)
at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:371)
at org.jboss.tools.ws.jaxrs.ui.navigation.JaxrsNameBindingHyperlinkDetector.getSelectedElements(JaxrsNameBindingHyperlinkDetector.java:95)
at org.jboss.tools.ws.jaxrs.ui.navigation.JaxrsNameBindingHyperlinkDetector.detectHyperlinks(JaxrsNameBindingHyperlinkDetector.java:70)
at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (JBDS-3033) Missing RichFaces maven archetypes
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3033?page=com.atlassian.jira.plugin.... ]
Fred Bricon resolved JBDS-3033.
-------------------------------
Labels: new_and_noteworthy (was: )
Release Notes Text: The Maven Central catalog is now available by default, providing more than 9600 archetypes to chose from, when creating a new Maven project.
Resolution: Done
Fixed in master. See release notes.
[~mmurray] : you might want to add something in the doc, but I don't know which status to give wrt docs
> Missing RichFaces maven archetypes
> ----------------------------------
>
> Key: JBDS-3033
> URL: https://issues.jboss.org/browse/JBDS-3033
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, maven
> Affects Versions: 8.0.0.Beta1
> Reporter: Juraj Húska
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 8.0.0.Beta3
>
>
> There is no RichFaces archetype available for selection, when trying to create a maven project.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months