Performance Check

sam1234 · July 16, 2009, 3:32pm

Hi,

As a performance check am updating 500 records(only in one column).
Am using the below connection:
performanceCheck.JDBC:cp
Transaction Type LOCAL_TRANSACTION
DataSource Class oracle.jdbc.pool.OracleDataSource
serverName 10.60.193.75
user ***
password ******
databaseName ***
portNumber 1521
networkProtocol TCP
Other Properties driverType=thin
Enable Connection Pooling true
Minimum Pool Size 1
Maximum Pool Size 20
Pool Increment Size 1
Block Timeout (msec) 1000
Expire Timeout (msec) 1000
Startup Retry Count 0
Startup Backoff Timeout (sec) 10

Update notification & Update operation only these two using this connection.
Whenever an updation(updating a cloumn in a table named as ‘X’) takes place “UPADATE notification” will get triggered, which in trun invoke other service which do update operation in other table named as ‘Y’ (Both X & Y table has same data). Here its taking more time to do the update in Y table for 500 records.
DB is in other machine & wM in my local machine.

Using logging

(Before and after the update operation)
“getCurrentdateString”
“pub.flow:debug”

Note: With & without logging nearly the same time.

Where could be the issue?

Network issue?
Else If i do separate connection for “NOTIFICATION” and “UPDATION” it will minimize the time?

reamon · July 16, 2009, 11:48pm

Are you measuring the time it takes to update X and separately measuring the time it takes to update Y (and just that time, not the time it takes for the update notification to fire)? How much longer is Y taking?

I doubt this is a network issue, nor would using different connections make a difference (same target host, same DB).

sam1234 · July 21, 2009, 4:12pm

Hi Rob,

Table X will be updated as a batch(using stand alone java code) our wM will have a UPDATE NOTIFICATION which in turn invoke a trigger service to update Y table. I noticed by increasing and changing the “Queue retrieval” and “Queue processing” there is some change in performance but even then its low, ex: updating 30 records in Y table taking nearly 4 min [ Queue retrieval capacity=10 and refill=10 and Queue processing maximum thread=10, NOTIFICATION interval=5 seconds

wM Service end time → 2009-07-21 14:46:26 IST
Stand alone Java service completion time → 2009-07-21 14:42:47 IST(+5 second this is notification interval)
]. Noticed the memory usage in statistic page it was only 31% (By the way am using local publishing, hope there is no difference in performance whether I use local publish or Broker).

If I use BASIC NOTIFICATION performance will be more? Please help me in this performance issue.

reamon · July 21, 2009, 8:57pm

Using basic notification will have no impact. The only real difference between update notification and basic notification is that the update notification will manage the DB triggers and buffer tables. Basic notification assumes that something else manages the triggers and buffer tables (I usually recommend basic notification–privs to the wM IS account can be minimized and triggers/buffer tables don’t get inadvertently dropped by errant admin activity in IS Administrator).

There will be some difference between local publish and Broker but it probably isn’t significant.

With each insert, there is a transaction commit. So compared to the “batch” update of the Java program the steps from getting the update notification through to committed record is a lot more work.

Notification poll wakes up.
Reads entries in the buffer table.
Moves each to staging table.
For each, publishes an event.
Updates staging table (mark as published).
IS trigger management thread retrieves up to 10 events.
Retrieves execution thread from pool (at beginning, will create new threads)
Invokes trigger service
Trigger service retrieves JDBC connection from pool (at beginng, will establish connection until pool is max)
Performs insert. Commit transaction.

I suspect that the expire timeout setting of the connection is a candidate for change.

Expire Timeout (msec) 1000

This means the connection needs to be idle for just 1 second before the adapter disconnects. Connecting and disconnecting is time consuming and hard on the DB process. Bump that to 30-60 seconds. Or longer. But make sure the interval in the connection definition is shorter than the timeout setting on the DB side.

The blocking timeout is a little too short as well. It is set such that a thread waiting for a connection from the pool will wait just 1 second before giving up. You might want to increase that.

Give these a shot and let us know the outcome.

sam1234 · July 23, 2009, 11:51am

