Marked Rollback - Queue Size

          Hi ,
          Few hours after my server has stared running, all of a sudden my queues get
          stuck. And the queue size increases without bound.
          HERE IS THE STATUS OF 1st QUEUE
          {weblogic.transaction.internal.JTATransactionImpl: name=null, xid=BEA1-2EC3483119FCF099F40D,
          status=Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
          Transaction timed out after 303 seconds Xid=BEA1-2EC3483119FCF099F40D(20175221),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=303,seconds left=60,activeThread=Thread[ExecuteThread: '0' for queue:
          'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=started,assigned=none),xar=JMS_cgJMSStore),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=started,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1099718),SCInfo[ahlAlertsDomain+ahlAlertsServer]=(state=active),properties=({weblogic.jdbc=t3://10.100.51.137:7501}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ahlAlertsServer+10.100.51.137:7501+ahlAlertsDomain+t3+,
          XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_cgJMSStore},NonXAResources={})],CoordinatorURL=ahlAlertsServer+10.100.51.137:7501+ahlAlertsDomain+t3+)],
          userProperties={weblogic.jdbc=t3://10.100.51.137:7501}, secondsActive=20488, servers=ahlAlertsServer,
          resourceNamesAndStatus=weblogic.jdbc.wrapper.JTSXAResourceImpl/started+JMS_cgJMSStore/started,
          coordinatorURL=ahlAlertsServer+10.100.51.137:7501+ahlAlertsDomain+t3+, serversAndStatus=ahlAlertsDomain+ahlAlertsServer/active}
          AND THE REST 19 SHOW
          {weblogic.transaction.internal.JTATransactionImpl: name=null, xid=BEA1-2F01483119FCF099F40D,
          status=Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
          Transaction timed out after 303 seconds Xid=BEA1-2F01483119FCF099F40D(12347967),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=303,seconds left=60,activeThread=Thread[ExecuteThread: '1' for queue:
          'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=started,assigned=none),xar=JMS_cgJMSStore),SCInfo[ahlAlertsDomain+ahlAlertsServer]=(state=active),properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ahlAlertsServer+10.100.51.137:7501+ahlAlertsDomain+t3+,
          XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_cgJMSStore},NonXAResources={})],CoordinatorURL=ahlAlertsServer+10.100.51.137:7501+ahlAlertsDomain+t3+)],
          userProperties={}, secondsActive=20482, servers=ahlAlertsServer, resourceNamesAndStatus=JMS_cgJMSStore/started,
          coordinatorURL=ahlAlertsServer+10.100.51.137:7501+ahlAlertsDomain+t3+, serversAndStatus=ahlAlertsDomain+ahlAlertsServer/active}
          Please advise. I am sure that I am not using any XA Drivers, but couldnt decipher
          the meaning of the status.
          Please help.
          Regards,
          Abhijeet

Sorry, it's fixed.
Solution: I have to reduce the size of the default queue first since it max out the limit

Similar Messages

JDBC Transaction is no longer active - status: 'Marked rollback'

I'm getting the folowing issue, we are not seeing this issue if we recycle the WLS
Using WLS V10.3.3
Can any one suggest on this issue, how to reslove this
85417.772: [Full GC [PSYoungGen: 117504K->0K(234880K)] [PSOldGen: 662564K->665699K(700416K)] 780068K->665699K(935296K) [PSPermGen: 133284K->132438K(225280K)], 30.2876423 secs] [Times: user=31.23 sys=0.68, real=30.32 secs]
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 39 seconds
BEA1-600C65F8B23E363DFDF0]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:193)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:209)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:99)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at com.vzw.pos.cmw.ejb.service.UserProfileService.getNewUserId(Unknown Source)
at com.vzw.pos.cmw.ejb.utils.CMWEjbUtil.createUserProfileVO(Unknown Source)
at com.vzw.pos.cmw.ejb.utils.CMWEjbUtil.createRosterVO(Unknown Source)
at com.vzw.pos.cmw.ejb.service.AdministrationBean.getRostersByUserId(Unknown Source)
at com.vzw.pos.cmw.ejb.service.Administration_ujnwz8_ELOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.vzw.pos.cmw.ejb.service.Administration_ujnwz8_ELOImpl.getRostersByUserId(Unknown Source)
at com.vzw.pos.cmw.action.CMWTopFrameAction.setUserRoleInSession(Unknown Source)
at com.vzw.pos.cmw.action.CMWTopFrameAction.changeLocation(Unknown Source)
at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.vzw.pos.cmw.filters.CMWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3710)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3676)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2272)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2178)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Aug 23, 2013 10:41:53 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 298 internal data record unavailable (probable closure due idle timeout), event received -32>
<Aug 23, 2013 10:41:53 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 286 internal data record unavailable (probable closure due idle timeout), event received -32>
<Aug 23, 2013 10:41:56 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 299 internal data record unavailable (probable closure due idle timeout), event received -32>
<Aug 23, 2013 10:42:51 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 286 internal data record unavailable (probable closure due idle timeout), event received -32>

