April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6911) jconsole fails if trying to connect to a standalone EAP instance running with offset ports

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/AS7-6911?page=com.atlassian.jira.plugin.s... ] Stan Silvert updated AS7-6911: ------------------------------ Git Pull Request: https://github.com/jbossas/jboss-as/pull/4401 > jconsole fails if trying to connect to a standalone EAP instance running with offset ports > ------------------------------------------------------------------------------------------ > > Key: AS7-6911 > URL: https://issues.jboss.org/browse/AS7-6911 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Stan Silvert > Labels: cli > > If JBoss AS7/8 is started using port-offset as following: > ie. with -Djboss.socket.binding.port-offset=100 > Then While connecting to it using "jconsole.sh" as a Local Process it throws the following Exception: > +++++++++++++++++++++++++++++ > Exception in thread "AWT-EventQueue-0" java.lang.RuntimeException: Error connecting to JBoss AS. > at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:80) > at sun.tools.jconsole.VMPanel.createPluginTabs(VMPanel.java:641) > at sun.tools.jconsole.VMPanel.propertyChange(VMPanel.java:315) > at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) > at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:75) > at javax.swing.event.SwingPropertyChangeSupport$1.run(SwingPropertyChangeSupport.java:80) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:646) > at java.awt.EventQueue.access$000(EventQueue.java:84) > at java.awt.EventQueue$1.run(EventQueue.java:607) > at java.awt.EventQueue$1.run(EventQueue.java:605) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:616) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) > Caused by: java.lang.NullPointerException > at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:109) > at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:77) > +++++++++++++++++++++++ > And the Code "org.jboss.as.cli.gui.JConsoleCLIPlugin" classes Line 109 throws NullPointerException, Because "cliGuiCtx" object is null and not initialized earlier: > 109 JOptionPane.showMessageDialog(cliGuiCtx.getMainWindow(), message); -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] Tomaz: agreed. This is what I meant in my comment on 2013-03-06. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6345) <vault> does not have module option

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/AS7-6345?page=com.atlassian.jira.plugin.s... ] Anil Saldhana commented on AS7-6345: ------------------------------------ I doubt this is a bug. It may be more like a feature request to provide a module option to specify a module. And even then I am unsure how much coding magic needs to happen. > <vault> does not have module option > ----------------------------------- > > Key: AS7-6345 > URL: https://issues.jboss.org/browse/AS7-6345 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Peter Skopek > > The <vault> element in standalone/domain.xml takes a 'code' attribute specifying the class to use as the implementation. It does not let you specify a 'module' option like most similar elements have, and instead always loads the class from the org.picketbox module. > The <vault> element should take a module option too. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6345) <vault> does not have module option

by Anil Saldhana (JIRA)

