September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15484) Provide support for scaled app when tailing log files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15484?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15484: ------------------------------------- Fix Version/s: 4.1.1.Alpha1 4.2.x > Provide support for scaled app when tailing log files > ----------------------------------------------------- > > Key: JBIDE-15484 > URL: https://issues.jboss.org/browse/JBIDE-15484 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Fix For: 4.1.1.Alpha1, 4.2.x > > > Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. > The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy > See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15484) Provide support for scaled app when tailing log files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15484?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15484: ---------------------------------------- Assignee: Xavier Coulon > Provide support for scaled app when tailing log files > ----------------------------------------------------- > > Key: JBIDE-15484 > URL: https://issues.jboss.org/browse/JBIDE-15484 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Alpha1, 4.2.x > > > Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. > The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy > See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-174) OutOfMemoryError when installing all SOA tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-174?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBTIS-174. ------------------------------------- Resolution: Rejected never mind - this was caused by using -vmargs from commandline which make eclipses ignore jbdevstudio.ini thus it was running with default 16mb settings. > OutOfMemoryError when installing all SOA tools > ---------------------------------------------- > > Key: JBTIS-174 > URL: https://issues.jboss.org/browse/JBTIS-174 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Reporter: Max Rydahl Andersen > Priority: Blocker > > Installed JBDS 7.1 Alpha1 > Installed all SOA connectors from Central > ...after this I can no longer run developer studio. It runs out of memory during startup. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-174) OutOfMemoryError when installing all SOA tools

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-174: ----------------------------------------- Summary: OutOfMemoryError when installing all SOA tools Key: JBTIS-174 URL: https://issues.jboss.org/browse/JBTIS-174 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: distribution Reporter: Max Rydahl Andersen Priority: Blocker Installed JBDS 7.1 Alpha1 Installed all SOA connectors from Central ...after this I can no longer run developer studio. It runs out of memory during startup. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15297) Error when restarting EAP 5.2 with JMX poller

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15297?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15297. --------------------------------- Won't fix. Closing. > Error when restarting EAP 5.2 with JMX poller > --------------------------------------------- > > Key: JBIDE-15297 > URL: https://issues.jboss.org/browse/JBIDE-15297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: EAP 5.2.0 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: affects_documentation > Fix For: 4.1.1.Alpha1 > > > When you have EAP 5.2 set up to use JMX for startup poller and Web Port for Shutdown poller, when you start and then restart the server, you get this error: > {code} > org.jboss.tools.jmx.core.JMXException: Error connecting to remote JMX. Please ensure your server is properly configured for JMX access. > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:156) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:239) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:231) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: > java.net.ConnectException: Connection refused] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:886) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713) > at javax.naming.InitialContext.lookup(InitialContext.java:411) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.createConnection(JBossServerConnection.java:170) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143) > ... 5 more > Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: > java.net.ConnectException: Connection refused > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619) > at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216) > at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:128) > at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:194) > at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:148) > at com.sun.proxy.$Proxy14.lookup(Unknown Source) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:753) > ... 9 more > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:579) > at java.net.Socket.connect(Socket.java:528) > at java.net.Socket.<init>(Socket.java:425) > at java.net.Socket.<init>(Socket.java:208) > at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) > at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:146) > at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) > ... 16 more > {code} > This is a common error indicating you don't have the credentials right, but it's not the case here - on the first start everything was ok. > In this case when the server is restarting, it is shown in the server view as Started before it actually is started and maybe that's the problem - the tooling then tries to connect via JMX prematurely and fails. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15163) Custom deploy scanner is not removed after server shutdown

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15163?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15163. --------------------------------- Verified in JBDS 7.1.0.Alpha1 B378 > Custom deploy scanner is not removed after server shutdown > ---------------------------------------------------------- > > Key: JBIDE-15163 > URL: https://issues.jboss.org/browse/JBIDE-15163 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.CR1 > Environment: OS X 10.8.4 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1 > > > There are new options in server editor as seen in JBIDE-9830. > Custom deployment scanner should now be removed after server stop (if the given checkbox is checked in the server editor). But they are not. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15369) Minor part of jbosstools-server/as submodule version should be incremented

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15369?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15369. --------------------------------- I verified that master uses 2.5.0 and maintenance uses 2.4.101 and also the feature and plugin versions in Alpha1 (B378) are 2.4.101. > Minor part of jbosstools-server/as submodule version should be incremented > -------------------------------------------------------------------------- > > Key: JBIDE-15369 > URL: https://issues.jboss.org/browse/JBIDE-15369 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > > API tooling reports that minor version should be incremented for as.core plugin because new APIs have been added since previous release. > In theory whole jbosstools-server/as sub-module should get new version 2.5.0 (current is 2.4.100). At the same time if master branch contains different API version in its version should be also increased. Question is which part of version should be changed to avoid conflicts in future between two streams. > This version changes should take place after JBIDE-15368 is taken care of. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-173) Teiid has custom user agreement text for attribution that fits better in about.html

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-173: ----------------------------------------- Summary: Teiid has custom user agreement text for attribution that fits better in about.html Key: JBTIS-173 URL: https://issues.jboss.org/browse/JBTIS-173 Project: JBoss Tools Integration Stack Issue Type: Bug Components: teiid Affects Versions: 4.1.0.Beta1 Reporter: Max Rydahl Andersen when installing from Beta1, Teiid has this text added to license text: "In addition, plugins contain work credited to Brian Goetz and Tim Peierls (http://www.jcip.net) (c) 2005, released under the Creative Commons Attribution License." This is already documented in the text before it and makes Teiid show up as "special" compared to the other features. This specific attribution should be added to the feature/plugins about.html instead as done for i.e. browsersim (https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jbos...) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-172) "JBoss jbpm5 runtime extension feature" is not using Red Hat license text

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-172: ----------------------------------------- Summary: "JBoss jbpm5 runtime extension feature" is not using Red Hat license text Key: JBTIS-172 URL: https://issues.jboss.org/browse/JBTIS-172 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: BPEL Affects Versions: 4.1.0.Beta1 Reporter: Max Rydahl Andersen When installing from Beta1 "JBoss jbpm5 runtime extension feature" uses Eclipse Foundation Software User Agreement. It should be using Red Hat, Inc. instead. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15484) Provide support for scaled app when tailing log files

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15484: ------------------------------------- Summary: Provide support for scaled app when tailing log files Key: JBIDE-15484 URL: https://issues.jboss.org/browse/JBIDE-15484 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- 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

12 years, 7 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 September 2013