Suraj Batuwana wrote:
Hi,
I have received a server side error as
Error when executing
query:org.apache.derby.client.am.DisconnectException: Execution failed
due to a distribution protocol error that caused deallocation of the
conversation. The requested command encountered an unarchitected and
implementation specific condition for which there was no architected
message.
com.ascential.xmeta.query.QueryException: Error when executing
query:org.apache.derby.client.am.DisconnectException: Execution failed
due to a distribution protocol error that caused deallocation of the
conversation. The requested command encountered an unarchitected and
implementation specific condition for which there was no architected
message.
I have used the IBM WebSphere Application Server Community Edition
Version 1.1 as the application server and the Derby 10.1 Net work
server as the database.
When create the datasource I have used the
<config-property-setting name="Password">pass</config-property-setting>
<config-property-setting name="PortNumber">1527</config-property-setting>
<config-property-setting
name="ServerName">localhost</config-property-setting>
<config-property-setting
name="DatabaseName">TestDB</config-property-setting>
<config-property-setting name="UserName">newuser</config-property-setting>
for the cloudscape datasource plan. Also I have used the
tranql-connector-derby-client-local-1.1.rar and
tranql-connector-derby-client-xa-1.1.rar as the tranql connectors.
While the above exception throws at the serverside following exception
will throw as derby.log
Server is ready to accept connections on port 1527.
Connection number: 1.
Connection number: 2.
Connection number: 3.
Connection number: 4.
------------ BEGIN SHUTDOWN ERROR STACK -------------
ERROR XSDG3: Meta-data for Container
[EMAIL PROTECTED] could not
be accessed
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at org.apache.derby.impl.store.raw.data.RAFContainer.run(Unknown Source)
at java.security.AccessController.doPrivileged1(Native Method)
at
java.security.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at
org.apache.derby.impl.store.raw.data.RAFContainer.openContainer(Unknown
Source)
at org.apache.derby.impl.store.raw.data.FileContainer.setIdent(Unknown
Source)
at
org.apache.derby.impl.store.raw.data.RAFContainer.setIdentity(Unknown
Source)
at
org.apache.derby.impl.services.cache.CachedItem.takeOnIdentity(Unknown
Source)
at org.apache.derby.impl.services.cache.Clock.addEntry(Unknown Source)
at org.apache.derby.impl.services.cache.Clock.find(Unknown Source)
at
org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown
Source)
at
org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown
Source)
at org.apache.derby.impl.store.raw.xact.Xact.openContainer(Unknown Source)
at
org.apache.derby.impl.store.access.btree.index.B2IFactory.readConglomerate(Unknown
Source)
at
org.apache.derby.impl.store.access.RAMAccessManager.conglomCacheFind(Unknown
Source)
at
org.apache.derby.impl.store.access.RAMTransaction.findExistingConglomerate(Unknown
Source)
at
org.apache.derby.impl.store.access.RAMTransaction.openStoreCost(Unknown
Source)
at
org.apache.derby.impl.sql.compile.CompilerContextImpl.getStoreCostController(Unknown
Source)
at
org.apache.derby.impl.sql.compile.FromBaseTable.getStoreCostController(Unknown
Source)
at
org.apache.derby.impl.sql.compile.FromBaseTable.estimateCost(Unknown
Source)
at
org.apache.derby.impl.sql.compile.OptimizerImpl.estimateTotalCost(Unknown
Source)
at
org.apache.derby.impl.sql.compile.OptimizerImpl.costBasedCostOptimizable(Unknown
Source)
at
org.apache.derby.impl.sql.compile.OptimizerImpl.costOptimizable(Unknown
Source)
After the above exception happens any operation doing with my
application get fails.
Note: None of this issue is happening when my application is running with
Derby 10.1 and IBM WebSphere Application Server 6.0.2.5.
So I have assumed this happens only when the Derby 10.1 and IBM
WebSphere Application Server Community Edition Version 1.1.
I am using the java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build
cn142ifx-20051115 (SR3 + 94164 + 97403 + 97482) (JIT enabled: jitc))
This comes with the IBM Websphere IBM Websphere Application Server
6.0.2.5.
Even with the
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build
pwi32devifx-20060818 (ifix: 108655: SR2 + 107350 + 108225 + 108262))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32
j9vmwi3223-20060504 (JIT enabled)
With comes with the IBM WebSphere Application Server Community Edition
Version 1.1 was not able to solve problem
Or when use a higher version of derby
I am using tranql-connector-derby-client-local-1.1.rar and
tranql-connector-derby-client-xa-1.1.rar as the tranql connectors not
the embedded one. Use the above TranQL is one of the project
requirements. Because of that I have not tested with embedded version
of the TranQL adapter.
The above exception happens when I run a set of test cases for my
application as a nightly build. The error occurs in the 3rd test
class. So I have removed the 3rd test class and run it again. I have
found that the same error happens in a different test class below.
Each of the test class has different functionalities
Is this a known issue among the community?
Is there any kind of solution for this?
Thanks,
Suraj
Hi Suraj -
Here's some possibilities:
Are you starting Network Server separately and then starting WAS CE (or
visa versa). If so the problem could be in how you are starting the
Network Server, the version of Network Server you are using or it could
be related to the fact that WAS CE starts it's own instance of Network
Server (as does the software it is based on, the Geronimo App Server).
If possible, use the Network Server instance that WAS CE starts and use
the client jarfile that comes with WAS CE. This will greatly simplify
the configuration and insure that the same version of Network Server and
Derby are used for all databases.
If you require a different version or separate instance of Network
Server be sure you start this instance listening on a different port
number that the one WAS CE uses AND be sure that the version of the
client jar matches or is a higher higher version than the most recent
version of the
Network Server being started (the client driver is backward compatible
but not necessarily forward compatible).
If this doesn't help please detail how you are starting Network Server
and supply the information from '....NetworkServerControl sysinfo' as
well as any console messages that may be displayed.
Is the derby.log file you cite found in the WAS CE installation tree or
elsewhere?
