July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ] Michal Jurc commented on JBIDE-22436: ------------------------------------- [~nickboldt]: Reproduced with JBDS 11.0.0.AM2. > Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22436 > URL: https://issues.jboss.org/browse/JBIDE-22436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.1.Final > Reporter: Michal Jurc > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBIDE-22436-10.0-helloworld.log, JBIDE-22436-9.1-helloworld.log, helloworld-cheatsheet.xml, jbds104-cheat-sheet-npe.log, kitchensink-cheatsheet.xml, npe-jbds11-fedora26-x64.log, org.jboss.tools.cheatsheet.test.zip > > > After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message: > {quote}An error has occurred. See error log for more details. > java.lang.NullPointerException{quote} > The detailed error log produces the same message. > The quickstarts and their cheat sheets work even after the prompt with NullPointerException message. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ] Michal Jurc updated JBIDE-22436: -------------------------------- Attachment: npe-jbds11-fedora26-x64.log > Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22436 > URL: https://issues.jboss.org/browse/JBIDE-22436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.1.Final > Reporter: Michal Jurc > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: JBIDE-22436-10.0-helloworld.log, JBIDE-22436-9.1-helloworld.log, helloworld-cheatsheet.xml, jbds104-cheat-sheet-npe.log, kitchensink-cheatsheet.xml, npe-jbds11-fedora26-x64.log, org.jboss.tools.cheatsheet.test.zip > > > After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message: > {quote}An error has occurred. See error log for more details. > java.lang.NullPointerException{quote} > The detailed error log produces the same message. > The quickstarts and their cheat sheets work even after the prompt with NullPointerException message. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24752) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.5.Final

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24752?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-24752: --------------------------------- Assignee: Koen Aers > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.5.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24752 > URL: https://issues.jboss.org/browse/JBIDE-24752 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.0.Final > > > This includes updating Hibernate Core to version 5.1.8.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24752) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.5.Final

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24752?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-24752: ------------------------------ Fix Version/s: 4.5.0.Final > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.5.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24752 > URL: https://issues.jboss.org/browse/JBIDE-24752 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.0.Final > > > This includes updating Hibernate Core to version 5.1.8.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24752) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.5.Final

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24752?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-24752. ------------------------------- Resolution: Done > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_1 to version 5.1.5.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24752 > URL: https://issues.jboss.org/browse/JBIDE-24752 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.5.0.Final > > > This includes updating Hibernate Core to version 5.1.8.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4477) Camel: False for automated startup does not work

by Timo Riikonen (JIRA)

