After I do three layer structure, the data shows that there is no problem, but the error why always jump out when to update the box:
The original concept Application Excution Errer (R0094)
The Application terminated.
Errer: COBRA System Exception: COBRA_TRANSACTION_ROLLEDBACK at line 4 clicked in the event of object cb_1 of w_main.

CodePudding user response:

Who is made of three layers, give a suggestion!

CodePudding user response:

Errer: COBRA System Exception: COBRA_TRANSACTION_ROLLEDBACK
I also encountered this problem, but not in the update, will appear from time to time,

Top!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

CodePudding user response:

Ha ha, it seems easerver5.2 problems.

Lz only gives a problem description, a lot of a lot of the cause of this error, have definitely analysis

But there is a suggestion: use JDBC to connect to the database

CodePudding user response:

How to use JDBC to connect to the database? To teach me.

CodePudding user response:

Easerver buffer pool, where the JDBC example, pb even the method to check it online, I also have to go to check,

In addition, you save on a table that had better not write trigger

CodePudding user response:

Use the EAServer connection caches.
In EAServerMaganer match, the following is a JDBC I've even SybaseASE125 database example, after with the cache in % % EAServer EAServer/Repository/ConnCache/generates a *. Props, I put my copy down,

5.0 the Properties # Sybase EAServer
Com. Sybase. Jaguar. Conncache. Checkallowed=false
Com. Sybase. Jaguar. Conncache. Config - property=(description=env-entry-value=https://bbs.csdn.net/topics/false, env - an entry - name=DYNAMIC_PREPARE, env - entry - type=Java. Lang, String)
Com. Sybase. Jaguar. Conncache. Conlibdll=com. Sybase. Jdbc2. JDBC. SybDriver
Com. Sybase. Jaguar. Conncache. Conlibname=JDBC
Com. Sybase. Jaguar. Conncache. Db_type=Sybase_ASE
Com. Sybase. Jaguar. Conncache. The description=
Com. Sybase. Jaguar. Conncache. The handler=eas_servlet
Com. Sybase. Jaguar. Conncache. Logbyconnection=false
Com. Sybase. Jaguar. Conncache. Name=cachename
Com. Sybase. Jaguar. Conncache. Password. E=+ PVhJQ35H2LUTXAujwI5EZS2Zh7viM7l
Com. Sybase. Jaguar. Conncache. Poolsize. Max=10
Com. Sybase. Jaguar. Conncache. Poolsize. Min=0
Com. Sybase. Jaguar. Conncache. Props. Codeset=utf-8
Com. Sybase. Jaguar. Conncache. Remotesvrname=JDBC: sybase: Tds: hostname: 5100/dbname
Com. Sybase. Jaguar. Conncache. SQL. Trace=false
Com. Sybase. Jaguar. Conncache. Useparenthandlers=false
Com. Sybase. Jaguar. Conncache. Username=sa
Com. Sybase. Jaguar. Conncache. Xa. Remotesvrname=JDBC: sybase: Tds: hostname: 5100

CodePudding user response:

EASERVER JAGUAR service sometimes oneself stopped, note that stopped this error message may appear when, ha ha, I also met, to open the service, for a few minutes to release,

CodePudding user response:

I think I should is your problems setting up the component transaction or submit method has a problem, you wrote your component transaction attribute and submit method write see you wrote

CodePudding user response:

I think the way using the WINDOWS service start JAGUAR stability is not very good, really is stable in DOS mode

CodePudding user response:

Also, when you invoke the component transaction rolled back and forth SetAbort affairs when do to PB client to throw out a COBRA_TRANSACTION_ROLLEDBACK abnormalities, the need to use the TRY CATCH processing

CodePudding user response:

Ha ha, it seems everyone is talking about the COBRA_TRANSACTION_ROLLEDBACK this question,
If your component does not support components, so, when you setabort, will certainly be out of this, does not support the component transaction must not use setabort, or old to you commit and rollback,
If if is to support the component transaction, you must use setabort will roll, pay attention to, must be!!
In addition, if the component at run time appear abnormal accident, also can appear COBRA_TRANSACTION_ROLLEDBACK exception, in this way, you will need when the component code is written, for exception capture,
4th floor, it seems that you don't know eas, this series of exceptions are normal, you just don't know, without proper handling,
As pb programmer, if you want to increase their own competitiveness, use pb + eas development is the best choice,
Interested can look at http://hi.baidu.com/zzutligang, here are some articles, and continue to update, the
I hope to communicate more lovers of pb + eas development: msn:[email protected]

CodePudding user response:

Support her Lord, collection

CodePudding user response:

Support her Lord, collection

CodePudding user response:

EAServer different versions to use corresponding PB version to use, otherwise there will be submitted without success, EAServer corresponding should be PB9 version 5.2,

CodePudding user response:

15 floor that is wrong, also support the PB10 EAS5.2, note in the EAS PBVM to PB version for the client with you, you can check your PB version, I've met in the EAS is PB10.2.0, client is PB10.2.1 save failed into 10.2.1 is good

CodePudding user response:

In EAServer Manager to modify two parameters:

Com.sybase.jaguar.com ponent. Tx_outcome failed
Com.sybase.jaguar.com ponent. Tx_vote true

It is ok