Hi Rob,
Please find my analysis.

Updating 30 records:
Min=5 con
Max=10 con
Block Timeout (msec) 1000
Expire Timeout (msec) 1000

Document Retrieval
Queue Re-fill size=4
Document processing
Max thread=10
End Time 2009-07-23 10:42:08 IST
Start Time 2009-07-23 10:37:43 IST

Total time = 4 min 25 sec

Updating 30 records:
Min=1 con
Max=10 con
Block Timeout (msec) 1000
Expire Timeout (msec) 1000

Document Retrieval
Queue Re-fill size=4
Document processing
Max thread=10
End Time 2009-07-23 10:50:44
Start Time 2009-07-23 10:46:17

Total time = 4 min 21 sec

Updating 30 records:
Min=1 con
Max=10 con
Block Timeout (msec) 10000
Expire Timeout (msec) 100

Document Retrieval
Queue Re-fill size=8
Document processing
Max thread=10
End Time 2009-07-23 11:06:43
Start Time 2009-07-23 11:03:18
Total time = 3 min 25 sec

Updating 30 records:
Min=1 con
Max=10 con
Block Timeout (msec) 10000
Expire Timeout (msec) 10000

Document Retrieval
Queue Re-fill size=8
Document processing
Max thread=10
End Time 2009-07-23 11:12:01
Start Time 2009-07-23 11:08:34
Total time = 3 min 27 sec

Among the above 3 option had less time than other(3’rd and 4’th options are more same). But even then 3:25 is too much time for 30 records. Why can’t we have bunch of subscription, instead of having individual record subscrption? Is that possible? If we have bunch/batch subscription no need of closing/opening connection of individual subscription will be needed, we can do our operation in a single connection itself.

One more query: If 30 records updated as a batch using JAVA stand alone application. Do our wM UPDATE_NOTIFICATION will be notified 30 times? or 1 time with bunch of records during that time(I hope its 30 times wM will be notified) is that possible for notification to publish 30 records at a time?

Regards,
Sam.

reamon · July 23, 2009, 10:11pm

What is the configuration of your subscription trigger? Serial or concurrent? I assume concurrent since you mentioned max threads of 10.

Increasing the refill level may actually be hurting the time. The refill level indicates that when the number of unprocessed docs reaches X, go get more. With a value of 8, you’re processing 2 docs then going to get the next 2 published docs from the queue. But that may not be the biggest time sink.

The update notification will fire 30 events. If all 30 are in the buffer table at poll time, and the Maximum Row value is 0 (no limit) or >= 30 then all 30 will be published at about the same time.

I wonder if establishing the DB connections is taking a bit of time? Each test you’re running has to build up the connection pool. You might bump the expire timeout to something like 7200000 (2 hours). You’ll want min connections to be 0 (>0 risks an integration hitting a stale connection and failing).

sam1234 · July 23, 2009, 11:26pm

Rob,

Yes its concurrent connection.

Instead of having 30 published document individually, is there any way to have single publishable document for all documents which were present in buffer table during the polling time. If all records published in a single publishable document list, we can subscribe in a document list and loop it and we can do the required operation, which will decrease the total time. Correct me if am wrong.

By the way, will let you know once i test with expire time out = 7200000(2 Hrs).

Sorry for this question, “Expire Timeout” → this field specifies the number of milliseconds that an inactive connection can remain in the pool before it is closed and removed from the pool. Correct my understanding, once the db operation is over, connection will be released(if connection is required by next operation since max connection is not enough to handle the required things) for next operation only if the expire timeout gets over before that the connection won’t be release even if there is no operation done using that connection. Correct me…

Regards,
Sam.

reamon · July 24, 2009, 1:51am

I do not know of a way to have the notifications inlude multiple rows in a single event.

Have you measured the time of each individual DB update operation? That might help indicate where the time is being spent.

Your understanding of the expire timeout appears to be accurate.

After a DB operation is complete, the connection is returned to the pool (still a live session with the DB) and the time the connection went idle is stored. The pool will hand-out the connection to the next DB operation. If the connection is not used before the idle time exceeds the expire timeout, the connection will be closed.