Here is DS configuration
Initial Capacity:                  75
Maximum Capacity:                  75
Capacity Increment:                    1
Seconds to trust an idle pool connection:     10
Shrink Frequency:                    900
Enable Connection Leak Profiling:          False
Enable Connection Profiling:               False
Test Frequency:                         120 seconds
Test Connections on Reserve:               True
Connection Reserve Timeout:               10 seconds
Connection Creation Retry Frequency:         1
Inactive Connection Timeout:               60 second
Maximum Waiting for Connection:               2147483647
Statment Cache Type:     LRU
Statment Cache Size:     10
Connection Creation Relay Frequency:      1
Remove Infected Connections Enabled:      True
Wrap Data types:     True
Ignore In-use connections:     True

6500 strict priority queue size ???

Hi guys,
Is it possible to adjust the 6500 line cards strict priority queue size? Most cards assign 85% of thebandwdith to the oridinary queues and 15% to the strict priority queue. It seems that it is not possible to adjust the size of the strict priority queue.
I have a customer who has numerous T1's encapsulated into IP and the gross amount of traffic is about 200Meg, all of which is real time. If I were to mark this as DSCP 46 (COS 5) it would saturate the strict priorty queue leading not only to performance problems on the T1's but would also starve the rest of the traffic on the 1Gig WAN link.
Any thoughts guys?
Regards, Steve

Hi Paresh,
Thanks for your reply. I think I didn't explain myself properly. There is a bandwidth allocation of memory for each port. The priority queue gets 15%by default. I have so much priority queue traffic that I want to increase this to 25% because all of it is strict priority (its voice after all). If this canot be done then I will be losing packets of voice since the priorty queue will not be able to accomdate the amount of traffic.
Best regards, Steve

Queue size

I am supposed to write a program in java where a single queue is shared by multiple java programs.
I tried create a queue in super class and let sub classes access and update it.But when I run the program and check the size of queue in the sub classes it seems like the queue is initializing everytime the superclass is called in each sub class.
The code is as follow:
import java.util.*;
class Que
{public Que() {}
LinkedList<String> queue=new LinkedList<String>();
public void Qadd(String S){queue.addFirst(S);}
public void Qremove(){queue.remove();}
public ListIterator<String> QListiterator() {return queue.listIterator();}
public int Qsize(){int y=queue.size();return y;}}
class Que1 extends Que
{public static void main(String args[]){
Que q=new Que();q.Qadd("A");q.Qadd("B");q.Qadd("C"...
q.Qadd("D");q.Qremove();int size=q.Qsize();
System.out.println("size:"+size);}}
class Que2 extends Que{
public static void main(String args[])
Que q=new Que();q.Qadd("D");
int size=q.Qsize();
System.out.println("size:"+size);}}
Now the size output is 3 and then 0.But I need 3 and then 3.
Can some1 direct me to the right direction in solving my problem??

are you actually running these in separate java instances (you are running the java program multiple times?). if so, you have a lot more work ahead of you. java does not magically share data between different programs. if you need to share data across multiple programs, you need to start looking into remote protocols and distributed processing (or use JMS).
is it possible you just want multiple threads in the same program instead of multiple programs? if so, then things get a lot simpler (not necessarily easy per-se, but much, much simpler).

Errors using weblogic sql driver: "No JDBC connection can be made because the transaction state is marked rollback"

One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
     at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)
     at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
     at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
     at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin

Joseph Weinstein <[email protected]> wrote:
>
>
YuanHui Liu wrote:
Joe,
We got the exact same error message. The error came after we got theJDBC connection,
and trying to create statement off it.
It occurs intermitently when we are running another standalone JAVAapp to do
some end of day work, which results in the DB Server being very busy(90+%CPU
usage) for about 5 minutes. We see a surge of requests to the WLSJDBC Connection
pool. This would sometimes result in all our subsequent DB requeststo fail and
lead to a crash.
We are using WLS6.0SP1. I do not think there's a 30 seconds wait leadingto a
connection timeout that caused this(rather it is the end effect).
Can you give us a more detailed explanation? Is there a miscommunicationbetween
our DB(Sybase12) and WLS?Hi. It looks to you like it's after you get the connection, but really
it's when the server is
gettng the pool connection. For performance/synchronization reasons we
do a clever
delay: When your code asks for a pool connection we quickly give you
the pool wrapper,
but we delay actually reserving the real underlying DBMS connection until
your first
real need for a connection, at your first JDBC call, such as createStatement()
etc.
It is while waiting for a pool connection long enough for the transaction
coordinator
to have timed you out before you ever get a chance. It's nothing to do
with the
DBMS or even JDBC, I believe. I think the weblogic server either has
too few execute-threads
and/or too few CPU cycles to do the work load.
Okay, so there's a lazy initialization of the connection.
From reading our log I believe our failur is immediate rather
than waiting for 30+ seconds(the default setting) from the DB,
the timeout occurred later as a result. At the time either because the DB Server
is very busy.
Since we are running WLS6.0 we have only one connection pool,
we have defined a max of 150 threads in the pool. While this
is happening the DB Server is being pinned by an overnight job,
but the WLS Server is not busy at all. The DB and WLS resides
on different physical boxes.
We also have a thread dump from the WLS console when we rebooted the server, it
showed that we are hanging on to the thread & jdbc
connections after these exceptions has occurred instead of releasing them, note
"16083"(~4.5 hours) seconds has passed:
142 116222 Retry rollback request for tx: 'transaction=(IdHash=2963855,Name =
[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()],Xid=30643:8f3838f3709bf53d,Status=Rolling
Back. [Reason = Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
begin=16083,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=server),SCInfo[server]=(state=active),properties=({weblogic.jdbc=t3://159.55.158.25:8005,
weblogic.transaction.name=[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()]}))'
Scheduled Trigger
So I would argue this problem actually chewed up resources on the WLS server.
-Yuanhui Liu
>>
>>
Thanks.
-YuanHui Liu
Joseph Weinstein <[email protected]> wrote:
lixin wrote:
One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)Hi. This sounds like a JVM thread starvation issue, and/or a server
load
issue. What is
happening is that the transaction is started, and times out beforethe
SSB even gets to
the first JDBC work. I would first verify that the customer is using
the very latest JVM
available for the machine.
Joe Weinstein
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin

[svn] 3337: Minor fix to an earlier check-in on FlexClient max-queue-size.

Revision: 3337
Author: [email protected]
Date: 2008-09-24 12:58:27 -0700 (Wed, 24 Sep 2008)
Log Message:
Minor fix to an earlier check-in on FlexClient max-queue-size.
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/config/ServerConfigurationParser.java

MatejLach wrote:
clamd is running, user and group clamav all have the relevant permissions as far as I can tell, however upon scanning my mail, I always end up with the following error:
Scanning error:
/home/username/.claws-mail/mimetmp/0000000e.mimetmp: lstat() failed: Permission denied. ERROR
Seems like a permissions error to me... maybe check the actual file it is attempting to scan... I know it is in your home folder, but just to be sure, you might want to check that everything is sane.

WLS 5.1 - Tx marked rollback after 30sec.

          In a JMS QueueReceiver class establishes and begins a UserTransaction after which
          there is a sql call that sometimes take > 30 seconds. As a result the follow message
          is received:
          Mon Jun 10 21:37:26 EDT 2002:<I> <TX> Transaction (TxC 214945161, xid = 1023759385810_1,
          timeout = 30, txState = Marked Rollback, root = null) rolled back after 30 sec.
          Is there any way to adjust this timeout period? Also, where is it originating?
          Thanks,
          Dave


For user tx's you can explicitly set the tx timeout using
          javax.transaction.UserTransaction.setTimeout(int)
          Kumar
          Dave wrote:
          > In a JMS QueueReceiver class establishes and begins a UserTransaction after which
          > there is a sql call that sometimes take > 30 seconds. As a result the follow message
          > is received:
          >
          > Mon Jun 10 21:37:26 EDT 2002:<I> <TX> Transaction (TxC 214945161, xid = 1023759385810_1,
          > timeout = 30, txState = Marked Rollback, root = null) rolled back after 30 sec.
          >
          > Is there any way to adjust this timeout period? Also, where is it originating?
          >
          > Thanks,
          > Dave

