May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11825) Remote server marked as started even if start failed

by Martin Malina (JIRA)

Martin Malina created JBIDE-11825: ------------------------------------- Summary: Remote server marked as started even if start failed Key: JBIDE-11825 URL: https://issues.jboss.org/browse/JBIDE-11825 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: JBT 3.3.0.Beta3 H141 Reporter: Martin Malina Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta3 When a remote AS7 fails to start (e.g. because of JBIDE-11824) and the process on the remote server stops immediately AS tooling still marks it as Started in server view. I think it is not acceptable to do that. Started should really mean started. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
5
0 / 0

[JBoss JIRA] (JBDS-2135) Paths added during installation are not added when JBDS starts with existing workspace

by Martin Malina (JIRA)

Martin Malina created JBDS-2135: ----------------------------------- Summary: Paths added during installation are not added when JBDS starts with existing workspace Key: JBDS-2135 URL: https://issues.jboss.org/browse/JBDS-2135 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: runtime Affects Versions: 5.0.0.Beta3 Environment: jbdevstudio-product-universal-5.0.0.v201205101833M-H138-Beta3.jar Reporter: Martin Malina Fix For: 5.0.0.CR1 When you add a path to be searched for runtimes during the installation of JBDS, it should be added and searched when you start JBDS after installation. This works under normal circumstances, but not in a specific case when you start your new JBDS installation with an existing workspace. In this case the path won't be searched nor included in the runtime paths. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (JBIDE-11900) Parameter subsitution value not taken into account when executing request

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-11900: ------------------------------------- Summary: Parameter subsitution value not taken into account when executing request Key: JBIDE-11900 URL: https://issues.jboss.org/browse/JBIDE-11900 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Reporter: Xavier Coulon Assignee: Yahor Radtsevich Fix For: 3.3.0.Beta3-SOA Using the KitchenSink quickstart from Central, when trying to run the WS tester with the following URL: {quote} http://localhost:8080/jboss-as-kitchensink/rest/members/\{id:[0-9][0-9]*\} {quote} a dialog appears to subsitute regexp with value, I set '1' and press ok, but the value is not taken into account, and the server complains about it: {code} 22:30:48,380 WARNING [org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher] (http-localhost-127.0.0.1-8080-2) Failed to parse request.: java.lang.IllegalArgumentException: You did not supply enough values to fill path parameters at org.jboss.resteasy.specimpl.UriBuilderImpl.buildFromValues(UriBuilderImpl.java:546) [resteasy-jaxrs-2.3.2.Final.jar:] ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (JBIDE-11989) Remote AS7 is broken - -Djboss.bind.address.management=null is set by default

by Martin Malina (JIRA)

Martin Malina created JBIDE-11989: ------------------------------------- Summary: Remote AS7 is broken - -Djboss.bind.address.management=null is set by default Key: JBIDE-11989 URL: https://issues.jboss.org/browse/JBIDE-11989 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: JBT trunk nightly 2012-05-24 Reporter: Martin Malina Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.CR1 When you setup a remote AS7 server (tried both 7.0.2 and 7.1.1) it will use -Djboss.bind.address.management=null in the launch command by default - this will break the start. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
10
0 / 0

[JBoss JIRA] (JBIDE-10947) Auto-detect and format JSON & XML in WS tester

by Jonathan Fuerth (JIRA)

Jonathan Fuerth created JBIDE-10947: --------------------------------------- Summary: Auto-detect and format JSON & XML in WS tester Key: JBIDE-10947 URL: https://issues.jboss.org/browse/JBIDE-10947 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Jonathan Fuerth When testing a web service, often the response data will be in JSON or XML format. It would be great if these could be auto-detected, syntax coloured, and (optionally?) reformatted and indented. Otherwise, I'm always going to have to copy the response data and paste it into jsonlint.com. :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
24
0 / 0

