[ http://issues.apache.org/jira/browse/DERBY-2144?page=comments#action_12459508 ] Suresh Thalamati commented on DERBY-2144: -----------------------------------------
I could not reporduce the problem on SuSE Linux 9.0 (i586) using ibm142 jvm. I saw similar error only when per process file limit in my environment was 1024,. once I fixed that query compiled without any problems. Error I saw with file descriptors are limited to 1024 in my environment. : ij> Select * from vwDerbyBasePackage_derbygen_DerbyRepositoryObject67ceb178; ERROR XSDG3: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFCon [EMAIL PROTECTED] could not be accessed ERROR XJ001: Java exception: '/home/suresht/work/tests/wombat/seg0/c16e1.dat (To o many open files): java.io.FileNotFoundException'. > Meta-data for Container could not be accessed when execute a SQL (select > statement) for a View with 322 sub tables and views > ---------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-2144 > URL: http://issues.apache.org/jira/browse/DERBY-2144 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.2.1.6 > Environment: IBM JDK 1.4.2 with the Websphere 6.0.2.5 as the > application server on Windows XP with service pack 2 > for Derby 10.1.2.6 > Reporter: Suraj Batuwana > Attachments: DerbyIssue.zip > > > I'm getting the following stack trace (in attached derby.log) when using > embedded network server derby 10.2.1.6 > I am getting following client side errors from my junit test cases as > > Error when executing > query:com.ibm.websphere.ce.cm.StaleConnectionException: Meta-data for > Container [EMAIL PROTECTED] could not be accessed > junit.framework.AssertionFailedError: Error when executing > query:com.ibm.websphere.ce.cm.StaleConnectionException: Meta-data for > Container [EMAIL PROTECTED] could not be accessed > Other than that I am seeing some of the errors from websphere server.log as > [11/15/06 11:04:47:738 IST] 0000002c SystemErr R > java.sql.SQLException: Failed to start database 'E:\Cloud_Branch\TestDB', see > the next exception for details.DSRA0010E: SQL State = XJ040, Error Code = > 40,000DSRA0010E: SQL State = XJ040, Error Code = 40,000 > at > sun.reflect.GeneratedConstructorAccessor243.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java(Compiled > Code)) > at > java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code)) > at > com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java:501) > at > com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java:544) > at > com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:1037) > at > com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:957) > at > com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1551) > > Also when creating the data source in websphere I have used following classes > as well > > Implementing class name > "org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource" > Implementing class name for XA > "org.apache.derby.jdbc.EmbeddedXADataSource" > Datasource Helper Class Name > "com.ibm.websphere.rsadapter.DerbyDataStoreHelper" > Driver Class Path > "c:\jars\derby-10.2.1.6.jar;c:\jars\derbynet-10.2.1.6.jar;c:\jars\derbytools-10.2.1.6.jar" > > After that I was able to extract the issue from my application > In my application there are 1000+ tables and 200+ views and each table > has its own index. > There is a particular view which uses 322 other tables and views like > as > > create view vwDerbyBasePackage_derbygen_DerbyRepositoryObject67ceb178 > (container_rid,derby_repos_object_id_derby,derby_created_by_user_derby,derby_creation_timestamp_derby,derby_modified_by_user_derby,derbymodificationtimestampxmet,derby_optimistic_lock_id_derby)AS > select > t.container_rid,t.derby_repos_object_id_derby,t.derby_created_by_user_derby,t.derby_creation_timestamp_derby,t.derby_modified_by_user_derby,t.derbymodificationtimestampxmet,t.derby_optimistic_lock_id_derby > from DerbyBasePackage_derbygen_DerbyRepositoryObject67ceb178 t > union all select > t0.container_rid,t0.derby_repos_object_id_derby,t0.derby_created_by_user_derby,t0.derby_creation_timestamp_derby,t0.derby_modified_by_user_derby,t0.derbymodificationtimestampxmet,t0.derby_optimistic_lock_id_derby > from DerbyCore_derbygen_XQMAnnotationse07f3bbc t0 > ........................................... > ........................................... > union all select > t322.container_rid,t322.derby_repos_object_id_derby,t322.derby_created_by_user_derby,t322.derby_creation_timestamp_derby,t322.derby_modified_by_user_derby,t322.derbymodificationtimestampxmet,t322.derby_optimistic_lock_id_derby > from BusinessObjects_derbygen_Table52171d14 t322 > > When I have execute the simple select on this particular view as SELECT * > FROM vwDerbyBasePackage_derbygen_DerbyRepositoryObject67ceb178 > I was able to reproduce the issue wich is in attached derby.log > How to reproduce the error > -------------------------- > createDB.sql in the attached zip file has all the sqls for database tables, > indexes and views > Error comes when run SELECT * FROM > vwDerbyBasePackage_derbygen_DerbyRepositoryObject67ceb178 > Can use the CreateDatabase.bat to create the derby database and > TestIssue.bat can use to test the issue. > Please refer > http://www.nabble.com/Re%3A-Error-when-executing-query%3Acom.ibm.websphere.ce.cm.StaleConnectionException%3A-Meta-data-for-Container-org.apache.derby.impl.store.raw.data.RAFContainer%406fd148fc-could-not-be-accessed-p7647298.html > For more information on this defect where Army and Suresh has describes the > reason for the defect. > Please let me know if any more details are needed regarding on this issue > -Suraj -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
