[JBoss JIRA] (JBIDE-17743) Manage SSH Keys shell has incorrectly aligned data
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17743?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17743:
----------------------------------
Description:
Specific SSH keys data in the table containing SSH keys in Manage SSH Keys are aligned to the left. It should be aligned to the right or the best to the center. See Type or Content columns.
!ssh_alignement.png!
was:
Specific SSH keys in the table containing SSH keys in Manage SSH Keys are aligned to the left. It should be aligned to the right or the best to the center.
!ssh_alignement.png!
> Manage SSH Keys shell has incorrectly aligned data
> --------------------------------------------------
>
> Key: JBIDE-17743
> URL: https://issues.jboss.org/browse/JBIDE-17743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Attachments: ssh_alignement.png
>
>
> Specific SSH keys data in the table containing SSH keys in Manage SSH Keys are aligned to the left. It should be aligned to the right or the best to the center. See Type or Content columns.
> !ssh_alignement.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 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 commented on JBIDE-14027:
---------------------------------------
Thanks for verifying, Axel.
> 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, 4.2.0.Beta3
>
> 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)
11 years, 9 months
[JBoss JIRA] (JBIDE-17743) Manage SSH Keys shell has incorrectly aligned data
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-17743:
-------------------------------------
Summary: Manage SSH Keys shell has incorrectly aligned data
Key: JBIDE-17743
URL: https://issues.jboss.org/browse/JBIDE-17743
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Beta3
Reporter: Marián Labuda
Priority: Minor
Attachments: ssh_alignement.png
Specific SSH keys in the table containing SSH keys in Manage SSH Keys are aligned to the left. It should be aligned to the right or the best to the center.
!ssh_alignement.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-14027) Remote EAP 5 fails to start correctly
by Axel Wathne (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14027?page=com.atlassian.jira.plugi... ]
Axel Wathne commented on JBIDE-14027:
-------------------------------------
Verified OK with 3.0.0.Beta3-v20140701-1056-B545 for both "default" and "all" profiles. Thank you guys.
> 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, 4.2.0.Beta3
>
> 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)
11 years, 9 months
[JBoss JIRA] (JBIDE-17722) Cannot edit custom deployment directory in server editor
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17722?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17722.
---------------------------------
Resolution: Done
I made a commit which adds a few apis but does not change existing ones. There was a lack of API for subsystems to work with working copies. While on the lowest level, the infrastructure was there, there were no easy methods to acquire a subsystem controller instantiated with a working copy.
This means the editor was always pulling data from the last saved server, and this was making the fields appear unchanged.
> Cannot edit custom deployment directory in server editor
> --------------------------------------------------------
>
> Key: JBIDE-17722
> URL: https://issues.jboss.org/browse/JBIDE-17722
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2
> JBoss Tools 4.2.0.Beta3-SNAPSHOT - nightly build from 2014/06/30
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta3
>
>
> This happens in both JBDS 8 Beta2 and JBT master nightly from today.
> When you try to use a custom dir for deployment on an AS5-style server, the field cannot be edited. Both on Mac and Windows (so probably Linux as well).
> What happens is that every time you try to type something (even delete/backspace), the cursor will just move to the front and nothing will happen.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17722) Cannot edit custom deployment directory in server editor
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17722?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17722:
-------------------------------------
Another thing that was fixed is that the editor was only showing absolute paths in the custom field, all the time. This has been fixed.
> Cannot edit custom deployment directory in server editor
> --------------------------------------------------------
>
> Key: JBIDE-17722
> URL: https://issues.jboss.org/browse/JBIDE-17722
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2
> JBoss Tools 4.2.0.Beta3-SNAPSHOT - nightly build from 2014/06/30
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta3
>
>
> This happens in both JBDS 8 Beta2 and JBT master nightly from today.
> When you try to use a custom dir for deployment on an AS5-style server, the field cannot be edited. Both on Mac and Windows (so probably Linux as well).
> What happens is that every time you try to type something (even delete/backspace), the cursor will just move to the front and nothing will happen.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-17696:
------------------------------------------
With -consoleLog -debug /path/to/the/.option I'm getting exception when updating maven configuration
{code}
org.eclipse.core.runtime.AssertionFailedException: assertion failed: ThreadJob(Updating Maven Project(1602),[MultiRule[R/],R/,R/]) conflicts and ran simultaneously with Updating Maven Project(1602)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
at org.eclipse.core.internal.jobs.JobManager.yieldRule(JobManager.java:1452)
at org.eclipse.core.internal.jobs.InternalJob.yieldRule(InternalJob.java:603)
at org.eclipse.core.runtime.jobs.Job.yieldRule(Job.java:760)
at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.waitForAllUpdates(DependencyGraphImpl.java:691)
at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.getReferencingComponents(DependencyGraphImpl.java:126)
at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.getReferencingComponents(DependencyGraphImpl.java:116)
at org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getReferencingComponents(VirtualComponent.java:579)
at org.eclipse.jst.j2ee.project.EarUtilities.getReferencingEARProjects(EarUtilities.java:274)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:370)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:118)
at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:747)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:876)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:291)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.clean(MavenBuilder.java:211)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:736)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:263)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:401)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
at org.eclipse.core.internal.resources.Project.build(Project.java:114)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:435)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
I was able to reproduce the issue using automated UI tests (I tried manually but I was not able to do so due to exception mentioned above).
Output i got:
{code}
[Thread[Worker-20,5,main]]Enabling Maven Dependency Management(1213) will yieldRule to ThreadJob(null,[P/testWEB_JPA_noRuntime])
[Thread[Worker-20,5,main]]Enabling Maven Dependency Management(1213) will yieldRule to ThreadJob(null,[P/testWEB_JPA_noRuntime])
[Thread[Worker-20,5,main]]Enabling Maven Dependency Management(1213) is waiting for ThreadJob(null,[P/testWEB_JPA_noRuntime]) to transition from WAITING state
{code}
If this is not enough, I can try manually again, but it might take some time.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x
by Oliver Pfau (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Oliver Pfau commented on JBIDE-17700:
-------------------------------------
Grep found the following:
Name Size Matches Path Encoding Date modified
.tmp8717534468579802689.instance 0 Bytes read error D:\EclipseRoot\eclipse_luna_64\configuration\org.eclipse.core.runtime\.manager 02.07.2014 08:26:03
.tmp5440640297512662375.instance 0 Bytes read error D:\EclipseRoot\eclipse_luna_64\configuration\org.eclipse.equinox.app\.manager 02.07.2014 08:26:08
plexus-classworlds-2.5.1.jar 48,6 KB 90 D:\EclipseRoot\eclipse_luna_64\plugins\org.eclipse.m2e.maven.runtime_1.5.0.20140605-2032\jars BINARY 05.05.2014 21:10:58
ECLIPSE_.SF 3,50 KB 1 D:\EclipseRoot\eclipse_luna_64\plugins\org.eclipse.m2e.maven.runtime_1.5.0.20140605-2032\META-INF ANSI 06.06.2014 02:32:34
MANIFEST.MF 16,7 KB 6 D:\EclipseRoot\eclipse_luna_64\plugins\org.eclipse.m2e.maven.runtime_1.5.0.20140605-2032\META-INF ANSI 06.06.2014 02:32:32
module.xml 2,27 KB 1 D:\EclipseRoot\eclipse_luna_64\plugins\org.jboss.tools.forge.runtime_1.4.144.Beta2-v20140523-1507-B33\forge-distribution-1.4.4.Final\modules\org\jboss\forge\maven\api\main ANSI 24.01.2014 19:19:48
plexus-classworlds-2.4.jar 45,9 KB 90 D:\EclipseRoot\eclipse_luna_64\plugins\org.jboss.tools.forge.runtime_1.4.144.Beta2-v20140523-1507-B33\forge-distribution-1.4.4.Final\modules\org\jboss\forge\maven\api\main BINARY 24.01.2014 19:19:48
plexus-classworlds-2.5.1.jar 48,6 KB 90 D:\EclipseRoot\eclipse_luna_64\plugins\org.jboss.tools.forge2.runtime_2.0.1.Beta2-v20140523-1507-B33\addon-repository\org-jboss-forge-addon-maven-2-6-0-Final BINARY 23.05.2014 11:14:54
> Cannot deploy jsf war with eclipse luna and jboss 7.1.x
> -------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Priority: Critical
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months