May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1328) Profile and optimise TransactionTable

by Manik Surtani (JIRA)

Profile and optimise TransactionTable ------------------------------------- Key: JBCACHE-1328 URL: http://jira.jboss.com/jira/browse/JBCACHE-1328 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transactions Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.2.0.GA The TxInterceptor uses TxTable.getLocalTransaction(gtx) for every remotely originating prepare and commit call. This is inefficient since it traverses all map entries, and will not scale. A simple Map keyed on gtx with txs as values would work, but perhaps a further optimisation is possible - transaction entries could be looked up by the InvocationContextInterceptor and stored in the InvocationContext. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-207) Release 2.0.2.CR1

by Anil Saldhana (JIRA)

Release 2.0.2.CR1 ----------------- Key: SECURITY-207 URL: http://jira.jboss.com/jira/browse/SECURITY-207 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2.Beta7 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1351) exclude-class-interceptors on a method level binding is ignored

by Kabir Khan (JIRA)

exclude-class-interceptors on a method level binding is ignored --------------------------------------------------------------- Key: EJBTHREE-1351 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1351 Project: EJB 3.0 Issue Type: Sub-task Reporter: Kabir Khan Assigned To: Kabir Khan -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-217) AuthenticationManager Interface JASPI valid method needs to consider a CallbackHandler

by Anil Saldhana (JIRA)

AuthenticationManager Interface JASPI valid method needs to consider a CallbackHandler -------------------------------------------------------------------------------------- Key: SECURITY-217 URL: http://jira.jboss.com/jira/browse/SECURITY-217 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2.Beta7 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR1 The Callbackhandler is quite critical for JASPI auth module processing. So rather than relying on the general cbh in the authentication manager, we should have a CBH as part of the method. -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1350) exclude-default-interceptors on a method level binding is ignored

by Kabir Khan (JIRA)

exclude-default-interceptors on a method level binding is ignored ----------------------------------------------------------------- Key: EJBTHREE-1350 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1350 Project: EJB 3.0 Issue Type: Sub-task Reporter: Kabir Khan Assigned To: Kabir Khan -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1349) exclude-default-interceptors on a class level binding is ignored

by Kabir Khan (JIRA)

exclude-default-interceptors on a class level binding is ignored ---------------------------------------------------------------- Key: EJBTHREE-1349 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1349 Project: EJB 3.0 Issue Type: Sub-task Reporter: Kabir Khan Assigned To: Kabir Khan -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5374) Add additional assertions in Delete Unit test in testsuite to check if ManagedComponent still exists after a delete.

by Mark Spritzler (JIRA)

Add additional assertions in Delete Unit test in testsuite to check if ManagedComponent still exists after a delete. -------------------------------------------------------------------------------------------------------------------- Key: JBAS-5374 URL: http://jira.jboss.com/jira/browse/JBAS-5374 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Mark Spritzler -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1348) @ExcludeDefaultInterceptors is ignored for lifecycle interceptors

by Kabir Khan (JIRA)

@ExcludeDefaultInterceptors is ignored for lifecycle interceptors ----------------------------------------------------------------- Key: EJBTHREE-1348 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1348 Project: EJB 3.0 Issue Type: Sub-task Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: AS 5.0.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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5517) Missing configuration for HA local datasource. No url-delimiter.

by Sumanth Kalyan (JIRA)

