December 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-13318) Cannot tail files at all

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13318?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-13318: ----------------------------------- Priority: Critical (was: Major) Increased priority to Critical, not sure this can be considered as blocker but did not find any workaround yet. > Cannot tail files at all > ------------------------ > > Key: JBIDE-13318 > URL: https://issues.jboss.org/browse/JBIDE-13318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 3.3.2 > > > Still getting {code}Could not find any files matching glob{code} using JBoss AS/EAP application type, either via server adapter or OpenShift Explorer. Maybe an OpenShift API change? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13318) Cannot tail files at all

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13318?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-13318: ----------------------------------- Description: Still getting {code}Could not find any files matching glob{code} using JBoss AS/EAP application type, either via server adapter or OpenShift Explorer. Maybe an OpenShift API change? (was: Still getting {code}Could not find any files matching glob{code} using JBoss AS/EAP application type, either via server adapter or OpenShift Explorer Maybe an OpenShift API change?) > Cannot tail files at all > ------------------------ > > Key: JBIDE-13318 > URL: https://issues.jboss.org/browse/JBIDE-13318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.2 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 3.3.2 > > > Still getting {code}Could not find any files matching glob{code} using JBoss AS/EAP application type, either via server adapter or OpenShift Explorer. Maybe an OpenShift API change? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13318) Cannot tail files at all

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13318: -------------------------------------- Summary: Cannot tail files at all Key: JBIDE-13318 URL: https://issues.jboss.org/browse/JBIDE-13318 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.2 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 3.3.2 Still getting {code}Could not find any files matching glob{code} using JBoss AS/EAP application type, either via server adapter or OpenShift Explorer Maybe an OpenShift API change? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13216) JBT Doesn't place the JDBC Driver correctly

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13216?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13216. --------------------------------- Verified in JBDS 5.0.2.GA B235. The generated seam 2.3 project -ds.xml file now contains <driver>h2-1.3.168-redhat-1.jar</driver> > JBT Doesn't place the JDBC Driver correctly > ------------------------------------------- > > Key: JBIDE-13216 > URL: https://issues.jboss.org/browse/JBIDE-13216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Environment: Juno, JBT Daily Plugin > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 3.3.2 > > > in the ds.xml file. the following gets generated under driver. Works fine under regular seam-gen. > {code} > <?xml version="1.0" encoding="UTF-8"?> > <datasources xmlns="http://www.jboss.org/ironjacamar/schema" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema http://www.jboss.org/ironjacamar/schema/datasources_1_0.xsd"> > <datasource > jndi-name="nationalparkDatasource" > enabled="true" > use-java-context="true" pool-name="nationalparkDatasource_pool"> > <connection-url>jdbc:hsqldb:MyDB</connection-url> > <driver>[Ljava.lang.String;@4633819a</driver> > <security> > <user-name>sa</user-name> > <password></password> > </security> > </datasource> > </datasources> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12123) When remote server fails to stop process is not terminated even if user opts for that

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12123?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12123. --------------------------------- Verified in JBDS 5.0.2.GA B235. Closing. > When remote server fails to stop process is not terminated even if user opts for that > ------------------------------------------------------------------------------------- > > Key: JBIDE-12123 > URL: https://issues.jboss.org/browse/JBIDE-12123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 3.3.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 3.3.2, 4.0.0.Beta1 > > > With JBIDE-11831 the situation with stopping remote servers is now improved, but it's still not ideal. > If the shutdown command fails we display an error: Server XX failed to stop. If you try again, it does the same. If you try for the third time, it will keep stopping until the timeout is reached and then a message is displayed: Server ... is not responding. Would you like to terminate the server or keep waiting? > I hit terminate and nothing happens. > Also, this message is accompanied by an empty error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13317) OpenShift wizard adds bogus decoration to 'use existing application' field

by Stefan Bunciak (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13317?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-13317: ----------------------------------- Attachment: decoration.png > OpenShift wizard adds bogus decoration to 'use existing application' field > -------------------------------------------------------------------------- > > Key: JBIDE-13317 > URL: https://issues.jboss.org/browse/JBIDE-13317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.2, 4.0.0.Final > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 3.3.2, 4.0.x > > Attachments: decoration.png > > > This bug occurs only on a newly created workspace, when no OpenShift application has been created yet. Once the wizard prefills the last used application type, the bogus decoration '*' no longer appears. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13317) OpenShift wizard adds bogus decoration to 'use existing application' field

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-13317: -------------------------------------- Summary: OpenShift wizard adds bogus decoration to 'use existing application' field Key: JBIDE-13317 URL: https://issues.jboss.org/browse/JBIDE-13317 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.Final, 3.3.2 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 3.3.2, 4.0.x This bug occurs only on a newly created workspace, when no OpenShift application has been created yet. Once the wizard prefills the last used application type, the bogus decoration '*' no longer appears. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12216) Remote server not behaving properly when management password is incorrect

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12216?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12216. --------------------------------- Verified in JBDS 5.0.2.GA B235 > Remote server not behaving properly when management password is incorrect > ------------------------------------------------------------------------- > > Key: JBIDE-12216 > URL: https://issues.jboss.org/browse/JBIDE-12216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 3.3.0.CR1 > Environment: jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 3.3.2 > > Attachments: JBIDE-12216a.patch, JBIDE-12216b.patch > > > When you start a remote AS7/EAP6 with the management port exposed and enter the user&passwd incorrectly, the server will keep starting until the timeout is reached. It would be nice if we could show an error right away. > Also when the management port is exposed, but startup poller is set to Web Port, it is even worse - server will start and will be shown as started. But when you try to access the server in MBean Explorer, it will use 100 % of CPU and eventually eclipse will crash. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-2437: ----------------------------------------- Note that in JBDS 5.0.1.GA it works fine > Cannot deploy BPEL project > -------------------------- > > Key: JBDS-2437 > URL: https://issues.jboss.org/browse/JBDS-2437 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.2.GA > Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA > Reporter: Andrej Podhradsky > Assignee: Douglas Palmer > Priority: Blocker > Attachments: deploy_error.png > > > Cannot deploy a bpel project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBDS-2437: --------------------------------------- Summary: Cannot deploy BPEL project Key: JBDS-2437 URL: https://issues.jboss.org/browse/JBDS-2437 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: SOA Tooling / Platform Affects Versions: 5.0.2.GA Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA Reporter: Andrej Podhradsky Assignee: Douglas Palmer Priority: Blocker Attachments: deploy_error.png Cannot deploy a bpel project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 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 December 2012