[JBoss JIRA] Created: (JBAS-4344) Problematic casting to String in org.jboss.jmx.connector.invoker.AuthenticationInterceptor
by David Dossot (JIRA)
Problematic casting to String in org.jboss.jmx.connector.invoker.AuthenticationInterceptor
------------------------------------------------------------------------------------------
Key: JBAS-4344
URL: http://jira.jboss.com/jira/browse/JBAS-4344
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.0.4.GA
Environment: Mac Os X, RedHat
Reporter: David Dossot
Assigned To: Dimitris Andreadis
There is a problematic cast in org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(Invocation invocation) on line 110:
String opname = (String) obj[1];
When Twiddling to get a particular attribute, the following code is used in org.jboss.console.twiddle.command.GetCommand.execute(String[] args) on line 165:
attributeNames.toArray(names);
(...)
AttributeList attrList = server.getAttributes(objectName, names);
So obj[1] ends up holding a String[] of attribute names (even if there is only one) and the cast fails:
14:14:44,760 ERROR [Twiddle] Exec failed
java.lang.ClassCastException: [Ljava.lang.String; cannot be cast to java.lang.String
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)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
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:589)
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.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
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:589)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:679)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:704)
at java.lang.Thread.run(Thread.java:637)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:331)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:194)
at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy0.getAttributes(Unknown Source)
at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:168)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)
--
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
16 years, 4 months
[JBoss JIRA] Created: (JBRULES-2108) A rule does not fire for all objects satisfying the rule code.
by Andrey Nechaev (JIRA)
A rule does not fire for all objects satisfying the rule code.
--------------------------------------------------------------
Key: JBRULES-2108
URL: https://jira.jboss.org/jira/browse/JBRULES-2108
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 4.0.7
Reporter: Andrey Nechaev
Assignee: Mark Proctor
The following code shows the problem:
public class DroolsTest {
private final static int NUM_FACTS = 20;
private final static String rule = "" +
"package test\n" +
"import com.test.DroolsTest;\n" +
"import com.test.DroolsTest.Foo;\n" +
"import com.test.DroolsTest.Bar;\n" +
"rule test\n" +
"\twhen\n" +
"\t\tFoo($p : id < " + Integer.toString(NUM_FACTS) + ") && Bar(id == $p)\n" +
"\tthen\n" +
"\t\tDroolsTest.incCounter();\n" +
"end";
private static int counter;
public static class Foo {
private final int id;
Foo(int id) {
this.id = id;
}
public int getId() {
return id;
}
}
public static class Bar {
private final int id;
Bar(int id) {
this.id = id;
}
public int getId() {
return id;
}
}
public static void main(String[] args) throws Exception {
RuleBase rb;
WorkingMemory wm;
counter = 0;
rb = RuleBaseFactory.newRuleBase();
wm = rb.newStatefulSession();
for(int i = 0; i < NUM_FACTS; i++) {
wm.insert(new Foo(i));
wm.insert(new Bar(i));
}
PackageBuilder bld = new PackageBuilder();
bld.addPackageFromDrl(new StringReader(rule));
rb.addPackage(bld.getPackage());
System.out.println(counter == NUM_FACTS ? "passed" : "failed");
}
public static void incCounter() {
++counter;
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months
[JBoss JIRA] Created: (JBAS-6292) Documentation should include transitioning from AS 4.2 to AS 5.0
by Bruce Link (JIRA)
Documentation should include transitioning from AS 4.2 to AS 5.0
----------------------------------------------------------------
Key: JBAS-6292
URL: https://jira.jboss.org/jira/browse/JBAS-6292
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Docs/Installation and Getting Started Guide
Affects Versions: JBossAS-5.0.0.GA
Environment: Not applicable
Reporter: Bruce Link
Assignee: Samson Kittoli
The installation and getting started guide should have a chapter on transitioning applications from JBoss AS 4.2 to JBoss AS 5.0. Examples discussed might be changes in build class path and configuration documents. For example, when using EJB3, the persistence.xml seems to need to specify a JBoss schema. The release notes is vague in this area.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months
[JBoss JIRA] Created: (JBBUILD-504) Fix warning messages in the app server buld.
by Paul Gier (JIRA)
Fix warning messages in the app server buld.
--------------------------------------------
Key: JBBUILD-504
URL: https://jira.jboss.org/jira/browse/JBBUILD-504
Project: JBoss Build System
Issue Type: Task
Components: JBossBuild/Buildmagic
Reporter: Paul Gier
Fix For: JBossBuild - Maint 2008
The app server build gives warning messages about the custom tasks being overridden for each module. This should be fixed so that these warnings do not continue.
{quote}
Trying to override old definition of task libraryset
Trying to override old definition of task execmodules
Trying to override old definition of task resolveproperties
Trying to override old definition of task resolver
Trying to override old definition of task require
Trying to override old definition of task _dump
Trying to override old definition of task _puke
Trying to override old definition of task moduleinit
Trying to override old definition of task moduleconfig
Trying to override old definition of task modulelibrary
Trying to override old definition of task projectinfo
Trying to override old definition of task library
Trying to override old definition of task Ant
Trying to override old definition of task moduleinfo
Trying to override old definition of task projecthelp
Trying to override old definition of task propertyfilter
Trying to override old definition of task call
Trying to override old definition of task property
{quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 4 months