[JBoss JIRA] (JBIDE-11719) Deadlock in WS component tests

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-11719: ------------------------------------- Summary: Deadlock in WS component tests Key: JBIDE-11719 URL: https://issues.jboss.org/browse/JBIDE-11719 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Denis Golovin Assignee: Brian Fitzpatrick Fix For: 3.3.0.CR1 After running jbosstools build locally with tests overnight I got frozen eclipse window after build finished. Below is stack trace generated by jstack for stalled eclipse instance which tells problem is in starting JavaCore plugin manually as {code}org.eclipse.jdt.core.JavaCore.getPlugin().start(bundle.getBundleContext());{code} The stacktrace is: {code}Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.6-b01 mixed mode): "Attach Listener" daemon prio=10 tid=0x00007fa044001000 nid=0x3cd3 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "[ThreadPool Manager] - Idle Thread" daemon prio=10 tid=0x00007fa020012000 nid=0x6c96 in Object.wait() [0x00007f9fab3f9000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106) - locked <0x00000000f6d31638> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) "WorkbenchTestable" prio=10 tid=0x00007fa07c91c800 nid=0x6c15 in Object.wait() [0x00007f9fb83a1000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c1d39810> (a org.eclipse.swt.widgets.RunnableLock) at java.lang.Object.wait(Object.java:485) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187) - locked <0x00000000c1d39810> (a org.eclipse.swt.widgets.RunnableLock) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4330) at org.eclipse.ui.internal.testing.WorkbenchTestable.runTest(WorkbenchTestable.java:112) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:32) at org.eclipse.ui.internal.testing.WorkbenchTestable$1.run(WorkbenchTestable.java:71) at java.lang.Thread.run(Thread.java:662) "Worker-5" prio=10 tid=0x00007f9f94001000 nid=0x6c13 in Object.wait() [0x00007f9fb85a3000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) - locked <0x00000000c133c9a0> (a org.eclipse.core.internal.jobs.WorkerPool) at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:50) "Worker-3" prio=10 tid=0x00007f9f9c001000 nid=0x6c11 in Object.wait() [0x00007f9fb87a5000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.core.internal.jobs.WorkerPool.sleep(WorkerPool.java:188) - locked <0x00000000c133c9a0> (a org.eclipse.core.internal.jobs.WorkerPool) at org.eclipse.core.internal.jobs.WorkerPool.startJob(WorkerPool.java:220) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:50) "Worker-2" prio=10 tid=0x00007f9f98001000 nid=0x6c10 waiting for monitor entry [0x00007f9fb88a6000] java.lang.Thread.State: BLOCKED (on object monitor) at org.eclipse.jdt.internal.core.search.processing.JobManager.currentJob(JobManager.java:58) - waiting to lock <0x00000000c133d040> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) at org.eclipse.jdt.internal.core.search.processing.JobManager$1$ProgressJob.run(JobManager.java:359) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) "Worker-1" prio=10 tid=0x00007fa00c006800 nid=0x6c0f sleeping[0x00007fa0785b8000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:301) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) "Java indexing" daemon prio=10 tid=0x00007fa07c707800 nid=0x6c06 waiting for monitor entry [0x00007fa00b889000] java.lang.Thread.State: BLOCKED (on object monitor) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:777) - waiting to lock <0x00000000c133d040> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) at org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execute(AddJarFileToIndex.java:180) at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:405) at java.lang.Thread.run(Thread.java:662) "Worker-JM" prio=10 tid=0x00007fa024131000 nid=0x6c02 in Object.wait() [0x00007fa0781fd000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c17fb130> (a java.util.ArrayList) at org.eclipse.core.internal.jobs.InternalWorker.run(InternalWorker.java:58) - locked <0x00000000c17fb130> (a java.util.ArrayList) "[Timer] - Main Queue Handler" daemon prio=10 tid=0x00007fa02407a800 nid=0x6c01 in Object.wait() [0x00007fa0782fe000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:141) - locked <0x00000000c177a2d0> (a java.lang.Object) at java.lang.Thread.run(Thread.java:662) "Bundle File Closer" daemon prio=10 tid=0x00007fa07c6ca000 nid=0x6bfe in Object.wait() [0x00007fa0787e0000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c177a390> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at java.lang.Object.wait(Object.java:485) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) - locked <0x00000000c177a390> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) "Start Level Event Dispatcher" daemon prio=10 tid=0x00007fa07c10d800 nid=0x6bfd in Object.wait() [0x00007fa078af2000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c177a590> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at java.lang.Object.wait(Object.java:485) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) - locked <0x00000000c177a590> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) "Framework Event Dispatcher" daemon prio=10 tid=0x00007fa07c241000 nid=0x6bfc in Object.wait() [0x00007fa078bf3000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c177b118> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at java.lang.Object.wait(Object.java:485) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:400) - locked <0x00000000c177b118> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:336) "Framework Active Thread" prio=10 tid=0x00007fa07c22b800 nid=0x6bfa in Object.wait() [0x00007fa078df5000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.osgi.framework.internal.core.Framework.run(Framework.java:1817) - locked <0x00000000c0fbd460> (a org.eclipse.osgi.framework.internal.core.Framework) at java.lang.Thread.run(Thread.java:662) "Low Memory Detector" daemon prio=10 tid=0x00007fa07c152800 nid=0x6bf8 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "C2 CompilerThread1" daemon prio=10 tid=0x00007fa07c150000 nid=0x6bf7 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "C2 CompilerThread0" daemon prio=10 tid=0x00007fa07c0e2000 nid=0x6bf6 waiting on condition [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Signal Dispatcher" daemon prio=10 tid=0x00007fa07c0bb000 nid=0x6bf5 runnable [0x0000000000000000] java.lang.Thread.State: RUNNABLE "Finalizer" daemon prio=10 tid=0x00007fa07c09e800 nid=0x6bf4 in Object.wait() [0x00007fa080a5e000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c18360a8> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118) - locked <0x00000000c18360a8> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) "Reference Handler" daemon prio=10 tid=0x00007fa07c09d000 nid=0x6bf3 in Object.wait() [0x00007fa080b5f000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x00000000c1836068> (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:485) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) - locked <0x00000000c1836068> (a java.lang.ref.Reference$Lock) "main" prio=10 tid=0x00007fa07c009800 nid=0x6be9 waiting on condition [0x00007fa083336000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at org.eclipse.jdt.internal.core.search.processing.JobManager.discardJobs(JobManager.java:91) at org.eclipse.jdt.internal.core.search.processing.JobManager.reset(JobManager.java:321) - locked <0x00000000c133d040> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.reset(IndexManager.java:732) - locked <0x00000000c133d040> (a org.eclipse.jdt.internal.core.search.indexing.IndexManager) at org.eclipse.jdt.internal.core.JavaModelManager.startIndexing(JavaModelManager.java:4944) at org.eclipse.jdt.internal.core.JavaModelManager.startup(JavaModelManager.java:4902) at org.eclipse.jdt.core.JavaCore.start(JavaCore.java:5158) at org.jboss.tools.ws.jaxrs.core.AbstractCommonTestCase.setupWorkspace(AbstractCommonTestCase.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:24) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:84) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) - locked <0x00000000c1d39810> (a org.eclipse.swt.widgets.RunnableLock) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) "VM Thread" prio=10 tid=0x00007fa07c096000 nid=0x6bf2 runnable "GC task thread#0 (ParallelGC)" prio=10 tid=0x00007fa07c01c800 nid=0x6bea runnable "GC task thread#1 (ParallelGC)" prio=10 tid=0x00007fa07c01e800 nid=0x6beb runnable "GC task thread#2 (ParallelGC)" prio=10 tid=0x00007fa07c020000 nid=0x6bec runnable "GC task thread#3 (ParallelGC)" prio=10 tid=0x00007fa07c022000 nid=0x6bed runnable "GC task thread#4 (ParallelGC)" prio=10 tid=0x00007fa07c024000 nid=0x6bee runnable "GC task thread#5 (ParallelGC)" prio=10 tid=0x00007fa07c025800 nid=0x6bef runnable "GC task thread#6 (ParallelGC)" prio=10 tid=0x00007fa07c027800 nid=0x6bf0 runnable "GC task thread#7 (ParallelGC)" prio=10 tid=0x00007fa07c029000 nid=0x6bf1 runnable "VM Periodic Task Thread" prio=10 tid=0x00007fa07c155000 nid=0x6bf9 waiting on condition JNI global references: 2441 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
7
0 / 0

