Problem with JDBC Queries ??

Question

Post reply

Problem with JDBC Queries ??

Lavanyasri

SSCarpal Tunnel

Points: 4907
More actions
September 28, 2011 at 2:37 am

#258018

HI All,
These queries taking more cpu time and running frequently , can any one have idea on these queries ??
EXEC master..xp_sqljdbc_xa_end @P0 OUT, @P1 OUT, @P2, @P3, @P4
EXEC master..xp_sqljdbc_xa_start @P0 OUT, @P1 OUT, @P2, @P3, @P4, @P5 OUT, @P6
EXEC master..xp_sqljdbc_xa_commit @P0 OUT, @P1 OUT, @P2, @P3, @P4
Regards,
Lavanya Sri

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply

spaghettidba SSC Guru Points: 105732 More actions · Answer 1

They look like XA transactions.

Do you have an EMS server around?

-- Gianluca Sartori

Lavanyasri SSCarpal Tunnel Points: 4907 More actions · Answer 2

HI ,

I don't know about the EMS server .

How to find EMS server is exist or not ??

My application access the SQL server through JDBC connectivity ..

Thanks ,

Lavanya Sri

Phil Parkin SSC Guru Points: 246880 More actions · Answer 3

This might be of interest.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Lavanyasri SSCarpal Tunnel Points: 4907 More actions · Answer 4

HI All,

I am continuously seeing the below queries taking more cpu time .

EXEC master..xp_sqljdbc_xa_end @P0 OUT, @P1 OUT, @P2, @P3, @P4

EXEC master..xp_sqljdbc_xa_start @P0 OUT, @P1 OUT, @P2, @P3, @P4, @P5 OUT, @P6

EXEC master..xp_sqljdbc_xa_commit @P0 OUT, @P1 OUT, @P2, @P3, @P4

couple of days back i changed the all my user databases isolation level to

" read committed snapshot " , but i didn't change the system databases isolation level .

Can you please suggest me is it compulsory to change the system databases isolation level also ???

i need u r suggestions ...

Thanks

Lavanya sri

Lavanyasri SSCarpal Tunnel Points: 4907 More actions · Answer 5

HI All,

Any updates on this . Its very urgent for me .

Please help on this , i am not find any solution in google also ..

Thanks

Lavanya

steveb. SSC-Forever Points: 46733 More actions · Answer 6

We really need more information to be able to provide any advice, since we do not know anything about your system and the application that is causing the issue.

Lavanyasri SSCarpal Tunnel Points: 4907 More actions · Answer 7

HI ,

I am using SQL Server 2005 standard edition 64 bit sp3 .

From SQl server we are using SQL JDBC 2.0 and we copied SQLJDBC_XA .Dll version is 2.0.1803.100 in Bin folder.

Application are conncting to SQL server with JDBC provider. They are using SQL JDBC 1.2 version .

Isolation level is : read_committed _snapshot

Can you please let me know what extra infromation you need from my side .

Thanks ,

Lavanya

Lavanyasri SSCarpal Tunnel Points: 4907 More actions · Answer 8

HI ,

Just i want to know when we will get these type of queries ?

It is due to application changes or Db changes ?

Thanks

chetanpunekar SSC Rookie Points: 34 More actions · Answer 9

Hi,

Even I am facing the similar issue.

Is there any way to find out why are these queries consuming so much CPU?

I have a 24 core machine with SQL Server 2008 R2 on it.

These queries consume around 2 to 3 cores each during my test.

Please let me know if you require any more information.

Thanks,

Chetan

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 10

Have you setup profiler to capture these statements? If not, try that. It will tell you what userid and from what server/workstation they are coming from and that should help you narrow down what is doing it.

chetanpunekar SSC Rookie Points: 34 More actions · Answer 11

Hi Marcus,

Thanks for your reply.

I didn't get what you are saying. Can you elaborate?

Thanks,

Chetan

Summer90 SSC-Dedicated Points: 32891 More actions · Answer 12

If you start a Profiler session just for the specific database that those queries are running against it will tell you what userid and where the queries are being run from. That way you can narrow down what could be running them.