June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-838) Can't get implementing classname for JSR77 MBean

by Eduardo Silva (JIRA)

[ https://issues.jboss.org/browse/WFLY-838?page=com.atlassian.jira.plugin.s... ] Eduardo Silva commented on WFLY-838: ------------------------------------ J2EEModuleHandler is causing the problem throwing the exception. private abstract static class J2EEModuleHandler extends J2EEDeployedObjectHandler { ... @Override Set<ObjectName> queryObjectNames(ModelReader reader, ObjectName name, QueryExp query) { throw MESSAGES.shouldNotGetCalled(); } It is overriding the queryObjectNames method. Different from the other Module Handlers like WebModuleHandler, AppClientModuleHandler. Shouldn't we just removing the queryObjectNames override? > Can't get implementing classname for JSR77 MBean > ------------------------------------------------ > > Key: WFLY-838 > URL: https://issues.jboss.org/browse/WFLY-838 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Anders Welen > Priority: Minor > Fix For: Awaiting Volunteers > > > The following exception are thrown when asking the MBean server for the classname implementing "jboss.jsr77:j2eeType=WebModule,name=MyWar.war,J2EEServer=default". > It should be a legal call. Why are the code clearly states it's illegal? > > java.lang.IllegalStateException: JBAS019905: Should not get called > at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers$J2EEModuleHandler.queryObjectNames(J2EEDeployedObjectHandlers.java:245) > at org.jboss.as.jsr77.managedobject.BaseHandler.getMBeanInfo(BaseHandler.java:64) > at org.jboss.as.jsr77.managedobject.J2EEDeployedObjectHandlers.getMBeanInfo(J2EEDeployedObjectHandlers.java:147) > at org.jboss.as.jsr77.managedobject.ManagedObjectHandlerRegistry.getMBeanInfo(ManagedObjectHandlerRegistry.java:112) > at org.jboss.as.jsr77.subsystem.JSR77ManagementMBeanServer.getMBeanInfo(JSR77ManagementMBeanServer.java:179) > at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanInfo(PluggableMBeanServerImpl.java:212) > > The error can easily be triggered by using JConsole to browse the same MBean. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1594) Domain Management logout 'feature' not working for HTTP BASIC authentication.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-1594: -------------------------------------- Summary: Domain Management logout 'feature' not working for HTTP BASIC authentication. Key: WFLY-1594 URL: https://issues.jboss.org/browse/WFLY-1594 Project: WildFly Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Alpha3 The logout capability assumes Digest authentication, where we have used LDAP for authentication we only use BASIC authentication. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1594) Domain Management logout 'feature' not working for HTTP BASIC authentication.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1594?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1594: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=976917 > Domain Management logout 'feature' not working for HTTP BASIC authentication. > ----------------------------------------------------------------------------- > > Key: WFLY-1594 > URL: https://issues.jboss.org/browse/WFLY-1594 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha3 > > > The logout capability assumes Digest authentication, where we have used LDAP for authentication we only use BASIC authentication. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1548) Add fallback querry to jconsole plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1548: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> made a comment on [bug 901311|https://bugzilla.redhat.com/show_bug.cgi?id=901311] A closely related issue is this one: - https://issues.jboss.org/browse/WFLY-1146 However WFLY-1146 has a problem in that it depends on internal sun APIs but also has the same problem as this issue in that it breaks as soon as username / password authentication is mandated. > Add fallback querry to jconsole plugin > -------------------------------------- > > Key: WFLY-1548 > URL: https://issues.jboss.org/browse/WFLY-1548 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Darran Lofthouse > Labels: JConsole, JMX, Plugin > Fix For: 8.0.0.Alpha3 > > > JConsolePlugin connecects to default port, despite chance to use proper info. > Problem: > Unless I miss somethingm JConsole has a bit tight isolation between components. There is no way for AS7 JConsolePlugin to access "connect dialog" info. Hence it has no idea what is the content of URL being passed as remote. > AS7 JConsolePlugin checks if MBeanServerConnection is instance of RemotinConnection. If its not, it fallbacks to default: localhost:9990. > However we can check for socket bindings and try to connect to proper socket. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1548) Add fallback querry to jconsole plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1548?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1548: ----------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> made a comment on [bug 901311|https://bugzilla.redhat.com/show_bug.cgi?id=901311] Not sure why this has a dev ack as I have already removed it once. I do not agree that there should be any attempt to automatically connect to the server if the user has chosen a local connection, the moment we move away from local authentication any attempts to automatically connect fail as there is no mechanism to obtain the users username and password. Where jconsole is connected to the process locally I suggest two alternatives: - - Add the CLI tab but with a clear message stating why the CLI is not currently available, potentially add an 'Establish Connection' button to the tab with the capability to prompt for a username and password if required and make use of the discovered address. - Add an MBean that can handle management ops, the CLI integration can use that MBean regardless of the connection method and would not require the establishment of additional connections. Due to the domain management implications there would be a few parties interested in this so I suggest we get a new discussion started on the dev list. However as I have said elsehwere I think this is attempting to fix a 'feature' that should not exist in it's current form anyway and the current approach whilst it fixes the current problem leaves it open for the next issue to be raised against it once something like the authentication requirements are changed. What we do need is the overall solution that works with the out of the box configuration but is flexible enough to cope with changes to this configuration. > Add fallback querry to jconsole plugin > -------------------------------------- > > Key: WFLY-1548 > URL: https://issues.jboss.org/browse/WFLY-1548 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Darran Lofthouse > Labels: JConsole, JMX, Plugin > Fix For: 8.0.0.Alpha3 > > > JConsolePlugin connecects to default port, despite chance to use proper info. > Problem: > Unless I miss somethingm JConsole has a bit tight isolation between components. There is no way for AS7 JConsolePlugin to access "connect dialog" info. Hence it has no idea what is the content of URL being passed as remote. > AS7 JConsolePlugin checks if MBeanServerConnection is instance of RemotinConnection. If its not, it fallbacks to default: localhost:9990. > However we can check for socket bindings and try to connect to proper socket. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1146) Export remoting-JMX address via JVM instrumentation buffer

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1146?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-1146. ------------------------------------ Fix Version/s: 8.0.0.Alpha3 Resolution: Rejected There are two reasons for rejecting this change: - 1 - It is dependent on an internal sun api which is subject to change and not guaranteed to always be available. 2 - The moment any authentication other than the local authentication mechanism is in place this prevents a connection to the server as no username or password can be entered. > Export remoting-JMX address via JVM instrumentation buffer > ---------------------------------------------------------- > > Key: WFLY-1146 > URL: https://issues.jboss.org/browse/WFLY-1146 > Project: WildFly > Issue Type: Feature Request > Components: JMX > Reporter: James Livingston > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha3 > > > Currently to connect to the AS with JConsole you need to manually enter the service:jmx:remoting-jmx:// address. When the local process connection is used, it retrieves the connection address via the Sun JDK management instrumentation buffer. > The exported address can be set via sun.management.ConnectorAddressLink.export(), and doing that would allow JConsole to connect without typing in the address (although still obviously require the jars to be on the classpath). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-75) Property string values should be trimmed when parsing to other objects

by James Perkins (JIRA)

James Perkins created LOGMGR-75: ----------------------------------- Summary: Property string values should be trimmed when parsing to other objects Key: LOGMGR-75 URL: https://issues.jboss.org/browse/LOGMGR-75 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Values from properties set via the configurator should be trimmed in most cases. For example {{Enum.valueOf()}} should use a trimmed string. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1586) java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-1586?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-1586: -------------------------------- Fix Version/s: (was: 8.0.0.Alpha3) > java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1586 > URL: https://issues.jboss.org/browse/WFLY-1586 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.0.0.Alpha2 > Environment: java version "1.7.0_25" > OpenJDK Runtime Environment (fedora-2.3.10.3.fc17-x86_64) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc17.x86_64 > Reporter: Carlo de Wolf > Assignee: Alessio Soldano > Priority: Blocker > Attachments: org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.txt > > > With the latest update of OpenJDK to 1.7.0.25-2.3.10.3 there is regression w.r.t. WebServices. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1586) java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-1586?page=com.atlassian.jira.plugin.... ] Carlo de Wolf commented on WFLY-1586: ------------------------------------- Do you have a link to the OpenJDK issue? > java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1586 > URL: https://issues.jboss.org/browse/WFLY-1586 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.0.0.Alpha2 > Environment: java version "1.7.0_25" > OpenJDK Runtime Environment (fedora-2.3.10.3.fc17-x86_64) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc17.x86_64 > Reporter: Carlo de Wolf > Assignee: Alessio Soldano > Priority: Blocker > Fix For: 8.0.0.Alpha3 > > Attachments: org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.txt > > > With the latest update of OpenJDK to 1.7.0.25-2.3.10.3 there is regression w.r.t. WebServices. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1643) Change license to Apache License 2.0

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1643?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1643 at 6/26/13 11:25 AM: ---------------------------------------------------------- A list of current contributors (using git ls-files and git-blame): ||Number of commits||Name||Email||Permission|| |14376|Bela Ban|belaban(a)yahoo.com|OK| |1930|Vladimir Blagojevic|vblagoje(a)redhat.com|OK| |88|Richard Achmatowicz|rachmatowicz|OK| |86|Ovidiu Feodorov|ovidiuf|OK| |74|Romuald Du Song|rds13|no code found| |54|Scott marlow|smarlownovell|OK| |46|Brian Stansberry|bstansberry|OK| |32|Jimmy Wilson|jiwils|OK| |32|Steve Wincock|steview|could not contact, contribution mainly ENCRYPT| |33|William Burns|mudokonman(a)gmail.com|OK| |22|Gray Watson|graywatson|OK| |22|Yaron|yaron-r|| |18|Manik Surtani|manik(a)surtani.org|OK| |18|Chris Lott|chrislott|| |12|wenbo|wenbo|OK (met at Google June 20)| |12|David Hotham|david.hotham(a)metaswitch.com|OK| |12|Ananda Bollu|akbollu|OK| |11|Dennis Reed|dereed(a)redhat.com|OK| |8|laran|laran|no code found| |8|Galder Zamarreno|galder(a)redhat.com|OK| |7|Luca Stancapiano|jedim(a)vige.it|jgroups.bnd| |6|John Georgiadis|igeorg|no code found| |6|Ben Browning|bbrowning(a)redhat.com|OK| |6|Paul Ferraro|pperraro(a)redhat.com|OK| |5|Pedro Ruivo|pruivo(a)gsd.inesc-id.pt|OK| |4|Radoslav Husar|rhusar(a)redhat.com|OK| |4|Chris Mills|ossiejnr|OK| |4|Thomas Sorgie|tsorgie|| |4|publicnmi|publicnmi|only comments in history.txt| |4|Sanne Grinovero|sanne(a)redhat.com|OK| |3|Dan Berindei|dan(a)infinispan.org|OK| |3|blc.jgroups|blc.jgroups(a)gmail.com|| |3|Nick Bailey|nickmbailey(a)gmail.com|OK| |2|rvansa|rvansa(a)redhat.com|OK| |2|gdvieira|gdvieira|only comment in history.txt| |2|Mark Riley|mark_riley99|no code found| |2|mimbert|mimbert|no code found| |2|mircea_markus|mmarkus(a)redhat.com|OK| |1|Bill DeCoste|bdecoste(a)gmail.com|OK| |1|Tristan Tarrant|ttarrant(a)redhat.com|OK| |1|Thomas SEGISMONT|tsegimont(a)gmail.com|OK| |1|Ales Justin|ales.justin(a)gmail.com|OK| |1|Raman Gupta|raman(a)rocketraman.com|OK| |1|Pedro Ruivo|pedroruivo2(a)gmail.com|OK| |1|Markus Wolf|mail(a)markus-wolf.de|OK| |1|Gustavo Fernandes|gustavonalle(a)gmail.com|OK| |1|Youngjae Chang|youngjae.chang(a)miracom.co.kr|OK| was (Author: belaban): A list of current contributors (using git ls-files and git-blame): ||Number of commits||Name||Email||Permission|| |14376|Bela Ban|belaban(a)yahoo.com|OK| |1930|Vladimir Blagojevic|vblagoje(a)redhat.com|OK| |88|Richard Achmatowicz|rachmatowicz|OK| |86|Ovidiu Feodorov|ovidiuf|OK| |74|Romuald Du Song|rds13|no code found| |54|Scott marlow|smarlownovell|OK| |46|Brian Stansberry|bstansberry|OK| |32|Jimmy Wilson|jiwils|OK| |32|Steve Wincock|steview|could not contact, contribution mainly ENCRYPT| |33|William Burns|mudokonman(a)gmail.com|OK| |22|Gray Watson|graywatson|OK| |22|Yaron|yaron-r|| |18|Manik Surtani|manik(a)surtani.org|OK| |18|Chris Lott|chrislott|| |12|wenbo|wenbo|OK (met at Google June 20)| |12|David Hotham|david.hotham(a)metaswitch.com|OK| |12|Ananda Bollu|akbollu|OK| |11|Dennis Reed|dereed(a)redhat.com|OK| |8|laran|laran|no code found| |8|Galder Zamarreno|galder(a)redhat.com|OK| |7|Luca Stancapiano|jedim(a)vige.it|jgroups.bnd| |6|John Georgiadis|igeorg|no code found| |6|Ben Browning|bbrowning(a)redhat.com|OK| |6|Paul Ferraro|pperraro(a)redhat.com|OK| |5|Pedro Ruivo|pruivo(a)gsd.inesc-id.pt|OK| |4|Radoslav Husar|rhusar(a)redhat.com|OK| |4|Chris Mills|ossiejnr|OK| |4|Thomas Sorgie|tsorgie|| |4|publicnmi|publicnmi|only comments in history.txt| |4|Sanne Grinovero|sanne(a)redhat.com|OK| |3|Dan Berindei|dan(a)infinispan.org|OK| |3|blc.jgroups|blc.jgroups(a)gmail.com|| |3|Nick Bailey|nickmbailey(a)gmail.com|OK| |2|rvansa|rvansa(a)redhat.com|OK| |2|gdvieira|gdvieira|only comment in history.txt| |2|Mark Riley|mark_riley99|no code found| |2|mimbert|mimbert|no code found| |2|mircea_markus|mmarkus(a)redhat.com|OK| |1|Bill DeCoste|bdecoste(a)gmail.com|OK| |1|Tristan Tarrant|ttarrant(a)redhat.com|OK| |1|Thomas SEGISMONT|tsegimont(a)gmail.com|OK| |1|Ales Justin|ales.justin(a)gmail.com|OK| |1|Raman Gupta|raman(a)rocketraman.com|| |1|Pedro Ruivo|pedroruivo2(a)gmail.com|OK| |1|Markus Wolf|mail(a)markus-wolf.de|OK| |1|Gustavo Fernandes|gustavonalle(a)gmail.com|OK| |1|Youngjae Chang|youngjae.chang(a)miracom.co.kr|OK| > Change license to Apache License 2.0 > ------------------------------------ > > Key: JGRP-1643 > URL: https://issues.jboss.org/browse/JGRP-1643 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.4 > > > Change the license from LGPL 2.1 to AL 2.0. This includes the following tasks: > * Identify all contributors who have code in master (to be 3.4) > * Remove contributors who are Red Hat employees (work-for-hire) > * Remove contributors who were Red Hat employees at the time of the contribution > * Contact the remaining contributors and ask for their permission to change the license > * Change the web site to list both LGPL 2.1 (<= 3.3) and AL 2.0 (>= 3.4) licenses > * Change LICENSE in master: include both licenses, state that code <= 3.3 is licensed under LGPL 2.1 and later code is licensed under AL 2.0 -- 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, 4 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 June 2013