[JBoss JIRA] (JBDS-2992) Generated CustomerWebServiceTest can not run on JBoss Dev Studio integration-stack
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-2992?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBDS-2992.
----------------------------
Fix Version/s: 7.1.x
Resolution: Done
I was able to reproduce this bug with JBDSIS 7.0.0.GA - this issue no longer exists with JBDSIS 7.0.1.CR2. Please retest using this update site URL:
https://devstudio.jboss.com/updates/7.0-development/integration-stack/
> Generated CustomerWebServiceTest can not run on JBoss Dev Studio integration-stack
> ----------------------------------------------------------------------------------
>
> Key: JBDS-2992
> URL: https://issues.jboss.org/browse/JBDS-2992
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration
> Environment: Both RHEL and Windows
> Oracle JDK1.7.0_25
> JBDS7.1.1
> updated Fuse integration-stack
> Reporter: Xiaohui Wu
> Assignee: Paul Leacu
> Fix For: 7.1.x
>
>
> Added Fuse integration-stack to JBoss Dev Studio at: https://devstudio.jboss.com/updates/7.0/integration-stack/
> Following instructions here:
> http://www.jboss.org/products/fuse
> Created new project using camel-webservice archetype. Build it, and try to Run As -> Local Camel Context. You will see there is an erro indicated cannot find the file:
> {code}
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [META-INF/spring/camelContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [META-INF/spring/camelContext.xml] cannot be opened because it does not exist
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209)
> {code}
> in fact the generated fileName is CamelContext.xml, not camelContext.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBDS-2992) Generated CustomerWebServiceTest can not run on JBoss Dev Studio integration-stack
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBDS-2992?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBDS-2992:
--------------------------------
Assignee: Paul Leacu
> Generated CustomerWebServiceTest can not run on JBoss Dev Studio integration-stack
> ----------------------------------------------------------------------------------
>
> Key: JBDS-2992
> URL: https://issues.jboss.org/browse/JBDS-2992
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration
> Environment: Both RHEL and Windows
> Oracle JDK1.7.0_25
> JBDS7.1.1
> updated Fuse integration-stack
> Reporter: Xiaohui Wu
> Assignee: Paul Leacu
>
> Added Fuse integration-stack to JBoss Dev Studio at: https://devstudio.jboss.com/updates/7.0/integration-stack/
> Following instructions here:
> http://www.jboss.org/products/fuse
> Created new project using camel-webservice archetype. Build it, and try to Run As -> Local Camel Context. You will see there is an erro indicated cannot find the file:
> {code}
> org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [META-INF/spring/camelContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [META-INF/spring/camelContext.xml] cannot be opened because it does not exist
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)
> at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
> at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209)
> {code}
> in fact the generated fileName is CamelContext.xml, not camelContext.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBIDE-15807) Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15807?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-15807.
------------------------------------
This was fixed since JBT4.2.0.Alpha1 was able to successfully start. Closing.
> Eclipe 4.4M3 with jbosstoolstarget-4.40.0.Alpa1-SNAPSHOT target platform does not start
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-15807
> URL: https://issues.jboss.org/browse/JBIDE-15807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.2.0.Alpha1
> Reporter: Daniel Azarov
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.0.Alpha2
>
> Attachments: mat.png, scr.png
>
>
> 1. I tried to run JBDS from developer's environment with vm args - -XX:MaxPermSize=512m -Xms1024m -Xmx2048m with all plugins from my workspace
> and I got follow exception:
> {code}
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.createEntry(HashMap.java:869)
> at java.util.HashMap.addEntry(HashMap.java:856)
> at java.util.HashMap.put(HashMap.java:484)
> at org.apache.felix.resolver.Candidates.copy(Candidates.java:1002)
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1288)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1083)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:261)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.refresh(ModuleContainer.java:877)
> at org.eclipse.osgi.storage.Storage.discardBundlesOnLoad(Storage.java:206)
> at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:87)
> at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:75)
> at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:287)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222)
> 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:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> 2. If I try to run new run configuration with only plugins from target platform I got follow stack trace:
> {code}
> !SESSION 2013-10-28 10:29:47.350 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_24
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.platform.ide
> Command-line arguments: -product org.eclipse.platform.ide -data /home/daniel/workspaces/JBDS_GIT/../runtime-New_configuration(2) -dev file:/home/daniel/workspaces/JBDS_GIT/.metadata/.plugins/org.eclipse.pde.core/New_configuration (2)/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog
> !ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2013-10-28 10:36:19.748
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Exception in org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle org.eclipse.equinox.simpleconfigurator.
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:782)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:151)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.osgi.launch.Equinox.start(Equinox.java:115)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:310)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:222)
> 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.addEntry(HashMap.java:770)
> at java.util.HashMap.put(HashMap.java:402)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196)
> at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> Root exception:
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.addEntry(HashMap.java:770)
> at java.util.HashMap.put(HashMap.java:402)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:960)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:451)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:409)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:399)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:347)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:427)
> at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:109)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:182)
> at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:196)
> at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:761)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:754)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:717)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:869)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:257)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1455)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1438)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1416)
> at org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:216)
> at org.eclipse.osgi.container.Module.doStart(Module.java:556)
> at org.eclipse.osgi.container.Module.start(Module.java:427)
> {code}
> 3. If I try same as 2. but with "Running Platform" as target platform - eclipse starts
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBIDE-16950) Very frequently, webapps are being undeployed right after being deployed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16950?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-16950:
---------------------------------------
I tried to replicate this on Windows 7, but still no luck.
> Very frequently, webapps are being undeployed right after being deployed
> ------------------------------------------------------------------------
>
> Key: JBIDE-16950
> URL: https://issues.jboss.org/browse/JBIDE-16950
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Environment: Win 7-64, JDK 7, AS 7.1.1, WildFly 8.0.0
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.Beta1
>
>
> I'm experiencing this issue where, after doing a full publishing, the deployed webapp is being undeployed right after being deployed.
> See http://screencast.com/t/JmwA0TlBrDWX
> The most reliable way (even though it's not 10% of the time) to reproduce the issue is to deploy a webapp to AS 7.1.1 or WF8, then remove it from the server, deploy it back. That's when the problem occurs :
> {noformat}
> 14:13:45,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:45,485 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /dontundeployme
> 14:13:45,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed "dontundeployme.war" (runtime-name : "dontundeployme.war")
> 14:13:50,708 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017535: Unregistered web context: /dontundeployme
> 14:13:50,730 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment dontundeployme.war (runtime-name: dontundeployme.war) in 23ms
> 14:13:50,999 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dontundeployme.war" (runtime-name: "dontundeployme.war")
> 14:13:56,004 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dontundeployme.war in deployment directory. To trigger deployment create a file called dontundeployme.war.dodeploy
> {noformat}
> Also, pretty quite frequently, deployment just fails (but I haven't been able to figure out a decisive pattern yet) as the server thinks deployments are duplicates (see screencast)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years