sam1234 · July 24, 2009, 10:50pm

Hi Rob,

Please find my all 3 options, in 3’rd option i have enabled the db connection which update table Y where i “passed the values to get updated in db table”, whereas in other 2 options didn’t pass value to db connection for update “here it took less time”.

Also I have pasted the individual time for each update, noticed time taken in db table update - tried both “LOCAL_TRANSACTOIN” & “NO_TRANSACTION” both timings were nearly same.

Enable Connection Pooling true
Minimum Pool Size 1
Maximum Pool Size 10
Pool Increment Size 1
Block Timeout (msec) 10000
Expire Timeout (msec) 7200000
Startup Retry Count 0
Startup Backoff Timeout (sec) 10

Document Retrieval
Queue Re-fill size=8

Document processing
Max thread=10

Here I have disabled the adapter connection service which update Y table. Only I had save pipeline invoke service within the service which got invoked by trigger.
END 2009-07-24 11:07:40
START 2009-07-24 11:07:39

Total time = 1 sec

Enable Connection Pooling true
Minimum Pool Size 1
Maximum Pool Size 10
Pool Increment Size 1
Block Timeout (msec) 10000
Expire Timeout (msec) 7200000
Startup Retry Count 0
Startup Backoff Timeout (sec) 10

Document Retrieval
Queue Re-fill size=8

Document processing
Max thread=10

Here enabled the db connection & didn’t pass any value to update service (so update didn’t takes place)
END 2009-07-24 11:20:45 IST
START 2009-07-24 11:20:42 IST

Total time = 3 sec

Enable Connection Pooling true
Minimum Pool Size 1
Maximum Pool Size 10
Pool Increment Size 1
Block Timeout (msec) 10000
Expire Timeout (msec) 7200000
Startup Retry Count 0
Startup Backoff Timeout (sec) 10

Document Retrieval
Queue Re-fill size=8

Document processing
Max thread=10

Enabled the db connection to updated by passing the values.

END 2009-07-24 11:38:00 IST
START 2009-07-24 11:34:26 IST

Total Time: 3 min 34 sec

Individual time taken for each update:

[15515]2009-07-24 11:38:00 IST [ISP.0090.0003C] End Time 07/24/09 11:38:00:465
[15505]2009-07-24 11:36:45 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:45:686

[15514]2009-07-24 11:37:53 IST [ISP.0090.0003C] End Time 07/24/09 11:37:53:372
[15503]2009-07-24 11:36:39 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:39:29

[15513]2009-07-24 11:37:46 IST [ISP.0090.0003C] End Time 07/24/09 11:37:46:700
[15501]2009-07-24 11:36:32 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:32:30

[15512]2009-07-24 11:37:39 IST [ISP.0090.0003C] End Time 07/24/09 11:37:39:966
[15499]2009-07-24 11:36:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:25:77

[15511]2009-07-24 11:37:32 IST [ISP.0090.0003C] End Time 07/24/09 11:37:32:91
[15497]2009-07-24 11:36:14 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:14:436

[15510]2009-07-24 11:37:20 IST [ISP.0090.0003C] End Time 07/24/09 11:37:20:904
[15495]2009-07-24 11:36:06 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:06:389

[15509]2009-07-24 11:37:13 IST [ISP.0090.0003C] End Time 07/24/09 11:37:13:904
[15493]2009-07-24 11:35:59 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:59:765

[15508]2009-07-24 11:37:06 IST [ISP.0090.0003C] End Time 07/24/09 11:37:06:357
[15491]2009-07-24 11:35:52 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:52:765

[15507]2009-07-24 11:36:59 IST [ISP.0090.0003C] End Time 07/24/09 11:36:59:717
[15489]2009-07-24 11:35:46 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:46:15

[15506]2009-07-24 11:36:52 IST [ISP.0090.0003C] End Time 07/24/09 11:36:52:232
[15487]2009-07-24 11:35:39 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:39:359

[15504]2009-07-24 11:36:45 IST [ISP.0090.0003C] End Time 07/24/09 11:36:45:576
[15485]2009-07-24 11:35:31 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:31:421

