[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov edited comment on JBIDE-19536 at 9/1/15 5:37 AM:
--------------------------------------------------------------------
I seem to encounter the same issue with JBDS9.0.0.Beta2 periodically (once in 1-2 work days). I'm not sure how I get to this state, and how to get out of it quick and easy. Just restarting JDBS doesn't help. So far the only thing that helps is cleaning and maven-updating projects.
It's bad, because it completely nullifies hot deploy. Fixing it requires a lengthy full rebuild or two.
!building.png!
I've cropped the buttons on the right of the queued operations. They're the red square "stop" buttons, not the gray X "remove finished" buttons.
I've attached 3 Visuam VM thread dumps. About 30 seconds between takes.
[^threaddump-1440009974151.tdump]
[^threaddump-1440009999047.tdump]
[^threaddump-1440010035476.tdump]
was (Author: vsevolodgolovanov):
I seem to encounter the same issue with JBDS9.0.0.Beta2 periodically (once in 1-2 work days). I'm not sure how I get to this state, and how to get out of it quick and easy. Just restarting JDBS doesn't help. So far the only thing that helps is cleaning and maven-updating projects.
It's bad, because it completely nullifies hot deploy. Fixing it requires a lengthy full rebuild or two.
!building.png!
I've cropped the buttons on the right of the queued operations. They're the reg square "stop" buttons, not the gray X "remove finished" buttons.
I've attached 3 Visuam VM thread dumps. About 30 seconds between takes.
[^threaddump-1440009974151.tdump]
[^threaddump-1440009999047.tdump]
[^threaddump-1440010035476.tdump]
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBIDE-20541) wildfly-jts-application-component-2 quickstart fails to validate
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20541?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-20541:
--------------------------------
Description:
See https://issues.jboss.org/browse/WFLY-5250 for followup.
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one example:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
exception}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
was:
See https://issues.jboss.org/browse/WFLY-5250 for followup.
The above quickstart fails to validate in eclipse. It has the following lines in it:
{code}
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:iiop="urn:iiop"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
version="3.1"
impl-version="2.0">
<assembly-descriptor>
<iiop:iiop>
<ejb-name>InvoiceManagerEJBImpl</ejb-name>
<iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
</iiop:iiop>
</assembly-descriptor>
</jboss:ejb-jar>
{code}
The key line to note is:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
{code}
urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
{code}
However, even once that is fixed, the quickstart still has other problems. For one example:
{code}
cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
exception}' is expected.
{code}
I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
> wildfly-jts-application-component-2 quickstart fails to validate
> -----------------------------------------------------------------
>
> Key: JBIDE-20541
> URL: https://issues.jboss.org/browse/JBIDE-20541
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
>
> See https://issues.jboss.org/browse/WFLY-5250 for followup.
> The above quickstart fails to validate in eclipse. It has the following lines in it:
> {code}
> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:iiop="urn:iiop"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
> http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> version="3.1"
> impl-version="2.0">
> <assembly-descriptor>
> <iiop:iiop>
> <ejb-name>InvoiceManagerEJBImpl</ejb-name>
> <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
> </iiop:iiop>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
> The key line to note is:
> {code}
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> {code}
> Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
> {code}
> urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
> {code}
> However, even once that is fixed, the quickstart still has other problems. For one example:
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
> java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
> permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
> javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
> java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
> exception}' is expected.
> {code}
> I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19335:
-------------------------------------
It;s default behavior for SWTException occurred in Eclipse. I have created simple plugin, logged SWTError to default plugin log and got similar dialog to dialog described in this issue
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBIDE-19335) org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19335?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-19335 at 9/1/15 4:10 AM:
-------------------------------------------------------------
It's default behavior for SWTException occurred in Eclipse. I have created simple plugin, logged SWTError to default plugin log and got similar dialog to dialog described in this issue
was (Author: vpakan):
It;s default behavior for SWTException occurred in Eclipse. I have created simple plugin, logged SWTError to default plugin log and got similar dialog to dialog described in this issue
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeLicenseFragment fails with SWTError without browser available
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19335
> URL: https://issues.jboss.org/browse/JBIDE-19335
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Environment: Linux
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> DownloadRuntimeLicenseFragment should work even without browser widget available and show html or text without html tags with <p> and <br> elements replaced with '\n'.
> Steps to tests the issue:
> 1. Linux disto without webkit or xulrunner (I was using xubuntu to verify)
> 2. Run JBT and try to download WildFly using Runtime Download dialog;
> 3. It should show not fail with SWTError when presenting license step, but show the link to the license, so you can click on it to open system browser or copy/past it into your favorite one
> 4. Close eclipse
> 5. Install libwebkit
> 6. Start eclipse, do WildFly downloading steps again and you should see license text inside dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20100:
----------------------------------------
{quote}a) I assume the dialog does not show up if there is just one connector available and it is GA'ed (non-early access), right ?{quote}
yes
{quote}b) it should automatically select an option - I suggest the supported version and after that what user chose last.
c) earlyaccess should not be the first item in the list.{quote}
right for both, I'll integrate that in the PR.
{quote}d) how do I disable earlyaccess so it will remove the EA updatesite from the list of updatesites it will look at ?{quote}
The link "Manage Early-Access" shows the installation page for which I submitted 2 screenshots here. On this page, user can see the Early-Access content they install and have the opportunity to disable it (remove features and repositories).
{quote}Once you have installed something from early access the earlyaccess updatesite is added to your jbds install and thus the choice you have here really does not guarantee you that the GA bits will be installed over what is in the earlyaccess. IMO, once a user the first time have said yes to earlyaccess and thus enabled earlyaccess he don't really have a choice anymore until he disables it.{quote}
And vice-versa, the fact that you have some Early-Access repositories enabled doesn't guarantee that when installing a connector, you get the Early-Access version of its features/plugins.
With our current implementation of Central and the connectors we have, the same feature isn't available in 2 different versions, what makes the difference is which features are installed by the GA version vs the EA one. In such case we have the guarantee that installing a GA connector doesn't install the EA additions.
Note that you comment is as true/false with the current implementation, so it's not a consequence of this UI change.
{quote}About the making JBDS users aware of using older JBDS - that was the main issue in this jira{quote}
I've read the first few lines of this Jira over and over again, and the main issue if that Fuse doesn't appear unless user think by themselves of enabling EA. The description doesn't even mention anything about older JBDS. It's more your mind which is focused on that part than the initial user request.
{quote}But I'm able to perform smoke tests (installation and key functionalities) on Mars TP, if it is needed.{quote}
To me, this means that we can put current Fuse IDE as an "Early Access" connector in JBDS 9. When developing Early-Access, it was exactly the purpose.
> how to make users aware of fuse and other tooling only being available from earlyaccess?
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20100
> URL: https://issues.jboss.org/browse/JBIDE-20100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.CR1
>
> Attachments: JBIDE-20100-2.png
>
>
> [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page.
> Some comments:
> "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list."
> "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something."
> Suggestion:
> "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature."
> I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ?
> and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ?
> But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9)
> [~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months