[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cannot store
On Sat, 07 Jul 2001, you wrote:
> hello,
>
> I am using ozone-1.0 on RedHat 7.1 , 256MB RAM.
>
> When I am trying to store an XML document of 200kb using SaxStore
> i get the following error on the server console. The command i have used to
> start ozone database
>
> ozone -Xmx240mb -dserver1
>
>
>
> info] (088) ClusterStore: loadCluster(): load cluster from disk: 230405
>
> [warn] (088) Transaction: ta(-63): uncaught exception: (DOMException(11):
>
> DOMException: Exception reason is unspecified.
>
> org.ozoneDB.xml.dom.AttrImpl)
>
> DOMException(11): DOMException: Exception reason is unspecified. (code 11)
>
> org.ozoneDB.xml.dom.AttrImpl
> at org.ozoneDB.xml.dom.DocumentImpl_Proxy.createElement(DocumentImpl_ Proxy.java:1146)
>
>
> at org.ozoneDB.xml.util.SAXChunkConsumer.startElement(SAXChunkConsumer.java:293)
>
>
> at org.ozoneDB.xml.util.SAXChunkConsumer.processChunk(SAXChunkConsumer.java:170)
>
>
> at org.ozoneDB.xml.util.XMLContainerHelperImpl.putChunk(XMLContainerHelperImpl.java:134)
>
>
> at java.lang.reflect.Method.invoke(Native Method)
>
> at org.ozoneDB.core.AbstractObjectContainer.invokeTarget(AbstractObjectContainer.java:212)
>
>
> at org.ozoneDB.core.Transaction.invokeObject(Transaction.java:512)
> at org.ozoneDB.core.DbRemote.DbInvoke.perform(DbInvoke.java:62)
>
> at org.ozoneDB.core.Transaction.performCommand(Transaction.java:273)
>
> at org.ozoneDB.core.TransactionManager.performCommand(TransactionManager.java:368)
>
>
> at org.ozoneDB.core.TransactionManager.handleCommand(TransactionManager.java:256)
>
>
> at org.ozoneDB.core.InvokeServer.handleClientEvent(InvokeServer.java:76)
>
> at org.ozoneDB.DxLib.net.DxMultiServerClient.run(DxMultiServerClient.java:44)
>
> at java.lang.Thread.run(Thread.java:484)
>
> [info] (088) InvokeServer: connection closed (user: root)
>
>
> Although i have increased the virtual memory why can't i store the an xml file
> of size 200kb.
We saw this problem several times in the past. To me it seems to be a problem
related to the underlying DOM code (OpenXML) and not a problem of the ozone
server and its memory management. But I'm not that familiar with this code.
Unfortunately nobody else seems to be willing to tackle this. Maybe this is
because there are efforts underway to rewrite the entire XML related code of
ozone. Are there any news from that front?
Falko
--
______________________________________________________________________
Falko Braeutigam mailto:falko@smb-tec.com
SMB GmbH http://www.smb-tec.com
----------------------------------------------------------------------
Post a message: mailto:ozone-users@ozone-db.org
Unsubscribe: mailto:ozone-users-request@ozone-db.org?body=unsubscribe
Contact adminstrator: mailto:ozone-users-owner@ozone-db.org
Read archived messages: http://www.ozone-db.org/
----------------------------------------------------------------------