BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 03-18-2008, 04:36 AM   #1 (permalink)
New Member
 
Join Date: Feb 2008
Model: 8310
PIN: N/A
Carrier: Vodafone
Posts: 5
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Oracle Connector (MDS Application via BES)

Please Login to Remove!

Dear BES Admins out there!

Here a short description of my Development Environment:
BES with MDS
Oracle (Express Version) on the same Server together with BES
4BlackBerry Devices (2x Curve, 1x 8800, 1x 8700) all with Firmware 4.2.x
MDS Studio on Laptop (where no BES or Oracle is running)
All the BlackBerrys are successfully connected to the BES and MDS ist also activated.
Pushing of MDS Apps works fine.
Also the MDS Apps themself works fine.

But now i have Projekt where i need to connect to an Oracle Database (Oracle Express) from a MDS Application via BES.

I configured the MDS Studio with the ojdbc14.jar which i downloaded from the oracle site.
The Connect to the Database via MDS Studio works fine. Also the Queries are giving the right results.

After that i tried to configure the BES DB Connectors. Therefor i started the BlackBerry Manager on BES and opend the MDS -> Edit Properties - > Connectors
Here i took the same ojdbc14.jar like i did in MDS Studio and set the Database Driver path in the Properties to point on that jar file.

Now i published the MDS Application from MDS Studio on the BES and pushed it to the Devices. Workd fine. Application is startable.
But when pushing the Button which should make a Querie on the DB i got an Error that MDS on BES is in a Malfunction. A look in the BlackBerry Manager on BES shows the status from MDS changing from "Normal" to "Warning".

I took a look in the Logfiles and found the following 2 WARNInGS and 1 ERROR:

################################################## #
############# WARNING 1 #######################
################################################## #
[WARN ] (03/09 22:04:18) [LifecycleHandler] Processor | Failed to process message. | DevicePIN=252C4E6E; AppID=7030333608451179067; Exception=Error in handling internal event.:Failed to initialize processor handler.:Device application not found.; DevicePIN=252C4E6E; Application Name=testoracle; EventDesc=APP_GRACEFULL_DELETE;
net.rim.wica.ag.services.processor.ProcessorExcept ion: Error in handling internal event.
at net.rim.wica.ag.services.processor.DeviceHandler.f orwardEventToWiclet(DeviceHandler.java:1195)
at net.rim.wica.ag.services.processor.DeviceHandler.f orwardEventToWiclet(DeviceHandler.java:1173)
at net.rim.wica.ag.services.processor.DeviceHandler.f orwardEventToWiclet(DeviceHandler.java:1113)
at net.rim.wica.ag.services.processor.DeviceHandler.h andleDelete(DeviceHandler.java:860)
at net.rim.wica.ag.services.processor.DeviceHandler.h andleEvent(DeviceHandler.java:395)
at net.rim.wica.ag.services.processor.ProcessorServic eImpl.forwardEventToDevice(ProcessorServiceImpl.ja va:884)
at net.rim.wica.ag.services.processor.ProcessorServic eImpl.handleEvent(ProcessorServiceImpl.java:185)
at net.rim.wica.ag.services.processor.LifecycleHandle r.forwardEventToProcessor(LifecycleHandler.java:15 7)
at net.rim.wica.ag.services.processor.LifecycleHandle r.onDeviceWicletMarkedForUninstall(LifecycleHandle r.java:80)
at net.rim.wica.ag.services.lifecycle.WicletServiceIm pl.markWicletDeletedFromDevice(WicletServiceImpl.j ava:1577)
at net.rim.wica.ag.services.lifecycle.WicletServiceIm pl.markWicletDeletedFromDevice(WicletServiceImpl.j ava:1544)
at net.rim.wica.ag.services.connector.system.SystemHa ndler.deleteWicletGraceful(SystemHandler.java:104)
at net.rim.wica.ag.services.connector.system.Lifecycl eStatusHandler.upgradeWiclet(LifecycleStatusHandle r.java:393)
at net.rim.wica.ag.services.connector.system.Lifecycl eStatusHandler.handle(LifecycleStatusHandler.java: 210)
at net.rim.wica.ag.services.connector.system.SystemCo nnectorImpl.invoke(SystemConnectorImpl.java:143)
at net.rim.wica.ag.services.connector.system.AsynchSy stemConnector.invoke(AsynchSystemConnector.java:59 )
at net.rim.wica.ag.services.connector.AsynchConnector Wrapper.sendMessage(AsynchConnectorWrapper.java:41 )
at net.rim.wica.ag.services.processor.WicletRequestPr ocessor.invokeConnector(WicletRequestProcessor.jav a:129)
at net.rim.wica.ag.services.processor.WicletRequestPr ocessor.processMessage(WicletRequestProcessor.java :56)
at net.rim.wica.ag.services.processor.WicletOperation Processor.processMessage(WicletOperationProcessor. java:50)
at net.rim.wica.ag.services.processor.InDeviceWicletH andler.asyncHandleMessage(InDeviceWicletHandler.ja va:127)
at net.rim.wica.ag.services.processor.AsynchHandler.r unNextTask(AsynchHandler.java:332)
at net.rim.wica.ag.base.thread.TaskContainer.run(Task Container.java:134)
at net.rim.wica.ag.services.processor.AsynchHandlerWo rker.run(AsynchHandlerWorker.java:54)
at net.rim.wica.ag.base.thread.SingleThreadAllocator. runNextTask(SingleThreadAllocator.java:70)
at net.rim.wica.ag.base.thread.TaskContainer.run(Task Container.java:134)
at net.rim.wica.ag.base.thread.AbstractThreadAllocato r$1.run(AbstractThreadAllocator.java:74)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: net.rim.wica.ag.services.processor.ProcessorExcept ion: Failed to initialize processor handler.
at net.rim.wica.ag.services.processor.OutDeviceWiclet Handler.initialize(OutDeviceWicletHandler.java:346 )
at net.rim.wica.ag.services.processor.ProcessorConfig uration$WicletHandlerSOFactory.create(ProcessorCon figuration.java:526)
at net.rim.wica.ag.base.sharedobject.impl.SharedObjec tMgrImpl$SharedObjectEntity.init(SharedObjectMgrIm pl.java:626)
at net.rim.wica.ag.base.sharedobject.impl.SharedObjec tMgrImpl.borrowSO(SharedObjectMgrImpl.java:149)
at net.rim.wica.ag.services.processor.DeviceHandler.f orwardEventToWiclet(DeviceHandler.java:1191)
... 28 more
Caused by: net.rim.wica.ag.services.lifecycle.DeviceWicletNot FoundException: Device application not found.
at net.rim.wica.ag.services.lifecycle.WicletServiceIm pl.getDeviceWiclet(WicletServiceImpl.java:441)
at net.rim.wica.ag.services.processor.OutDeviceWiclet Handler.initialize(OutDeviceWicletHandler.java:342 )
... 32 more