MDS Time Delivery Queue size is increasing

Hello Everyone
We are using ICM 8.5.3 , I am getting this message in Event Viewer of Rogger A & Rogger B servers.
Computer:      LHRRGRA.ef.UCCE
Description:
MDS Time Delivery Queue size is increasing, current size is 5525, but will continue to send messages.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Cisco Systems, Inc. ICM" />
    <EventID Qualifiers="41220">32810</EventID>
    <Level>3</Level>
    <Task>4</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-06-08T06:12:08.000000000Z" />
    <EventRecordID>127461</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LHRRGRA.ef.UCCE</Computer>
    <Security />
</System>
<EventData>
    <Data>5525</Data>
    <Binary>06010000000000003D9030012A8004A160975AA23D45CD0114000000010041006D6473004C485243444352475241003535323500</Binary>
</EventData>
</Event>
Anyone knowns why getting this.
Regards
Irfan Tariq

The MDS processes on these Routers are unable to communicate quickly enough over their private connection.
You''ll want to check the network connectivity, QoS configuration, link speed, congestion, .... Also be sure to follow this document letter by letter :
http://docwiki.cisco.com/wiki/Contact_Center_Networking:_Offload,_Receive_Side_Scaling_and_Chimney
Cheers,
Kris

Maximum Integration Queue size?

The default integration event queue size is 1000 transactions, Does anyone know what the maximum integration queue size is?
Thanks
John

Hi !
I don't know if there's a limit, but you can ask the Customer Care to increase this value. For myself, I ask for 6.000 and I have it...
Hope this will help, feel free to ask more !
Max

Queue size for XNET Write Signal Waveform

Hello,
I'm trying to use XNET librairy to play a predefined waveform on an output signal. I'm working with LabVIEW 2014 SP1, XNET 14.5 on a W7 Pro 32 bits operating system. I use a NI PCI-8512 card. It's my first application using xnet library.
In my test application, I give to user the possibility to define the waveform to play. The total time and the sample frequency are settable. The output CAN signal is cyclic, with a cycle time of 0.01s (10Hz). I chose to use same frequency for sample my waveform and the CAN writing.
I've difficulties to work with the queue size. In this example, that's good but I don't really why. I've tested different values of Queue size and 100000 seems to be good until 60sec. But for longer times (about 5 minutes), this method is not good...
What is the good way to work in this mode, and how to use efficiently the queue size property? The information and the example in the NI-XNET Hardware and Software Help are not very probant...
Thanks per advance!
Francis M | Voir mon profil
Certified LabVIEW Developer
Solved!
Go to Solution.

Sounds like you have the concept. I've never done this with signals, only frames, but I assume there is a queued option. You'll want to read the help, or just try it and see if it works. Attached is an example that does not run which demonstrates something similar to what I've done in the past. Basically fill the buffer, wait a little, then add more frames to fill it again. Repeat until there are no more frames to add to the buffer.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Attachments:
XNET Queued Buffer Example.vi ‏12 KB

Can I get the queue size for ExecutorService

Can I get the queue size for ExecutorService created by newSingleThreadExecutor.

You would need to go to the implemented class or another interface. That interface does not define that method - read the JavaDoc on the API for more

Queue size of User events

Hello Everyone,
I am using LabVIEW 8.6
I am using CreateUser Events, Generate User Events for notification between Parallel loops.
Can anyone please explain how these events are queued???
what is the Queue Size and what happens if this queue is filled???
Thanks a lot in advance.
With Regards,
Avni Vyas

