Assert in NsDom.cpp from dbxml 2.3.8

I was able to temporarily workaround my previous assert problems by including the function declarations inline, rather than in a separate file. That got me a little farther, but I hit another assert.
Sorry if I just keep finding new ways to harp on the same bug.
Here is the error:
Assertion failed: tmp == first, NsDom.cpp:1015
Here is the query:
declare namespace model = "http://bpointsys.com/model";
declare ordering ordered;
declare function model:getModel($root as element()*,$name as xs:string)
as element()?
if ($root/testmodel[@name=$name]) then
let $dataset := collection()/testdata[string(@modelname)=$name]
let $max := max($dataset/@iteration)
let $lastrun := $dataset[@iteration=$max][1]
for $m in $root/testmodel[@name=$name]
return element { fn:local-name($m) } {
$m/../@class,
$m/@*,
attribute lastrun {
string($lastrun/@endtime)
attribute lastrunby {
string(collection()/config:config/auth/users/user[string(@id) =
                    string ($lastrun/@user)]/@name)
attribute result {
string($lastrun/@result)
$m/node()
else
model:getModel(collection()/(testmodel:testmodels|testmodel:cannedmodels),$name)

I get a similar assert for this much simpler query when running as a 'removeStep' in an xmodify operation on a document.
[kraney@future control]$ rlwrap dbxml
Joined existing environment
dbxml> open config.dbxml
dbxml> setNamespace testmodel "http://bpointsys.com/schema/testmodel"
Binding testmodel -> http://bpointsys.com/schema/testmodel
dbxml> getDoc testmodels
1 documents found
dbxml> contextQuery "//workingCopy[@user='dev' and @instance='']"
2 objects returned for expression '//workingCopy[@user='dev' and @instance='']'
dbxml> removeNodes "/testmodel:testmodels/workingCopy[@user='dev' and @instance='']"
Removing nodes: /testmodel:testmodels/workingCopy[@user='dev' and @instance='']
Assertion failed: !next || (next->_nsElemPrev == this), NsDom.cpp:1312
Also,
dbxml> removeNodes "//workingCopy[@user='dev' and @instance='']"
Removing nodes: //workingCopy[@user='dev' and @instance='']
Assertion failed: !next || (next->_nsElemPrev == this), NsDom.cpp:1312                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • Assertion from dbxml 2.3.8

    I am getting an assert error from dbxml 2.3.8
    example:
    [kraney@future control]$ rlwrap dbxml
    Joined existing environment
    dbxml> open config.dbxml
    dbxml> setNamespace testmodel "http://bpointsys.com/schema/testmodel"
    Binding testmodel -> http://bpointsys.com/schema/testmodel
    dbxml> query "import module namespace model = 'http://bpointsys.com/model' at 'file:///home/kraney/workspace/control/test.dbxml'; model:getModel(collection()/testmodel:cannedmodels,'Fake')"
    Assertion failed: qp_->getType() == QueryPlan::PATHS, QueryPlanHolder.cpp:82
    The test.dbxml file is the following:
    module namespace model = "http://bpointsys.com/model";
    declare function model:getModel($root as element()*,$name as xs:string)
    as element()?
    if ($root/testmodel[@name=$name]) then
    else
    };

    Hi Kris,
    I've found the cause of this bug, and we will aim to release a fix for it soon.
    John

  • SQL Server Assertion: File: "logmgr.cpp" , line=5512

    Hi All,
    We are using Sql Server 2005 Express , 
    we got the below exception of Sql Server Assertion
    2014-11-17 00:26:12.59 spid51      Error: 17066, Severity: 16, State: 1.
    2014-11-17 00:26:12.59 spid51      SQL Server Assertion: File: <"logmgr.cpp">, line=5512 Failed Assertion = '!(minLSN.m_fSeqNo < lfcb->lfcb_fSeqNo)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    2014-11-17 00:26:12.61 spid51      Error: 3624, Severity: 20, State: 1.
    2014-11-17 00:26:12.61 spid51      A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running
    DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. 
    2014-11-17 00:27:34.81 Server      Using 'dbghelp.dll' version '4.0.5'
    2014-11-17 00:27:34.81 Server      ***Unable to get thread context - no pss
    2014-11-17 00:27:34.81 Server      * *******************************************************************************
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * BEGIN STACK DUMP:
    2014-11-17 00:27:34.81 Server      *   11/17/14 00:27:34 spid 0
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * Non-yielding Scheduler
    2014-11-17 00:27:34.81 Server      *
    2014-11-17 00:27:34.81 Server      * *******************************************************************************
    2014-11-17 00:27:34.81 Server      Stack Signature for the dump is 0x000003E6
    2014-11-17 00:27:35.75 Server      External dump process return code 0x20000001.
    External dump process returned no errors.
    2014-11-17 00:27:35.75 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    99%. Interval: 75000 ms.
    2014-11-17 00:28:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 135953 ms.
    2014-11-17 00:29:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 195953 ms.
    2014-11-17 00:30:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 255953 ms.
    2014-11-17 00:31:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 315953 ms.
    2014-11-17 00:32:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 375953 ms.
    2014-11-17 00:33:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 435953 ms.
    2014-11-17 00:34:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 495953 ms.
    2014-11-17 00:35:05.77 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2014-11-17 00:35:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 555953 ms.
    2014-11-17 00:36:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    97%. Interval: 615953 ms.
    2014-11-17 00:37:35.77 Server      Process 51:0:0 (0x1574) Worker 0x20AA00E8 appears to be non-yielding on Scheduler 0. Thread creation time: 13059477540625. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle
    98%. Interval: 675953 ms.

    Assertion error are usually some corruption in SQL Server database. And non yielding scheduler seems like bug what is output of
    select @@Version
    Did you tried running dbcc checkdb on SQL Server 2005 database
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Preformance issues when upgrading from dbxml 2.3.8 to 2.4.13

    I have recently upgraded my dbxml distribution from 2.3.8 to 2.4.13 (including the latest patch). I have noticed that many of the queries I issue take longer than they used to. Specifically if the query is complex it takes 10 times as long as it did with 2.3.8. Also I have noted a difference in speed between issuing the query via the dbxml shell (query takes ~45 seconds) vs issuing it through a c++ interface (query takes 4+ minutes). The query am issuing is:
    for $i in collection('projectDatabase.dbxml')/project
    where $i[obsblock/obsblockStatus eq 'INCOMPLETE' and obsblock/receiverBand eq '3MM' and obsblock/remainingTime >= 1.0 and ((obsblock/reqRaCoverage/@low <= 2.61799 and obsblock/reqRaCoverage/@low >= 0.654498) or (obsblock/reqRaCoverage/@high <= 2.61799 and obsblock/reqRaCoverage/@high >= 0.654498) or (0.654498 <= obsblock/reqRaCoverage/@high and 0.654498 >= obsblock/reqRaCoverage/@low) or ((obsblock/reqRaCoverage/@high < obsblock/reqRaCoverage/@low) and ((0.654498 <= obsblock/reqRaCoverage/@high) or (2.61799 <= obsblock/reqRaCoverage/@high) or (0.654498 >= obsblock/reqRaCoverage/@low) or (2.61799 >= obsblock/reqRaCoverage/@low)))) and obsblock/arrayConfiguration eq 'C' and projectID ne'opnt' and projectID ne'rpnt' and projectID ne'tilt' and projectID ne'fringe' and projectID ne'test']
    return $i
    if I simplify the query by removing references to the obsblock/reqRaCoverage/@low and obsblock/reqRaCoverage/@high nodes:
    for $i in collection('projectDatabase.dbxml')/project
    where $i[obsblock/obsblockStatus eq 'INCOMPLETE' and obsblock/receiverBand eq '3MM' and obsblock/remainingTime >= 1.0 and obsblock/arrayConfiguration eq 'C' and projectID ne'opnt' and projectID ne'rpnt' and projectID ne'tilt' and projectID ne'fringe' and projectID ne'test']
    return $i
    it returns much faster. I am wondering if this is an issue with optimization of the complex query?
    The database is fully indexed and was re-indexed when I upgraded to 2.4.13

    Doug,
    I've got your container. It's a wholedoc container with document indexes (a lot of them). Here's what I see for query speeds for your large, slow query using the dbxml shell.
    Query is:
    query "for $i in collection('pdb.dbxml')/project where $i[obsblock/obsblockStatus eq 'INCOMPLETE' and obsblock/receiverBand eq '3MM' and obsblock/remainingTime >= 1.0 and ((obsblock/reqRaCoverage/@low <= 2.61799 and obsblock/reqRaCoverage/@low >= 0.654498) or (obsblock/reqRaCoverage/@high <= 2.61799 and obsblock/reqRaCoverage/@high >= 0.654498) or (0.654498 <= obsblock/reqRaCoverage/@high and 0.654498 >= obsblock/reqRaCoverage/@low) or ((obsblock/reqRaCoverage/@high < obsblock/reqRaCoverage/@low) and ((0.654498 <= obsblock/reqRaCoverage/@high) or (2.61799 <= obsblock/reqRaCoverage/@high) or (0.654498 >= obsblock/reqRaCoverage/@low) or (2.61799 >= obsblock/reqRaCoverage/@low)))) and obsblock/arrayConfiguration eq 'C' and projectID ne'opnt' and projectID ne'rpnt' and projectID ne'tilt' and projectID ne'fringe' and projectID ne'test'] return $i"
    2.3.11 -- 2.4 seconds
    2.4.13 -- 60 seconds
    That is a significant slowdown and it needs further investigation but is almost certainly related to the fact that it is wholedoc storage. The optimizer appears to be choosing unwisely. This will take a few days to work out.
    I also changed the container to be node storage with node indexes and the times went to:
    2.3.11 -- 13 sec (slower than wholedoc)
    2.4.13 -- 40 sec (faster than wholedoc)
    I do know why your application is slower than the dbxml shell. There is a new flag that should almost always be used for wholedoc container queries -- DBXML_DOCUMENT_PROJECTION. Add that to you query excecution.
    Another thing -- query preparation is a bit slower in 2.4 so you should use prepared queries whenever possible to amortize that cost.
    Regards,
    George

  • MDIS assertion log: A2iMultiThread.cpp" line="254" !m_hasLock

    Hi MDM Gurus,
    Issue: MDIS services need to be restarted once a week for the automatic import to occur
    The assrtion log on our MDIS server keeps logging this message:
    <Open ts-long="14:39:46 GMT, Tuesday, April 12, 2011" ts="2011/04/12 14:39:46.703 GMT" pid="***" host="*****" compile-type="WIN32_RELEASE">
              <Assert ts="2011/04/12 14:39:46.703 GMT" tid="3084" entry-no="127015" file="..\..\..\GenericLibs\Base\*A2iMultiThread.cpp" line="254">!m_hasLock*</Assert>
    has anyone come across this? we applied Note 1321795 - MDM 5.5 SP06 Patch05 Release Note after we were advised by a previouss OSS note raised, but now its still occurring albeit less frequently of restarting the services every day as it would not import the data automatically

    this surely seems to a bug !
    if this is happening in the Production server - plz raise a high prio OSS with SAP
    btw : is the MDM server / MDIS running in a cluster ?? or single SID ?
    thanks
    -Adrivit

  • FAST transform mechanism from .dbxml.XmlDocument to .w3c.dom.Document

    Hi,
    I'm looking for a FAST transform mechanism, converting com.sleepycat.dbxml.XmlDocument (retrieved from container) to org.w3c.dom.Document. Right now, i do that like this:
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder builder;
    try {
    builder = factory.newDocumentBuilder();
    } catch (ParserConfigurationException e1) {
    return null;
    //xc = XmlContainer
    org.w3c.dom.Document doc = builder.parse(xc.getDocument("theDoc.xml").getContentAsInputStream());
    This works just fine. But the code seems to be slow... After only 1200 requests/s on this code, the container crashes. Is there any faster mechanism retrieving and converting whole documents?
    Thanks.
    P.S.
    EnvironmentConfig has set the following options:
    setInitializeLocking(true);
    setInitializeCache(true);
    setAllowCreate(true);

    no one at all?

  • The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

    One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
    process could not execute 'sp_repldone/sp_replcounters' on XXXXX". 
    Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause. 
    ***********Error messages from SQL Logs******
    **Dump thread - spid = 0, EC = 0x0000000111534460
    Message
    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
    Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
    Error: 3624, Severity: 20, State: 1.
    SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    Error: 17066, Severity: 16, State: 1.
    External dump process return code 0x20000001.
    External dump process returned no errors.
    Thank you in advance.

    You need to determine if this error is a transient one or a show stopper one.
    It sounds like your log reader agent has crashed and can't continue.
    If so your best bet is to call Microsoft CSS and open a support incident.
    It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
    If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
    I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Winocc.cpp line 329 - using CWGraph in MFC OCX project

    I'm trying to create my own custom ActiveX control for use in a third party application.  My control consists of a dialog window (CDialog derived) that I use for data display.  This works fine, but if I drop a CWGraph control onto my dialog, the control crashes the app with an assert in winocc.cpp Line:329.  Is what I'm attempting possible?  Can anyone tell me why it crashes?  I'm using VS2005.  I've included a dummy project that shows the problem.  I'm still sort of new to VC++ so I may very well have missed something obvious.
    Thanks-
    Attachments:
    MyTestOCX.zip ‏4258 KB

    Hi codeman,
    Have you tried replacing your CWGraph control with any other common Visual Studio controls, like a button.  I don't think that it is the CWGraph that is causing your application to crash.  I think it is some of your code behind the project.  I'd like to see if we can verify the operation with a different kind of control.
    Regards,
    Marty H.
    National Instruments

  • Dbxml:lookup-index fails with edge-element-presence

    The custom xquery function dbxml:lookup-index seems broken for edge-element-presence indices when a namespace is specified:
    dbxml> lookupedge edge-element-presence 'http://ceridwen.us/default' node11 'http://ceridwen.us/default' node1
    1 objects returned for eager index lookup 'edge-element-presence'
    dbxml> q "declare default element namespace 'http://ceridwen.us/default'; dbxml:lookup-index('test', 'node11', 'node1')"
    0 objects returned for eager expression 'declare default element namespace 'http://ceridwen.us/default'; dbxml:lookup-index('test', 'node11', 'node1')'
    dbxml> q "declare default element namespace 'http://ceridwen.us/default'; dbxml:lookup-index('test', 'node11')"
    2 objects returned for eager expression 'declare default element namespace 'http://ceridwen.us/default'; dbxml:lookup-index('test', 'node11')'Dbxml-2.5.16, OSX 10.6.4
    Edited by: jralls on Aug 22, 2010 12:22 PM

    Is this what you need?
    dbxml> listin
    Default Index: node-element-presence-none edge-element-presence-none
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/test}:dataType
    Index: node-attribute-equality-string node-attribute-equality-double for node {http://ceridwen.us/test}:elemType
    Index: node-attribute-equality-string node-attribute-equality-double for node {}:first
    Index: node-attribute-equality-string node-attribute-equality-double for node {http://ceridwen.us/test}:first
    Index: edge-attribute-equality-string node-attribute-equality-string node-attribute-equality-double for node {http://www.w3c.org/1999/xlink}:href
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/test}:name
    Index: unique-node-metadata-equality-string for node {http://www.sleepycat.com/2002/dbxml}:name
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default}:node11
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default}:node12
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default2}:node2
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default}:node311
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default}:node312
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default}:node321
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/default}:node322
    Index: node-element-equality-string node-element-equality-double for node {http://ceridwen.us/test}:ref
    Index: edge-attribute-equality-string node-attribute-equality-string node-attribute-equality-double for node {http://www.w3c.org/1999/xlink}:role
    Index: node-attribute-equality-string node-attribute-equality-double for node {http://www.w3c.org/1999/xlink}:second
    Index: node-attribute-equality-string node-attribute-equality-double for node {http://www.w3c.org/1999/xlink}:title
    Index: node-attribute-equality-string node-attribute-equality-double for node {http://www.w3c.org/1999/xlink}:type
    20 indexes found.This comes from
        DbXml::XmlContainer cnt = sto->getContainer();
        DbXml::XmlTransaction txn = m_mgr->createTransaction();
        try {
         DbXml::XmlUpdateContext uc = m_mgr->createUpdateContext();
         std::string xlink_uri("http://www.w3c.org/1999/xlink");
         std::string href("href");
         std::string role("role");
         std::string attr_eq("edge-attribute-equality-string");
         std::string node_pr("edge-element-presence-none");
         cnt.addIndex(txn, xlink_uri, href, attr_eq, uc);
         cnt.addIndex(txn, xlink_uri, role, attr_eq, uc);
         cnt.addDefaultIndex(txn, node_pr, uc);
         txn.commit();
        catch(DbXml::XmlException& e) {
         logError() << "XmlStorage: Opening container  " << name.sstr() << "  threw "
                 << e.what() << endl;
         throw;
        }There are only two documents in the container:
    <t:TestDoc xmlns:t="http://ceridwen.us/test" t:first="an attribute" xmlns:xlink="http://www.w3c.org/1999/xlink" xlink:second="another attribute">
       This is the root node of a test document
       <t:name>The Test Document</t:name>
       <t:dataType>TestDocument</t:dataType>
       <node1 xmlns="http://ceridwen.us/default" first="a node attribute">This element has 2 subnodes
           <node11>This is the first element under node 1</node11>
           <node12>This is the second element under node 1</node12>
       </node1>
       <node2 xmlns="http://ceridwen.us/default2">This element has three text nodes</node2>
       <node2 xmlns="http://ceridwen.us/default2">This is the second text node</node2>
       <node2 xmlns="http://ceridwen.us/default2">This element is the last one</node2>
       <Table xmlns="http://ceridwen.us/default">
          <t:DataRow t:elemType="Instance">
             <node311>First List Element</node311>
             <node312>Second List Element</node312>
          </t:DataRow>
          <t:DataRow t:elemType="Instance">
             <node321>Another First List Element</node321>
             <node322>Another Second List Element</node322>
          </t:DataRow>
       </Table>
       <?XmlStorage-html default-html?>
       <!--This is a gratuitous comment for testing.-->
    </t:TestDoc>
    <t:TestDoc xmlns:t="http://ceridwen.us/test" t:first="an attribute" xmlns:xlink="http://www.w3c.org/1999/xlink" xlink:second="another attribute">
       This is the root node of a test document
       <t:name>The Test Document</t:name>
       <t:dataType>TestDocument</t:dataType>
       <node1 xmlns="http://ceridwen.us/default" first="a node attribute">
          This element has 2 subnodes
          <node11>This is the first element under node 1</node11>
          <node12>This is the second element under node 1</node12>
       </node1>
       <node2 xmlns="http://ceridwen.us/default2">This element has three text nodes</node2>
       <node2 xmlns="http://ceridwen.us/default2">This is the second text node</node2>
       <node2 xmlns="http://ceridwen.us/default2">This element is the last one</node2>
       <Table xmlns="http://ceridwen.us/default">
          <t:DataRow t:elemType="Instance">
             <node311>First List Element</node311>
             <node312>Second List Element</node312>
          </t:DataRow>
          <t:DataRow t:elemType="Instance">
             <node321>Another First List Element</node321>
             <node322>Another Second List Element</node322>
          </t:DataRow>
       </Table>
       <?XmlStorage-html default-html?>
       <!--This is a gratuitous comment for testing.-->
       <t:ref xlink:href="dbxml:/test/The%20Test%20Document00000001" xlink:role="data:text/plain,reference" xlink:title="The Test Document"xlink:type="simple"/>
    </t:TestDoc>(Aside: It would be really nice if the dbxml shell's print command had a "pretty" option!)

  • ASSERTION FAILED of replica-related stub in a non-clustered SLSB

    Wl 6.1 sp2
    Solaris 2.8
    We have 50 SLSBs running on non-clustered WL servers. Yet we are seeing
    the following ASSERTION FAILED error, which from the stacktrace seems to
    hint the ejb stub is doing something cluster-related... I have attached
    ejb-jar.xml of the offending bean; someone please verify we are not
    building cluster-capable stubs, and if we are building the right stub,
    please explain why the exception is happening. Thanks!
    ******** STACKTRACE
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Assertion
    violated ]
    at weblogic.utils.Debug.assert(Debug.java:74)
    at weblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
    at
    weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
    marySecondaryReplicaHandler.java:94)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
    RemoteRef.java:294)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :265)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy14.getStatus(Unknown Source)
    at
    com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
    ******* EJB-JAR.XML
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    <remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    <remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>

    Hi Rajesh,
    This error was reported on our QA system error log, and only occurred a
    couple of times in a very specific time frame. I will ask QA again if it
    has happened since the first report.
    However, even if this bug is minor and not production-worthy, what I am more
    concerned about is the fact that the stacktrace seem to indicate the bug is
    cluster-related, when we set our SLSBs to be non-clustered. Can someone
    please confirm, given the ejb-jar.xml and weblogic-ejb-jar.xml I've posted
    below, that I have properly configured and deployed our beans to be
    non-clustered? I don't want to introduce cluster overhead (and cluster
    bugs) when we don't need to!
    Gene
    "Rajesh Mirchandani" <[email protected]> wrote in message
    news:[email protected]...
    The reason I asked you if it is readily reproducable is because I had seenthis
    issue (support case) in WLS 6.1(no sp). The problem there was that itcould not
    be reproduced again and so I did not analyze it further.
    Is this happening under load ?
    Gene Chuang wrote:
    Hi Rob,
    AccountStatus is calling AccountService, which is a SLSB. I have
    attached
    its ejb-jar.xml in my original post, and here's the corresponding
    weblogic-ejb-jar.xml:
    !DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic6.0.0
    EJB//EN' 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
    <!-- Generated XML! -->
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <stateless-session-descriptor>
    <pool>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    </pool>
    <stateless-clustering>
    <stateless-bean-is-clusterable>False</stateless-bean-is-clusterable>
    >>
    >>
    <stateless-bean-methods-are-idempotent>False</stateless-bean-methods-are-ide
    mpotent>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    <trans-timeout-seconds>300</trans-timeout-seconds>
    </transaction-descriptor>
    <jndi-name>accountservice.AccountServiceHome</jndi-name>
    </weblogic-enterprise-bean>
    <transaction-isolation>
    <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    </transaction-isolation>
    </weblogic-ejb-jar>
    "Rob Woollen" <[email protected]> wrote in message
    news:[email protected]...
    It looks like AccountStatus is calling a stateful session bean that
    uses
    in-memory replication. (The PrimarySecondary stub is only used forin-memory
    replicated sfsb.)
    Do you have any sfsb?
    -- Rob
    Gene Chuang wrote:
    Wl 6.1 sp2
    Solaris 2.8
    We have 50 SLSBs running on non-clustered WL servers. Yet we are
    seeing
    the following ASSERTION FAILED error, which from the stacktrace
    seems to
    hint the ejb stub is doing something cluster-related... I haveattached
    ejb-jar.xml of the offending bean; someone please verify we are not
    building cluster-capable stubs, and if we are building the rightstub,
    please explain why the exception is happening. Thanks!
    ******** STACKTRACE
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[Assertion
    violated ]
    at weblogic.utils.Debug.assert(Debug.java:74)
    atweblogic.rmi.cluster.BasicReplicaList.reset(BasicReplicaList.java:175)
    at
    weblogic.rmi.cluster.PrimarySecondaryReplicaHandler.setPiggybackResponse(Pri
    marySecondaryReplicaHandler.java:94)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.setPiggybackResponse(ReplicaAware
    RemoteRef.java:294)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :265)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy14.getStatus(Unknown Source)
    at
    com.go2.dtc.service.AccountStatus.accountIsOnline(AccountStatus.java:57)
    >>>>
    ******* EJB-JAR.XML
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    ><remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >>>>>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
    JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <home>com.go2.ejb.services.accountservice.AccountServiceHome</home>
    ><remote>com.go2.ejb.services.accountservice.AccountService</remote>
    <ejb-class>com.go2.ejb.services.accountservice.AccountServiceBean</ejb-class
    >>>>>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>getStatus</method-name>
    <method-params>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>accountservice.AccountServiceHome</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>changeSearchListingStatus</method-name>
    <method-params>
    <method-param>int</method-param>
    <method-param>java.lang.String</method-param>
    </method-params>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • SunStudio 12. 2 throws assertion failed: 0, file ../lnk/exrttiutils.cc

    When compiling with SunStudio12 update 2 we get the following:
    Assertion failed: 0, file ../lnk/exrttiutils.cc line 215
    Since this is not part of our code base, we assume its part of the compiler support stuff. As you can see the error message does not provide us much help in finding where in our code this is occurring, any ideas? We'd love to produce a testcase but don't have clue where to begin...

    The assertion is actually coming from the runtime library libCrun.so.1, and it fires when an "impossible" situation (like a corrupted virtual table or exception record) occurs during exception handling. If this assertion happens at compile time, and not run time, some compiler component is at fault.
    Please add the following two options to the command line that resulted in the assertion:
    -filt=%none -V
    The -filt=%none prevents the verbose output (-V) from being scrambled, and the last component listed before the assertion is the one that failed. Please post your results here.
    We will then need a test case, but let's be sure what is happening first.

  • Weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ invalid assig

    does any one know why we get this call stack? what does this mean? We didn't change our deployment descriptor but it just comes up suddenly.
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ invalid assignment from 'Object' to 'Object' ]
    at weblogic.utils.Debug.assertion(Debug.java:57)
    at weblogic.utils.classfile.expr.LocalVariableExpression.codeAssign(LocalVariableExpression.java:38)
    at weblogic.utils.classfile.expr.AssignStatement.code(AssignStatement.java:28)
    at weblogic.utils.classfile.expr.CompoundStatement.code(CompoundStatement.java:26)
    at weblogic.utils.classfile.CodeAttribute.setCode(CodeAttribute.java:44)
    at weblogic.rmi.internal.StubGenerator.addMethodCode(StubGenerator.java:457)
    at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:125)
    at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:86)
    at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:769)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:810)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:797)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
    at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:232)
    at weblogic.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:45)
    at weblogic.rmi.cluster.ReplicaAwareRemoteObject.initialize(ReplicaAwareRemoteObject.java:77)
    at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:50)
    at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:79)
    at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.j
    ava:45)
    at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:180)
    at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:154)
    at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:168)
    at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:382)
    at weblogic.jndi.internal.WLEventContextImpl.rebind(WLEventContextImpl.java:118)
    at weblogic.ejb20.internal.StatelessEJBHome.activate(StatelessEJBHome.java:115)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1096)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:270)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.deploy(Application.java:429)
    at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:241)
    at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:2946)
    at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:2864)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1638)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1085)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:337)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
    430)
    at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:
    1034)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:340)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
    430)
    at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    You should contact [email protected]. That appears to be a WLS bug.
    -- Rob
    Guowei Shieh wrote:
    does any one know why we get this call stack? what does this mean? We didn't change our deployment descriptor but it just comes up suddenly.
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ invalid assignment from 'Object' to 'Object' ]
    at weblogic.utils.Debug.assertion(Debug.java:57)
    at weblogic.utils.classfile.expr.LocalVariableExpression.codeAssign(LocalVariableExpression.java:38)
    at weblogic.utils.classfile.expr.AssignStatement.code(AssignStatement.java:28)
    at weblogic.utils.classfile.expr.CompoundStatement.code(CompoundStatement.java:26)
    at weblogic.utils.classfile.CodeAttribute.setCode(CodeAttribute.java:44)
    at weblogic.rmi.internal.StubGenerator.addMethodCode(StubGenerator.java:457)
    at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:125)
    at weblogic.rmi.internal.StubGenerator.<init>(StubGenerator.java:86)
    at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:769)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:810)
    at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:797)
    at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:79)
    at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:232)
    at weblogic.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:45)
    at weblogic.rmi.cluster.ReplicaAwareRemoteObject.initialize(ReplicaAwareRemoteObject.java:77)
    at weblogic.rmi.cluster.ReplicaAwareRemoteObject.<init>(ReplicaAwareRemoteObject.java:50)
    at weblogic.rmi.cluster.ClusterableRemoteObject.<init>(ClusterableRemoteObject.java:79)
    at weblogic.rmi.cluster.ClusterableRemoteBinderFactory.getStateToBind(ClusterableRemoteBinderFactory.j
    ava:45)
    at weblogic.jndi.internal.WLNamingManager.getReplacement(WLNamingManager.java:180)
    at weblogic.jndi.internal.WLNamingManager.getStateToBind(WLNamingManager.java:154)
    at weblogic.jndi.internal.ServerNamingNode.rebindHere(ServerNamingNode.java:168)
    at weblogic.jndi.internal.BasicNamingNode.rebind(BasicNamingNode.java:382)
    at weblogic.jndi.internal.WLEventContextImpl.rebind(WLEventContextImpl.java:118)
    at weblogic.ejb20.internal.StatelessEJBHome.activate(StatelessEJBHome.java:115)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1096)
    at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1362)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:270)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:83)
    at weblogic.j2ee.Application.deploy(Application.java:429)
    at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:241)
    at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:2946)
    at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:2864)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1638)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1085)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:337)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
    430)
    at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:
    1034)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:340)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:
    430)
    at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:386)
    at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

  • Is there any solution for dbxml cluster?

    Dbxml is an embedded xml database.
    If I have several web servers (cluster) and each of them use dbxml to store data, How can I sync the stored data?
    Can dbxml's container store dbxml file in one remote filesystem (not locally)?

    Thanks for your reply!
    After I read the replication strategy, I find there can only be one master existed in replication group. That is only one application can write data to dbxml. Others can only read data from dbxml.
    So this scenario can't be suitable for our web server (cluster). We need all web server application can write data to it's local dbxml. And all the dbxml should be sync.
    How can I do this using dbxml?

  • Error trying to import python dbxml package

    Hi,
    I can see a similar thread fro windows (see: Python API setup problem on Windows but I'm having this problem with fedora15 (64bit) / Python2.7 / BDB XML 2.5.16:
    I can build and install BDB XML without any problems following the standard documentation. I'm then trying to get the Python API to work.
    I followed the instructions and the bsddb3.db library works fine:
    #$ python
    #>>> from bsddb3.db import *
    #>>> print version()
    (4, 8, 26)
    #>>> exit()
    the problem is trying to import dbxml:
    #$ python
    #>>> from bsddb3.db import *
    #>>> from dbxml import *
    Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    File "/usr/lib64/python2.7/site-packages/dbxml.py", line 25, in <module>
    dbxml = swigimport_helper()
    File "/usr/lib64/python2.7/site-packages/dbxml.py", line 24, in swig_import_helper
    return _mod
    UnboundLocalError: local variable '_mod' referenced before assignment
    #>>>
    And if I then try to reimport:
    (following directly on from the above snippet)
    #>>> from dbxml import *
    Segmentation fault
    ... and python closes.
    Any thoughts?
    Thanks!
    Edited by: 898830 on 23-Nov-2011 11:11
    Edited by: 898830 on 23-Nov-2011 11:13

    Hi,
    After an interesting few days I think it is now working! complete reinstall seemed to do it.
    Thanks!

  • Random segfaults when doing an xupdate at the container level

    I am having an error where updates to a container are causing segfaults in weird ways. I am on 2.4.16 with the latest patch applied. my query is attempting to mark a node as 'empty'...
    > for $q in collection('dbxml:/rx.dbxml')//results[text()="http://myurl.com/results"] return (replace value of node $q with '')
    Its replicable on certain containers, but not others, making me think that an index is out of whack or something weird is going on, but doc() updates still work so I'm not really sure why the container keyword would be different. All containers are configured exactly the same way, its just that some won't let me run this query without barf city. To top off the weirdness, the transactions are actually successful in the end once I get the db back up and recovered from the segv.
    I have some ideas but none of them really explain the kinda sporadic nature of the issue.
    1) I am creating a query context before using this call - should I have an update context as well?
    2) Could an index be hosed somewhere? Why would that happen? (disclaimer - I've been through several migrations and seen similar bugs along the way)
    3) Could the fact that the text in the node is a url make it unhappy?
    I have pasted a backtrace below of where the segv happens if it helps at all.
    Thanks in advance!
    eleddy
    Program received signal SIGSEGV, Segmentation fault.
    NsDomElement (this=0x68106e0, node=<value optimized out>, document=<value optimized out>) at NsDom.cpp:107
    107          if (isDocumentNode()) {
    Current language: auto; currently c++
    (gdb) bt
    #0 NsDomElement (this=0x68106e0, node=<value optimized out>, document=<value optimized out>) at NsDom.cpp:107
    #1 0x00002ae326e0c8e1 in DbXml::NsDomElement::getElemNext (this=0x6810b40) at NsDom.cpp:320
    #2 0x00002ae326e500e4 in DbXml::ElementDescendantAxis::nextNode (this=0x6826470, context=<value optimized out>) at DbXmlNodeImpl.cpp:2176
    #3 0x00002ae326e51756 in DbXml::DbXmlAxis::next (this=0x6826470, context=0x6816128) at DbXmlNodeImpl.cpp:1642
    #4 0x00002ae326e48c0d in DbXml::ResultAdapter::next (this=<value optimized out>, context=0x6816128) at ../dataItem/DbXmlResult.hpp:44
    #5 0x00002ae326ed1a70 in DbXml::StepIterator::next (this=0x68b78a0, context=0x6816128) at StepQP.cpp:765
    #6 0x00002ae326ebbae4 in DbXml::PredicateFilter::doNext (this=0x68b7b10, context=0x6816128) at PredicateFilterQP.cpp:459
    #7 0x00002ae326eba3d0 in DbXml::PredicateFilter::next (this=0x68b7b10, context=0x6816128) at PredicateFilterQP.cpp:420
    #8 0x00002ae326eb9b2e in DbXml::QueryPlanToASTResult::next (this=0x68191d0, context=0x6816128) at QueryPlanToAST.cpp:63
    #9 0x00002ae327642947 in ForTupleResult::next () from /usr/local/xmldb/lib/libxqilla.so.4
    #10 0x00002ae327641253 in XQReturn::createUpdateList () from /usr/local/xmldb/lib/libxqilla.so.4
    #11 0x00002ae3277509d0 in UApplyUpdates::createSequence () from /usr/local/xmldb/lib/libxqilla.so.4
    #12 0x00002ae32762162e in ASTNodeImpl::CreateSequenceResult::getResult () from /usr/local/xmldb/lib/libxqilla.so.4
    #13 0x00002ae327749960 in LazySequenceResult::next () from /usr/local/xmldb/lib/libxqilla.so.4
    #14 0x00002ae327662668 in XQQuery::QueryResult::next () from /usr/local/xmldb/lib/libxqilla.so.4
    #15 0x00002ae326dc438c in DbXml::LazyDIResults::hasNext (this=0x6824620) at Results.cpp:358
    #16 0x00002ae326dd8ca4 in DbXml::XmlResults::hasNext (this=<value optimized out>) at XmlResults.cpp:74
    #17 0x00002ae326d9428d in DbXml::QueryExpression::execute (this=0x682ea30, txn=0x6802570, contextItem=0x0, context=<value optimized out>, flags=<value optimized out>)
    at QueryExpression.cpp:147
    #18 0x00002ae326dd04ed in DbXml::XmlQueryExpression::execute (this=<value optimized out>, context=@0x30, flags=0) at XmlQueryExpression.cpp:92

    In cases like these it's best to give more detail, such as:
    o platform/compiler/version
    RHEL 4 64bit/gcc4.1.2. using python/swig wrapperso container type, index type
    default container types, with these options: DB_CREATE|DB_EXCL|DBXML_TRANSACTIONAL. indexes are all node indexeso indexes on the container
    5 node indexes, very simpleo concurrent vs single-threaded access
    single writer multiple readers -> we are having really good concurrency success so I don't think that' the issue. I'm following the rule to the T hereo configuration specified on environment and containers
    containers created with DB_CREATE|DB_EXCL|DBXML_TRANSACTIONAL and opened with DBXML_TRANSACTIONAL. environment. environments are created with DB_CREATE|DB_THREAD|DB_INIT_LOCK|DB_INIT_LOG|DB_INIT_MPOOL|DB_INIT_TXN and the config is below
    environment.set_lk_detect(DB_LOCK_MINWRITE)
    environment.set_lk_max_lockers(20000)
    environment.set_lk_max_locks(10000)
    environment.set_lk_max_objects(5000)
    environment.set_lg_max(104857600)
    environment.set_lg_bsize(20971520)
    environment.set_lg_regionmax(41943040)
    environment.set_timeout(3000000, DB_SET_TXN_TIMEOUT)That sort of thing. Intermittent problems are often related to either unintended concurrency in an application or uninitialized variables. The latter can often be detected using valgrind if your are on a Linux platform. It also wouldn't hurt to reindex the problem containers to see if that has an effect.
    I will try reindexing in a staging environment, but this database is pretty big and they are live so its not really an option to reindex all the time (plus its not like the indexing can really happen while people are using it which makes it difficult). I've already dealt with a similar indexing bug in the past and I thought the latest version fixed that problem. I will see what valgrind can pull up but like I said I'm relying on python/swig and valgrind can be pretty misleading with PyMallocThanks for sending a stack but it's not all that illuminating. Another thing is to know if the issue is reproducible in a debug build where you'd get a better stack.
    I did a fresh install already with the latest patches and that didn't solve the issue. the forum has been really good at diagnosing without taking it to the debug build level so if things get bad or if you need more info I'll take it to that level but perhaps someone has similar issues or it rings a bell that we can explore first

Maybe you are looking for