[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19184:
--------------------------------------
Assignee: Victor Rubezhny (was: Max Rydahl Andersen)
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JSF projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19184:
-----------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-19184 (was: JBDS-3339)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Affects Version/s: 4.2.2.Final
(was: 8.0.2.GA)
Component/s: jsp/jsf/xml/html source editing
(was: jsp/jsf/xml/html source editing)
Docs QE Status: (was: NEW)
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JSF projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19184:
-----------------------------------
Fix Version/s: 4.2.3.Beta1
4.3.0.Alpha2
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JSF projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19184:
-----------------------------------
Priority: Critical (was: Major)
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JSF projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19049:
-------------------------------------
I've bumped this to 'later'. The entire notion of a classpath probably needs to change substantially.
Aside from that, it seems wf 8.2 does not run with java9 via cmd line:
{code}
[rob@localhost bin]$ export JAVA_HOME=/home/rob/apps/java/jdk9/jdk1.9.0/
[rob@localhost bin]$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/rob/apps/jboss/unzipped/wildfly-8.2.0.CR1-SNAPSHOT.zip.expanded
JAVA: /home/rob/apps/java/jdk9/jdk1.9.0//bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
Unrecognized VM option 'MaxPermSize=256m'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}
> Enable JBoss servers to run with java 9
> ---------------------------------------
>
> Key: JBIDE-19049
> URL: https://issues.jboss.org/browse/JBIDE-19049
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: Java9
> Fix For: LATER
>
>
> I briefly tried to use java 9 for our tooling and to run servers.
> I downloaded it from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> I use OS X 10.10 Yosemite.
> There are a couple of problems:
> 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
> 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
> {code}
> nattura:bin rasp$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3339) Threadlock when JS autocomplete turned on
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3339?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3339:
-------------------------------------
Steps to replicate it could be to place mouse pointer over some JS element and ask for content assist at the same time for huge JS project. Stack trace indicates that hover presenter and proposals calculation stuck on lock introduced by request to tern to sync files.
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBDS-3339
> URL: https://issues.jboss.org/browse/JBDS-3339
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 8.0.2.GA
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Max Rydahl Andersen
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JSF projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3199) Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3199?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3199:
-----------------------------------
looks good to me. Ship it [~manaRH]!!! :-)
> Creating a new HTML5 "from scratch" retains "kitchensink" string in datasources instead of picking up actual project names
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3199
> URL: https://issues.jboss.org/browse/JBDS-3199
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 8.1.0.GA
>
>
> These "kitchensink" strings are retained:
> grep -ir kitchen *
> main/resources/META-INF/persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS</jta-data-source>
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileQuickstartDS"
> main/webapp/WEB-INF/kitchensink-quickstart-ds.xml: pool-name="kitchensink-quickstart" enabled="true"
> test/resources/arquillian-ds.xml: <datasource jndi-name="java:jboss/datasources/KitchensinkHTML5MobileTestDS"
> test/resources/META-INF/test-persistence.xml: <jta-data-source>java:jboss/datasources/KitchensinkHTML5MobileTestDS</jta-data-source>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-19049:
--------------------------------
Fix Version/s: LATER
(was: 4.3.0.Alpha1)
> Enable JBoss servers to run with java 9
> ---------------------------------------
>
> Key: JBIDE-19049
> URL: https://issues.jboss.org/browse/JBIDE-19049
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: Java9
> Fix For: LATER
>
>
> I briefly tried to use java 9 for our tooling and to run servers.
> I downloaded it from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> I use OS X 10.10 Yosemite.
> There are a couple of problems:
> 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
> 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
> {code}
> nattura:bin rasp$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19049:
-------------------------------------
{quote}
We're not yet at the point
where a tool running on a build of JDK 9 or JDK 10 can access the
contents of different JDK 9 or JDK 10 build but we'll get there (in a
few months I hope, there are a few issues to sort out first and a number
of other big changes in this areas that are higher priority at the moment).
{quote}
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-February.txt
> Enable JBoss servers to run with java 9
> ---------------------------------------
>
> Key: JBIDE-19049
> URL: https://issues.jboss.org/browse/JBIDE-19049
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.2.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: Java9
> Fix For: 4.3.0.Alpha1
>
>
> I briefly tried to use java 9 for our tooling and to run servers.
> I downloaded it from here:
> https://jdk9.java.net/download/
> {code}
> nattura:8.0.2 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
> {code}
> I use OS X 10.10 Yosemite.
> There are a couple of problems:
> 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
> 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
> {code}
> nattura:bin rasp$ ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
> JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> Unrecognized VM option 'MaxPermSize=256m'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19183) Constant AssertionFailedExceptions from FreeMarker Editor
by Eric Sirianni (JIRA)
Eric Sirianni created JBIDE-19183:
-------------------------------------
Summary: Constant AssertionFailedExceptions from FreeMarker Editor
Key: JBIDE-19183
URL: https://issues.jboss.org/browse/JBIDE-19183
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: freemarker
Environment: Eclipse 4.4.1
Linux
Reporter: Eric Sirianni
I get constant "assertion failed" errors in the freemarker editor. The error is associated with the following stack trace in my eclipse log:
{noformat}
!ENTRY org.eclipse.ui 4 0 2015-02-06 12:28:37.974
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: assertion failed:
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
at org.eclipse.jface.text.Position.setLength(Position.java:185)
at org.eclipse.jface.text.rules.FastPartitioner.computePartitioning(FastPartitioner.java:634)
at org.eclipse.jface.text.AbstractDocument.computePartitioning(AbstractDocument.java:1430)
at org.eclipse.jface.text.TextUtilities.computePartitioning(TextUtilities.java:431)
at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:451)
at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:569)
at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:567)
at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:227)
at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2830)
at org.eclipse.jface.text.TextViewer.invalidateTextPresentation(TextViewer.java:3501)
at org.jboss.ide.eclipse.freemarker.editor.Editor.resetRange(Editor.java:282)
at org.jboss.ide.eclipse.freemarker.editor.Editor.highlightRelatedRegions(Editor.java:257)
at org.jboss.ide.eclipse.freemarker.editor.Editor.handleCursorPositionChanged(Editor.java:174)
at org.jboss.ide.eclipse.freemarker.editor.Editor.mouseUp(Editor.java:200)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
{noformat}
This happens across multiple FreeMarker templates, all with very basic syntax.
I am using version 1.4.1.Final of the FreeMarker plugin.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months