November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (GPD-29) referencing an unknown class gives exception at deployment

by Koen Aers (JIRA)

referencing an unknown class gives exception at deployment ---------------------------------------------------------- Key: GPD-29 URL: http://jira.jboss.com/jira/browse/GPD-29 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers preferrably, this should be a warning in the problems view. in case the class is not found to be included in the .par, it just shouldn't be included. maybe a warning would be good; -- 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

15 years, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (GPD-63) Inner classes are not deployed.

by Matej Knopp (JIRA)

Inner classes are not deployed. ------------------------------- Key: GPD-63 URL: http://jira.jboss.com/jira/browse/GPD-63 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.0.13 Reporter: Matej Knopp Assigned To: Koen Aers When process is being deployed, the inner classes are ignored. So when I have class Foo with inner class Bar, the Foo.class file gets deployed, but the Foo$Bar.class is not. -- 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

15 years, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBRULES-1215) Solver in debug mode asks toString() of a Move after doing it

by Geoffrey De Smet (JIRA)

Solver in debug mode asks toString() of a Move after doing it ------------------------------------------------------------- Key: JBRULES-1215 URL: http://jira.jboss.com/jira/browse/JBRULES-1215 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Optional so it's incorrect in the logs: DEBUG Move ([Queen-0] 0 @ 0 => 0) ignored because not doable. DEBUG Move ([Queen-0] 0 @ 1 => 1) with score (-4.0) and acceptChance (1.0). should be DEBUG Move ([Queen-0] 0 @ 0 => 0) ignored because not doable. DEBUG Move ([Queen-0] 0 @ 0 => 1) with score (-4.0) and acceptChance (1.0). Also fix the logging output in the manual as it now shows this bug. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4028) nosuchmethoderror

by tony anecito (JIRA)

nosuchmethoderror ----------------- Key: JBAS-4028 URL: http://jira.jboss.com/jira/browse/JBAS-4028 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: Windows 2000 Professional JDK 1.6.0 Reporter: tony anecito 21:10:46,843 ERROR [[/invoker]] Exception sending context initialized event to l istener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigure Listener java.lang.NoSuchMethodError: javax.servlet.ServletContext.getContextPath()Ljava/ lang/String; at com.sun.faces.config.WebConfiguration.getServletContextName(WebConfig uration.java:191) -- 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

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1053) Write a test for JBMESSAGING-1031

by Clebert Suconic (JIRA)

Write a test for JBMESSAGING-1031 --------------------------------- Key: JBMESSAGING-1053 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1053 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.4.0.GA I have fixed JBMESSAGING-1031 using a manual test.. we need to add a testcase. -- 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

15 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-478) Create indexes to improve performance

by Tim Fox (JIRA)

Create indexes to improve performance ------------------------------------- Key: JBMESSAGING-478 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-478 Project: JBoss Messaging Issue Type: Sub-task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Create indexes in memory so that we don't have to iterate through all the messages in memory to find the ones that match. Also make sure it all works when messages are paged to storage. -- 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

15 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1109) Clustered proxy factories don't bind home proxies

by Brian Stansberry (JIRA)

Clustered proxy factories don't bind home proxies ------------------------------------------------- Key: EJBTHREE-1109 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1109 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.2.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 5.0.0.Beta3 StatefulClusterProxyFactory and StatelessClusterProxyFactory differ from the others in not binding home proxies. -- 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

15 years, 11 months

4
15
0 / 0

[JBoss JIRA] Created: (JBAS-3945) RunAs Causes Unexpected Principal Propagation Switch

by Stefan Schulze (JIRA)

RunAs Causes Unexpected Principal Propagation Switch ---------------------------------------------------- Key: JBAS-3945 URL: http://jira.jboss.com/jira/browse/JBAS-3945 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Environment: JBoss 4.0.5.GA JSE 1.5.0_09 Reporter: Stefan Schulze Assigned To: Scott M Stark Attachments: runAsError.zip My application is using JAAS authentication on web and ejb side. An authenticated user calls a stateless session bean from the web application which uses 'runAs' to change security role and calls a second stateless session bean. The second bean recuperates an 'anonymous' principal but it should be the authenticated user. This does not happen on our production server (JBoss 3.2.7) but on JBoss 4.05.GA. Test case: I try to attach my test case (where can I attach it ???) which boils down the problem. To run it, please - unzip the file (runAsError.zip) - you can import the content as a project in Eclipse if you prefer - change the 'jboss.dist' property in the 'ant.properties' file to your jBoss 4.0.5.GA installation - run the 'install' target of 'build.xml' which creates a new jboss container called 'runAsError' - start the 'runAsError' container (run -c runAsError) - run the 'test' target of 'build.xml' What happens: Standalone client calls Session1.hello() with caller principal 'max' . Session1 calls Session2.hello2() using runAs 'internal'. Session2 should get caller principal 'max' but gets 'anonymous'. See Exception that is thrown in SessionBean2.hello2(). It seems to be a different bug than http://jira.jboss.com/jira/browse/JBAS-1852 since I run the JBAS-1852 test and it seemed to work (I had some troubles with the DatabaseServerLoginModule that were probably related to my incompetence ;-). -- 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

15 years, 11 months

5
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-987) support DeliveryActive MDB activation config property

by William DeCoste (JIRA)

support DeliveryActive MDB activation config property ----------------------------------------------------- Key: EJBTHREE-987 URL: http://jira.jboss.com/jira/browse/EJBTHREE-987 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 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

15 years, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1013) Manual merge queue feature via JMX

by Evgueni Smoliar (JIRA)

Manual merge queue feature via JMX ---------------------------------- Key: JBMESSAGING-1013 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1013 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management, JMS Clustering Environment: Clustering/load balancing Reporter: Evgueni Smoliar Assigned To: Tim Fox In a case of disaster recovery you are obliged always to recover last running cluster node. Otherwise some messages will remain in the queue waiting for this node to startup. Idd there is a workaround for this, but it's not always easy to do. Would me much nicer to have a manual function to merge queues ( or reallocate messages) preferably available via JMX. For more detail please check forum. -- 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

15 years, 11 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007