Mdb (Modular debugger) question

Under Solaris there is mdb installed,
is it able to call a function of a program
being debuged the way as 'call' in gdb?

Thanks.
I read already the appropriate topics in the "Programming WebLogic Enterprise JavaBeans" and played also with parameters initial-beans-in-free-pool and max-beans-in-free-pool, without success.
I also watched the weblogic servers monitor pages of the MDB, and while he is blocking for some reason instead of starting the next child MDB the "use count" is only 1. For me it seams that weblogic does not recognize that the child MDBs finished working.

Similar Messages

  • Forte Debugger Question - How to break on exception?

    I am running my midlet under Forte Community Edition 3.0, and I am trying to track down a crash. The output window shows that a NullPointerException was thrown, so it should be a simple matter of finding the line with the offending allocation, but I cant find any way to make the debugger break on an exception. Is this possible?
    Thx,
    Fred

    I'll answer my own question here....the best thing I have found so far is to put a high level catch in the code, then call Exception.printStackTrace in the catch block. Its not ideal, but it helps find the offending code.
    Fred

  • Xcode debugger question

    How do i setup the debugger in xcode?

    The debugger is already setup in Xcode, do you have a specific question?

  • Intel Modular Server Question

    Hi,
    I have an Intel  MFSYS35 Modular Server with MFS5520VIB compute modules. Currently, I have 1TB hard drives installed. I was looking to upgrade to 3TB or possibly 4TB drives. Are only certain models compatible?
    Thanks,
    This topic first appeared in the Spiceworks Community

    Hi,
    I have an Intel  MFSYS35 Modular Server with MFS5520VIB compute modules. Currently, I have 1TB hard drives installed. I was looking to upgrade to 3TB or possibly 4TB drives. Are only certain models compatible?
    Thanks,
    This topic first appeared in the Spiceworks Community

  • ABAP Debugger Question

    Hello,
    When I debug an ABAP program, is there any way to display a list of names of all the program's internal tables? (global and local)
    Thx.
    Andy

    Hi andrew,
    First Switch to New ABAP Debugger if you are currently using Classic Debugger.
    In Desktop1 Tab(the default tab) select the Globals Tab in the Right side. There you can see all itabs, variables which are available globally.
    Regards
    Karthik D

  • Jdeveloper 9i - Debugger Question

    Some more info:
    1> I start java in debug mode
    set PATH=d:\jdev9i\jdk\jre\bin;%PATH%
    cd d:\jdev9i\j2ee\home
    java -ojvm -XXdebug,detached,port4000 -jar oc4j.jar
    2> You'll see the following message:
    *** Port is 4000 ***
    *** Connect debugger anytime for on demand debugging. ***
    Then, OC4J will start up.
    3> Back in JDeveloper, bring up the Project Settings dialog box.
    Select Debugger on the left side, check the Remote Debugging
    checkbox, and select the Attach to OJVM radio button.
    4> Put breakpoints in my code
    5> When you press Debug button on the toolbar (or from the menu),
    you will be presented with the Attach to OJVM dialog box where
    you enter the host name of the OC4J machine (leave blank if it's
    the same machine) and the debugging port number (4000). Press
    Ok, and the debugger will connect to OC4J.
    6> Next I start mmy web application from the browser using
    http://localhost:8888/property
    7> This triggers my breakpoints.
    ****However here is my problem. At some point in my flow I have to download an applet and I have breakpoints in it that I want to hit. However Jdeveloper just ignores those breakpoints completely.
    So how do I switch between the client applet and server side in a debugging session.
    Please help urgent!
    (Hope Liz Looney-> the debugger pro answers)
    FYI: Jdeveloper9i has a cool debugger!!!

    Hi,
    Your applet is running in the client (the browser). That's a different JVM than the one in the server (OC4J).
    You've connected JDev's debugger to the server JVM (OC4J), but you haven't connected it to the client JVM where your applet is running.
    Just like with server side java, you have 2 tasks:
    1. Start the JVM with debug options.
    2. Connect to the JVM with JDev's remote debugger.
    ....................Start the JVM with debug options....................
    If you install a JDK from Sun, then it should have automatically installed the Java Plug-in. (If you are using the JDK which comes with JDeveloper, then I don't know how you get the Java Plug-in.) So, assuming that you can get a JDK from Sun...
    From the Windows Control Panel open up the section for the Java Plug-in. Now, depending on which JDK you have installed, the control panel looks a little bit different. I'd recommend using the Plug-in for JDK 1.4, because it gives much more flexibility for specify Java Runtime Parameters. There are several tabs: Basic, Advanced, Browser, Proxies, Cache, Certificates, and About.
    Click on the Advanced tab. Here you can specify which JRE to use and the Java Runtime Parameters. In the Java Runtime Parameters, enter the following:
    -client -Xdebug -Xrunjdwp:transport=dt_socket,address=6000,server=y,suspend=n
    The -client part is to specify the HotSpot Client JVM. Currently OJVM does not work correctly with JDK 1.4, so you'll have to use the HotSpot Client JVM.
    The other options are the JPDA debug options.
    The address=6000 part specifies port number for the debugger to connect to. If your browser is running on the same machine as OC4J, you want to make sure that you use a different port number. (Remember you were using 4000 for debugging OC4J).
    The suspend=n part specifies that you want the JVM to start up and not to WAIT for a debugger connection. If you put suspend=y, the JVM would stop and wait for the debugger to connect. (You may decide later that for your situation, suspend=y would be appropriate.)
    Click on the Browser tab. Here you can check which browsers where you want to use the Java Plug-in. Make sure that the browser you will use for your applet is checked.
    Click on the Basic tab. Here you can choose whether to show or hide the Java console.
    Press the Apply button and then re-start your browser.
    ....................Connect JDev's remote debugger....................
    You should create another project for remote debugging your applet. Because you are using a HotSpot JVM, you must choose the Attach to JDPA radio button in the Project Settings dialog box, on the Debugger panel.
    Put breakpoints in your applet.
    Select your applet remote debugging project and press the Debug button on the toolbar. You will be presented with the Attach to JPDA dialog box, which looks just like the Attach to OJVM dialog that you use for remote debugging OC4J. Again, enter the host name of the browser machine (leave blank if it's the same machine as JDev) and the debugging port number (6000). Press Ok, and the debugger will connect to the browser's JVM using the JPDA (Java Platform Debugger Architecture) protocol.
    Now, when your applet executes the code where your breakpoint is, JDev's debugger should stop at the breakpoint.
    Remember that you have 2 debugging sessions going on simultaneously. You can use the Run Manager window (do View | Run Manager from the main menu) to control which debugging process is the active session. The toolbar buttons will always operate on the active debugging process.
    Some people find it easier to run the client and debug the server or to debug the client and run the server, but you can do both at the same time. You'll have to see which you find easiest for you
    -Liz
    PS - I'm glad you like JDev's Debugger!

  • Debugger question

    I'm using xCode debugger, however I cannot see values in variables for object-oriented code. Instead, I expand out the structures and see "isa". What is this and how can I see values when debugging objects.

    I have the following code in my Javascript file :
    MHCTIFFSave = app.trustedFunction( function (File,cFile)
    app.beginPriv();
    this.saveAs(File,"com.adobe.acrobat.tiff");
    app.endPriv();
    WHen I execute it in the debugger - I get this :
    MHCTIFFSave("Z:\\Test.gif","test");
    NotAllowedError: Security settings prevent access to this property or method.
    Doc.saveAs:4:Console undefined:Exec
    undefined
    I thought that this was a trusted function and this would prevent me from seeing this message .

  • Debugger question: how to step into a message call

    Hi everyone:
    If my understanding of the workings of the following objective C statement is correct,
    NSString *s = [NSString stringWithFormat:@"Hello %@", @"World"];
    what happens there is that it sends the "stringWithFormat" message to the "NSString" class. Correct?
    If so, is it possible to step into that message with a debugger? (For some reason when I try to do it, the debugger simply steps over it.)

    You don't have the source code to NSString so all you would see is machine code.

  • MDB tx processing question

    Tom,
    My understanding was that WebLogic by default configuration would pull n messages at a time from the a foreign jms server (via JMS connection poller) ; and process the n messages using the same MDB in n different transactions. Is this correct?
    If it is , what would be the conditions when the message would just stay in WebLogic layer - and weblogic MDB will continuously try to process the message - assuming the code in MDB called setRollbackOnly upon processing failure within the MDB. MDB is transactional.
    We see a thread that seems to sit in the state below in our application - no matter how many threaddumps I take the thread stays at this point. I see no other thread waiting on a lock for anything. But this seemingly stuck thread is causing 5 messages on Tibco EMS to stay in pending state until I shutdown the WLS node - which then breaks the tibco session and tibco then makes the messages available for redelivery and another WLS instance picks it up. Do note that WLS does not report any stuck threads either (stuck thread timeout set to 600 seconds) and my threaddumps span across 5 seconds to 45 minutes.
    "ContinuousJMSMessagePoller :MessageProcessor-Tes-Mts" id=4973 idx=0xde tid=1717 prio=5 alive, daemon
    at java/util/HashMap.get(HashMap.java:344)[optimized]
    at org/jboss/cache/UnversionedNode.getDirect(UnversionedNode.java:203)[inlined]
    at org/jboss/cache/invocation/NodeInvocationDelegate.getDirect(NodeInvocationDelegate.java:212)[optimized]
    at org/jboss/cache/CacheImpl._get(CacheImpl.java:702)[optimized]
    at sun/reflect/GeneratedMethodAccessor176.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)[optimized]
    at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[optimized]
    at java/lang/reflect/Method.invoke(Method.java:585)[optimized]
    at org/jgroups/blocks/MethodCall.invoke(MethodCall.java:330)
    at org/jboss/cache/interceptors/CallInterceptor.invoke(CallInterceptor.java:53)
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/EvictionInterceptor.handleGetKeyValueMethod(EvictionInterceptor.java:200)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/PessimisticLockInterceptor.handleGetKeyValueMethod(PessimisticLockInterceptor.java:347)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:81)
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)[inlined]
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:58)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/TxInterceptor.handleNonTxMethod(TxInterceptor.java:456)
    at org/jboss/cache/interceptors/TxInterceptor.handleGetKeyValueMethod(TxInterceptor.java:250)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/CacheMgmtInterceptor.handleGetKeyValueMethod(CacheMgmtInterceptor.java:81)
    at org/jboss/cache/interceptors/MethodDispacherInterceptor.invoke(MethodDispacherInterceptor.java:84)[optimized]
    at org/jboss/cache/interceptors/Interceptor.nextInterceptor(Interceptor.java:111)
    at org/jboss/cache/interceptors/InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:73)
    at org/jboss/cache/invocation/AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:123)
    at org/jboss/cache/invocation/AbstractInvocationDelegate.invoke(AbstractInvocationDelegate.java:64)
    at org/jboss/cache/invocation/CacheInvocationDelegate.get(CacheInvocationDelegate.java:382)
    at com/myapp/core/CacheService.get(CacheService.java:188)
    at com/myapp/core/CacheService.getFinancialInstrument(CacheService.java:273)
    at com/myapp/util/TradeDalUtils.lookupFinancialInstrument(TradeDalUtils.java:768)
    at com/myapp/xom/ReferenceData.getFinancialInstrumentByIdentifier(ReferenceData.java:330)
    at com/myapp/xom/CMMExecutionModel.getFiForPrimaryExecutionItem(CMMExecutionModel.java:1170)
    at sun/reflect/GeneratedMethodAccessor57908.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;(Unknown Source)
        at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)[optimized]
    at java/lang/reflect/Method.invoke(Method.java:585)[optimized]
    at ilog/rules/inset/IlrExecMethodValue.getValue(Lilog/rules/inset/IlrMatchContext;)Ljava/lang/Object;(Unknown Source)
    at ilog/rules/inset/IlrExecNaryValue.a(Lilog/rules/inset/IlrMatchContext;)[Ljava/lang/Object;(Unknown Source)[optimized]
    at ilog/rules/inset/IlrExecNaryValue.a(ILjava/lang/Class;Lilog/rules/inset/IlrMatchContext;)[Ljava/lang/Object;(Unknown Source)
        at ilog/rules/inset/IlrExecStaticMethodValue.getValue(Lilog/rules/inset/IlrMatchContext;)Ljava/lang/Object;(Unknown Source)
        at ilog/rules/inset/IlrExecStoreValue.getValue(Lilog/rules/inset/IlrMatchContext;)Ljava/lang/Object;(Unknown Source)
        at ilog/rules/inset/IlrExecBinaryTest.evaluate(Lilog/rules/inset/IlrMatchContext;)Z(Unknown Source)
        at ilog/rules/inset/IlrExecAndTest.evaluate(Lilog/rules/inset/IlrMatchContext;)Z(Unknown Source)
        at ilog/rules/engine/IlrTestRuleMem.i(Lilog/rules/engine/IlrPartial;)Z(Unknown Source)
        at ilog/rules/engine/IlrTestRuleMem.if(Lilog/rules/engine/IlrPartial;IIJ)Lilog/rules/engine/IlrRuleInstance;(Unknown Source)
        at ilog/rules/engine/IlrDefaultRuleMem.aa()V(Unknown Source)
        at ilog/rules/engine/IlrRuleMem.T()V(Unknown Source)
        at ilog/rules/engine/IlrAgenda.a([Lilog/rules/engine/IlrRule;Lilog/rules/engine/IlrAgendaFilter;IZ)I(Unknown Source)[optimized]
    at ilog/rules/engine/IlrEngine.fireAgendaRules([Lilog/rules/engine/IlrRule;Lilog/rules/engine/IlrAgendaFilter;IZ)I(Unknown Source)[inlined]
    at ilog/rules/inset/IlrExecRuleTask.a(Lilog/rules/engine/IlrTaskEngine;)V(Unknown Source)[inlined]
    at ilog/rules/inset/IlrExecRuleTask.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/inset/IlrExecTask.run(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/engine/IlrTaskEngine.execute(Lilog/rules/inset/IlrExecTaskInstance;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/inset/IlrExecTaskInstance.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeItem(Lilog/rules/engine/IlrWorkItem;Lilog/rules/inset/IlrExecFlowNode;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeSubFlow(Lilog/rules/inset/IlrExecFlowNode;Z)I(Unknown Source)
    at ilog/rules/inset/IlrExecFlowTask.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)
    at ilog/rules/inset/IlrExecTask.run(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/engine/IlrTaskEngine.execute(Lilog/rules/inset/IlrExecTaskInstance;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/inset/IlrExecTaskInstance.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeItem(Lilog/rules/engine/IlrWorkItem;Lilog/rules/inset/IlrExecFlowNode;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeSubFlow(Lilog/rules/inset/IlrExecFlowNode;Z)I(Unknown Source)
    at ilog/rules/inset/IlrExecFlowTask.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)
    at ilog/rules/inset/IlrExecTask.run(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)V(Unknown Source)[optimized]
    at ilog/rules/engine/IlrTaskEngine.execute(Lilog/rules/inset/IlrExecTaskInstance;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/inset/IlrExecTaskInstance.execute(Lilog/rules/engine/IlrTaskEngine;Lilog/rules/engine/IlrWorkItem;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.executeItem(Lilog/rules/engine/IlrWorkItem;Lilog/rules/inset/IlrExecFlowNode;ZZ)I(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.if(Z)V(Unknown Source)
    at ilog/rules/engine/IlrTaskEngine.a(Z)V(Unknown Source)
    at ilog/rules/engine/IlrContext.a(Z)Lilog/rules/engine/IlrParameterMap;(Unknown Source)
    ^-- Holding lock: ilog/rules/engine/IlrContext@0x1393f318[recursive]
    at ilog/rules/engine/IlrContext.execute()Lilog/rules/engine/IlrParameterMap;(Unknown Source)
    ^-- Holding lock: ilog/rules/engine/IlrContext@0x1393f318[recursive]
    at ilog/rules/bres/xu/spi/IlrEngineManager.execute()Ljava/util/Map;(Unknown Source)
    ^-- Holding lock: ilog/rules/engine/IlrContext@0x1393f318[thin lock]
    at ilog/rules/bres/xu/spi/IlrTransactionalEngineManager.execute()Ljava/util/Map;(Unknown Source)
    ^-- Holding lock: ilog/rules/bres/xu/spi/IlrTransactionalEngineManager@0x13897c90[thin lock]
    at ilog/rules/bres/xu/spi/IlrManagedXUConnection.contextExecute(Lilog/rules/bres/xu/cci/IlrXUConnection;)Ljava/util/HashMap;(Unknown Source)
    at ilog/rules/bres/xu/cci/IlrXUConnection.contextExecute()Ljava/util/HashMap;(Unknown Source)
    at ilog/rules/bres/xu/cci/IlrXUInteraction.contextExecute(Ljavax/resource/cci/Record;Ljavax/resource/cci/Record;)Z(Unknown Source)[inlined]
    at ilog/rules/bres/xu/cci/IlrXUInteraction.dispatchExecution(Ljava/lang/String;Ljavax/resource/cci/InteractionSpec;Ljavax/resource/cci/Record;Ljavax/resource/cci/Record;)Z(Unknown Source)[inlined]
    at ilog/rules/bres/xu/cci/IlrXUInteraction.execute(Ljavax/resource/cci/InteractionSpec;Ljavax/resource/cci/Record;Ljavax/resource/cci/Record;)Z(Unknown Source)[inlined]
    at ilog/rules/bres/xu/cci/IlrXUInteraction.execute(Ljavax/resource/cci/InteractionSpec;Ljavax/resource/cci/Record;)Ljavax/resource/cci/Record;(Unknown Source)[optimized]
    at ilog/rules/bres/session/IlrRuleSessionExecuteImpl.executeInteraction(Ljavax/resource/cci/Interaction;Ljavax/resource/cci/Record;Lilog/rules/bres/session/IlrRuleSessionExecuteImpl$Warnings;)Ljavax/resource/cci/Record;(Unknown Source)
    at ilog/rules/bres/session/IlrRuleSessionExecuteImpl.execute(Ljavax/resource/cci/ConnectionFactory;Ljava/lang/String;Ljava/util/Map;Lilog/rules/bres/session/IlrRuleSessionExecuteImpl$Warnings;ZZLjavax/resource/cci/Interaction;)Ljava/util/HashMap;(Unknown Source)
    at ilog/rules/bres/session/IlrRuleSessionExecuteImpl.executeStateless(Ljavax/resource/cci/ConnectionFactory;Ljavax/resource/cci/Connection;Ljavax/resource/cci/Interaction;Lilog/rules/bres/session/IlrSessionRequest;Lilog/rules/bres/session/IlrRuleSessionExecuteImpl$Warnings;)Lilog/rules/bres/session/IlrSessionResponse;(Unknown Source)
    at ilog/rules/bres/session/ejb/IlrStatelessRuleSessionEJB.executeRules(Lilog/rules/bres/session/IlrSessionRequest;)Lilog/rules/bres/session/IlrSessionResponse;(Unknown Source)
    at ilog/rules/bres/session/ejb/IlrStatelessRuleSessionEJB_ugt9ms_ELOImpl.executeRules(IlrStatelessRuleSessionEJB_ugt9ms_ELOImpl.java:145)
    at ilog/rules/bres/session/ejb/IlrGateLocal.executeRules(Lilog/rules/bres/session/IlrSessionRequest;)Lilog/rules/bres/session/IlrSessionResponse;(Unknown Source)
    at com/myapp/rules/jrules/JRuleSession.executeRules(JRuleSession.java:79)
    at com/myapp/core/RuleInvoker.invokeRule(RuleInvoker.java:52)
    at com/myapp/core/statemachine/StateMachine.executeRule(StateMachine.java:143)
    at com/myapp/core/statemachine/StateMachine.doTransition(StateMachine.java:109)
    at com/myapp/core/statemachine/StateMachine.doStateMachineTransitions(StateMachine.java:87)
    at com/myapp/core/statemachine/StateMachine.doTransition(StateMachine.java:64)
    at com/myapp/core/messagehandler/tes/TesMessageHandler.doTESMessageProcessing(TesMessageHandler.java:263)
    at com/myapp/core/messagehandler/tes/TesMessageHandler.tesProcessing(TesMessageHandler.java:134)
    at com/myapp/core/messagehandler/tes/TesMessageHandler.process(TesMessageHandler.java:112)
    at com/myapp/core/FullReSequenceMessageProcessor.doStateMachine(FullReSequenceMessageProcessor.java:173)
    at com/myapp/core/FullReSequenceMessageProcessor.processMessage(FullReSequenceMessageProcessor.java:333)
    at com/myapp/core/MessageProcessorMDB.onMessage(MessageProcessorMDB.java:81)
    at weblogic/ejb/container/internal/MDListener.execute(MDListener.java:429)[inlined]
    at weblogic/ejb/container/internal/MDListener.transactionalOnMessage(MDListener.java:335)[inlined]
    at weblogic/ejb/container/internal/ContinuousJMSMessagePoller.processOneMessage(ContinuousJMSMessagePoller.java:129)[optimized]
    at weblogic/ejb/container/internal/JMSMessagePoller.pollContinuously(JMSMessagePoller.java:394)
    at weblogic/ejb/container/internal/ContinuousJMSMessagePoller.pollForChild(ContinuousJMSMessagePoller.java:185)
    at weblogic/ejb/container/internal/JMSMessagePoller.run(JMSMessagePoller.java:530)
    at java/lang/Thread.run(Thread.java:595)
    at jrockit/vm/RNI.c2java(IIII)V(Native Method)
    -- end of trace
    Edited by: user1631781 on Jun 9, 2010 10:05 AM

    My understanding was that WebLogic by default configuration would pull n messages at a time from the a foreign >jms server (via JMS connection poller) ; and process the n messages using the same MDB in n different >transactions. Is this correct? Its possible for MDB to process more than one message in a transaction using a weblogic specific feature called MDB Transaction batching.This depends on the max-messages-in-transactions descriptor in weblogic-ejb-jar.xml. This controls mdb transaction batch size.
    http://download.oracle.com/docs/cd/E15051_01/wls/docs103/ejb/message_beans.html#wp1161543
    In your case the thread seems to be stuck at the application code level. I doubt if it is related to transactions.
    at java/util/HashMap.get(HashMap.java:344)[optimized]
    at org/jboss/cache/UnversionedNode.getDirect(UnversionedNode.java:203)[inlined]

  • Debugger questions

    In the docs I saw:
    If you let your mouse pointer rest over a variable or function in an Editor
    tab, the result of evaluating that variable or function is displayed as a
    help tip.
    and
    You can turn off the display of help tips using the Display JavaScript
    variables and Enable UI help tips checkboxes on the Help Options page of
    the Preferences dialog.
    I can't get either help tips or the var display to work on XP whether the script
    is running or not. Is this a known problem or is there a magic incantation I am
    missing? The databrowser is working just fine, though, so I'm not completely blind.
    ciao,
    -X

    [email protected] wrote:
    > Just got confirmation. It's a bug.
    >
    > I dunno when a fix can be incorporated. But the right folks know.
    >
    > Sorry!
    >
    > Bob
    > Adobe Workflow Scripting
    Thanks for the report.

  • Creating own macros for adb

    Hi,
    I was looking at the 'proc' adb macro and it is basically printing
    all the process information offsetting from the process base address.
    Question is how does the macro know what info is at what offset ?
    Ofcourse /usr/include/sys/proc.h would be one source.
    How do you find out what information is at what offset ? eg., how does the proc macro know that ppid is at a particular offset ?
    I am trying to find information to write a tool which will let one navigate all kernel data structures logically (something line 'analyse/system' tool found on VMS).
    Tried adbgen, but that still needs offset info.
    Thanks,
    -A

    Hi - I believe adbgen will figure out the offsets within the structures. The .adb file contains the necessary includes and then just takes information on headers and the field to be printed (and what type to print the value as).
    Something you may want to consider is using mdb or the Modular DeBugger. It is new in Solaris 7/8 and allows you to run you own dynamically loaded code from the debugger. Since the modules you can run are written in C you can make decisions and print out information far more complex than adb.
    Refer to the Solaris Modular Debugger Guide on docs.sun.com if this is something that interests you.
    Alan
    Sun Developer Technical Support
    http://www.sun.com/developers/support

  • Distributed JDBC/JMS transaction commit order

    I am using WLS 10.3.0. I have an app with container-managed EJBs which participate in distributed transactions using XA drivers for two resources, (1) a jdbc connection to Oracle database, and (2) WebLogic JMS server. In a typical EJB call, I am writing a record to the database and sending a message to a local queue which is being consumed by a MDB. My question is how can I guarantee that by the time the MDB receives the JMS message, the record will be guaranteed to have been committed in the database. It appears that occasionally the record is not yet there. Is there a way to force the jdbc commit to happen before the JMS message gets consumed? I know there is a commit_point_strength parameter that determines commit order for the database resource, but I don't see such a concept for JMS...

    "The Default Time-to-Deliver attribute for XAConnectionFactory for the Weblogic JMS connection queue, is a minimum interval from when the message is SENT, to when it is available to be processed. What is really needed is a delay from COMMIT time -- not from the sent time."
    <jay>
    Not entirely true. Delay is not from when message is “SENT, Default Time-To-Deliver is delay at within JMS subsystem before it delivers message to consumer. It means that "Send" thread will not block for this delay and "Send" side executes no different whether there is "Time-to-Deliver" configured or not.
    </jay>
    "For example, imagine a distributed transaction does a JMS send, followed by a query that takes 10 seconds, followed by a commit. If Default Time-to-Deliver is set to 5 seconds, it will be completly ignored, since the 10 seconds from the send to the commit is a larger interval. So at commit it is still very possible that the MDB will receive the message before the database transaction is committed."
    <jay>
    This is not true also. JMS message will be available for delivery only after distributed transaction commits and more specifically "commit" part of the JMS resource completes - clock for "message delivery delay" will not start until distributed transaction is committed. Considering transaction will not commit until slow running query completes execution above scenario will not cause “Default Time-to-Deliver” workaround to fail.
    Slow execution of the XA.commit() request from TM (Weblogic) to database may cause concern , however considering that TM (WebLogic) receive response of the XA.prepare() from all participating resources before XA.commit(), commit should execute with delay not more than few milliseconds and chances are negligible that proposed workaround will fail.
    </jay>
    "The bottom line, is that this parameter is not an effective way to control the race condition unless the JMS send is always performed as the last action in a distributed transaction.
    For this reason we have gone with inserting a small configurable sleep at the start of the onMessage() methods in the MDB. Not a very elegant solution, but the one ne that works reliably."
    <jay>
    I think "Default Time-to-Deliver" is no less effective or no less reliable solution than placing sleep() in onMessage(), however it is more cleaner solution because it uses application server built in feature instead of updating code in onMessage().
    </jay>
    -jayesh@yagna

  • Netscape Directory Server core dumps

    Hi,
    I have NDS version 5.1 running on Solaris 10. My software is querying the LDAP at around 10-15 requests/sec. The LDAP memory is runnig at around 50M. (I have around 900 entries in the LDAP tree). At some random instance of time, the LDAP memory shoots up from 50M to 3.2 GB when it goes out of memory and then restarts. My software has a LDAP connection pool to it and one of the threads goes OutOfmemory after the error.
    The LDAP does a core dump during the process. From the analysis of the core dump, it seems that it is trying to access some memory which is not part of the LDAP process map.
    bash-3.00$ mdb core
    mdb: failed to initialize /lib/libc_db.so.1: libthread_db call failed unexpectedly
    mdb: warning: debugger will only be able to examine raw LWPs
    Loading modules: [ libc.so.1 libuutil.so.1 ld.so.1 ]
    ::stacklibc_psr.so.1`memcpy+0x234(87c00038, 6b646174, 74776f6a, 8, 6b646174, 0)
    libslapd.so`slapi_dup_control+0x94(53db678, 2ce38f8, fc93ff2c, 0, 2ce38f8,2ce38f8)
    0x2f3b4(7e55c80, 2f30150, 2ce6bb8, 4c7fde8, 2f30150, ffffffff)
    0xfef17d18(2f60164, fc940000, 0, 0, fef17c74, 1)
    0xff2c8a20(0, 0, 0, 0, 0, 0)
    ::statusdebugging core file of ns-slapd (32-bit) from XXXXXX
    initial argv:XXXXXXXX
    threading model: multi-threaded using native lwps
    status: process terminated by SIGSEGV (Segmentation Fault)
    >
    The failure is at address 0xfee8063c.
    0xfee8063c::dislibc_psr.so.1`memcpy+0x20c: 0x2480012
    libc_psr.so.1`memcpy+0x210: nop
    libc_psr.so.1`memcpy+0x214: ldub [%i1], %o2
    libc_psr.so.1`memcpy+0x218: stb %o2, [%i0]
    libc_psr.so.1`memcpy+0x21c: add %i1, 1, %i1
    libc_psr.so.1`memcpy+0x220: subcc %i3, 1, %i3
    libc_psr.so.1`memcpy+0x224: 0x184ffffc
    libc_psr.so.1`memcpy+0x228: add %i0, 1, %i0
    libc_psr.so.1`memcpy+0x22c: ba +0x60 <libc_psr.so.1`memcpy+0x28c>
    libc_psr.so.1`memcpy+0x230: nop
    libc_psr.so.1`memcpy+0x234: ld [%i1], %o2
    libc_psr.so.1`memcpy+0x238: st %o2, [%i0]
    libc_psr.so.1`memcpy+0x23c: add %i1, 4, %i1
    libc_psr.so.1`memcpy+0x240: subcc %i3, 4, %i3
    // Looking for register i1
    ::regs%g0 = 0x00000000 %l0 = 0x87c00038
    %g1 = 0xff37c840 libsh.so`_shi_sysAllocPool+0xd4 %l1 = 0xff16c2bc
    %g2 = 0x00000000 %l2 = 0x07970778
    %g3 = 0x0000036c %l3 = 0x05410000
    %g4 = 0x00000001 %l4 = 0xff165a34
    %g5 = 0x87c00038 %l5 = 0x00000000
    %g6 = 0x00000000 %l6 = 0x01000000
    %g7 = 0xfd06ca00 %l7 = 0x00000004
    %o0 = 0x87c00038 %i0 = 0x87c00038
    %o1 = 0x74776f72 %i1 = 0x6b646174
    %o2 = 0xefe4617c %i2 = 0x74776f6a
    %o3 = 0x00000002 %i3 = 0x00000008
    %o4 = 0x00000002 %i4 = 0x6b646174
    %o5 = 0x053d9c28 %i5 = 0x00000000
    %o6 = 0xfc93fe00 %i6 = 0xfc93fe60
    %o7 = 0xff0c0c44 libslapd.so`slapi_ch_malloc+0x64 %i7 = 0xff0e8e78
    libslapd.so`slapi_dup_control+0x94
    %psr = 0xfe401004 impl=0xf ver=0xe icc=nZvc
    ec=0 ef=4096 pil=0 s=0 ps=0 et=0 cwp=0x4
    %y = 0x00000002
    %pc = 0xfee8063c libc_psr.so.1`memcpy+0x234
    %npc = 0xfee80640 libc_psr.so.1`memcpy+0x238
    %sp = 0xfc93fe00
    0x6b646174::dismdb: failed to read instruction at 6b646174: no mapping for address
    >
    The register "i1"'s content was memory address 0x6b646174 which is not part of process address space.
    Has anyone experienced similar problem before? I was trying to find the same in the forum but without any luck. This problem is happening quiet regularly.

    Seeems like content of register i1 got missed.. here is the content..
    %l2 = 0x07970778
    %l3 = 0x05410000
    %l4 = 0xff165a34
    %l5 = 0x00000000
    %l6 = 0x01000000
    %l7 = 0x00000004
    %i0 = 0x87c00038
    %i1 = 0x6b646174
    %i2 = 0x74776f6a
    %i3 = 0x00000008
    %i4 = 0x6b646174
    %i5 = 0x00000000
    %i6 = 0xfc93fe60

  • A question in flash Cs5 debugger

    hi
       my code :
              var  o:Object={a:int,b:int};
              o.a=3;
              o.b=4;
        in cs5 debugger  " var pannel"   o| Object(@1bf1bc9)
       my question is " what is the mean of @1bf1bc9 here ??"

    I don't know for sure, but I think that flash doesn't actually keep the names we give things and changes them internally into various numbers. I'm using CS4 and I see numbers after all kinds of things including the main timeline, the currentLabels array, loaderInfo, everything.

  • MDB and MessageConsumer Queue Questions

    (1) Does a MessageConsumer object, when called on its onMessage() method, provide the same JMS queue processing as a Message Driven Bean (MDB) called on it's onMessage() method? That is, the message remains on the queue until the onMessage() method completes in both cases.
    (2) Does the same apply to a MessageConsumer's receive() method? That is, the message remains on the queue until the next receive is called?
    Thanks

    Unfortunately, MDBs do not currently support running on a separate queue. They run on
    the default queue.
    -- Rob
    Nicole wrote:
    Hi Folks,
    as we got problems on thread deadlocks using JMS, we decided to define our own thread
    queue to be used by our application. In the documentation it is described, that you
    need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
    you connect your EJB to the named thread queue, which you will need to add to your
    config.xml.
    What I could find out was, that this works fine for stateful or stateless session
    beans, but it looks like message driven beans do ignore this option.
    So here are my questions:
    Which thread queue is used by message driven beans?
    How can I change the thread queue?
    Many thanks,
    Nicole

Maybe you are looking for