wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes WebSphere 4.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "WebSphere 4.0 "PiggyBank" Red Book" Watch "WebSphere 4.0 "PiggyBank" Red Book" New topic
Author

WebSphere 4.0 "PiggyBank" Red Book

Jim Shaw
Greenhorn

Joined: Aug 28, 2001
Posts: 2
Howdy Pardners.
I'm trying to run the PiggyBank example from IBM (http://publib-b.boulder.ibm.com/Redbooks.nsf/RedpieceAbstracts/sg246134.html?Open).
* WebSphere 4.0 (trial edition) is on RedHat 7.1.
* Oracle 8.17i Enterprise edition runs on NT 4.0.
I'm trying to use Oracle as my CMP store, using classes12.zip from Oracle 8.17i, but I'm having very little luck.
The error I receive on startup is:
[01.08.29 13:02:20:519 GMT+11:00] 22330efb EJBEngine I WSVR0037I: Starting EJB jar: PiggyBank EJBs
[01.08.29 13:02:21:625 GMT+11:00] 22330efb JDBCPersister W JDBC persister creation failed
[01.08.29 13:02:21:721 GMT+11:00] 22330efb EJBEngine I WSVR0062E: Failed to start EJB, PiggyBank Application#piggybank-ejb.jar#Customer: String index out of range: -1
I've read the "Errata" from IBM regarding their use of the Oracle reserved word "NUMBER", and have made the changes accordingly. The persister now generates the following:
CREATE TABLE "CUSTOMER"
("ID" INTEGER NOT NULL,
"NAME" VARCHAR(32));
ALTER TABLE "CUSTOMER"
ADD CONSTRAINT "CUSTOMERPK" PRIMARY KEY ("ID");
CREATE TABLE "ACCOUNT"
("ACCNUMBER" INTEGER NOT NULL,
"BALANCE" INTEGER,
"CHECKING" SMALLINT,
"CUSTOMERID" INTEGER);
ALTER TABLE "ACCOUNT"
ADD CONSTRAINT "ACCOUNTPK" PRIMARY KEY ("ACCNUMBER");
Has anyone out there ever attempted the Pig and had similar problems?
Please let me know if I can provide addition details - I didn't want to completely clutter the page!
Thanks,
~NJ!~
Jim Shaw
Greenhorn

Joined: Aug 28, 2001
Posts: 2
Well, solved this one on my own. Seems that the datasource manager mishandles the combining of strings to create the complete Oracle URL. Might have been easier had I used DB2 for my first attempt.
*CLOSED*
 
Consider Paul's rocket mass heater.
 
subject: WebSphere 4.0 "PiggyBank" Red Book
 
Similar Threads
Failed to start EJB on WAS4.0 Advanced Edition
websphere error
Oracle Connection in Websphere 4.0
Websphere Server Shutting down
Error while connecting to Oracle using DataSource