October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1077) @RunAsPrincipal not propagated

by William DeCoste (JIRA)

@RunAsPrincipal not propagated ------------------------------ Key: EJBTHREE-1077 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1077 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA Reporter: William DeCoste Assigned To: William DeCoste -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1188) UnversionedNode.isValid - out of sync (deleted/remotely deleted nodes)

by Mircea Markus (JIRA)

UnversionedNode.isValid - out of sync (deleted/remotely deleted nodes) ---------------------------------------------------------------------- Key: JBCACHE-1188 URL: http://jira.jboss.com/jira/browse/JBCACHE-1188 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: all Reporter: Mircea Markus Assigned To: Mircea Markus Fix For: 2.2.0.GA considering the scenario: thread1: node = cache.get("a/b/c"); thread2(possibly running on another node/JVM): cache.remove("a/b/c"); thread1: node.getAttribute("attr1");//at this point the node is not longer in the cache. we should allow user to check this through isValid node.getAttribute("attr2"); -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4180) Reduce coupling between JMX and HASingleton

by Brian Stansberry (JIRA)

Reduce coupling between JMX and HASingleton ------------------------------------------- Key: JBAS-4180 URL: http://jira.jboss.com/jira/browse/JBAS-4180 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Look at HASingletonController and HASingletonElectionPolicy and factor out the JMX-related stuff. For a unit test, just tried to deploy an HASingletonController as a simple MC bean, no JMX. Fails to start with NPE because HASingletonController is a ServiceMBeanSupport subclass and w/o JMX registration it won't work. -- 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, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBRULES-1242) Archived package assets cannot be restored

by Shahad Ahmed (JIRA)

Archived package assets cannot be restored ------------------------------------------ Key: JBRULES-1242 URL: http://jira.jboss.com/jira/browse/JBRULES-1242 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.1 Reporter: Shahad Ahmed Assigned To: Mark Proctor If you archive (i.e. delete) a package, the archived package does not show up in the list of archived assets under the Admin/Manage Archived Assets option. Consequently there seems to be no way of retrieving an archived package definition. I understand that the rules etc in a package are not archived when you archive a package, but I assume the package definition itself should be available in the list of archived assets? The problem is that if you accidentally archive a package, then you cannot recreate a package with the same name ( it looks as if the BRMS does not allow you to create rules or packages with the same name as archived assets), nor can you retrieve the old package as it is not in the list of archived assets. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1295) DSL Mapping files does not support comments and empty lines

by Edson Tirelli (JIRA)

DSL Mapping files does not support comments and empty lines ----------------------------------------------------------- Key: JBRULES-1295 URL: http://jira.jboss.com/jira/browse/JBRULES-1295 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.2 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.0.3, 4.1.0 Hi Mark, I encountered a problem in DROOLS 4.0.2 (I was upgrading from 3.x). The problem consists in the fact that the DSL syntax has changed, now it does not accept empty lines, and lines continuing on the new line i.e.: # this is ok # <--- Error, empty line [then] name = java expression 1 \ java expression 2 <--- Error, it does not recognize anymore "\" Now, I have a very large DSL file (sorry, I cannot disclose it) and I'm lazy enough not to edit that one, so instead I patched DROOLs with the following code (see the attached files). The code I added is a bit ugly (I'm in a hurry, always in a hurry :( ) I have done some basic tests, but since they are linked to the files that I cannot disclose (once again, sorry for that) they are not added here. Anyway, here's the patch. Feel free to modify the code. .java - my current version .old - the svn extracted one .diff - unified diff I would have also some comments about the class loaders, but I will need to confirm that before making any comment. Hope it will be included (in this form or another) in the next release. Best Regards, Radu -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1766) Portal Administration Icons

by Wesley Hales (JIRA)

Portal Administration Icons --------------------------- Key: JBPORTAL-1766 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1766 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Wesley Hales Create icons for different types of portlets (Described in section 6.2.3.3 of reference guide) -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Deleted: (JBPORTAL-1770) Display icons in portlets list and provide icons for portlets

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-1770?page=all ] Thomas Heute deleted JBPORTAL-1770: ----------------------------------- > Display icons in portlets list and provide icons for portlets > ------------------------------------------------------------- > > Key: JBPORTAL-1770 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-1770 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Heute > Assigned To: Wesley Hales > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1770) Display icons in portlets list and provide icons for portlets

by Thomas Heute (JIRA)

Display icons in portlets list and provide icons for portlets ------------------------------------------------------------- Key: JBPORTAL-1770 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1770 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Admin Reporter: Thomas Heute Assigned To: Wesley Hales Fix For: 2.6.3 Final, 2.8 Final -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1073) Allow mail attribute 'to' resolve EL Expressions

by Fady Matar (JIRA)

Allow mail attribute 'to' resolve EL Expressions ------------------------------------------------ Key: JBPM-1073 URL: http://jira.jboss.com/jira/browse/JBPM-1073 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Fady Matar Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.3 Allow the attribute 'to' in the mail module to resolve EL expressions. Currently the 'to' attribute only encodes hard coded emails -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1109) Client-side race condition while closing connection

by Ovidiu Feodorov (JIRA)

Client-side race condition while closing connection --------------------------------------------------- Key: JBMESSAGING-1109 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.GA Reporter: Ovidiu Feodorov Assigned To: Tim Fox Priority: Minor I've got this while receiving a large number of messages on 20 concurrent sessions (with receive()) @Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message org.jboss.jms.exception.MessagingJMSException: Failed to invoke at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157) at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138) at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java) at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java) at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java) at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703) at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673) at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659) at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54) at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1634) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.remoting.Client.invoke(Client.java:536) at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186) ... 17 more -- 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, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007