[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release 0.5 - Problems, Comments & Suggestions

Oops!
I'd meant to start off by saying:
Hurrah for ozone 0.5! Unfortuneately, it doesn't seem to run code that
an under 0.4. Here's the problem and some suggestions 7 comments.
Cheers,
Charles

Charles Benett wrote:
> 
> Hi!
> 
> PROBLEM
> After you have unzipped the src, UNIX/LINUX users need to make the files
> in the bin directory executable. (If x.bat exists, make x executable).
> 
> SUGGESTION
> If you have ant installed elsewhere, you may want to make sure that the
> ozone version is in your path before any other versions of ant. I think
> there is some ozone-specific stuff in there.
> 
> COMMENT - VITAL
> Use ant bin-jar to create ozone.jar in the /bin directory. Ths is the
> one you want in you classpath to use ozone.
> 
> PROBLEM - MAJOR
> Err, something seems to have broken in 0.5.  I get the folllowing error
> message in 0.5 but nothing in 0.4
> 
> 0.5 Client error message:
> [CustomerAdminApp] Entering create list method.
> Problem creating object:org.ozoneDB.OzoneInternalExc:
> java.lang.NullPointerException:
> org.ozoneDB.UnexpectedException: org.ozoneDB.OzoneInternalExc:
> java.lang.NullPointerException:
>         at
> com.benett.system.db.CustomerListPDO_Proxy.initCustomerList_update(CustomerListPDO_Proxy.java:82)
>         at
> com.benett.system.cli.CustomerAdminApp.createList(CustomerAdminApp.java:139)
>         at
> com.benett.system.cli.CustomerAdminApp.main(CustomerAdminApp.java:76)
> Exiting normally.
> 
> 0.5Server error message:
> [info] (191) AdminPort: Admin logged in.
> [info] (511) AdminPort: commandPort: AdminCommand: 1
> [info] (503) InvokeServer: connection established...
> [info] (951) InvokeServer: user logged in: charles
> [CustomerListPDO] Constructor called.
> [warn] (951) Transaction: invokeObject()
>     java.lang.NullPointerException:
>         at org.ozoneDB.core.MethodKey.hashCode(MethodKey.java:60)
>         at java.util.Hashtable.get(Hashtable.java:317)
>         at org.ozoneDB.DxLib.DxHashMap.elementForKey(DxHashMap.java:59)
>         at
> org.ozoneDB.core.AbstractObjectContainer.methodFor(AbstractObjectC
>             ontainer.java:115)
>         at
> org.ozoneDB.core.AbstractObjectContainer.invokeTarget(AbstractObje
>             ctContainer.java:172)
>         at
> org.ozoneDB.core.wizardStore.WizardObjectContainer.invokeTarget(Wi
>             zardObjectContainer.java:147)
>         at org.ozoneDB.core.Transaction.invokeObject(Transaction.java:421)
>         at org.ozoneDB.core.DbRemote.DbInvoke.perform(DbInvoke.java:63)
>         at
> org.ozoneDB.core.Transaction.performCommand(Transaction.java:217)
>         at
> org.ozoneDB.core.TransactionManager.performCommand(TransactionMana
>             ger.java:316)
>         at
> org.ozoneDB.core.TransactionManager.completeTransaction(Transactio
>             nManager.java:285)
>         at
> org.ozoneDB.core.TransactionManager.handleCommand(TransactionManag
>             er.java:203)
>         at
> org.ozoneDB.core.InvokeServer.handleClientEvent(InvokeServer.java:
>             77)
>         at
> org.ozoneDB.DxLib.net.DxMultiServerClient.run(DxMultiServerClient.
>             java:37)
>         at java.lang.Thread.run(Thread.java:475)
> [warn] (951) Transaction: ta(9): uncaught exception:
> (org.ozoneDB.OzoneInternalExc: java.lang.NullPointerException: )
>     org.ozoneDB.OzoneInternalExc: java.lang.NullPointerException:
>         at org.ozoneDB.core.Transaction.invokeObject(Transaction.java:447)
>         at org.ozoneDB.core.DbRemote.DbInvoke.perform(DbInvoke.java:63)
>         at
> org.ozoneDB.core.Transaction.performCommand(Transaction.java:217)
>         at
> org.ozoneDB.core.TransactionManager.performCommand(TransactionMana
>             ger.java:316)
>         at
> org.ozoneDB.core.TransactionManager.completeTransaction(Transactio
>             nManager.java:285)
>         at
> org.ozoneDB.core.TransactionManager.handleCommand(TransactionManag
>             er.java:203)
>         at
> org.ozoneDB.core.InvokeServer.handleClientEvent(InvokeServer.java:
>             77)
>         at
> org.ozoneDB.DxLib.net.DxMultiServerClient.run(DxMultiServerClient.
>             java:37)
>         at java.lang.Thread.run(Thread.java:475)
> [info] (951) InvokeServer: connection closed (user: charles)
> 
> 0.4 Client output is:
> [CustomerAdminApp] Entering create list method.
> [CustomerAdminApp] New customer list created in database.
> Exiting normally.
> 
> 04 Server output is:
> [info] (551) AdminPort: Admin logged in.
> [info] (191) AdminPort: commandPort: AdminCommand: 1
> [info] (983) InvokeServer: connection established...
> [info] (335) InvokeServer: user logged in: charles
> [CustomerListPDO] Constructor called.
> [AuditTrailPDO] New AuditTrialPDO created.
> [AuditTrailPDO] [CustomerListPDO] New customer list created:
> [CustomerListPDO] New customer list created:
> [info] (335) InvokeServer: connection closed (user: charles)
> 
> The code used in the 0.5 version is compiled with 0.5
> 
> SUGGESTION
> Rather than using "ant" which calls the default target, which happens to
> be main, you can step through the dependencies of main. This makes it
> easier to keep track of the warnings & error messages.
> 
> ant DxLib
> throws 1 warning re deprecated APIs
> 
> ant tools
> throws 2 warnings, both for deprecated API's
> 
> ant server - OK
> ant odmg -OK
> ant xa -OK
> 
> ant blob
> - opp throws messages like:
> [exec]       trying to process BLOBContainer.java...
> (./org/ozoneDB/blob/BLOBContainer.java)
> [exec]       trying to process BLOBContainerImpl.ocd... no descriptor
> file found.
> I've no idea if this is a problem
> 
> ant xml
> - opp throws lots of messages per blob, as well as noram method
> signatures
> 
> ant samples
> - more .ocd messages from opp
> 
> ant javadoc-api
> throws a ton of warnings
> 
> COMMENT
> Contrary to the install instruction, ant does not automatically create
> the javadocs for the core, use ant javadoc-core