[ https://issues.jboss.org/browse/JBDS-4477?page=com.atlassian.jira.plugin.... ] Timo Riikonen updated JBDS-4477: -------------------------------- Summary: Camel: False for automated startup does not work (was: False for automated startup does not work) > Camel: False for automated startup does not work > ------------------------------------------------ > > Key: JBDS-4477 > URL: https://issues.jboss.org/browse/JBDS-4477 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 10.4.0.GA > Environment: JBoss Fuse 6.3 on RHEL Linux 3.10.0-514.el7.x86_64 on Wmware on Windows 10 64 bit on a laptop > Reporter: Timo Riikonen > Priority: Minor > > Routes usually start despite of the settings. I am not sure if they always start or only sometimes: this is new application and if this sometimes works correctly, that is too rare occurrence. > Example logs entries in Hawtio are on below. As you can see it detects the "do not start" setting and says nothing started. Then immediately after that it starts it anyway. > If I pause half of the routes manually, then sometimes in next installation it does not start those that were paused (if I can trust on UI), and sometimes it starts all. > 2017-07-21 09:59:38 > INFO > org.apache.camel.blueprint.BlueprintCamelContext > Skipping starting of route FtpReadTestR as its configured with autoStartup=false > 2017-07-21 09:59:38 > INFO > org.apache.camel.blueprint.BlueprintCamelContext > Total 1 routes, of which 0 are started. > 2017-07-21 09:59:38 > INFO > org.apache.camel.blueprint.BlueprintCamelContext > Apache Camel 2.17.0.redhat-630187 (CamelContext: FtpReadTestC) started in 0.019 seconds -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4478) Auto-deployment and auto-compilation work almost randomly

by Timo Riikonen (JIRA)

[ https://issues.jboss.org/browse/JBDS-4478?page=com.atlassian.jira.plugin.... ] Timo Riikonen updated JBDS-4478: -------------------------------- Steps to Reproduce: 1) I create an application with Camel routes 2) I compile and deploy it on Camel 3) I add a space character into pom.xml and save it 4) New version deploys automatically 5) I leave the computer on for the night 6) I add a space character into pom.xml and save it again 7) Project does not compile. It tries to deploy, but as it has deleted Manifest and has not created, it gives an error that is correct, but difficult for beginners to understand: "missing or invalid Manifest" 8) I restart Eclipse (and with Eclipse application servers as well) 9) No changes 10) I make mvn clean install 11) Auto-deployment gets stuck and lasts for forever 12) I uninstall and reinstall application 13) I test. Ok. 14) I add a space on pom.xml again 15) Auto-deployment does not happen 16) Wait for 10 minutes 17) I add a space on pom.xml again 18) Auto-deployment works again was: 1) I create an application with Camel routes 2) I compile and deploy it on Camel 3) I add a space character into pom.xml and save it 4) New version deploys automatically 5) I leave the computer on for the night 6) I add a space character into pom.xml and save it again 7) Project does not compile. It tries to deploy, but as it has deleted Manifest and has not created, it gives an error that is correct, but difficult for beginners to understand: "missing or invalid Manifest" 8) I restart Eclipse (and with Eclipse application servers as well) 9) No changes 10) I make mvn clean install 11) Auto-deployment gets stuck and lasts for forever 12) I uninstall and reinstall application 13) I test. Ok. 14) I add a space on pom.xml again 15) Auto-deployment does not happen ...) Somehow I tend to get the auto-deployment to work again, but I need to test more to define what makes it to function again. > Auto-deployment and auto-compilation work almost randomly > --------------------------------------------------------- > > Key: JBDS-4478 > URL: https://issues.jboss.org/browse/JBDS-4478 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 10.4.0.GA > Environment: JBoss Fuse 6.3 on RHEL Linux 3.10.0-514.el7.x86_64 on Wmware on Windows 10 64 bit on a laptop > Reporter: Timo Riikonen > > One problem with auto-compilation and perhaps two problems with auto-deployment. See the steps. > Error message about Manifest: > !ENTRY org.fusesource.ide.server.karaf.core 4 4 2017-07-21 09:04:21.172 > !MESSAGE Deployment problem: Binary archive /home/perttu/workspace/.metadata/.plugins/org.fusesource.ide.server.karaf.core/JBoss_Fuse_6.3_Runtime_Server/tempRemoteDeploy/fuse-1.0.0-SNAPSHOT.jar is not valid or lacking a valid MANIFEST.MF! > Error message that is probably irrelevant to the issue (I don't know what makes this): > !ENTRY org.fusesource.ide.camel.model.service.core 2 0 2017-07-21 09:18:48.075 > !MESSAGE ParseAttributes: Unsupported EIP will be ignored: camelContext -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4477) False for automated startup does not work

by Timo Riikonen (JIRA)

[ https://issues.jboss.org/browse/JBDS-4477?page=com.atlassian.jira.plugin.... ] Timo Riikonen updated JBDS-4477: -------------------------------- Description: Routes usually start despite of the settings. I am not sure if they always start or only sometimes: this is new application and if this sometimes works correctly, that is too rare occurrence. Example logs entries in Hawtio are on below. As you can see it detects the "do not start" setting and says nothing started. Then immediately after that it starts it anyway. If I pause half of the routes manually, then sometimes in next installation it does not start those that were paused (if I can trust on UI), and sometimes it starts all. 2017-07-21 09:59:38 INFO org.apache.camel.blueprint.BlueprintCamelContext Skipping starting of route FtpReadTestR as its configured with autoStartup=false 2017-07-21 09:59:38 INFO org.apache.camel.blueprint.BlueprintCamelContext Total 1 routes, of which 0 are started. 2017-07-21 09:59:38 INFO org.apache.camel.blueprint.BlueprintCamelContext Apache Camel 2.17.0.redhat-630187 (CamelContext: FtpReadTestC) started in 0.019 seconds was:Routes usually start despite of the settings. I am not sure if they always start or only sometimes: this is new application and if this sometimes works correctly, that is too rare occurence. > False for automated startup does not work > ----------------------------------------- > > Key: JBDS-4477 > URL: https://issues.jboss.org/browse/JBDS-4477 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 10.4.0.GA > Environment: JBoss Fuse 6.3 on RHEL Linux 3.10.0-514.el7.x86_64 on Wmware on Windows 10 64 bit on a laptop > Reporter: Timo Riikonen > Priority: Minor > > Routes usually start despite of the settings. I am not sure if they always start or only sometimes: this is new application and if this sometimes works correctly, that is too rare occurrence. > Example logs entries in Hawtio are on below. As you can see it detects the "do not start" setting and says nothing started. Then immediately after that it starts it anyway. > If I pause half of the routes manually, then sometimes in next installation it does not start those that were paused (if I can trust on UI), and sometimes it starts all. > 2017-07-21 09:59:38 > INFO > org.apache.camel.blueprint.BlueprintCamelContext > Skipping starting of route FtpReadTestR as its configured with autoStartup=false > 2017-07-21 09:59:38 > INFO > org.apache.camel.blueprint.BlueprintCamelContext > Total 1 routes, of which 0 are started. > 2017-07-21 09:59:38 > INFO > org.apache.camel.blueprint.BlueprintCamelContext > Apache Camel 2.17.0.redhat-630187 (CamelContext: FtpReadTestC) started in 0.019 seconds -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4478) Auto-deployment and auto-compilation work almost randomly

by Timo Riikonen (JIRA)

[ https://issues.jboss.org/browse/JBDS-4478?page=com.atlassian.jira.plugin.... ] Timo Riikonen updated JBDS-4478: -------------------------------- Description: One problem with auto-compilation and perhaps two problems with auto-deployment. See the steps. Error message about Manifest: !ENTRY org.fusesource.ide.server.karaf.core 4 4 2017-07-21 09:04:21.172 !MESSAGE Deployment problem: Binary archive /home/perttu/workspace/.metadata/.plugins/org.fusesource.ide.server.karaf.core/JBoss_Fuse_6.3_Runtime_Server/tempRemoteDeploy/fuse-1.0.0-SNAPSHOT.jar is not valid or lacking a valid MANIFEST.MF! Error message that is probably irrelevant to the issue (I don't know what makes this): !ENTRY org.fusesource.ide.camel.model.service.core 2 0 2017-07-21 09:18:48.075 !MESSAGE ParseAttributes: Unsupported EIP will be ignored: camelContext was: One problem with auto-compilation and perhaps two problems with auto-deployment. See the steps. > Auto-deployment and auto-compilation work almost randomly > --------------------------------------------------------- > > Key: JBDS-4478 > URL: https://issues.jboss.org/browse/JBDS-4478 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Affects Versions: 10.4.0.GA > Environment: JBoss Fuse 6.3 on RHEL Linux 3.10.0-514.el7.x86_64 on Wmware on Windows 10 64 bit on a laptop > Reporter: Timo Riikonen > > One problem with auto-compilation and perhaps two problems with auto-deployment. See the steps. > Error message about Manifest: > !ENTRY org.fusesource.ide.server.karaf.core 4 4 2017-07-21 09:04:21.172 > !MESSAGE Deployment problem: Binary archive /home/perttu/workspace/.metadata/.plugins/org.fusesource.ide.server.karaf.core/JBoss_Fuse_6.3_Runtime_Server/tempRemoteDeploy/fuse-1.0.0-SNAPSHOT.jar is not valid or lacking a valid MANIFEST.MF! > Error message that is probably irrelevant to the issue (I don't know what makes this): > !ENTRY org.fusesource.ide.camel.model.service.core 2 0 2017-07-21 09:18:48.075 > !MESSAGE ParseAttributes: Unsupported EIP will be ignored: camelContext -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4476) Undeploy still failing with FUSE -> Karaf -> Camel

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4476?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4476: --------------------------------------- Hello [~timo.riikonen], thanks for the report. Can you precise which Camel/Fuse integration project you are trying to deploy/undeploy? Can you precise the version of Fuse Runtime you are using? When you say that you haven't found any errors in log, is it in the "Fuse Runtime" log (in the <fuse runtime>/data/log/fuse.log) or in the "Eclipse" log (<workspace>/.metadata/.log)? or both? regards, > Undeploy still failing with FUSE -> Karaf -> Camel > -------------------------------------------------- > > Key: JBDS-4476 > URL: https://issues.jboss.org/browse/JBDS-4476 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: fuse-tooling > Affects Versions: 9.2.0 > Environment: JBoss Fuse 6.3 on RHEL Linux 3.10.0-514.el7.x86_64 on Wmware on Windows 10 64 bit on a laptop > Reporter: Timo Riikonen > > When I uninstall Camel application, they randomly do uninstall, don't uninstall or partially uninstall. What I noticed happening, is that shutting them down takes apparently too long time and after the shut down, uninstall doesn't happen any more, but normal start. I presume because of some timeout. > I haven't found any error logs about this problem. > I gave Major priority because this can be nasty when you are trying to deploy different version of the same application and you have no idea that the old version was running there still. If you succeed, you have randomly several versions running of the same application. If you fail to deploy the other version, you have the old version running instead. Very random behavior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
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 July 2017