August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3405) Unable to secure JMX Invoker

by amdonov (JIRA)

Unable to secure JMX Invoker ---------------------------- Key: JBAS-3405 URL: http://jira.jboss.com/jira/browse/JBAS-3405 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.3 SP1 Environment: Windows Sun JDK 1.5 Reporter: amdonov I am having the same problem securing the JMX invoker as the user in the referenced forum thread. However, I'm running 4.0.4.GA instead of 4.0.3 SP1. When, performing a clean installation using the installer. I selected the default configuration and elected to secure the invokers. The install completes without error. JBoss has the following error which is unfortunatly only written at the DEBUG level. 2006-07-20 10:40:47,541 DEBUG [org.jboss.mx.modelmbean.ModelMBeanInvoker] Failed to invoke ctor(MBeanInvoker) for: class org.jboss.jmx.connector.invoker.AuthenticationInterceptor java.lang.NoSuchMethodException: org.jboss.jmx.connector.invoker.AuthenticationInterceptor.<init>(org.jboss.mx.server.MBeanInvoker) at java.lang.Class.getConstructor0(Class.java:2647) at java.lang.Class.getConstructor(Class.java:1629) at org.jboss.mx.modelmbean.ModelMBeanInvoker.getInterceptors(ModelMBeanInvoker.java:739) at org.jboss.mx.modelmbean.ModelMBeanInvoker.configureInterceptorStack(ModelMBeanInvoker.java:678) at org.jboss.mx.modelmbean.XMBean.configureInterceptorStack(XMBean.java:400) at org.jboss.mx.modelmbean.ModelMBeanInvoker.init(ModelMBeanInvoker.java:504) at org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:486) at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654) at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697) at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:211) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1422) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1417) at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350) at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:181) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) at org.jboss.system.ServiceController.install(ServiceController.java:226) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy6.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:464) at java.lang.Thread.run(Thread.java:595) 2006-07-20 10:40:47,551 DEBUG [org.jboss.system.ServiceCreator] Created bean: Access to the adaptors is not restricted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3524) Support Kerberos authentication in CSIv2

by David Robison (JIRA)

Support Kerberos authentication in CSIv2 ---------------------------------------- Key: JBAS-3524 URL: http://jira.jboss.com/jira/browse/JBAS-3524 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: IIOP service Affects Versions: JBossAS-4.0.4.GA Environment: JBoss 4.0.4.GA Reporter: David Robison Assigned To: Francisco Reverbel JacORB supports Kerberos Authentication as part of its SAS implementation. I would be useful for JBoss to support it as part of his JBoss CSIv2 implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBJMX-99) Ant task <jmx><setAttribute> problem : unable to use <value> tag inside

by Benoit Lavenier (JIRA)

Ant task <jmx><setAttribute> problem : unable to use <value> tag inside ----------------------------------------------------------------------- Key: JBJMX-99 URL: http://jira.jboss.com/jira/browse/JBJMX-99 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: Windows XP, JRE 1.5 Eclipse 3.2 Ant 1.6.5 Reporter: Benoit Lavenier The Ant task JMX (org.jboss.ant.JMX) has a code error in the subclass "Setter" (used by <setAttribute> sub task) The methode named setValue in Setter subclass should be "addValue" Please refer to the folowwing url : http://ant.apache.org/manual/develop.html , and the "Supporting nested elements" section I think the following code will works fine : // "setValue" method (of subclass Setter) remaned in "addValue" public void addValue(Param value) { // This will only consider the last <value> tag, if more than one tag this.value = value; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-523) Implement topic hierarchies

by Tim Fox (JIRA)

Implement topic hierarchies --------------------------- Key: JBMESSAGING-523 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-523 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Implement topic hierarchies so a subscription can subscribe to a wildcard, e.g. news.* and will receive all messages sent to topics news.uk, news.usa, news.usa.local etc etc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

5
8
0 / 0

[JBoss JIRA] Created: (JBRULES-380) Create some decision table examples

by william hayhurst (JIRA)

Create some decision table examples ----------------------------------- Key: JBRULES-380 URL: http://jira.jboss.com/jira/browse/JBRULES-380 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Decision tables, Documentation Affects Versions: 3.0 Reporter: william hayhurst Assigned To: Mark Proctor Attachments: barbarian.xls As per IRC, some more fleshed out examples of decision tables in action. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

5
14
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-146) Clustered EJB setting at the application level (EAR)

by Galder Zamarreno (JIRA)