[15502]2009-07-24 11:36:38 IST [ISP.0090.0003C] End Time 07/24/09 11:36:38:936
[15483]2009-07-24 11:35:24 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:24:312

[15500]2009-07-24 11:36:31 IST [ISP.0090.0003C] End Time 07/24/09 11:36:31:936
[15481]2009-07-24 11:35:16 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:16:546

[15498]2009-07-24 11:36:24 IST [ISP.0090.0003C] End Time 07/24/09 11:36:24:967
[15479]2009-07-24 11:35:09 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:09:734

[15496]2009-07-24 11:36:14 IST [ISP.0090.0003C] End Time 07/24/09 11:36:14:342
[15477]2009-07-24 11:35:02 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:02:968

[15494]2009-07-24 11:36:06 IST [ISP.0090.0003C] End Time 07/24/09 11:36:06:296
[15475]2009-07-24 11:34:52 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:52:859

[15492]2009-07-24 11:35:59 IST [ISP.0090.0003C] End Time 07/24/09 11:35:59:655
[15473]2009-07-24 11:34:46 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:46:203

[15490]2009-07-24 11:35:52 IST [ISP.0090.0003C] End Time 07/24/09 11:35:52:624
[15471]2009-07-24 11:34:39 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:39:313

[15488]2009-07-24 11:35:45 IST [ISP.0090.0003C] End Time 07/24/09 11:35:45:921
[15469]2009-07-24 11:34:32 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:32:781

[15486]2009-07-24 11:35:39 IST [ISP.0090.0003C] End Time 07/24/09 11:35:39:249
[15468]2009-07-24 11:34:32 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:32:781

[15484]2009-07-24 11:35:31 IST [ISP.0090.0003C] End Time 07/24/09 11:35:31:312
[15465]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:813

[15482]2009-07-24 11:35:24 IST [ISP.0090.0003C] End Time 07/24/09 11:35:24:203
[15464]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:766

[15480]2009-07-24 11:35:16 IST [ISP.0090.0003C] End Time 07/24/09 11:35:16:437
[15463]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:625

[15478]2009-07-24 11:35:09 IST [ISP.0090.0003C] End Time 07/24/09 11:35:09:625
[15462]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:500

[15476]2009-07-24 11:35:02 IST [ISP.0090.0003C] End Time 07/24/09 11:35:02:859
[15461]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:453

[15474]2009-07-24 11:34:52 IST [ISP.0090.0003C] End Time 07/24/09 11:34:52:781
[15460]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:203

[15472]2009-07-24 11:34:46 IST [ISP.0090.0003C] End Time 07/24/09 11:34:46:78
[15459]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:78

[15470]2009-07-24 11:34:39 IST [ISP.0090.0003C] End Time 07/24/09 11:34:39:219
[15458]2009-07-24 11:34:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:25:985

[15467]2009-07-24 11:34:32 IST [ISP.0090.0003C] End Time 07/24/09 11:34:32:547
[15457]2009-07-24 11:34:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:25:906

[15466]2009-07-24 11:34:32 IST [ISP.0090.0003C] End Time 07/24/09 11:34:32:547
[15456]2009-07-24 11:34:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:25:813