################################################## #
############# WARNING 2 #######################
################################################## #
[WARN ] (03/09 22:04:22) [DBConnector] Connector | Failed to process request on target database server. | AppName=testoracle; DevicePIN=252C4E6E;
net.rim.wica.ag.services.connector.db.DBConnectorE xception: Database handler class not defined.
at net.rim.wica.ag.services.connector.db.DataSource.g etSQLStatementHandler(DataSource.java:409)
at net.rim.wica.ag.services.connector.db.DBConnector. invoke(DBConnector.java:193)
at net.rim.wica.ag.services.connector.db.DBConnector. run(DBConnector.java:115)
at net.rim.wica.ag.base.thread.AbstractThreadAllocato r$1.run(AbstractThreadAllocator.java:74)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: net.rim.wica.ag.services.connector.db.sqlhandler.O racleSQLStatementHandler
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at net.rim.wica.ag.services.connector.db.DataSource.g etSQLStatementHandler(DataSource.java:405)
... 5 more

################################################## #
############# ERROR 1 #######################
################################################## #
[ERROR] (03/09 22:04:22) [RequestCallback] Processor | Failed to process message. | DevicePIN=252C4E6E; AppName=testoracle; MsgType=FAULT; MsgID=18069; OpName=fault; OpCode=0; SecurityMode=SECURITY_MODE_UNSECURE; DeliveryMode=DELIVERY_MODE_STANDARD; InternalMsg=requestMsgCode: 1
category: 2
code: 4
name: BackeEndError
data: MDS Server is malfunctioning. Please contact technical support.
; ErrCause=Database handler class not defined.;java.lang.ClassNotFoundException: net.rim.wica.ag.services.connector.db.sqlhandler.O racleSQLStatementHandler;
net.rim.wica.ag.services.connector.db.DBConnectorE xception: Database handler class not defined.
at net.rim.wica.ag.services.connector.db.DataSource.g etSQLStatementHandler(DataSource.java:409)
at net.rim.wica.ag.services.connector.db.DBConnector. invoke(DBConnector.java:193)
at net.rim.wica.ag.services.connector.db.DBConnector. run(DBConnector.java:115)
at net.rim.wica.ag.base.thread.AbstractThreadAllocato r$1.run(AbstractThreadAllocator.java:74)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: net.rim.wica.ag.services.connector.db.sqlhandler.O racleSQLStatementHandler
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at net.rim.wica.ag.services.connector.db.DataSource.g etSQLStatementHandler(DataSource.java:405)
... 5 more
################################################## #
################################################## #
################################################## #

I hope anybody here has an Idea - I think it is hopefully only a small mistake in my configuration on BES?
I didn´t find any solution in Forums etc.

I say thank you to anybody who tries to help me to find a solution and i promise to post a solution here when "we" solved the Problem!!!

Thanks for your time
Lars.
Offline  
Old 01-07-2009, 05:50 AM   #2 (permalink)
New Member
 
Join Date: Jan 2009
Model: 8707
PIN: N/A
Carrier: Celcom
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have the same error as per your message. Anybody have the solution to this issue??
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright © 2004-2014 BlackBerryForums.com.
The names RIM © and BlackBerry © are registered Trademarks of BlackBerry Inc.