Clustered EJB setting at the application level (EAR) ---------------------------------------------------- Key: JBCLUSTER-146 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-146 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry We are using clustering for tests. Our application is an ear-archive which has no information about clustering. If we will built up a cluster, we have to change the ejb-jar.xml to set the clustered-tag on True. This is very intricate. Out support team have to unpack the ear - set the clustered-tag for every bean and so on. Is it possible to set the clustered-tag all beans in a ear-Archive? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAOP-283) Better documentation for metadata and CallLoggingInterceptor

by Kabir Khan (JIRA)

Better documentation for metadata and CallLoggingInterceptor ------------------------------------------------------------ Key: JBAOP-283 URL: http://jira.jboss.com/jira/browse/JBAOP-283 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
15
0 / 0

[JBoss JIRA] Created: (JBPORTAL-953) wiki not visible

by Sacha Labourey (JIRA)

wiki not visible ---------------- Key: JBPORTAL-953 URL: http://jira.jboss.com/jira/browse/JBPORTAL-953 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Sacha Labourey deploying wiki.war from portletswap in JBP deploy's folder doesn't make it visible in the list of creatable portlet (admin interface) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (HIBERNATE-43) SQL native Request who respond only the first letter

by Alexandre PETRILLO (JIRA)

SQL native Request who respond only the first letter ---------------------------------------------------- Key: HIBERNATE-43 URL: http://jira.jboss.com/jira/browse/HIBERNATE-43 Project: Hibernate Issue Type: Bug Environment: Jboss 4.0.4 G.A. patch 1 Reporter: Alexandre PETRILLO Assigned To: Steve Ebersole I need to do some sql native query (to a data base Oracle 9i) from an EJB session Bean. I use Jboss in version 4.0.4 G.A. patch 1 My simple code : public List doNativeQueryMultiple(String sqlQuery) { List list = manager.createNativeQuery(sqlQuery).getResultList(); return list; } This is some exemple for understand the probleme. SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : O,N SELECT 'TOTO' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : TOTO,NON SELECT 'TOT' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc Response is : T,N SELECT 'OUI' val FROM dual union SELECT 'abc' FROM dual Order BY 1 asc Response is : O,a SELECT 'OUI' val FROM dual union SELECT 'abcd' FROM dual Order BY 1 asc Response is : OUI,abcd SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOT' FROM dual Order BY 1 asc Response is : O,N,T SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOTO' FROM dual Order BY 1 asc Response is : OUI,NON,TOTO When the response of the request is correct, the return class type is java.lang.String And when is incorrect , the return class type is java.lang.Charactere, and the response contain the first letter. The bug is when the size of all of the selected string have the same length. The test done by Jboss for determine the class return type maybe is wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBJMX-98) Monitoring Only Sends Single Notification Message

by Brian Husted (JIRA)

Monitoring Only Sends Single Notification Message ------------------------------------------------- Key: JBJMX-98 URL: http://jira.jboss.com/jira/browse/JBJMX-98 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: Windows 2000, Sun JDK 1.5, Single CPU 1GB RAM Reporter: Brian Husted I have configured a threshold monitoring mbean to monitor the QueueDepth on a JMS queue. When the QueueDepth is greater than 500, I have registered to receive a notification on the ConsoleAlterListener. The problem is that only one notification is sent when the QueueDepth exceeds 500. The depth will go back down below 500 and minutes later it will again exceed 500 but a notificaiton is NOT sent. I did notice that if I click the clear-all-alerts button on the web-console then the notification will be sent again but only if you clear it each time it appears. Below is my config for the threshold monitor. I have tested this with the ConsoleAlertMonitor and a custom MBeanListener and I experience the same problem with either configuration. [Code] <?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="org.jboss.monitor.ThresholdMonitor" name="jboss.monitor:service=SlaveQueue_Monitor"> <attribute name="MonitorName">SlaveQueue Monitor</attribute> <depends optional-attribute-name="ObservedObject">jboss.mq.destination:service=Queue,name=B</depends> <attribute name="ObservedAttribute">QueueDepth</attribute> <depends-list optional-attribute-name="AlertListeners"> <depends-list-element>jboss.alerts:service=ConsoleAlertListener</depends-list-element> </depends-list> <attribute name="Threshold">500</attribute> <attribute name="Period">2000</attribute> <attribute name="CompareTo">-1</attribute> <attribute name="Enabled">true</attribute> </mbean> </server> [/Code] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006