When a register for events node runs, it creates a queue of all the events it registered and returns a reference which you can use (you can wire it into the dynamic event terminal on a case structure).
The details of the queue are all handled behind the scenes, but I'm guessing it's probably a 32 bit length (which, on a machine with 32 bits of address space, means you'd run out of memory long before you fill the queue). In any case, it should be "large enough" for anything you would want to use it for.
There are documents online and in the LabVIEW help on the use of user events, so you should search for and read those. There are probably also examples in the example finder (Help>>Find Examples).
One important thing to remember is NEVER to wire the reference from a register node into more than one event structure. You can do it techincally, but you'll lose events without realizing it.
Try to take over the world!

Marked rollback from enlistresource

I have BC4J-EJB deployed on OAS 10.1.2.0.0. (J2EE and WC)
Database is 8.1. (Is this combination maybe problem?)
When I tried to start my ejb-client i got the error.
OAS log contain this message Marked rollback from enlistresource.
Client stack trace is ;
racle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
     at oracle.jbo.server.DBTransactionImpl.initTransaction(DBTransactionImpl.java:1173)
     at oracle.jbo.server.DBTransactionImpl.initTxn(DBTransactionImpl.java:5823)
     at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:248)
     at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:271)
     at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:291)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.connectToDSUsingEnv(AbstractRemoteApplicationModuleImpl.java:2094)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processSvcMsgRequest(AbstractRemoteApplicationModuleImpl.java:3968)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processSvcMsgEntries(AbstractRemoteApplicationModuleImpl.java:4129)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.readServiceMessage(AbstractRemoteApplicationModuleImpl.java:3389)
     atoracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processMessage(AbstractRemoteApplicationModuleImpl.java:1859)
     at oracle.jbo.server.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:7336)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.sync(AbstractRemoteApplicationModuleImpl.java:1825)
     at oracle.jbo.server.remote.ejb.ServerApplicationModuleImpl.doMessage(ServerApplicationModuleImpl.java:60
     at oracle.jbo.server.ejb.SessionBeanImpl.doMessage(SessionBeanImpl.java:376)
     at RemoteAmOrgDeo_StatefulSessionBeanWrapper16.doMessage(RemoteAmOrgDeo_StatefulSessionBeanWrapper16.java:445)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Na
Thanks.

I have BC4J-EJB deployed on OAS 10.1.2.0.0. (J2EE and WC)
Database is 8.1. (Is this combination maybe problem?)
When I tried to start my ejb-client i got the error.
OAS log contain this message Marked rollback from enlistresource.
Client stack trace is ;
racle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
     at oracle.jbo.server.DBTransactionImpl.initTransaction(DBTransactionImpl.java:1173)
     at oracle.jbo.server.DBTransactionImpl.initTxn(DBTransactionImpl.java:5823)
     at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:248)
     at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:271)
     at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:291)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.connectToDSUsingEnv(AbstractRemoteApplicationModuleImpl.java:2094)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processSvcMsgRequest(AbstractRemoteApplicationModuleImpl.java:3968)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processSvcMsgEntries(AbstractRemoteApplicationModuleImpl.java:4129)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.readServiceMessage(AbstractRemoteApplicationModuleImpl.java:3389)
     atoracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.processMessage(AbstractRemoteApplicationModuleImpl.java:1859)
     at oracle.jbo.server.ApplicationModuleImpl.doMessage(ApplicationModuleImpl.java:7336)
     at oracle.jbo.server.remote.AbstractRemoteApplicationModuleImpl.sync(AbstractRemoteApplicationModuleImpl.java:1825)
     at oracle.jbo.server.remote.ejb.ServerApplicationModuleImpl.doMessage(ServerApplicationModuleImpl.java:60
     at oracle.jbo.server.ejb.SessionBeanImpl.doMessage(SessionBeanImpl.java:376)
     at RemoteAmOrgDeo_StatefulSessionBeanWrapper16.doMessage(RemoteAmOrgDeo_StatefulSessionBeanWrapper16.java:445)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Na
Thanks.

FCoE Queue Size Calculation

Hi Experts,
Can anyone tell me how FCoE queue size is calculated? What about the pause and resume thresholds?
Thanks

Sorry, it's fixed.
Solution: I have to reduce the size of the default queue first since it max out the limit

Backing store queue size configuration

I have a backing store for my cache and have set it up for write-behinds. However I do not see any documentation to set the write-behind queue size. The JMX value "Coherence > Cache > DistributedCache > MyCache > QueueSize" shows 0. What does 0 mean - is it unbounded or no buffering?
Thanks,
Ashwin.

Hi Ashwin,
this is what the documentation says about QueueSize (on CacheMBean):
QueueSize Integer RO The size of the write-behind queue size. Applicable only for WRITE-BEHIND persistence type.
As you see, this is a read only value, and I believe it means that everything is flushed, and if positive, it means the number of unwritten entries.
You can specify the number of entries to buffer (for retries) from those entries which have failed to be written.
http://wiki.tangosol.com/display/COH34UG/read-write-backing-map-scheme
Look at the write-requeue-threshold setting for that.
I believe, not-yet-attempted writes are not discarded before the first attempt, the write-requeue-threshold does not apply to those.
Best regards,
Robert

Marked Rollback - Queue Size

Similar Messages

Maybe you are looking for