January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-505) RoundRobinPointToPointRouter occasionally throws ArithmeticException: / by zero

by Ovidiu Feodorov (JIRA)

RoundRobinPointToPointRouter occasionally throws ArithmeticException: / by zero ------------------------------------------------------------------------------- Key: JBMESSAGING-505 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-505 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.0.1.CR5 This error message shows up in logs when all receivers are removed from the router. It is harmless and it doesn't affec functionality. -- 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, 4 months

3
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-683) CLONE -MSSQL configuration appears invalid

by Markus Lutum (JIRA)

CLONE -MSSQL configuration appears invalid ------------------------------------------ Key: JBMESSAGING-683 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-683 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR5 Reporter: Markus Lutum Assigned To: Clebert Suconic Fix For: 1.0.1.GA The MSSQL persistence manager config appears to be invalid. This needs to be tested with the entire functional tests suite. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-705) ConnectionFactory service is registered under JMX "jboss.messaging.destination:" domain, it shoud be "jboss.messaging.connectionfactory:" or similar.

by Ovidiu Feodorov (JIRA)

ConnectionFactory service is registered under JMX "jboss.messaging.destination:" domain, it shoud be "jboss.messaging.connectionfactory:" or similar. ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-705 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-705 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.CR1 -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-757) JDBCPersistenceManager incorrectly detects if a replytoId was null when restoring a message from a ResultSet

by Ilya Bochkov (JIRA)

JDBCPersistenceManager incorrectly detects if a replytoId was null when restoring a message from a ResultSet ------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-757 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-757 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP2 Reporter: Ilya Bochkov Assigned To: Ovidiu Feodorov JDBCPersistenceManager, line 728: boolean replyToExists = rs.wasNull(); -- incorrectly detects if a value was null or not. should do exactly the opposite: boolean replyToExists = !rs.wasNull(); -- note the negation -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-756) Enable mdb-failure smoke test so it will run with the smoke test suite

by Ovidiu Feodorov (JIRA)

Enable mdb-failure smoke test so it will run with the smoke test suite ---------------------------------------------------------------------- Key: JBMESSAGING-756 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-756 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.SP4 -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-755) Bring mdb-failure's README.html up to date

by Ovidiu Feodorov (JIRA)

Bring mdb-failure's README.html up to date ------------------------------------------ Key: JBMESSAGING-755 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-755 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.SP4 -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4031) failing org.jboss.test.jacc.test.* tests

by Dimitris Andreadis (JIRA)

failing org.jboss.test.jacc.test.* tests ---------------------------------------- Key: JBAS-4031 URL: http://jira.jboss.com/jira/browse/JBAS-4031 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Client VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.EL OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Scott M Stark Priority: Critical Fix For: JBossAS-4.2.0.CR1 A lot of JACC tests (currenty 62) fail with the message: SecurityException; nested exception is: java.lang.SecurityException: Denied: (javax.security.jacc.EJBMethodPermission StatefulSession create,Home,java.lang.String)[Home:create(java.lang.String)], caller=null java.rmi.AccessException: SecurityException; nested exception is: java.lang.SecurityException: Denied: (javax.security.jacc.EJBMethodPermission StatefulSession create,Home,java.lang.String)[Home:create(java.lang.String)], caller=null at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:388) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:136) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:637) at org.jboss.ejb.Container.invoke(Container.java:975) 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.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:231) 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 javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201) at $Proxy15.invoke(Unknown Source) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) Caused by: java.lang.SecurityException: Denied: (javax.security.jacc.EJBMethodPermission StatefulSession create,Home,java.lang.String)[Home:create(java.lang.String)], caller=null at org.jboss.ejb.plugins.JaccAuthorizationInterceptor.checkSecurityAssociation(JaccAuthorizationInterceptor.java:115) at org.jboss.ejb.plugins.JaccAuthorizationInterceptor.invokeHome(JaccAuthorizationInterceptor.java:76) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:189) at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invokeHome(StatefulSessionInstanceInterceptor.java:143) at org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:56) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:125) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:161) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:132) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:107) at org.jboss.ejb.SessionContainer.internalInvokeHome(SessionContainer.java:637) at org.jboss.ejb.Container.invoke(Container.java:975) 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.unified.server.UnifiedInvoker.invoke(UnifiedInvoker.java:231) 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 javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201) at $Proxy15.invoke(Unknown Source) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.remoting.Client.invoke(Client.java:604) at org.jboss.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175) 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 $Proxy2.create(Unknown Source) at org.jboss.test.security.test.EJBSpecUnitTestCase.testStatefulCreateCaller(EJBSpecUnitTestCase.java:163) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-3729) Add alternate run-as mappings for container callbacks

by Scott M Stark (JIRA)

Add alternate run-as mappings for container callbacks ----------------------------------------------------- Key: JBAS-3729 URL: http://jira.jboss.com/jira/browse/JBAS-3729 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2, EJB3, Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-4.0.6.CR1 Other app servers support anlternate run-as semantics from the container init/destroy lifecycle callbacks. Weblogic for example: http://e-docs.bea.com/wls/docs81/webapp/weblogic_xml.html#1041058 This is an equivalent of <run-as> for init method for servlets. For example: <init-as> <servlet-name>FooServlet</servlet-name> <principal-name>joe</principal-name> </init-as> <destroy-as> <servlet-name>BarServlet</servlet-name> <principal-name>bob</principal-name> </destroy-as> This would allow more control over how these methods interact with secured resources. Similar options could be added for ejb lifecycle methods as well. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-695) We need to be able to run our functional testsuite with other databses besides HSQLDB

by Clebert Suconic (JIRA)

We need to be able to run our functional testsuite with other databses besides HSQLDB ------------------------------------------------------------------------------------- Key: JBMESSAGING-695 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-695 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Right now we can't as part of the database is different when we run Clustered or non Clustered tests. Maybe we should aways use the same DDL to simplify things. (I'm not sure aobut that.. just guessing) Also... it looks like we will have some residual data on the database in between tests. -- 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, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-739) Make sure db schema is correct

by Tim Fox (JIRA)

Make sure db schema is correct ------------------------------ Key: JBMESSAGING-739 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-739 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.CR1 When 1.2 is released we want to make sure the db schema is optimal, since we don't want to have to change it again unless we really have to. We may be able to trim some fields from the message table. -- 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, 4 months

2
2
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 January 2007