Entry from log file:
[15515]2009-07-24 11:38:00 IST [ISP.0090.0003C] End Time 07/24/09 11:38:00:465
[15514]2009-07-24 11:37:53 IST [ISP.0090.0003C] End Time 07/24/09 11:37:53:372
[15513]2009-07-24 11:37:46 IST [ISP.0090.0003C] End Time 07/24/09 11:37:46:700
[15512]2009-07-24 11:37:39 IST [ISP.0090.0003C] End Time 07/24/09 11:37:39:966
[15511]2009-07-24 11:37:32 IST [ISP.0090.0003C] End Time 07/24/09 11:37:32:91
[15510]2009-07-24 11:37:20 IST [ISP.0090.0003C] End Time 07/24/09 11:37:20:904
[15509]2009-07-24 11:37:13 IST [ISP.0090.0003C] End Time 07/24/09 11:37:13:904
[15508]2009-07-24 11:37:06 IST [ISP.0090.0003C] End Time 07/24/09 11:37:06:357
[15507]2009-07-24 11:36:59 IST [ISP.0090.0003C] End Time 07/24/09 11:36:59:717
[15506]2009-07-24 11:36:52 IST [ISP.0090.0003C] End Time 07/24/09 11:36:52:232
[15505]2009-07-24 11:36:45 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:45:686
[15504]2009-07-24 11:36:45 IST [ISP.0090.0003C] End Time 07/24/09 11:36:45:576
[15503]2009-07-24 11:36:39 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:39:29
[15502]2009-07-24 11:36:38 IST [ISP.0090.0003C] End Time 07/24/09 11:36:38:936
[15501]2009-07-24 11:36:32 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:32:30
[15500]2009-07-24 11:36:31 IST [ISP.0090.0003C] End Time 07/24/09 11:36:31:936
[15499]2009-07-24 11:36:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:25:77
[15498]2009-07-24 11:36:24 IST [ISP.0090.0003C] End Time 07/24/09 11:36:24:967
[15497]2009-07-24 11:36:14 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:14:436
[15496]2009-07-24 11:36:14 IST [ISP.0090.0003C] End Time 07/24/09 11:36:14:342
[15495]2009-07-24 11:36:06 IST [ISP.0090.0003C] Start Time 07/24/09 11:36:06:389
[15494]2009-07-24 11:36:06 IST [ISP.0090.0003C] End Time 07/24/09 11:36:06:296
[15493]2009-07-24 11:35:59 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:59:765
[15492]2009-07-24 11:35:59 IST [ISP.0090.0003C] End Time 07/24/09 11:35:59:655
[15491]2009-07-24 11:35:52 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:52:765
[15490]2009-07-24 11:35:52 IST [ISP.0090.0003C] End Time 07/24/09 11:35:52:624
[15489]2009-07-24 11:35:46 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:46:15
[15488]2009-07-24 11:35:45 IST [ISP.0090.0003C] End Time 07/24/09 11:35:45:921
[15487]2009-07-24 11:35:39 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:39:359
[15486]2009-07-24 11:35:39 IST [ISP.0090.0003C] End Time 07/24/09 11:35:39:249
[15485]2009-07-24 11:35:31 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:31:421
[15484]2009-07-24 11:35:31 IST [ISP.0090.0003C] End Time 07/24/09 11:35:31:312
[15483]2009-07-24 11:35:24 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:24:312
[15482]2009-07-24 11:35:24 IST [ISP.0090.0003C] End Time 07/24/09 11:35:24:203
[15481]2009-07-24 11:35:16 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:16:546
[15480]2009-07-24 11:35:16 IST [ISP.0090.0003C] End Time 07/24/09 11:35:16:437
[15479]2009-07-24 11:35:09 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:09:734
[15478]2009-07-24 11:35:09 IST [ISP.0090.0003C] End Time 07/24/09 11:35:09:625
[15477]2009-07-24 11:35:02 IST [ISP.0090.0003C] Start Time 07/24/09 11:35:02:968
[15476]2009-07-24 11:35:02 IST [ISP.0090.0003C] End Time 07/24/09 11:35:02:859
[15475]2009-07-24 11:34:52 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:52:859
[15474]2009-07-24 11:34:52 IST [ISP.0090.0003C] End Time 07/24/09 11:34:52:781
[15473]2009-07-24 11:34:46 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:46:203
[15472]2009-07-24 11:34:46 IST [ISP.0090.0003C] End Time 07/24/09 11:34:46:78
[15471]2009-07-24 11:34:39 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:39:313
[15470]2009-07-24 11:34:39 IST [ISP.0090.0003C] End Time 07/24/09 11:34:39:219
[15469]2009-07-24 11:34:32 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:32:781
[15468]2009-07-24 11:34:32 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:32:781
[15467]2009-07-24 11:34:32 IST [ISP.0090.0003C] End Time 07/24/09 11:34:32:547
[15466]2009-07-24 11:34:32 IST [ISP.0090.0003C] End Time 07/24/09 11:34:32:547
[15465]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:813
[15464]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:766
[15463]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:625
[15462]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:500
[15461]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:453
[15460]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:203
[15459]2009-07-24 11:34:26 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:26:78
[15458]2009-07-24 11:34:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:25:985
[15457]2009-07-24 11:34:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:25:906
[15456]2009-07-24 11:34:25 IST [ISP.0090.0003C] Start Time 07/24/09 11:34:25:813

