[JBoss JIRA] Created: (JBAS-3431) AuthorizationInterceptor throwing ArrayIndexOutOfBoundsException
by Anil Saldhana (JIRA)
AuthorizationInterceptor throwing ArrayIndexOutOfBoundsException
----------------------------------------------------------------
Key: JBAS-3431
URL: http://jira.jboss.com/jira/browse/JBAS-3431
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX, Security
Affects Versions: JBossAS-4.0.4.GA
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1
As Originally reported in JBJMX-97, the user says:
==========================================================================================
I have secured the jmx-invoker-service using JAAS and the standard UsersRolesLoginModule. I am able to authenticate (basic authentication) through the web UI and manage the console using the same login config.
I am getting a remote connection to the JMX server from an InitialContext that is populated with the user name and password:
env.put(Context.SECURITY_PRINCIPAL, userName);
env.put(Context.SECURITY_CREDENTIALS, password);
Then I look up the MBeanServerConnection and try to get the MBeanInfo
MBeanServerConnection server = lookup("jmx/invoker/RMIAdaptor", MBeanServerConnection.class);
ObjectName name = new ObjectName(theName);
MBeanInfo info = server.getMBeanInfo(name);
At this point the server throws an ArrayIndexOutOfBoundsException from org.jboss.jmx.connector.invoker.AuthorizationInterceptor line 107.
If I try and set an attribute:
server.setAttribute(name, new Attribute("searchText", searchText));
I get instead at the same line:
java.lang.ClassCastException: javax.management.Attribute
at org.jboss.jmx.connector.invoker.AuthorizationInterceptor.invoke(AuthorizationInterceptor.java:107)
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
==========================================================================================
--
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
19 years, 5 months
[JBoss JIRA] Created: (JBAS-3776) Update SerialVersionUIDUnitTestCase to test against new versions
by Ryan Campbell (JIRA)
Update SerialVersionUIDUnitTestCase to test against new versions
----------------------------------------------------------------
Key: JBAS-3776
URL: http://jira.jboss.com/jira/browse/JBAS-3776
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Ryan Campbell
Priority: Critical
Fix For: JBossAS-4.0.6.CR1
Here is how to build the .ser database of serialVersionUIDs:
Builid jboss-4.0.5 with jdk14
cd build/output
java -XX:MaxPermSize=512m -Xmx2000m -cp ../../varia/output/classes org.jboss.tools.SerialVersionUID jboss-4.0.5.GA/
cp serialuid.ser $WORK/Branch_4_0/testsuite/src/etc/serialVersionUID/405.ser
Then the SerialVersionUIDUnitTestCase needs to be updated to test against 4.0.3SP1, 4.0.4, and 4.0.5.
The badpackages list will probably need to be different for each version.
--
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
19 years, 5 months
[JBoss JIRA] Created: (JBAS-3838) ServerInfo does not check response from getThreadInfo for null
by Darran Lofthouse (JIRA)
ServerInfo does not check response from getThreadInfo for null
--------------------------------------------------------------
Key: JBAS-3838
URL: http://jira.jboss.com/jira/browse/JBAS-3838
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: MicroContainer bus
Affects Versions: JBossAS-4.0.5.GA
Reporter: Darran Lofthouse
Assigned To: Darran Lofthouse
Fix For: JBossAS-4.2.0.CR1
The ServerInfo MBean does not check the response from getThreadInfo for null. If getThreadInfo is called for a thread that no longer exists it returns null. Currently it is possible for the following NullPointerException to be logged: -
java.lang.NullPointerException
at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.system.server.ServerInfo.getThreadCpuUtilization(ServerInfo.java:557)
at org.jboss.system.server.ServerInfo.listThreadCpuUtilization(ServerInfo.java:510)
at sun.reflect.GeneratedMethodAccessor113.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
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
19 years, 5 months