Missing configuration for HA local datasource. No url-delimiter. ---------------------------------------------------------------- Key: JBAS-5517 URL: http://jira.jboss.com/jira/browse/JBAS-5517 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Environment: Linux AS 4.0, MySql 5.0.51, IBM Power Server Reporter: Sumanth Kalyan Assigned To: Adrian Brock We are Using JBoss-4.2.2GA Server for testing and Evaluation for Production Deployment. We are looking for the feature fail over for the DB. we have configured the server mysql-ds.xml for the same. Configured mysql configuration is as provided. <?xml version="1.0" encoding="UTF-8"?>   <datasources> <ha-local-tx-datasource> <jndi-name>MySqlDS</jndi-name> <use-java-context>true</use-java-context> <connection-url>jdbc:mysql://192.168.0.219:3306/MIS||jdbc:mysql://192.168.0.218:3306/MIS</connection-url> <url-delimeter>||</url-delimeter> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>xxxxxxx</user-name> <password>xxxxxxx</password> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>  <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>  <new-connection-sql>select current_date()</new-connection-sql>  <check-valid-connection-sql>select current_date()</check-valid-connection-  <min-pool-size>5</min-pool-size>  <max-pool-size>20</max-pool-size> <set-tx-query-timeout/>  <query-timeout>300</query-timeout>  <metadata> <type-mapping>mySQL</type-mapping> </metadata> </ha-local-tx-datasource> </datasources> we are getting a constant error saying (We have also tested the same with Single Piped Delimeter) org.jboss.util.NestedSQLException: Missing configuration for HA local datasource. No url-delimiter. ; - nested throwable: (or g.jboss.resource.JBossResourceException: Missing configuration for HA local datasource. No url-delimiter. ) but we have configured the parameter in the xml file. on further analsys in debug mode we found the tag itself is not read. <server> <mbean code='org.jboss.resource.connectionmanager.TxConnectionManager' display-name='ConnectionManager for DataSource MySqlDS' name='jboss.jca:service=LocalTxCM,name=MySqlDS'> <attribute name='TrackConnectionByTx'>true</attribute> <attribute name='LocalTransactions'>true</attribute> <depends optional-attribute-name='ManagedConnectionPool'> <mbean code='org.jboss.resource.connectionmanager.JBossManagedConnectionPool' display-name='Connection Pool for DataSource MySqlDS' name='jboss.jca:service=ManagedConnectionPool,name=MySqlDS'> <depends optional-attribute-name='ManagedConnectionFactoryName'> <mbean code='org.jboss.resource.connectionmanager.RARDeployment' display-name='ManagedConnectionFactory for DataSource MySqlDS' name='jboss.jca:service=ManagedConnectionFactory,name=MySqlDS'> <depends optional-attribute-name='OldRarDeployment'>jboss.jca:service=RARDeployment,name='jboss-ha-local-jdbc.rar'</depends> <attribute name='RARName'/> <attribute name='ConnectionDefinition'>javax.sql.DataSource</attribute> <attribute name='ManagedConnectionFactoryProperties'> <properties> <config-property name='ConnectionURL' type='java.lang.String'>jdbc:mysql://192.168.0.219:3306/MIS||jdbc:mysql://192.168.0.218:3306/MIS</config-property> <config-property name='DriverClass' type='java.lang.String'>com.mysql.jdbc.Driver</config-property> <config-property name='UserName' type='java.lang.String'>misuser</config-property> <config-property name='Password' type='java.lang.String'>misuser</config-property> <config-property name='NewConnectionSQL' type='java.lang.String'>select current_date()</config-property> <config-property name='CheckValidConnectionSQL' type='java.lang.String'>select current_date()</config-property> <config-property name='ValidConnectionCheckerClassName' type='java.lang.String'>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</config-property> <config-property name='ExceptionSorterClassName' type='java.lang.String'>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</config-property> <config-property name='TransactionQueryTimeout' type='boolean'>true</config-property> <config-property name='QueryTimeout' type='int'>300</config-property> <config-property name='ValidateOnMatch' type='boolean'>true</config-property> </properties> </attribute> </mbean> </depends> <attribute name='PoolJndiName'>MySqlDS</attribute> <attribute name='MinSize'>5</attribute> <attribute name='MaxSize'>20</attribute> <attribute name='BlockingTimeoutMillis'>30000</attribute> <attribute name='IdleTimeoutMinutes'>15</attribute> <attribute name='BackGroundValidation'>False</attribute> <attribute name='BackGroundValidationMinutes'>10</attribute> <attribute name='PreFill'>False</attribute> <attribute name='UseFastFail'>False</attribute> <attribute name='Criteria'>ByNothing</attribute> </mbean> </depends> <attribute name='JndiName'>MySqlDS</attribute> <depends optional-attribute-name='CachedConnectionManager'>jboss.jca:service=CachedConnectionManager</depends> <depends optional-attribute-name='TransactionManagerService'>jboss:service=TransactionManager</depends> </mbean> <mbean code='org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService' display-name='Binding for DataSource MySqlDS' name='jboss.jca:service=DataSourceBinding,name=MySqlDS'> <attribute name='JndiName'>MySqlDS</attribute> <attribute name='UseJavaContext'>true</attribute> <depends optional-attribute-name='ConnectionManager'>jboss.jca:service=LocalTxCM,name=MySqlDS</depends> </mbean> <mbean code='org.jboss.ejb.plugins.cmp.jdbc.metadata.DataSourceMetaData' name='jboss.jdbc:service=metadata,datasource=MySqlDS'> <depends optional-attribute-name='MetadataLibrary'>jboss.jdbc:service=metadata</depends> <attribute name='TypeMapping'>mySQL</attribute> </mbean> </server> would request you to provide the solution for the same. Also we are looking for Switching back to the same DB Once the DB has been restored. We are already running on the tight schedule, looking forward for earlier response. Thanks Sumanth Kalyan -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2010) error after deleting a WSRP consumer