Guide me which values I can try in db connections to minimize the update time.

Regards,
Sam.

reamon · July 25, 2009, 2:11am

Great work in zeroing in on where the time is being spent!

Over a minute for a single record update is really, really suspicious. I guess it is time to dig in to the specifics of the DB. What JDBC driver, what DB, where is it, what tables are being updated, etc. We should review the adapter service too. Can you post the details of that? Also, what are the versions of IS, JDBC adapter, DB, driver, etc.

This is a real head scratcher.

sam1234 · July 27, 2009, 9:56am

Hi Rob,

It’s JDBC adapter V 6.5
Oracle DB (it’s in my friend’s machine.)
IS 7.1.2
Driver → oracle.jdbc.pool.OracleDataSource
Table - Am updating only one column in 1 table.(Ex: updating an email-id of that table)

Any other information on TABLE’s? I have attached the adapter service screen shot.
Please let me know if need more information from my side.

Regards,
Sam

reamon · July 28, 2009, 8:08am

Looks pretty straight forward.

Couple of brainstorming ideas:

Mismatch of default character encoding between the IS JVM and the DB?
Set driverType=thin in the other properties.

That’s about all that comes to mind at this point.

sam1234 · July 28, 2009, 9:32am

Hi Rob,

Already am using ‘driverType=thin’.

How can we find the mismatch of default character encoding b/w IS JVM and db? If it mismatch how its working?

Regards,
Sam.

reamon · July 29, 2009, 7:04pm

I’ve reached the end of ideas for looking at what might be amiss. Perhaps a session with wM tech support is the next step. They’ll want to see the details of your Java app, your IS package and probably the details of the Oracle DB configuration.

sam1234 · July 30, 2009, 11:16pm

Hi Rob,

Will check again with other db. Also if i get any solution will let you know. Thanks for your extended help in fixing my issue.

Regards,
Sam.

Topic		Replies	Views
Issues with JDBC Basic Notification - Throughput very poor and unable to improve it webMethods , Integration-Server-and-ESB	15	1617	April 2, 2021
JDBC : Select multiple records using NOT in query webMethods , Integration-Server-and-ESB , Adapters-and-E-Standards	12	2520	April 2, 2021
regarding JDBC Connection pool webMethods , Integration-Server-and-ESB , Flow-and-Java-services	11	3823	April 2, 2021
Improving JDBC notification processing webMethods , Integration-Server-and-ESB , Adapters-and-E-Standards	9	1246	April 2, 2021
Unable to invoke adapter serviceUnable to get connection factory from connection webMethods , Integration-Server-and-ESB , Adapters-and-E-Standards	25	10430	April 2, 2021

Performance Check

Using logging

Total time = 4 min 25 sec

Total time = 4 min 21 sec

Document Retrieval Queue Re-fill size=8 Document processing Max thread=10 End Time 2009-07-23 11:06:43 Start Time 2009-07-23 11:03:18 Total time = 3 min 25 sec

Document Retrieval Queue Re-fill size=8 Document processing Max thread=10 End Time 2009-07-23 11:12:01 Start Time 2009-07-23 11:08:34 Total time = 3 min 27 sec

Total time = 1 sec

Total time = 3 sec

Related topics

Document Retrieval
Queue Re-fill size=8
Document processing
Max thread=10
End Time 2009-07-23 11:06:43
Start Time 2009-07-23 11:03:18
Total time = 3 min 25 sec

Document Retrieval
Queue Re-fill size=8
Document processing
Max thread=10
End Time 2009-07-23 11:12:01
Start Time 2009-07-23 11:08:34
Total time = 3 min 27 sec