October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1212) Rete throws NoClassDefFoundError when asserting facts with classess loaded by inaccessible classloader.

by Alexander Gavrilov (JIRA)

Rete throws NoClassDefFoundError when asserting facts with classess loaded by inaccessible classloader. -------------------------------------------------------------------------------------------------------- Key: JBRULES-1212 URL: http://jira.jboss.com/jira/browse/JBRULES-1212 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.1 Reporter: Alexander Gavrilov Assigned To: Mark Proctor We using drools as part of security enfocement engine in our application, based on Tapestry4 framework. Tapestry4 pages and components is abstract classes with some abstract methods, for which tapestry generates implementation at runtime. For example, if i declare page public abstract SomePage extends BasePage { } Tapestry will generate class in default package like public SomePage$_0 extends BasePage { } On page loading whe using instantiated page objects ans Drools Facts to ensure, that current user has permissions to load this page. In the previos verions we used (3.0.6) all worked fine. After update to version 4.0.1 whe got the NoClassDefFoundError when triyng to assert Page object into working memory. This is becouse tapestry creates classes for pages in private classloader, which is child of the application classloader. When Drools tries to generate shadowing proxy for generated Page class it generate code like public class SomePage$_0ShadowProxy extends SomePage$_0 { } Later, when it tries to load this class with MapBackedClassLoader, it can not find definition for class SomePage$_0 and throws NoClassDefFoundError. This type of error does not handled correctly by drools. -- 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

18 years, 5 months

3
8
0 / 0

[JBoss JIRA] Created: (JBRULES-1233) Solver should use slf4j, like jbrms

by Geoffrey De Smet (JIRA)

Solver should use slf4j, like jbrms ----------------------------------- Key: JBRULES-1233 URL: http://jira.jboss.com/jira/browse/JBRULES-1233 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional which can use log4j behind it -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-1066) equivalent of pooled-actors group functionality in mailnodes

by Ross McDonald (JIRA)

equivalent of pooled-actors group functionality in mailnodes ------------------------------------------------------------ Key: JBPM-1066 URL: http://jira.jboss.com/jira/browse/JBPM-1066 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2.2, jBPM jPDL 3.2.1 Environment: any Reporter: Ross McDonald Assigned To: Tom Baeyens Priority: Minor It would be nice to be able to specify a group to mail to within mail nodes, to save having to put semicolon separated actors in. This would enable the database to control who is going to be emailed, and avoid the need to keep updating processes 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-305) Provide support for JMS transport

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-305?page=all ] David Lloyd updated JBREM-305: ------------------------------ JBoss Forum Reference: http://jboss.com/index.html?module=bb&op=viewtopic&t=120444 > Provide support for JMS transport > --------------------------------- > > Key: JBREM-305 > URL: http://jira.jboss.com/jira/browse/JBREM-305 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 beta > Reporter: Thomas Diesler > Assigned To: David Lloyd > Fix For: 4.0.0.Beta1 > > > The web service layer has a need for JMS transport -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-59) JCA work for JBoss-5.0.0Beta

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-59?page=comments#action_12380678 ] Dimitris Andreadis commented on JBAS-59: ---------------------------------------- What other work relates to this task? The only subtask is scheduled for CR1. > JCA work for JBoss-5.0.0Beta > ---------------------------- > > Key: JBAS-59 > URL: http://jira.jboss.com/jira/browse/JBAS-59 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Weston Price > Fix For: JBossAS-5.0.0.Beta3 > > > Schedule -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3151) Convert HA-JNDI stubs to Remoting

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3151?page=all ] Dimitris Andreadis reassigned JBAS-3151: ---------------------------------------- Assignee: Ron Sigal (was: Tom Elrod) Assign to Ron. It could also be rescheduled. > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: JBAS-3151 > URL: http://jira.jboss.com/jira/browse/JBAS-3151 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assigned To: Ron Sigal > Fix For: JBossAS-5.0.0.Beta3 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2145) Testsuite JBossMQ destination deployment is broken

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2145?page=all ] Dimitris Andreadis closed JBAS-2145. ------------------------------------ Fix Version/s: (was: JBossAS-5.0.0.Beta3) Resolution: Out of Date I suppose this is not current anymore? > Testsuite JBossMQ destination deployment is broken > -------------------------------------------------- > > Key: JBAS-2145 > URL: http://jira.jboss.com/jira/browse/JBAS-2145 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-5.0.0.Beta1 > Reporter: Adrian Brock > Assigned To: Sacha Labourey > > The change to only deploy destinations as part of the testsuite run > is broken. e.g. > 2005-08-19 15:03:28,885 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/scratch/cruisecontrol/checkout/jboss-head-testsuite/testsuite/outp > ut/resources/messaging/test-destinations-full-service.xml > org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:name=A,service=Queue > at org.jboss.system.ServiceCreator.install(ServiceCreator.java:72) > at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:429) > at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:151) > at org.jboss.system.ServiceController.install(ServiceController.java:216) > at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) > Sacha, why did you change this? > This needs fixing properly anyway such that the tests run against both JBossMQ and JBoss Messaging. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2149) ByValueContainerInvoker

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2149?page=all ] Dimitris Andreadis updated JBAS-2149: ------------------------------------- Comment: was deleted > ByValueContainerInvoker > ----------------------- > > Key: JBAS-2149 > URL: http://jira.jboss.com/jira/browse/JBAS-2149 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Adrian Brock > Fix For: JBossAS-5.0.0.Beta3 > > > Remove the use of ByValueInvokerInterceptor from the testsuite. > This was deprecated in JBoss4 and removed in JBoss5, it should be using the MarshalledInvokerInterceptor. -- 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

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4484) org.jboss.security.auth.callback.MapCallback not serializable

by Dirk Gfroerer (JIRA)

org.jboss.security.auth.callback.MapCallback not serializable ------------------------------------------------------------- Key: JBAS-4484 URL: http://jira.jboss.com/jira/browse/JBAS-4484 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Environment: Linux ghlx06 2.4.21-50.EL #1 SMP Tue May 8 17:10:00 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux RHEL 3 x86_64 Reporter: Dirk Gfroerer Assigned To: Scott M Stark I'm securing access to my EJBs via a security domain. Everything was working fine until I had to add a second login module to my application-policy in login-config.xml. I now do have to login-modules both of them are flagged as being sufficient. However if now a user tries to login and uses an invalid account / password I get the following exception: Exception in thread "main" java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) 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:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy0.create(Unknown Source) at de.guhsoft.eDHR.OrderManager.testclient.GetUserInformation.doAction(GetUserInformation.java:71) at de.guhsoft.eDHR.OrderManager.testclient.GetUserInformation.main(GetUserInformation.java:92) Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) ... 12 more Caused by: java.io.NotSerializableException: org.jboss.security.auth.callback.MapCallback at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416) at java.lang.Throwable.writeObject(Throwable.java:648) 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:597) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:343) 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:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) -- 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

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-880) Non persistent messages can be sent one way

by Tim Fox (JIRA)

Non persistent messages can be sent one way ------------------------------------------- Key: JBMESSAGING-880 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-880 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 When sending non persistent messages from client to server. They can be sent oneway, i.e. no need to wait for a response that the message has been receive on the server. This should massively increase performance since we will not be hostage to networks with large RTT. -- 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

18 years, 5 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007