by Prabhat Jha (JIRA)

error after deleting a WSRP consumer ------------------------------------ Key: JBPORTAL-2010 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2010 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.5 Final Reporter: Prabhat Jha Assigned To: Thomas Heute Fix For: 2.6.5 Final -Create a bea consumer - Create instance of hello world portlet - Delete bea consumer - Go to portlet definitions. you will get the following. This is not a WSRP problem. There should be a check if provider exists or not. javax.portlet.PortletException: /WEB-INF/jsf/portlets.xhtml: Exception getting value of property selectedPortlet of base of type : org.jboss.portal.core.admin.ui.PortletManagerBean at org.apache.myfaces.portlet.MyFacesGenericPortlet.handleExceptionFromLifecycle(MyFacesGenericPortlet.java:310) at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:502) at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:323) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133) at javax.portlet.GenericPortlet.render(GenericPortlet.java:306) Caused by java.lang.NullPointerException at org.jboss.portal.core.admin.ui.PortletManagerBean.getSelectedPortlet(PortletManagerBean.java:340) at sun.reflect.GeneratedMethodAccessor726.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.myfaces.el.PropertyResolverImpl.getProperty(PropertyResolverImpl.java:457) at org.apache.myfaces.el.PropertyResolverImpl.getValue(PropertyResolverImpl.java:85) at org.jboss.portal.faces.el.DelegatingPropertyResolver.getValue(DelegatingPropertyResolver.java:166) at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:141) at com.sun.el.parser.AstValue.getValue(AstValue.java:96) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:183) at com.sun.facelets.el.ELText$ELTextVariable.toString(ELText.java:160) at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:45) at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:34) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:232) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:540) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132) at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:498) at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:323) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133) at javax.portlet.GenericPortlet.render(GenericPortlet.java:306) at org.jboss.portal.faces.loader.FacesPortlet.render(FacesPortlet.java:100) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeRender(PortletContainerImpl.java:483) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:405) at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:86) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:106) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeRequired(TransactionInterceptor.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:72) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:50) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(ProducerCacheInterceptor.java:58) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.portlet.AjaxInterceptor.invoke(AjaxInterceptor.java:51) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.ModesInterceptor.invoke(ModesInterceptor.java:62) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:47) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.WindowStatesInterceptor.invoke(WindowStatesInterceptor.java:55) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.PortletSessionSynchronizationInterceptor.invoke(PortletSessionSynchronizationInterceptor.java:80) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:46) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor$1.doCallback(ContextDispatcherInterceptor.java:104) at org.jboss.portal.web.command.CommandDispatcher$CallbackCommand.execute(CommandDispatcher.java:74) -- 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, 2 months

2
1
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 May 2008