[JBoss JIRA] (JBIDE-11704) test timeout after 1800 seconds in org.jboss.tools.ws.jaxrs.core.test

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11704: ---------------------------------- Summary: test timeout after 1800 seconds in org.jboss.tools.ws.jaxrs.core.test Key: JBIDE-11704 URL: https://issues.jboss.org/browse/JBIDE-11704 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta3 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.14.1:test (default-test) on project org.jboss.tools.ws.jaxrs.core.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 1800 seconds -> [Help 1] https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
6
0 / 0

[JBoss JIRA] (JBIDE-11728) Wrong JAX-RS web service URL in Web Service Tester after setting query parameters in "WS Tester: URL parameters" dialog

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11728: ----------------------------------------- Summary: Wrong JAX-RS web service URL in Web Service Tester after setting query parameters in "WS Tester: URL parameters" dialog Key: JBIDE-11728 URL: https://issues.jboss.org/browse/JBIDE-11728 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta3, 3.3.0.CR1 When I invoke Web Service Tester with Context Menu of JAX-RS method in JAX-RS explorer, URL of JAX-RS web service is correct: in my case: "http://localhost:8080/project2/MyRESTApplication/query?name={name:java.la...". When I click on Invoke button, dialog for setting parameters is shown. So I set "name" query parameter and click OK. After this step, URL in Web Service Tester has changed to "http:/localhost:8080/project2/MyRESTApplication/query?name=user". There is one less slash after http:. Response on this URL is "Connection Refused". If you add one slash after http:, everything is working again :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
4
0 / 0

[JBoss JIRA] (JBIDE-11771) Cannot set URL parameter in "WS Tester: URL parameters" dialog when default values are used

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11771: ----------------------------------------- Summary: Cannot set URL parameter in "WS Tester: URL parameters" dialog when default values are used Key: JBIDE-11771 URL: https://issues.jboss.org/browse/JBIDE-11771 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.CR1 Attachments: 01_regexp_validation.png When trying to set any value for URL parameters, it says: is not valid based on the regular expression "java.lang.String=default1". There is wrong regular expression validation, it seems it involves default value in validation computation as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
5
0 / 0

[JBoss JIRA] (JBIDE-11770) "WS Tester: URL parameters" dialog cannot be confirmed with default values

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11770: ----------------------------------------- Summary: "WS Tester: URL parameters" dialog cannot be confirmed with default values Key: JBIDE-11770 URL: https://issues.jboss.org/browse/JBIDE-11770 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta3 Reporter: Jaroslav Jankovič Assignee: Brian Fitzpatrick Fix For: 3.3.0.CR1 When using @DefaultValue with some *Path parameters (PathParam, QueryParam, MatrixParam ...) and invoking this method in Web Service Tester (JAX-RS REST Web Services explorer) I tried to call GET method. Dialog for setting parameters showed. I couldn't click OK button because I didn't set any of values, but as I set default values for each of them I should be able to confirm the dialog and default values should be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2012