Weblogic7.0 with MS SQL Server 2000 and Callable Statement

Question

Hello,
we have a little problem with our weblogic application.
In the SQL Server we have written a simple stored procedure
CREATE PROCEDURE nextval
@sequence_id INT OUT
AS
-- return an error if sequence does not exist
-- so we will know if someone truncates the table
set @sequence_id = -1
UPDATE sequences
SET @sequence_id = sequence_id = sequence_id + 1
RETURN @sequence_id
GO
It's a simple pk generator.
Also we have written a simple java application to test this procedure (getting
the connection over the weblogic datasource) and everything works fine.
But in the application running on weblogic we have problems with the second call.
Here the exceptions:
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@397317
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal nextVal = 30037
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@4377a3
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:33:24: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:33:24: [LOGLEVEL: 0] ****** PKGenerator.nextVal SQLException =
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 29 seconds
Name=[EJB de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],Xid=220:408eb51e3b228e43(691834),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=29,seconds left=30,activeThread=Thread[ExecuteThread: '14' for queue:
'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none,xar=weblogic.jdbc.jts.Connection@ffb40),SCInfo[fiatbank+gina]=(state=active),properties=({weblogic.transaction.name=[EJB
de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],
weblogic.jdbc=t3://192.168.0.27:7001, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+,
Resources={})],CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+)]). No further
JDBC access is allowed within this transaction.
the two files are:
PKGenerator.java (Weblogic application)
CallableSamples1.java (TestApplication)
Has anyone an idea, if weblogic has a problem or we have made a mistake?
Bye
Steffen
[files.zip]

Answer 1

Steffen Schenk wrote:
Hello,
we have a little problem with our weblogic application.Hi. It's not a JDBC issue, it's an EJB/transaction coordinator issue.
Any transactional EJB JDBC is done under the (usually silent) control of the
transaction coordinator. For instance, if your code calls Connection.commit()
in a transactional EJB, it will cheerfully be ignored, because only the transaction
coordinator knows when and whether to commit the whole transaction, not the
individual EJB, which may have been called as part of a larger transaction. Another
aspect of the coordinator's overseeing of the transaction is that once the transaction
is over, which may be right in the middle of an EJB's running if the transaction
timeout limit has been reached, then the coordinator will roll back or commit the
transaction as appropriate and take control of the JDBC objects. Any further attempt
by the EJB to do any JDBC will result in an exception.
>
In the SQL Server we have written a simple stored procedure
CREATE PROCEDURE nextval
@sequence_id INT OUT
AS
-- return an error if sequence does not exist
-- so we will know if someone truncates the table
set @sequence_id = -1
UPDATE sequences
SET @sequence_id = sequence_id = sequence_id + 1
RETURN @sequence_id
GO
It's a simple pk generator.
Also we have written a simple java application to test this procedure (getting
the connection over the weblogic datasource) and everything works fine.
But in the application running on weblogic we have problems with the second call.
Here the exceptions:
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@397317
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal nextVal = 30037
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn vor = null
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal conn nach = weblogic.jdbc.rmi.SerialConnection@4377a3
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal prepareCall
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal set gina
03.09.2002 / 14:32:45: [LOGLEVEL: 0] PKGenerator.nextVal registeredOUtparameter
03.09.2002 / 14:33:24: [LOGLEVEL: 0] PKGenerator.nextVal execute = false
03.09.2002 / 14:33:24: [LOGLEVEL: 0] ****** PKGenerator.nextVal SQLException =
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 29 seconds
Name=[EJB de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],Xid=220:408eb51e3b228e43(691834),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=29,seconds left=30,activeThread=Thread[ExecuteThread: '14' for queue:
'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none,xar=weblogic.jdbc.jts.Connection@ffb40),SCInfo[fiatbank+gina]=(state=active),properties=({weblogic.transaction.name=[EJB
de.fiatbank.vehicle.template.beans.TemplateDetailEJB.create(java.util.ArrayList,java.util.ArrayList,java.util.ArrayList,java.lang.String)],
weblogic.jdbc=t3://192.168.0.27:7001, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+,
Resources={})],CoordinatorURL=gina+192.168.0.27:7001+fiatbank+t3+)]). No further
JDBC access is allowed within this transaction.
the two files are:
PKGenerator.java (Weblogic application)
CallableSamples1.java (TestApplication)
Has anyone an idea, if weblogic has a problem or we have made a mistake?
Bye
Steffen
Name: files.zip
files.zip Type: Zip Compressed Data (application/x-zip-compressed)
Encoding: base64