April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14073) add remote deployment feature as EAP6 CLI does to JBDS.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14073?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14073: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > add remote deployment feature as EAP6 CLI does to JBDS. > ------------------------------------------------------- > > Key: JBIDE-14073 > URL: https://issues.jboss.org/browse/JBIDE-14073 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Labels: UHG > Fix For: 4.2.x > > > EAP6 CLI provides feature to do remote deployment: > bin/jboss-cli.sh --connect --controller="127.0.0.1:9999" --command="deploy ../tmp/sample.war" --user="User" > Is it possible to have such feature available in JBDS? -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15287) Allow customization of automatically-added deployment scanner attributes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15287?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15287. --------------------------------- Resolution: Done We definitely shouldn't change the values of the default scanner, as we did not add the default scanner. Please open a new jira, as this jira has been fixed. > Allow customization of automatically-added deployment scanner attributes > ------------------------------------------------------------------------ > > Key: JBIDE-15287 > URL: https://issues.jboss.org/browse/JBIDE-15287 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Specifically timeouts. https://community.jboss.org/message/758366#758366 -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15250: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Explode utility jars in EAR/WAR deployments > ------------------------------------------- > > Key: JBIDE-15250 > URL: https://issues.jboss.org/browse/JBIDE-15250 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.0.1.Final > Reporter: Kevin Formsma > Assignee: Rob Stryker > Fix For: 4.2.x > > > For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects. > A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14001: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > First restart of JBDS/App Server results in deployed archive being deleted from deploy directory. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14001 > URL: https://issues.jboss.org/browse/JBIDE-14001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.1.Final > Environment: Windows 7 > Reporter: David Stephan > Assignee: Rob Stryker > Fix For: 4.2.x > > > After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly. > Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted. > After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar. > Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable". -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15391) Investigate having ports UI add relevant command line args to server startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15391?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15391: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Investigate having ports UI add relevant command line args to server startup > ---------------------------------------------------------------------------- > > Key: JBIDE-15391 > URL: https://issues.jboss.org/browse/JBIDE-15391 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.x > > > Subject seems pretty complete; forum post contains more information. Investigate how feasible it is for the editor sections to add relevant command line arguments to override standalone.xml's defaults. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15383: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Server Launch Configuration loses Classpath User Entries > -------------------------------------------------------- > > Key: JBIDE-15383 > URL: https://issues.jboss.org/browse/JBIDE-15383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Fix For: 4.2.x > > Attachments: JBIDE_1.png, JBIDE_2.png, JBIDE_3.png > > > Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. > This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. > Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". > The attachments describe what happens: > * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. > * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). > * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. > * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. > I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. > I've been able to replicate this on two separate (similarly configured) machines. > This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new issue. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15313) Investigate how to handle Wildfly port multiplexing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15313?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15313: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Investigate how to handle Wildfly port multiplexing > ---------------------------------------------------- > > Key: JBIDE-15313 > URL: https://issues.jboss.org/browse/JBIDE-15313 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.x > > > While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen. > This jira will investigate what's necessary and what may need to 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15635) Null Pointer when code assumes runtime type cannot be null

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15635: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Null Pointer when code assumes runtime type cannot be null > ---------------------------------------------------------- > > Key: JBIDE-15635 > URL: https://issues.jboss.org/browse/JBIDE-15635 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Mac OSX 10.8.5 > Oracle JDK 1.7.0_40 > JBoss Developer Studio > Version: 7.0.1.GA > Build id: GA-v20130930-2238-B7 > Build date: 20130930-2238 > Reporter: Cojan van Ballegooijen > Assignee: Rob Stryker > Fix For: 4.2.x > > Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png > > > - Installed JBoss Developer 7.0.0GA using > - Upgraded to 7.0.1GA > - Starting JBoss Developer Studio shows the following error window > An internal error occurred during: "Refreshing JBoss Tutorials...". > java.lang.NullPointerException > - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet" > - Starting a new Java EE Web project results in the following error > An error has occurred. See error log for more details. > java.lang.NullPointerException > No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files. > Found .log in ~/workspace/.metadata > !SESSION 2013-10-08 16:14:47.792 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation > !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252 > !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences > !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for ALT+COMMAND+Z: > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean, > Open CDI Named Bean, > Category(org.eclipse.ui.category.navigate,Navigate,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu, > Shows the Surround With quick menu, > Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for COMMAND+SHIFT+F10: > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service, > Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class., > Category(org.eclipse.ui.category.file,File,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu, > Show the system menu, > Category(org.eclipse.ui.category.window,Window,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:248) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15671) WildFly / EAP domain mode management UI

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15671?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15671: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > WildFly / EAP domain mode management UI > --------------------------------------- > > Key: JBIDE-15671 > URL: https://issues.jboss.org/browse/JBIDE-15671 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Ondrej Zizka > Assignee: Rob Stryker > Fix For: 4.2.x > > Attachments: domainmodeinitialmockup.bmml, domainmodeinitialmockup.png > > > Max brought the topic of Domain mode management UI. > The domain mode needs a special treatment. > Logically it's a matrix, and calls for a matrix-like UI instead of a tree. > The structure would be similar to the pictures of domain mode in tutorials (TBD: link). > An inspiration may be taken from AS web console. > As a preliminary solution, a tree may be used, in which case it may omit host controllers which do not play much role in domain mode management, from the admin PoV. > The nodes would represent server groups, and their leaves would represent particular servers (JVMs). -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12351) Remote JMX connection to servers cannot be established with IPv6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12351: -------------------------------- Assignee: (was: Rob Stryker) Fix Version/s: (was: 4.1.x) These issues are now available for interested parties to investigate a fix for. > Remote JMX connection to servers cannot be established with IPv6 > ---------------------------------------------------------------- > > Key: JBIDE-12351 > URL: https://issues.jboss.org/browse/JBIDE-12351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 3.3.0.Final > Environment: Fedora 17 32bit > EAP 6.0.0.GA > Reporter: Martin Malina > > When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log: > {code} > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > {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

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 April 2014