[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, 3 months
[JBoss JIRA] Created: (EJBTHREE-649) Query Performance within transaction decreasing progressively when using default FlushModeType.AUTO
by Andreas Zimmer (JIRA)
Query Performance within transaction decreasing progressively when using default FlushModeType.AUTO
---------------------------------------------------------------------------------------------------
Key: EJBTHREE-649
URL: http://jira.jboss.com/jira/browse/EJBTHREE-649
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Environment: WinXP SP2, Oracle 9i Enterprise Rel. 9.2.0.1.0, JBoss 4.0.4GA, EJB3.0 RC8-FD
Reporter: Andreas Zimmer
Query Performance within a Transaction is progressively decreasing when working with EJB3.0 default FlushModeType.AUTO:
20 queries/reads within transaction - 10 msecs average per query/read
1000 (same as before) queries/reads within transaction - 130 msecs average per query/read (factor 13+)
With FlushModeType.COMMIT query performance within the same scenario ist constant at expected 10 msecs but FlushModeType.COMMIT imposes restrictions which our projects can't cope with. We need updates within transaction being visible in subsequent queries of the same transaction.
The case is explained in some detail in the JBoss Forum Thread as provided in JBoss Forum Reference.
--
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, 3 months
[JBoss JIRA] Created: (EJBTHREE-694) @OneToOne relation fails, when foreign key is in inverse side
by Martin Isheim (JIRA)
@OneToOne relation fails, when foreign key is in inverse side
-------------------------------------------------------------
Key: EJBTHREE-694
URL: http://jira.jboss.com/jira/browse/EJBTHREE-694
Project: EJB 3.0
Issue Type: Bug
Components: EJB3 Extensions
Affects Versions: EJB 3.0 RC8 - FD
Environment: JBoss AS 4.0.4 GA3 with jboss-EJB-3.0_RC8-FD installed as described in the release.
Reporter: Martin Isheim
I defined a OneToOne relation from "UserEntity" to "PasswordEntity", with the foreign key in the "PasswordEntity" (for historical reasons).
With EntityManager.persist() the entities were inserted into the database, but the foreignKey column in "PasswordEntity" is empty.
Reading the "UserEntity" provides an empty relation.
Here the getter from "UserEntity":
<code>
private PasswordEntity password;
@OneToOne(optional = true, cascade = CascadeType.ALL)
@PrimaryKeyJoinColumn(name = "ENTITYKEY", referencedColumnName = "USERKEY")
public PasswordEntity getPassword() {
return password;
}
</code>
Since the relation is unidirectional, "PaswordEntity" has no getter/setter.
Regards.
--
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, 3 months
[JBoss JIRA] Created: (EJBTHREE-684) Ejb3 deployer does not allow method overriding with Java 1.5 Covariant return types
by Swarn Dhaliwal (JIRA)
Ejb3 deployer does not allow method overriding with Java 1.5 Covariant return types
-----------------------------------------------------------------------------------
Key: EJBTHREE-684
URL: http://jira.jboss.com/jira/browse/EJBTHREE-684
Project: EJB 3.0
Issue Type: Bug
Affects Versions: EJB 3.0 RC8 - FD
Environment: Jboss-4.0.4.GA with ejb3 installed using the installer 'jboss-4.0.4.GA-Patch1-installer.jar'
Reporter: Swarn Dhaliwal
We have ejb3 entities which use method overiding with java 1.5 covariant return types. The code works correctly in jboss-4.0.4rc1 with ejb3 installed using the installer.
However when trying to deploy the same code in the aforementioned version a compilation exception is thrown indicating that there are duplicate methods in the class. The code looks like the following :
public abstract class AbstractEntity {
protected abstract Object getId();
}
public class ConcreteEntity extends AbstractEntity {
public String getId() {
return id;
}
}
--
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, 3 months