I am getting an exception when Cocobase tried to connect to our db2 datasource using the native driver. I do not get an exception using the toolbox driver.

I do not have the stack trace because of some AS400 nuttiness, but here is what I remember: the exception was in the Cocobase connect() method, and was a NullPointerException at a Hashtable.put(). Since this Hashtable method will throw a NPE if the key or value is null, I think I might be missing some piece of the configuration.

The question is: what key/value elements are you expecting when you call that put() method in connect()?

P.S.-> If I can regenerate the stack trace, I will add it later, but it may be several days, I don't have that kind of time right now.

If you can send us the jdbc URL you're using to support@thoughtinc.com we can verify if there are any issues with it.

One 'trick' you can do with CocoBase is to enable debug before you connect. For connecting with CBFacade, just call cbf.setDebugLevel(5) before connecting. If you're using the raw CocoBase Runtime CocoPowder use myBase.setDebug(true); instead. In either case the debug messages should help you detect the problem.

And please send us the URL if you wish so we can review it.

THOUGHT Support

Here is the URL property in our config file:

iseries.primaryDatabaseURL=jdbc:db2://HOSTNAME;naming=SQL;libraries=*LIBL;errors=full;date format=iso;time format=iso;block size=512

We basically took the existing as400 url and replaced the jdbc subgroup from as400 to db2.

Other datasource properties are set in this config file as well.

Thanks for the debug information. I will try that next chance I get.

But you don't have access to the cocobase code to tell me what key/value is expected at that Hashtable?

This URL looks valid, so without knowing what exception you're getting it's unclear where your error is coming from.

When you use a standard URL such as this with no :cocoprop or :cocorep entries, we simply call the jdbc driver connect facilities and pass the values in, in a fully standard way. Any 'null' values might be related to null issues in the driver itself and not CocoBase, but without the full stacktrace derived from a debug mode connect it is impossible to tell exactly what's happening.

Does that make sense?

THOUGHT Support

That absoultely makes sense.

I was just hoping that there would be just one connect method, and in that method, there would be one Hashtable access. And then you could tell me something like "after we connect, we add an element to the internal cache hashtable that maps database URL to driver shortName" or something like that, and I could check and make sure we set the shortName property of the datasource.

I'm taking from your answer that it isn't something that simple? :)

It sounds like you are you referring to a DataSource. We do support DataSource connections, which supports a 'short name' connection style. But when you are connecting to a raw jdbc driver, then as a wrapper to CocoBase you have to supply all of that information to the tool. You can do this by reading your connection properties from some location such as a properties file so you don't have to type it in, but you must include a proper jdbc connection for each connection to the runtime layer.

Does that make sense?

THOUGHT Support

exactly! And I believe that we are missing at least one important piece of information when we populate those properties, and you are using that missing property in your Hashtable put() method resulting in an NPE. We now are on exactly the same page.

It looks like the DB2StdConnectionPoolDataSource has about 50 setters. Which are the mandatory ones? Do you have any example code?

That's Version/Database specific, and not CocoBase specific. If you can find the correct setting details for your particular environment, then CocoBase can access the DataSource through a URL such as:

jdbc:cocoprop=jndiurl=jdbc/MyDataSource

Does this make sense?

THOUGHT Support