July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17926) JBOSS EAP 6.2.0 Database connection manager not available Shutdown

by kusuma thatavarthi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17926?page=com.atlassian.jira.plugi... ] kusuma thatavarthi commented on JBIDE-17926: -------------------------------------------- Hi Fred, I faced this issue on command prompt. I have not tested this on eclipse. Thanks, Kusuma > JBOSS EAP 6.2.0 Database connection manager not available Shutdown > ------------------------------------------------------------------ > > Key: JBIDE-17926 > URL: https://issues.jboss.org/browse/JBIDE-17926 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: kusuma thatavarthi > Priority: Critical > > Problem occurs when i try to unschedule jobs during JBoss Shutdown. > For reference: > http://stackoverflow.com/questions/24776554/error-occurred-while-unschedu.... > 12:39:50,020 ERROR [com.kony.sync.console.job.scheduler.ConsoleJobScheduler] (ServerService Thread Pool -- 20) Error occurred while unscheduling jobs for application ID:PaaSJobs: org.qu > artz.JobPersistenceException: Failed to obtain DB connection from data source 'syncQuartzDS': java.sql.SQLException: Could not retrieve datasource via JNDI url 'java:jboss/datasources/C > onsoleDB' java.sql.SQLException: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:jboss/datasources/ConsoleDB [See nested exception: java.sql.SQLExce > ption: Could not retrieve datasource via JNDI url 'java:jboss/datasources/ConsoleDB' java.sql.SQLException: javax.resource.ResourceException: IJ000451: The connection manager is shutdow > n: java:jboss/datasources/ConsoleDB] > at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:715) [quartz-all-1.8.6.jar:] > at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:69) [quartz-all-1.8.6.jar:] > at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3785) [quartz-all-1.8.6.jar:] > at org.quartz.impl.jdbcjobstore.JobStoreTX.executeInLock(JobStoreTX.java:90) [quartz-all-1.8.6.jar:] > at org.quartz.impl.jdbcjobstore.JobStoreSupport.removeTrigger(JobStoreSupport.java:1458) [quartz-all-1.8.6.jar:] > at org.quartz.core.QuartzScheduler.unscheduleJob(QuartzScheduler.java:965) [quartz-all-1.8.6.jar:] > at org.quartz.impl.StdScheduler.unscheduleJob(StdScheduler.java:290) [quartz-all-1.8.6.jar:] > at com.kony.sync.console.job.scheduler.ConsoleJobScheduler.unscheduleJob(ConsoleJobScheduler.java:225) [syncconsole.jar:] > at com.kony.sync.services.context.SyncContextListener.contextDestroyed(SyncContextListener.java:221) [classes:] > at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3427) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStop(WebDeploymentService.java:171) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.as.web.deployment.WebDeploymentService.access$100(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.as.web.deployment.WebDeploymentService$2.run(WebDeploymentService.java:113) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_26] > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_26] > at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_26] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_26] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_26] > at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_26] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'java:jboss/datasources/ConsoleDB' java.sql.SQLException: javax.resource.ResourceException: IJ000451: The co > nnection manager is shutdown: java:jboss/datasources/ConsoleDB > at org.quartz.utils.JNDIConnectionProvider.getConnection(JNDIConnectionProvider.java:163) [quartz-all-1.8.6.jar:] > at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:109) [quartz-all-1.8.6.jar:] > at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:712) [quartz-all-1.8.6.jar:] > ... 20 more > Terminate batch job (Y/N)? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17026) Unable to load hibernate plugins when JBDS is running with JDK8

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17026?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17026. -------------------------------- Verified with JBDS 8.0.0.Beta3b, GNU/Linux 64 > Unable to load hibernate plugins when JBDS is running with JDK8 > --------------------------------------------------------------- > > Key: JBIDE-17026 > URL: https://issues.jboss.org/browse/JBIDE-17026 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1a, L64, Fedora 19, JDK 1.8 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > While using JDK8 for JBDS I cannot expand hibernate configuration console. Error message: Proejct 'hbtest1' has higher compiler option than running Eclipse. Hibernate plugins unable to load its classes. Please decrease the compiler option or run the eclipse with higher JDK level. > I was trying to do various project settings related to compiler level but nothing I tried helped. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2919) Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2919?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-2919: -------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta3) Description: Moving to 8.0.0.CR1 (as agreed with [~maxandersen]) > Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8 > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2919 > URL: https://issues.jboss.org/browse/JBDS-2919 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: server > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 8.0.0.CR1 > > > Moving to 8.0.0.CR1 (as agreed with [~maxandersen]) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17937) Add a "Nightly" label on N&N when it's not release yet.

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17937?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17937: --------------------------------------- well, we would have to call it '4.2.0.Nightly' back again once '4.2.0.Beta3' is released, right ? > Add a "Nightly" label on N&N when it's not release yet. > ------------------------------------------------------- > > Key: JBIDE-17937 > URL: https://issues.jboss.org/browse/JBIDE-17937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > When we start aggregating the N&N for an upcoming version, the page appears in http://tools.jboss.org/documentation/whatsnew/jbosstools, but there's no label yet, because there's no entry for that version in 'products.yml' since it's not been released yet. > In that case, there should be a "Nightly" label and no link to download (that's already the case) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17938) No local processes in JMX Navigator when Eclipse is run with java 7

by Martin Malina (JIRA)

Martin Malina created JBIDE-17938: ------------------------------------- Summary: No local processes in JMX Navigator when Eclipse is run with java 7 Key: JBIDE-17938 URL: https://issues.jboss.org/browse/JBIDE-17938 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Beta3 Environment: JBDS 8.0.0.Beta3b B193 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.CR1 When I install and run JBDS with java 7, there are no local processes shown in the JMX navigator. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17551) Duplicate full class name causing jacoco to fail

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17551?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17551: --------------------------------------- [~mickael_istria], [~nickboldt], I'm confused.. do you have more information on the duplicate class that was reintroduced ? Is there anything I should do/fix ? Thanks! > Duplicate full class name causing jacoco to fail > ------------------------------------------------ > > Key: JBIDE-17551 > URL: https://issues.jboss.org/browse/JBIDE-17551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > Jacoco reports are failing for webservices. When in verbose, the error is > {code} > /home/mistria/git/jbosstools-webservices/jacoco/jacoco-reports.xml:13: Error while creating report > at org.jacoco.ant.ReportTask.execute(ReportTask.java:498) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) > 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:606) > at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) > at org.apache.tools.ant.Task.perform(Task.java:348) > at org.apache.tools.ant.Target.execute(Target.java:390) > at org.apache.tools.ant.Target.performTasks(Target.java:411) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) > at org.apache.tools.ant.Project.executeTarget(Project.java:1368) > at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > at org.apache.tools.ant.Project.executeTargets(Project.java:1251) > at org.apache.tools.ant.Main.runBuild(Main.java:809) > at org.apache.tools.ant.Main.startAnt(Main.java:217) > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) > Caused by: java.io.IOException: Error while analyzing class tests/org.jboss.tools.ws.jaxrs.ui.test/target/classes/org/jboss/tools/ws/jaxrs/ui/internal/utils/Logger$1.class. > at org.jacoco.core.analysis.Analyzer.analyzerError(Analyzer.java:139) > at org.jacoco.core.analysis.Analyzer.analyzeClass(Analyzer.java:133) > at org.jacoco.core.analysis.Analyzer.analyzeAll(Analyzer.java:164) > at org.jacoco.ant.ReportTask.createBundle(ReportTask.java:570) > at org.jacoco.ant.ReportTask.createReport(ReportTask.java:545) > at org.jacoco.ant.ReportTask.createReport(ReportTask.java:542) > at org.jacoco.ant.ReportTask.execute(ReportTask.java:492) > ... 17 more > Caused by: java.lang.IllegalStateException: Can't add different class with same name: org/jboss/tools/ws/jaxrs/ui/internal/utils/Logger$1 > at org.jacoco.core.analysis.CoverageBuilder.visitCoverage(CoverageBuilder.java:89) > at org.jacoco.core.analysis.Analyzer$1.visitEnd(Analyzer.java:81) > {code} > Jacoco (and life in general) doesn't like having different classes with same full name. > Here are the culprits in that case: > {quote} > mistria@mistria--rh:~/git/jbosstools-webservices$ find . -name Logger\$1.class > ./plugins/org.jboss.tools.ws.jaxrs.ui/target/classes/org/jboss/tools/ws/jaxrs/ui/internal/utils/Logger$1.class > [...] > ./tests/org.jboss.tools.ws.jaxrs.ui.test/target/classes/org/jboss/tools/ws/jaxrs/ui/internal/utils/Logger$1.class > {quote} > You should consider either having the test directly consuming the Logger from the non-test bundle, or at least change the package when duplicating a class. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17937) Add a "Nightly" label on N&N when it's not release yet.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17937?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17937: --------------------------------------------- I'm wondering if we should get rid of: 4.2.0.Nightly: build_type: nightly update_site_url: http://download.jboss.org/jbosstools/updates/nightly/core/master/ download_url: http://download.jboss.org/jbosstools/builds/nightly/core/master/latestBui... and call it: 4.2.0.Beta3: build_type: nightly update_site_url: http://download.jboss.org/jbosstools/updates/nightly/core/master/ download_url: http://download.jboss.org/jbosstools/builds/nightly/core/master/latestBui... ? > Add a "Nightly" label on N&N when it's not release yet. > ------------------------------------------------------- > > Key: JBIDE-17937 > URL: https://issues.jboss.org/browse/JBIDE-17937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > When we start aggregating the N&N for an upcoming version, the page appears in http://tools.jboss.org/documentation/whatsnew/jbosstools, but there's no label yet, because there's no entry for that version in 'products.yml' since it's not been released yet. > In that case, there should be a "Nightly" label and no link to download (that's already the case) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17937) Add a "Nightly" label on N&N when it's not release yet.

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17937?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17937: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Add a "Nightly" label on N&N when it's not release yet. > ------------------------------------------------------- > > Key: JBIDE-17937 > URL: https://issues.jboss.org/browse/JBIDE-17937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Fix For: 4.2.0.CR1 > > > When we start aggregating the N&N for an upcoming version, the page appears in http://tools.jboss.org/documentation/whatsnew/jbosstools, but there's no label yet, because there's no entry for that version in 'products.yml' since it's not been released yet. > In that case, there should be a "Nightly" label and no link to download (that's already the case) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17937) Add a "Nightly" label on N&N when it's not release yet.

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-17937: ------------------------------------- Summary: Add a "Nightly" label on N&N when it's not release yet. Key: JBIDE-17937 URL: https://issues.jboss.org/browse/JBIDE-17937 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: website Affects Versions: 4.2.0.Beta3 Reporter: Xavier Coulon When we start aggregating the N&N for an upcoming version, the page appears in http://tools.jboss.org/documentation/whatsnew/jbosstools, but there's no label yet, because there's no entry for that version in 'products.yml' since it's not been released yet. In that case, there should be a "Nightly" label and no link to download (that's already the case) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17937) Add a "Nightly" label on N&N when it's not release yet.

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17937?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17937: ------------------------------------- Assignee: Xavier Coulon > Add a "Nightly" label on N&N when it's not release yet. > ------------------------------------------------------- > > Key: JBIDE-17937 > URL: https://issues.jboss.org/browse/JBIDE-17937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > When we start aggregating the N&N for an upcoming version, the page appears in http://tools.jboss.org/documentation/whatsnew/jbosstools, but there's no label yet, because there's no entry for that version in 'products.yml' since it's not been released yet. > In that case, there should be a "Nightly" label and no link to download (that's already the case) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 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 2014