[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17733:
----------------------------------------
[~fbricon] Are you aware of any example that references the EGit connector in Central?
> Remove EGit from Central Discovery
> ----------------------------------
>
> Key: JBIDE-17733
> URL: https://issues.jboss.org/browse/JBIDE-17733
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: discovery
> Affects Versions: 4.2.0.Beta2
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta3
>
>
> Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed.
> So we should remove EGit from our Central discovery catalogs.
--
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 edited comment on JBIDE-14027 at 7/1/14 8:17 AM:
-------------------------------------------------------------
[~mmalina] With 3.0.0.Beta3-v20140630-1657-B543 I get the same error. But that was built yesterday morning I guess? So I will try again tomorrow and see if a v20140701 build is available.
was (Author: axelw):
[~mmalina] With 3.0.0.Beta3-v20140630-1657-B543 I get the same error. But that was built yesterday morning i guess? So I will try again tomorrow and see if a v20140701 build is available.
> 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-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 edited comment on JBIDE-17700 at 7/1/14 8:18 AM:
-------------------------------------------------------------
Now when I publish the war the exception comes up which lead me to this tracker entry...restarted eclipse and it works.
was (Author: olpf):
Now when I publish the war the exception comes up which lead me to this tracker entry.
> 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
[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:
-------------------------------------
[~mmalina] With 3.0.0.Beta3-v20140630-1657-B543 I get the same error. But that was built yesterday morning i guess? So I will try again tomorrow and see if a v20140701 build is available.
> 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-17733) Remove EGit from Central Discovery
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17733:
---------------------------------------------
I wonder when it was added actually.
But as always with central connectors the main issue is if we have any examples that declare it needs the egit connector. if yes, thats problematic, if no - then it makes sense to remove.
> Remove EGit from Central Discovery
> ----------------------------------
>
> Key: JBIDE-17733
> URL: https://issues.jboss.org/browse/JBIDE-17733
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: discovery
> Affects Versions: 4.2.0.Beta2
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta3
>
>
> Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed.
> So we should remove EGit from our Central discovery catalogs.
--
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:
-------------------------------------
After I killed eclipse and restarted it has a problem with the workspace. Found an exception in the .log:
!ENTRY org.jboss.tools.common 4 0 2014-06-30 15:19:44.405
!MESSAGE
!STACK 0
org.jboss.tools.common.validation.JBTValidationException
at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:188)
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.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254)
at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381)
at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259)
at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95)
at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269)
at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321)
at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258)
at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691)
Caused by: java.lang.NullPointerException
at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:179)
... 10 more
On the next start the exception seems to be away (no error dialog on start)
> 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
[JBoss JIRA] (JBIDE-17404) CordovaSim cannot be launched on RHEL7
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-17404.
--------------------------------------------
Resolution: Done
Please verify this issue with/without libs described in comment above
> CordovaSim cannot be launched on RHEL7
> --------------------------------------
>
> Key: JBIDE-17404
> URL: https://issues.jboss.org/browse/JBIDE-17404
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Environment: RHEL7 latest, 64bit
> Installed webkitgtk3-devel 0:2.0.4-6-el7
> TicketMonster Cordava example from latest WFK
> JBDS 8.0.0.Beta1
> OpenJDK 7
> Reporter: Karel Piwko
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta3
>
> Attachments: CordovaSimFailure.png, snapshot1.png
>
>
> Launching BrowserSim fails with NPE, adding information from workspace log
> Before webkitgtk3-devel is installed
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162
> !MESSAGE BrowserSim is failed to start with the following error:
> "No more handles"
> Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path.
> If not, use your package manager to install libwebkitgtk.
> Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>.
> Stack trace:
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84)
> {code}
> After:
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395
> !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17733) Remove EGit from Central Discovery
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17733?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17733:
-----------------------------------
Fix Version/s: 4.2.0.Beta3
> Remove EGit from Central Discovery
> ----------------------------------
>
> Key: JBIDE-17733
> URL: https://issues.jboss.org/browse/JBIDE-17733
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: discovery
> Affects Versions: 4.2.0.Beta2
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta3
>
>
> Egit is already included in all Eclipse packages we target (JEE, Standard, PDE, if not all) and is included in JBDS product definition. It is also a dependency of OpenShift tooling so that anything that has OpenShift tools installed is guaranteed to have EGit installed.
> So we should remove EGit from our Central discovery catalogs.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months