[ https://issues.jboss.org/browse/AS7-6345?page=com.atlassian.jira.plugin.s... ] Anil Saldhana reassigned AS7-6345: ---------------------------------- Assignee: Peter Skopek (was: Stefan Guilhen) > <vault> does not have module option > ----------------------------------- > > Key: AS7-6345 > URL: https://issues.jboss.org/browse/AS7-6345 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: James Livingston > Assignee: Peter Skopek > > The <vault> element in standalone/domain.xml takes a 'code' attribute specifying the class to use as the implementation. It does not let you specify a 'module' option like most similar elements have, and instead always loads the class from the org.picketbox module. > The <vault> element should take a module option too. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Tomaz Cerar <tcerar(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] What should be accepted solution to this? Given that composite operation (cli batch) works as expected and verified? In EAP 6.0.x modcluster:add() operation also did not expect or take any attributes: output of operation definition in EAP 6.0.0.GA [standalone@localhost:9999 subsystem=modcluster] :read-operation-description(name=add) { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Operation adding the modcluster subsystem.", "request-properties" => {}, "reply-properties" => {}, "read-only" => false } } Said this, I see no need to add new feature such as adding convenience attribute to subsystem=modcluster:add this late in development stage. I could be nice RFE for 6.2 but absolutely not for 6.1 as it would require lots of additional work (model version upgrade, transformers, additional testing) > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-6911) jconsole fails if trying to connect to a standalone EAP instance running with offset ports

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/AS7-6911?page=com.atlassian.jira.plugin.s... ] Stan Silvert reassigned AS7-6911: --------------------------------- Assignee: Stan Silvert (was: Alexey Loubyansky) > jconsole fails if trying to connect to a standalone EAP instance running with offset ports > ------------------------------------------------------------------------------------------ > > Key: AS7-6911 > URL: https://issues.jboss.org/browse/AS7-6911 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Stan Silvert > Labels: cli > > If JBoss AS7/8 is started using port-offset as following: > ie. with -Djboss.socket.binding.port-offset=100 > Then While connecting to it using "jconsole.sh" as a Local Process it throws the following Exception: > +++++++++++++++++++++++++++++ > Exception in thread "AWT-EventQueue-0" java.lang.RuntimeException: Error connecting to JBoss AS. > at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:80) > at sun.tools.jconsole.VMPanel.createPluginTabs(VMPanel.java:641) > at sun.tools.jconsole.VMPanel.propertyChange(VMPanel.java:315) > at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) > at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:75) > at javax.swing.event.SwingPropertyChangeSupport$1.run(SwingPropertyChangeSupport.java:80) > at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) > at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:646) > at java.awt.EventQueue.access$000(EventQueue.java:84) > at java.awt.EventQueue$1.run(EventQueue.java:607) > at java.awt.EventQueue$1.run(EventQueue.java:605) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87) > at java.awt.EventQueue.dispatchEvent(EventQueue.java:616) > at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) > at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) > at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) > at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) > Caused by: java.lang.NullPointerException > at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:109) > at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:77) > +++++++++++++++++++++++ > And the Code "org.jboss.as.cli.gui.JConsoleCLIPlugin" classes Line 109 throws NullPointerException, Because "cliGuiCtx" object is null and not initialized earlier: > 109 JOptionPane.showMessageDialog(cliGuiCtx.getMainWindow(), message); -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-529) org.jboss.jca.common.api.validator.ValidateException: ResourceAdapter metadata should contains inbound or outbound at least

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-529?page=com.atlassian.jira.plugin.... ] Jesper Pedersen closed JBJCA-529. --------------------------------- Resolution: Out of Date > org.jboss.jca.common.api.validator.ValidateException: ResourceAdapter metadata should contains inbound or outbound at least > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-529 > URL: https://issues.jboss.org/browse/JBJCA-529 > Project: IronJacamar > Issue Type: Enhancement > Components: Common > Reporter: Carlo de Wolf > Assignee: Stefano Maestri > > And thus I'm left in the dark. Without any guidance I can only grope around in the dark seeking some handhold. But alas the message gives no hint and my quest continues. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-905) Arquillian/Remote support

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-905?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-905: ---------------------------------- Fix Version/s: (was: 1.1.0.CR1) > Arquillian/Remote support > ------------------------- > > Key: JBJCA-905 > URL: https://issues.jboss.org/browse/JBJCA-905 > Project: IronJacamar > Issue Type: Task > Components: Arquillian > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-470) Proxy Jdbc adapters instance

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-470?page=com.atlassian.jira.plugin.... ] Jesper Pedersen closed JBJCA-470. --------------------------------- Resolution: Won't Fix > Proxy Jdbc adapters instance > ---------------------------- > > Key: JBJCA-470 > URL: https://issues.jboss.org/browse/JBJCA-470 > Project: IronJacamar > Issue Type: Feature Request > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > It should be possible to cast a jdbc class (for example COnnection) to specific vendor implementation (for example OracleCnnection). > This feature should be configurable (attribute in datasource element in -ds.xml) > Implement it as fast as possible (i.e. javaassit) > Provide a test suite -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-479) Fine grained Metadata validation

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-479?page=com.atlassian.jira.plugin.... ] Jesper Pedersen closed JBJCA-479. --------------------------------- Resolution: Out of Date > Fine grained Metadata validation > -------------------------------- > > Key: JBJCA-479 > URL: https://issues.jboss.org/browse/JBJCA-479 > Project: IronJacamar > Issue Type: Feature Request > Components: Common > Reporter: Stefano Maestri > Labels: community_contribution > > This task is about improve metadata validation to get a finer grained control during Metadata creation. > The current implementation of metadata validate()= method consider only xsd's constraints. IOW it is checking more or less mandatory fields presence and cardinalities of collection. There are much more stuffs that can be verified at a logical level. For example some fields are specifying porperty that make sense only when they are activated by other (boolean) fields, or we can check also related fields for consistency (example: min_pool-size < max_poolsize) -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013