Resource Manager problems

Hi All,
I've tried to create plan using :
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => 'ESERVICE_RSRC_PLAN');
Without specyfying groups, so i've got an error.
Next when i've tried to create plan again using :
execute DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => 'ESERVICE_RSRC_PLAN',CONSUMER_GROUP1 => 'SYS_GROUP', GROUP1_CPU => 100,
CONSUMER_GROUP2 => 'OTHER_GROUPS', GROUP2_CPU => 100);
I've got an error ora-29364 saying that :
'plan directive ESERVICE_RSRC_PLAN, SYS_GROUP already exists'
So when i've tried to delete directive using :
EXECUTE DBMS_RESOURCE_MANAGER.DELETE_PLAN_DIRECTIVE (plan => 'ESERVICE_RSRC_PLAN',group_or_subplan => 'SYS_GROUP');
I've got an error :
ORA-29358: resource plan ESERVICE_RSRC_PLAN does not exist
Appreciate for any help.
Best Regards Arkadiusz Masny

You have two issues,
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN will create a simple resource manager plan with new groups you have to use new group names for it to work.
The total CPU at each level must total 100, to use a simple plan the following will work..
execute DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN
(SIMPLE_PLAN => 'ESERVICE_RSRC_PLAN',
CONSUMER_GROUP1 => 'NEW_GROUP_1', GROUP1_CPU => 90,
CONSUMER_GROUP2 => 'NEW_GROUP_2', GROUP2_CPU => 10);
to use the existing group the follwoing SQL should work (NB I copied and pasted out of dbconsole, trying to manage this stuff using SQL is too much typing...)
BEGIN
dbms_resource_manager.clear_pending_area();
dbms_resource_manager.create_pending_area();
dbms_resource_manager.create_plan( 'ESERVICE_RSRC_PLAN', '');
dbms_resource_manager.create_plan_directive(
plan => 'ESERVICE_RSRC_PLAN2',
group_or_subplan => 'OTHER_GROUPS',
comment => '',
cpu_p1 => 10, cpu_p2 => NULL, cpu_p3 => NULL, cpu_p4 => NULL,
cpu_p5 => NULL, cpu_p6 => NULL, cpu_p7 => NULL, cpu_p8 => NULL,
parallel_degree_limit_p1 => NULL,
active_sess_pool_p1 => NULL,
queueing_p1 => NULL,
switch_group => '',
switch_time => NULL,
switch_estimate => false,
max_est_exec_time => NULL,
undo_pool => NULL,
max_idle_time => NULL,
max_idle_blocker_time => NULL,
switch_time_in_call => NULL
dbms_resource_manager.create_plan_directive(
plan => 'ESERVICE_RSRC_PLAN2',
group_or_subplan => 'SYS_GROUP',
comment => '',
cpu_p1 => 90, cpu_p2 => NULL, cpu_p3 => NULL, cpu_p4 => NULL,
cpu_p5 => NULL, cpu_p6 => NULL, cpu_p7 => NULL, cpu_p8 => NULL,
parallel_degree_limit_p1 => NULL,
active_sess_pool_p1 => NULL,
queueing_p1 => NULL,
switch_group => '',
switch_time => NULL,
switch_estimate => false,
max_est_exec_time => NULL,
undo_pool => NULL,
max_idle_time => NULL,
max_idle_blocker_time => NULL,
switch_time_in_call => NULL
dbms_resource_manager.submit_pending_area();
END;

Similar Messages

  • VXI Resource manager problem

    I have the following configuration:
    VXI-PCI system (National Instrument 777119-32 VXI-PCI 8015 interface kit +
    National Instrument 777178-01 mainframe extender.)
    One PC.
    Two VXI cages.
    In the first VXI cage at slot 0, I installed NI zero slot controller,
    configured to logical address 1.
    In the second VXI cage at slot 0, I installed NI zero slot controller,
    configured to logical address 2.
    The VXI cages are chained using MXI-2/M3 cable.
    In the first VXI cage at slot 1, I installed a RACAL Instrument (1260-35
    with option OPT-01T) that also needs a logical address, configured to
    logical address 3.
    In the second VXI cage at slot 1, I installed a RACAL Instrument device
    (1260-45 with option OPT-01T) that also needs a logical addre
    ss, configured
    to logical address 4.
    Running the Resource manager with only one RACAL device in either cage -
    result OK (logical addresses 1,2,3 or 1,2,4).
    Running a full system result - FAIL with the message "The device at logical
    address 3 did not respond to the read protocols command.
    The same problem appears if I configure the logical address of the OPT-01T
    to 255 (auto assign logical address).
    Please advice.
    Thanks
    Eli Nachumzon
    ATE Development
    Engineering Dept.
    ADC teledata
    Tel: +972-9-9591453
    Fax: +972-9-9591805
    E-mail: [email protected]

    Eli-
    I just noticed this unanswered question. I am guessing you've gotten your answer from another source by now, but in case anyone else has similar issues, I recommend our Logical Address Wizard, which helps configure multi-chassis MXI systems. Your case illustrates a common mistake when assigning LA's; having your two VXI-MXI-2's at LA 1 and 2 will not work. According to the LA Wizard, a combination like LA 4 (containing an instrument at LA 5) and LA 6 (containing an instrument at LA 7) would work.
    -Scot

  • File Server Resource Manager will not load WMI Objects on Windows 8.0/8.1 Preview with Hyper-V and Server Tools Loaded

    Hi Folks,
    I have a problem getting "File Server Resource Manager" to start properly because WMI objects are not loading??? I don't understand this at all because I am able to access them with other Apps, etc. I have been over my Services list as well but
    have not yet discovered which Service turns on/off "File Server Resource Manager". I have looked in Windows\System32\ and I can not find SrmSvc. I found other Srm's there though. I also found the FSRM Snapin which generates the Figure below but I
    can not find it in the WMI Browser. I believe the Firewall is OKAY since I have been over that thoroughly. I do have the Server Tools Installed for Windows 8.0 or Windows 8.1 Clients as well as the Windows Updates applied, which is where I got "File Server
    Resource Manager" in the first place. I have had WMI and Powershell 3.0 Package, installed since Windows 7 but I run a repair on them anyway.
    I have read through "File Server Resource Manager could not load WMI objects on Windows Server 2012
    Article ID: 2831687" but since I don't seem to have SrmSvc the solution doesn't help me. I haven't been able to find a similar one for the Windows Client.
    If there is anything you could share on this problem I would be much obliged.
    Thanks again,
    Crysta
    PhotM Phantom of the Mobile

    Hello,
    The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
    As the question is off topic here, I am moving it to the
    Where is the Forum... forum.
    Karl
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
    My Blog: Unlock PowerShell
    My Book:
    Windows PowerShell 2.0 Bible
    My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

  • RH8 hangs with 100% CPU when closing a topic. Resource Manager to blame?

    Please refer to the following thread for background information: http://forums.adobe.com/thread/734972?tstart=0
    I'm re-listing this issue, as it has rasied its ugly head again, and I've no resolution this time.
    Summary:
    The original issue was that RH8 would hang whenever I closed a topic for anywhere between 15-30 seconds before allowing me to interact with the application again. Attempting to interact with the GUI during this freeze would result in the 'Not Responding' message at the upper-left of the application window (suffice it to say I'm on a PC with Windows).
    After much investigation it was suggested to me that my profile may be corrupt, and in order to test this, another user should log on and see whether they experienced the same problem. As it is, they did not. So I had my Systems Admin recreate my domain profile, and everything worked just fine.
    ...until now.
    Last week we all upgraded from Windows XP to Windows 7 (32 bit). We also changed our anti-virus software. The awful hanging issue in RH has returned.
    We've attempted the solution from last time, by recreating my profile on the domain, to no avail. We have in fact gone to the extent of reformatting the hard drive and reinstalling Windows, the anti-virus software and RH8 (plus all available patches) from scratch. In case anyone is wondering, we've tried running RH without the antivirus installed, and when installed have also tried excluding the RH application folder and all my project folders, just in case it was the anti-virus software at fault. Regardless, the RH problem exists.
    I can't understand why I'm now having this problem. Truth be told, I never really understood why recreating my domain profile in the first place resolved the problem last time.
    However, I have now discovered something else...
    In my RH Resource Manager I have a few thousand images in the Image folder. Not much I can do about this - the applications I write Help for have many screens users can access, and I write the Help for half a dozen applications. When I delete the contents of the images folder within the Resources Manager, RH works perfectly - no hanging whatsoever. As soon as I import the images into this folder again, the hanging is back. I have tested this a few times now, and have rebooted and had another user log on to confirm, and it happens every time. I'm dumbfounded of course, particularly because the same set of images has been sitting in the Resource Manager for months (since my original post about this issue, last year), and RH has been working perfectly.
    I've also tried Peter Grainge's suggestion to create an empty BaseCSS_res.dll file (http://www.grainge.org/pages/authoring/rh8/using_rh8.htm), but as I've installed all the RH8 updates, this shouldn't be an issue.
    I've also tried deleting the CPD file without success.
    Thanks in advance.

    It seems this has been resolved!
    Many thanks for all the suggestions. Peter ultimately forwarded the solution - something that he'd sourced from a rep at Adobe, as follows:
    Every file/folder change in the root folder of RH8 Resource Manager triggers a rescan of all the sub-folder/files. That is why in case of thousand image it will take time. Like xxxx said we may ask user for root folder, it should not be project folder or frequently changing folder.
    Probably he is using the default path given in the root folder and RoboHelp changes a temporary css file in that folder very frequently, in fact with every topic close.
    That is causing the slowness and it should be easy to reproduce in the default scenario. This is RH8 only issue.
    So, to fix my issue:
    Open the Resource Manager Pod.
    Click the Add/Edit Categories icon. The Add/Edit Categories window appears.
    Within this window, change the 'Root Folder' path to something other than the default. In my case, I create a new folder on my root hard drive, outside of the Robohelp folder, just to be sure.
    So far this is working perfectly - no 'hanging'. I'll keep an eye on it.
    I love the comment "This is RH8 only issue."
    Oh?! Is it? Was it fixed in a patch, Adobe? Please don't tell me that it was fixed in RH9, because there's no way known I should have to pay for an upgrade to resolve something that certainly looks like a bug. As happy and grateful I am to have this resolved, it has cost me a week's work.

  • MQSeries as a Transactional Resource Manager with Weblogic Server

              I am trying to setup the example given in the BEA white paper:
              Using MQSeries as a Transactional Resource Manager with Weblogic Server.
              Version 1.
              October 25, 2001.
              I followed the instructions given in the documents, but when i run client program
              >java MQClient t3://localhost:7001 "MQSeries test"
              I received the following exception below. Does anyone how what is the reason for
              this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
              6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
              for java and the MQSeries classes for Java Message Service on the weblogic
              server machine.
              sending: "MQSEries test"
              Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
              sted exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.rmi.ServerError: A error occurred the server; nested exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              ; nested exception is:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              at java.lang.System.loadLibrary(System.java:820)
              at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              at java.security.AccessController.doPrivileged(Native Method)
              at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
              at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
              at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
              at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
              at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              --------------- nested within: ------------------
              weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
              [java.rmi.ServerError: A error occurred the server; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.rmi.ServerError: A error occurred the server; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                      at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                      at java.lang.System.loadLibrary(System.java:820)
                      at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                      at java.security.AccessController.doPrivileged(Native Method)
                      at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                      at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                      at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                      at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                      at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
                      at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
                      at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
                      at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                      at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                      at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                      at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                      at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                      at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                      at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
                      at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                      at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                      at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                      at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
                      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              ; nested exception is:
                      java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              Start server side stack trace:
              java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                      at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                      at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                      at java.lang.System.loadLibrary(System.java:820)
                      at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                      at java.security.AccessController.doPrivileged(Native Method)
                      at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                      at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                      at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                      at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              149)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                      at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                      at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              a:80)
                      at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              ctionManager.java:150)
                      at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              a:666)
                      at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                      at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                      at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                      at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                      at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                      at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                      at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                      at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              AQueueConnectionFactory.java:53)
                      at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                      at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                      at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                      at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                      at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              a:267)
                      at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:22)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
              at $Proxy1.bridgeWLS2MQS(Unknown Source)
              at MQClient.main(MQClient.java:54)
              

    The point is that over TCPIP the MQ XA connection factory is not available.
              The MQ shared memory/JNI driver is required to access it, which limits
              access to those processes that are on the same box as the MQ q manager.
              This is an MQ series limitation.
              Douglas WF Acheson wrote:
              > Hello,
              >
              > If memory server me correct, default connection to MQ Series is through
              > JNI calls and shared memory. You have to change the protocol to TCPIP when
              > connection to the queue manager on another box (do not know much about XA
              > with MQ Series); that is when you connect to MQ Series vi JMS on another
              > box you must do something like the following:
              >
              > qcf = new MQQueueConnectionFactory() ;
              > qcf.setHostName(hostName) ;
              > qcf.setPort(port) ;
              > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
              > qcf.setQueueManager(qManagerName) ;
              >
              > Then when you create you queues, sesions etc. you are point at the correct Q
              > manager.
              >
              > Hope this helps ...
              >
              > Douglas WF Acheson
              >
              > "Raja Mukherjee" <[email protected]> wrote in message
              > news:[email protected]...
              > > On a closer look at the original post (sorry for missing that, it was
              > early
              > > in the morning), you would not be able to use XA if your QM and WLS are in
              > > different boxes. Check on this newsgroup, there are several posts on this
              > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
              > on
              > > the sames box. This is a MQSeries limitation not WLS.
              > >
              > > .raja
              > >
              > >
              > > "ibrahim Nehme" <[email protected]> wrote in message
              > > news:[email protected]...
              > > >
              > > > I am trying to setup the example given in the BEA white paper:
              > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
              > > > Version 1.
              > > > October 25, 2001.
              > > > I followed the instructions given in the documents, but when i run
              > client
              > > program
              > > >
              > > > >java MQClient t3://localhost:7001 "MQSeries test"
              > > > I received the following exception below. Does anyone how what is the
              > > reason for
              > > >
              > > > this exception(s) and how i can solve the problem? My MQSeries Server
              > and
              > > Weblogic
              > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
              > > classes
              > > > for java and the MQSeries classes for Java Message Service on the
              > weblogic
              > > > server machine.
              > > > ---------------------------------------
              > > > sending: "MQSEries test"
              > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
              > > server; ne
              > > > sted exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.rmi.ServerError: A error occurred the server; nested exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > > ; nested exception is:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > >
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > > at java.lang.System.loadLibrary(System.java:820)
              > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > > at java.security.AccessController.doPrivileged(Native Method)
              > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > > at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > > at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > > at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > > at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > > at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > > at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > > at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > > at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > > at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > > at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > > at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > > at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > > at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End server side stack trace
              > > >
              > > > <<no stack trace available>>
              > > > --------------- nested within: ------------------
              > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
              > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.rmi.ServerError: A error occurred the server; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > >         at java.lang.System.loadLibrary(System.java:820)
              > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > >         at java.security.AccessController.doPrivileged(Native Method)
              > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > >         at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > >         at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > >         at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > >         at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > >         at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > >         at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > >         at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > >         at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > >         at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End  server side stack trace
              > > > ; nested exception is:
              > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >
              > > > Start server side stack trace:
              > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
              > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
              > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
              > > >         at java.lang.System.loadLibrary(System.java:820)
              > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
              > > >         at java.security.AccessController.doPrivileged(Native Method)
              > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
              > > >         at
              > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
              > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
              > > >         at
              > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
              > > > 149)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
              > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
              > > >         at
              > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
              > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
              > > >         at
              > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
              > > > a:80)
              > > >         at
              > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
              > > > ctionManager.java:150)
              > > >         at
              > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
              > > > a:666)
              > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
              > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
              > > >         at
              > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
              > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
              > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
              > > >         at
              > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
              > > > )
              > > >         at
              > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
              > > > AQueueConnectionFactory.java:53)
              > > >         at
              > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
              > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
              > > >         at
              > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
              > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
              > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
              > > >         at
              > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
              > > > a:267)
              > > >         at
              > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > > > java:22)
              > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > End  server side stack trace
              > > > ]
              > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
              > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
              > > > at MQClient.main(MQClient.java:54)
              > >
              > >
              

  • Start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager ...

    Hello Group,
    We are using Weblogic Version 9.2.3 & facing some problem related to 'jackrabbit' not available. I feel we are facing problem similar to the one mentioned in following link
    Re: What causes XAER_RMFAIL : Resource manager is unavailable / unregistered
    Following above post, we tried increased the Initial Capacity of this 'jackrabbit' Resource Adapter to 50. Initially it was 1. Although this doesn't change anything. Although it works fine for a few hours but seems like after server has run for a few hours and served some requests it starts showing this exception.
    Following is our weblogic-ra.xml file.
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <native-libdir></native-libdir>
    <jndi-name>repository</jndi-name>
    <enable-access-outside-app>true</enable-access-outside-app>
    <enable-global-access-to-classes>true</enable-global-access-to-classes>
    <security></security>
    <outbound-resource-adapter>
    <default-connection-properties>
    <pool-params></pool-params>
    <logging></logging>
    </default-connection-properties>
    <connection-definition-group>
    <connection-factory-interface>javax.jcr.Repository</connection-factory-interface>
    <default-connection-properties>
    <pool-params>
         <initial-capacity>50</initial-capacity>
         <max-capacity>100</max-capacity>
    </pool-params>
    <logging></logging>
    <properties>
    <property>
    <name>HomeDir</name>
    <value>jackrabbit-preferences</value>
    </property>
    <property>
    <name>ConfigFile</name>
    <value>jackrabbit-preferences/repository.xml</value>
    </property>
    </properties>
    </default-connection-properties>
    <connection-instance>
    <jndi-name>jackrabbit</jndi-name>
    <connection-properties>
    <pool-params>
         <initial-capacity>50</initial-capacity>
         <max-capacity>250</max-capacity>
    </pool-params>
    <logging></logging>
    <properties>
    <property>
    <name>HomeDir</name>
    <value>jackrabbit-preferences</value>
    </property>
    </properties>
    </connection-properties>
    </connection-instance>
    </connection-definition-group>
    </outbound-resource-adapter>
    </weblogic-connector>
    Also please find below the exception that we see in the logs.
    Caused by: ag.mycompany1.workflow.runtime.DocumentManagementServiceException: null: javax.jcr.RepositoryException: start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager is unavailable
    javax.transaction.xa.XAException: Internal error: XAResource 'jackrabbit' is unavailable
         at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:1143)
         at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:685)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1181)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
         at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
         at weblogic.connector.outbound.ConnectionHandlerBaseImpl.prepareHandle(ConnectionHandlerBaseImpl.java:670)
         at weblogic.connector.outbound.ConnectionHandlerBaseImpl.createConnectionHandle(ConnectionHandlerBaseImpl.java:361)
         at weblogic.connector.outbound.ConnectionInfo.createConnectionHandle(ConnectionInfo.java:411)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:308)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:98)
         at org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:89)
         at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactory.createSession(JcrSessionFactory.java:38)
         at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactoryUtils.getSession(JcrSessionFactoryUtils.java:72)
         at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactory.getSession(JcrSessionFactory.java:33)
         at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.doWithJcrVfs(AbstractJcrDocumentRepositoryService.java:537)
         at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.doWithJcrVfs(AbstractJcrDocumentRepositoryService.java:564)
         at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.retrieveFileContent(AbstractJcrDocumentRepositoryService.java:186)
         at com.mycompany2.infinity.bpm.vfs.impl.AbstractDocumentRepositoryServiceImpl.retrieveFileContent(AbstractDocumentRepositoryServiceImpl.java:46)
         at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl$5.withVfs(DocumentManagementServiceImpl.java:112)
         at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl.adaptVfsCall(DocumentManagementServiceImpl.java:417)
         at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl.retrieveDocumentContent(DocumentManagementServiceImpl.java:108)
         at sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at ag.mycompany1.workflow.runtime.beans.interceptors.CallingInterceptor.invoke(CallingInterceptor.java:18)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.POJOExceptionHandler.invoke(POJOExceptionHandler.java:23)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.GuardingInterceptor.invoke(GuardingInterceptor.java:87)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.AbstractLoginInterceptor.performCall(AbstractLoginInterceptor.java:142)
         at ag.mycompany1.workflow.runtime.beans.interceptors.AbstractLoginInterceptor.invoke(AbstractLoginInterceptor.java:80)
         at ag.mycompany1.workflow.runtime.spring.SpringBeanLoginInterceptor.invoke(SpringBeanLoginInterceptor.java:58)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.spring.SpringSessionInterceptor$1.doInConnection(SpringSessionInterceptor.java:104)
         at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:342)
         at ag.mycompany1.workflow.runtime.spring.SpringSessionInterceptor.invoke(SpringSessionInterceptor.java:52)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.spring.SpringConfigurationInterceptor.invoke(SpringConfigurationInterceptor.java:94)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.PropertyLayerProviderInterceptor.invoke(PropertyLayerProviderInterceptor.java:85)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.beans.interceptors.DebugInterceptor.invoke(DebugInterceptor.java:25)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.spring.SpringTxInterceptor$1.doInTransaction(SpringTxInterceptor.java:62)
         at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
         at ag.mycompany1.workflow.runtime.spring.SpringTxInterceptor.invoke(SpringTxInterceptor.java:47)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
         at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.execute(MethodInvocationImpl.java:55)
         at ag.mycompany1.workflow.runtime.beans.InvocationManager.invoke(InvocationManager.java:46)
         at $Proxy175.retrieveDocumentContent(Unknown Source)
         at ag.mycompany1.workflow.runtime.spring.DocumentManagementServiceBean.retrieveDocumentContent(DocumentManagementServiceBean.java:70)
         at sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at ag.mycompany1.workflow.runtime.spring.SpringServiceFactory$SpringServiceInvocationHandler.invoke(SpringServiceFactory.java:159)
         at $Proxy175.retrieveDocumentContent(Unknown Source)
         at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.loadPreferences(AbstractDocumentServicePreferencesManager.java:318)
         at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.getPreferences(AbstractDocumentServicePreferencesManager.java:269)
         at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.getPreferencesEditor(AbstractDocumentServicePreferencesManager.java:133)
         at com.mycompany2.infinity.bpm.bcc.configuration.TrafficLightViewPropertyProvider.<init>(TrafficLightViewPropertyProvider.java:85)
         at com.mycompany2.infinity.bpm.bcc.configuration.TrafficLightViewPropertyProvider.getInstance(TrafficLightViewPropertyProvider.java:103)
         at com.mycompany2.sims.workflow.tlv.TrafficLightDataLoader.persistData(TrafficLightDataLoader.java:129)
         at com.mycompany2.sims.workflow.tlv.TrafficLightDataLoader.loadData(TrafficLightDataLoader.java:73)
         at com.mycompany2.sims.workflow.SyncSettingsBean.reload(SyncSettingsBean.java:73)
         at com.mycompany2.sims.workflow.EnterpriseSettings.isWorklistConfigured(EnterpriseSettings.java:143)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.myfaces.el.PropertyResolverImpl.getProperty(PropertyResolverImpl.java:457)
         at org.apache.myfaces.el.PropertyResolverImpl.getValue(PropertyResolverImpl.java:85)
         at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:141)
         at com.sun.el.parser.AstValue.getValue(AstValue.java:96)
         at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:183)
         at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
         at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:233)
         at com.sun.facelets.tag.TagAttribute.getBoolean(TagAttribute.java:79)
         at com.sun.facelets.tag.jstl.core.ChooseWhenHandler.isTestTrue(ChooseWhenHandler.java:49)
         at com.sun.facelets.tag.jstl.core.ChooseHandler.apply(ChooseHandler.java:67)
         at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
         at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
         at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
         at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:109)
         at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
         at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
         at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
         at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524)
         at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
         at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
         at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
         at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
         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:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at ag.mycompany1.web.jsf.common.ExceptionFilter.doFilter(ExceptionFilter.java:45)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:290)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:250)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:207)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:161)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at ag.mycompany1.web.jsf.common.LoginFilter.doFilter(LoginFilter.java:250)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3251)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    : start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager is unavailable
    Any help in this regard is highly appreciated. Thanks.

    Hi,
    Can you please try increase the below MaxXACallMillis setting in Weblogic set 'Maximum Duration of XA Calls' to a bigger value
    MaxXACallMillis: Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain.
    http://docs.oracle.com/cd/E12840_01/wls/docs103/jta/trxcon.html
    The parameter is exposed through administration console: services --> jta --> advanced --> "Maximum Duration of XA Calls:"
    Check the below docs for more information
    WLS 10.3: Intermittent XA error: XAResource.XAER_RMERR (Doc ID 1118264.1)
    Hope it Helps

  • Oracle 10g database as Resource manager and heuristic transaction decision

    Hi,
    I have read in documents about distributed tarnsaction that resource manager like oracle databasecthat are involved in distributed transaction can take heuristic decision(unilateral decision) and can either rollback or commit the transaction associated with itself without having confirmation from the transaction manager.
    I want to know how a resource manager take this unilateral decision and can we set this as parameter either in resource manager or in application server.
    Thanks in advance

    Hi,
    Following are some links to documents.
    Handling Heuristic Completions
    http://edocs.bea.com/wls/docs81/ConsoleHelp/jta.html
    A heuristic completion (or heuristic decision) occurs when a resource makes a unilateral decision during the completion stage of a distributed transaction to commit or rollback updates. This can leave distributed data in an indeterminate state. Network failures or resource timeouts are possible causes for heuristic completion. In the event of an heuristic completion, one of the following heuristic outcome exceptions may be thrown:
    HeuristicRollback—one resource participating in a transaction decided to autonomously rollback its work, even though it agreed to prepare itself and wait for a commit decision. If the Transaction Manager decided to commit the transaction, the resource's heuristic rollback decision was incorrect, and might lead to an inconsistent outcome since other branches of the transaction were committed.
    HeuristicCommit—one resource participating in a transaction decided to autonomously commit its work, even though it agreed to prepare itself and wait for a commit decision. If the Transaction Manager decided to rollback the transaction, the resource's heuristic commit decision was incorrect, and might lead to an inconsistent outcome since other branches of the transaction were rolled back.
    HeuristicMixed—the Transaction Manager is aware that a transaction resulted in a mixed outcome, where some participating resources committed and some rolled back. The underlying cause was most likely heuristic rollback or heuristic commit decisions made by one or more of the participating resources.
    2. Understanding EJB Transaction
    http://www2.sys-con.com/itsg/virtualcd/Java/archives/0504/tyagi/index.html
    Unilateral Decisions
    The transaction manager allows certain heuristic or speculative decisions to be made based on the state of all participating resources in a transaction and the underlying two-phase commit protocol. A heuristic decision occurs when one of the resources in the transaction unilaterally decides to commit or roll back the transaction without permission from the transaction manager
    3. Oracle® Containers for J2EE
    http://download.oracle.com/docs/cd/B31017_01/web.1013/b28958.pdf
    Heuristics
    To achieve consensus, two-phase commit is a blocking protocol. This means that, if a coordinator fails before delivering the final phase messages, the participants must remain blocked, holding onto resources. Modern transaction systems add heuristics to two-phase commit, which allows such participants to make unilateral decisions about whether they will commit or rollback. If a participant makes a choice that turns out to be different from the one taken by other participants, then non-atomic behavior occurs.
    I got this problem while trying to do a distributed J2EE tarnsaction with two XA (one MQ and other Oracle 10g database XA) and one non-xa (oracle 10g database). According to above docs a resource manager can decide tarnsaction final state unilaterally and that can result in unatomic transaction.
    Do oracle also make such decision and if yes then on what ground it takes decision? Can we change this according to our requirement either always rollback/commit anywhere as parameter setting?
    Thanks

  • Oracle Resource Manager function with SAP BI7

    Hi,
    Have anyone considered or using Oracle Database Resource Manager (Oracle 10.2) feature for SAP BI application in your site? I dont see a single OSS hit on this feature.
    We have a SAP BI system that has few power users (who can run large STAR_TRANSFORMATION queries that analyzes large volume of data) and the main user community (our sales force > 3000+ users) who can run smaller queries of such nature or queries of different types.
    We want to see if there is any way we can control the resource utilization on the database server.
    Thanks in advance,
    Raj

    > Of course, this would require an additional specifications such as SERVICE in the TNS and Listener files.
    Yes - but I'm not sure if that would give the necessary effect. Once the statement reaches the database kernel engine, it gets processed, no matter if you limit the TNS/listener usage because TNS is no more involved when the statement reaches the OLAP engine.
    > In the BI environment, I'm thinking you need this db feature to control database resources when loads and reports overlaps or even several small and large queries run concurrently despite however many app server a system has, all these come to the database.
    I think SAPs answer is: Buy a bigger box (or use RAC to distribute the load)
    > The big question is whether SAP would support such a setup.
    The feature is not listed explicitly in note 105047 - Support for Oracle functions in the SAP environment. I'd make a call at BC-DB-ORA and ask what they think about that.
    I understand your problem very well but I doubt, that there's an easy way of accomplishing this with standard tools.
    Markus

  • XAER_RMFAIL : Resource manager is unavailable

    Weblogic 8.1, I don't recall which service pack, sp10? Maybe?
    Anyway, here's the relevant stack trace. We had a strange WLS implosion last
    night that we're tracking down. We saw these when our code was trying to get
    a connection out of the datapool.
    <Mar 1, 2006 10:09:12 PM PST> <Warning> <JTA> <BEA-110030> <XA resource
    [weblogic.jdbc.wrapper.JTSXAResourceImpl] has not responded in the last 120
    second(s).>
    01 Mar 2006 22:09:21,652 WARN com.pfizer.ecms.as.MetricsSession - logEvent:
    exception: start() failed on resource
    'weblogic.jdbc.wrapper.JTSXAResourceImpl': XAER_RMFAIL : Resource manager is
    unavailable
    javax.transaction.xa.XAException: Internal error: XAResource
    'weblogic.jdbc.wrapper.JTSXAResourceImpl' is unavailable
    at
    weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceD
    escriptor.java:1019)
    at
    weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResour
    ceDescriptor.java:572)
    at
    weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInf
    o.java:1068)
    at
    weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceI
    nfo.java:1001)
    at
    weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceIn
    fo.java:203)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:419)
    at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:207)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:154)
    at
    weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
    :298)
    at
    com.pfizer.ecms.asutil.DataAccessManager.getConnection(DataAccessManager.jav
    a:117)
    Here's our configuration:
    <JDBCConnectionPool CapacityIncrement="1"
    DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="1"
    MaxCapacity="150" Name="OraclePool"
    Password="*****"
    Properties="user=******" ShrinkPeriodMinutes="5"
    Targets="myserver" TestConnectionsOnCreate="true"
    TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
    TestTableName="dual" URL="jdbc:oracle:thin:@garrison.back:1521:IC"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="true"
    JNDIName="dbpool" Name="OracleSource"
    PoolName="OraclePool" Targets="myserver"/>
    Looking this up, I was pointed to a JTA FAQ page on edocs, and it basically
    said we should be Refreshing the connection pool, but the RefreshMinutes
    parameter is deprecated, and as you can see we're testing connections as is.
    We're puzzled by a couple of things, almost certainly application related,
    but still relevant. We have 150 connections allocated to the pool, but even
    at peak load during the day we bounce around the 40 mark. When we got the
    above exception, we were hitting the 150 ceiling. We don't quite know why
    yet.
    During this time, our DB server was pretty heaviliy loaded. There were some
    horrendous queries running, some data imports, etc. Bascially a bunch of
    stuff that happens at the beginning of the month. However, there weren't
    necessarily a lot of actual users on the system, just a select few.
    One of the things that was happening was a user was using the web interface,
    and sent off a huge horrible query. When it didn't come back in a reasonable
    amount of time, he simply hit "Refresh" on the page, thereby submitting the
    query again (thank you Sir, may I have another!). This was partly why the
    database was so heavily loaded.
    Now, we're puzzled by a couple of things. One, is the spike of actual
    connections in the DB Pool up to 150. This makes no sense.
    Second, is this error detailed above. I've tried some contrived
    experiements, and I can not raise this specific exception myself. My
    experiment was to issue a "update table set column = 1 where id = 1" in a
    generic SQL browser, thus locking the row, and then issue the identical
    command through a Session Bean call. It has happily sat there for up to 10
    minutes (600 seconds, which is our default <JTA Name="inf4.2"
    TimeoutSeconds="600"/> setting), and it eventually times out, but not with
    the same exception. Rather I get "java.sql.SQLException: ORA-01013: user
    requested cancel of current operation" from Weblogic, and
    "weblogic.transaction.internal.TimedOutException:" from my client.
    Apparently, according to the original exception, an XA Resource has not
    responded within 120 seconds, but through my testing, that XA resource isn't
    necessarily a SQL connection waiting on a query.
    Could someone provide insight as to what resource the system may be waiting
    on? For in theory, to me, that's what is consuming our DB Pool. I'm assuming
    that whatever they're waiting on (the DB apparently), they're ALL waiting on
    it, and the reason that the pool spikes is because the system can never find
    a "valid" connection, thus trying again with a new one. Is that what it
    happening?
    Clearly we basically have a tuning issue, but in fact, I'm looking for a
    stability solution. When this occurred, our system run 3 load balanced
    "legs". The middle leg was having the problem. When we dropped it, leg 3
    picked up and then IT had the problem. However, once we killed all 3 of them
    and restarted, they recovered.
    So I'm looking for some idea to keep Weblogic alive, even at the expense of
    booting off these offending transactions, and not having to restart the
    servers.
    Perhaps over time the system would have recovered on its own (most probably
    in fact), but if we can get things cut off early (as well as beating users
    that hit Refresh constantly when things "stick"), we can prevent these from
    escalating the effectively downing the whole site.
    Any thoughts would be appreciated.
    Regards,
    Will Hartung
    ([email protected])

    Will Hartung wrote:
    Weblogic 8.1, I don't recall which service pack, sp10? Maybe?Well, we're only up to sp5 here, so we'll have to catch up ;)
    Please try this:
    <JDBCConnectionPool CapacityIncrement="1"
    DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="45"
    MaxCapacity="45" Name="OraclePool"
    Password="*****"
    Properties="user=******"
    Targets="myserver" TestConnectionsOnCreate="true"
    TestConnectionsOnRelease="false" TestConnectionsOnReserve="true"
    KeepXAConnTillTxComplete="true"
    TestTableName="dual" URL="jdbc:oracle:thin:@garrison.back:1521:IC"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="true"
    JNDIName="dbpool" Name="OracleSource"
    PoolName="OraclePool" Targets="myserver"/>
    You don't want the pool in flux at runtime, either shrinking or
    growing. Just have it make what you need at startup and keep it.
    Test-on-release is a waste of cycles. Also, I set keep-xa-con
    till tx complete, to ensure that only one connection is ever
    used for a given tx. XA allows connections to be changed at the
    granularity of a single JDBC call, but that provides no real
    benefit, and some overhead.
    Let me know if this helps, and do let me know what real
    service pack you're running.
    thanks
    Joe
    Anyway, here's the relevant stack trace. We had a strange WLS implosion last
    night that we're tracking down. We saw these when our code was trying to get
    a connection out of the datapool.
    <Mar 1, 2006 10:09:12 PM PST> <Warning> <JTA> <BEA-110030> <XA resource
    [weblogic.jdbc.wrapper.JTSXAResourceImpl] has not responded in the last 120
    second(s).>
    01 Mar 2006 22:09:21,652 WARN com.pfizer.ecms.as.MetricsSession - logEvent:
    exception: start() failed on resource
    'weblogic.jdbc.wrapper.JTSXAResourceImpl': XAER_RMFAIL : Resource manager is
    unavailable
    javax.transaction.xa.XAException: Internal error: XAResource
    'weblogic.jdbc.wrapper.JTSXAResourceImpl' is unavailable
    at
    weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceD
    escriptor.java:1019)
    at
    weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResour
    ceDescriptor.java:572)
    at
    weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInf
    o.java:1068)
    at
    weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceI
    nfo.java:1001)
    at
    weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceIn
    fo.java:203)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:419)
    at weblogic.jdbc.jts.Driver.createLocalConnection(Driver.java:207)
    at weblogic.jdbc.jts.Driver.connect(Driver.java:154)
    at
    weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
    :298)
    at
    com.pfizer.ecms.asutil.DataAccessManager.getConnection(DataAccessManager.jav
    a:117)
    Here's our configuration:
    <JDBCConnectionPool CapacityIncrement="1"
    DriverName="oracle.jdbc.driver.OracleDriver" InitialCapacity="1"
    MaxCapacity="150" Name="OraclePool"
    Password="*****"
    Properties="user=******" ShrinkPeriodMinutes="5"
    Targets="myserver" TestConnectionsOnCreate="true"
    TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
    TestTableName="dual" URL="jdbc:oracle:thin:@garrison.back:1521:IC"/>
    <JDBCTxDataSource EnableTwoPhaseCommit="true"
    JNDIName="dbpool" Name="OracleSource"
    PoolName="OraclePool" Targets="myserver"/>
    Looking this up, I was pointed to a JTA FAQ page on edocs, and it basically
    said we should be Refreshing the connection pool, but the RefreshMinutes
    parameter is deprecated, and as you can see we're testing connections as is.
    We're puzzled by a couple of things, almost certainly application related,
    but still relevant. We have 150 connections allocated to the pool, but even
    at peak load during the day we bounce around the 40 mark. When we got the
    above exception, we were hitting the 150 ceiling. We don't quite know why
    yet.
    During this time, our DB server was pretty heaviliy loaded. There were some
    horrendous queries running, some data imports, etc. Bascially a bunch of
    stuff that happens at the beginning of the month. However, there weren't
    necessarily a lot of actual users on the system, just a select few.
    One of the things that was happening was a user was using the web interface,
    and sent off a huge horrible query. When it didn't come back in a reasonable
    amount of time, he simply hit "Refresh" on the page, thereby submitting the
    query again (thank you Sir, may I have another!). This was partly why the
    database was so heavily loaded.
    Now, we're puzzled by a couple of things. One, is the spike of actual
    connections in the DB Pool up to 150. This makes no sense.
    Second, is this error detailed above. I've tried some contrived
    experiements, and I can not raise this specific exception myself. My
    experiment was to issue a "update table set column = 1 where id = 1" in a
    generic SQL browser, thus locking the row, and then issue the identical
    command through a Session Bean call. It has happily sat there for up to 10
    minutes (600 seconds, which is our default <JTA Name="inf4.2"
    TimeoutSeconds="600"/> setting), and it eventually times out, but not with
    the same exception. Rather I get "java.sql.SQLException: ORA-01013: user
    requested cancel of current operation" from Weblogic, and
    "weblogic.transaction.internal.TimedOutException:" from my client.
    Apparently, according to the original exception, an XA Resource has not
    responded within 120 seconds, but through my testing, that XA resource isn't
    necessarily a SQL connection waiting on a query.
    Could someone provide insight as to what resource the system may be waiting
    on? For in theory, to me, that's what is consuming our DB Pool. I'm assuming
    that whatever they're waiting on (the DB apparently), they're ALL waiting on
    it, and the reason that the pool spikes is because the system can never find
    a "valid" connection, thus trying again with a new one. Is that what it
    happening?
    Clearly we basically have a tuning issue, but in fact, I'm looking for a
    stability solution. When this occurred, our system run 3 load balanced
    "legs". The middle leg was having the problem. When we dropped it, leg 3
    picked up and then IT had the problem. However, once we killed all 3 of them
    and restarted, they recovered.
    So I'm looking for some idea to keep Weblogic alive, even at the expense of
    booting off these offending transactions, and not having to restart the
    servers.
    Perhaps over time the system would have recovered on its own (most probably
    in fact), but if we can get things cut off early (as well as beating users
    that hit Refresh constantly when things "stick"), we can prevent these from
    escalating the effectively downing the whole site.
    Any thoughts would be appreciated.
    Regards,
    Will Hartung
    ([email protected])

  • RESOURCE MANAGER IN E-BUSINESS SUITE

    Hi All,
    I have little problem with database resource manager in E-Business database.
    I have set up some resource plan, assigned consumer group and user APPS to this consumer group (of course it is new initial consumer group for that user). At instance level I've set up RESOURCE_MANAGER_PLAN to new plan.
    When I'm on console and use sqlplus, or from my workstation use SQLNavigator and connect as APPS - its resource_consumer_group column from v$session is set to desired new consumer group, but when I start application most of sessions connected as APPS are in DEFAULT_CONSUMER_GROUP - please advice, anyone has any ideas ???
    Best Regards
    Radek

    ADF requires Java EE 5 compatible server - OC4J doesn't meet these requirements.
    You can upgrade your EBS to run on WebLogic, and then you can use the same server for both ADF and EBS.

  • RESOURCE MANAGER IN E-BUSINESS SUITE DATABASE

    Hi All,
    I have little problem with database resource manager in E-Business database.
    I have set up some resource plan, assigned consumer group and user APPS to this consumer group (of course it is new initial consumer group for that user). At instance level I've set up RESOURCE_MANAGER_PLAN to new plan.
    When I'm on console and use sqlplus, or from my workstation use SQLNavigator and connect as APPS - its resource_consumer_group column from v$session is set to desired new consumer group, but when I start application most of sessions connected as APPS are in DEFAULT_CONSUMER_GROUP - please advice, anyone has any ideas ???
    Best Regards
    Radek

    EBS installs come with the database packaged with the install. You do not need a separate database install. Pl post EBS related issues in the EBS forums at http://forums.oracle.com/forums/category.jspa?categoryID=3
    HTH
    Srini

  • Virtualised Multi-Instance SQL Server Cluster - Processor Resource Management

    Hi - We're in the process of implementing a multi-instance SQL 2014 guest cluster on Windows 2012 R2.  To our dismay, it seems that Windows System Resource Manager (WSRM) is deprecated in Windows 2012 R2, so we're now stuck for how best to manage CPU usage
    between SQL instances....
    As far as I can see, I'm left with two options, but both of these have problems:
    1) Use SQL Processor affinity within the guest cluster, with each SQL instance assigned to dedicated v-CPU.  However, I'm not certain that setting SQL Processor affinity within a VM will actually have the desired affect!?..
    - When there is physical CPU capacity available, I'd hope Hyper-V would provide it to whichever v-CPU is demanding it.  
    - When VM processor demand exceeds the physical CPU capacity, I'd hope the SQL instances would receive a proportion of the physical CPU time according to the number of v-CPU(s) assigned through the affinity settings.
    2) Use a VM (actually 2, because its a 2-node guest cluster) per SQL instance!..  This is not ideal, as we need multiple SQL instances and it would result in have an administrative and performance overhead
    Does anyone have any information or thoughts on this?  How can we manage a virtualised multi-instance SQL deployment now that WSRM has been deprecated?  Help me please!

    I'm not sure what are the requirements for each of the 2 VMs in in the SQL guest cluster.
    I'm assuming the guest cluster resides on a Hyper-V CSV with at least 2 Hyper-V hosts, and the 2 VMs are configured with Anti-affinity to ensure they never reside on the same Hyper-V host.
    I've been able to configure CPU resources to VMs from the standard controls in Hyper-V Manager:
    See this blog post
    What edition of SQL 2014 you're using?
    This matters because of these limitations.
    Also consider running SQL Server with Hyper-V Dynamic Memory - see Best Practices
    and Considerations
    Hyper-V performance tuning - CPU
    Hyper-V 2012 Best Practices
    Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
    Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

  • The resource manager is doing work outside a global transaction

    I use Orable 8.1.7.4 with Sun Java Application Server 7.0.0_04. The XA data source I use is oracle.jdbc.xa.client.OracleXADataSource.
    Oracle JDBC driver version is 10.1.0.2.0.
    I have an J2EE application with 2 EJB modules. Each EJB module works use own ConnectionPool.
    All Entity beans are CMP, CMT.
    All methods have transactional attribute REQUIRED.
    When I work with beans from single EJB module only, all works fine.
    When I try to call session bean method from a session bean from ANOTHER EJB module - an exception will be thrown:
    WARNING: JTS5041: The resource manager is doing work outside a global transaction
    oracle.jdbc.xa.OracleXAException
    Anyone got any idea?

    I remember having exact same problem with 9.2 drivers, the problem got fixed with 9.2.0.5 drivers -- perhaps Oracle hasn't ported the same fix to 10g drivers. As a workaround try creating non-XA datasource to avoid the exceptions.

  • I have a color management problem.  I have OS X v 10.5, Adobe Photoshop Elements 6, and an Epson Stylus Photo R800.  I want to print images I have scanned on a Epson Perfection 1660 Photo and corrected in Photoshop and get the colors accurate.

    i have a color management problem.  I have OS X v 10.5, Adobe Photoshop Elements 6, and an Epson Stylus Photo R800.  I want to print images I have scanned on a Epson Perfection 1660 Photo and corrected in Photoshop and get the colors accurate.

    I used the ColorSync utility to verify, and it came back with this report:
    /Library/Printers/EPSON/InkjetPrinter/PrintingModule/SPR800_Core.plugin/Contents /Resources/ICCProfiles/SPR800 Standard.icc
       Tag 'dmnd': Tag size is not correct.
    /Library/Application Support/Adobe/Color/Profiles/Recommended/CoatedFOGRA27.icc
       Tag 'desc': Tag size is not correct.
    /Library/Printers/EPSON/InkjetPrinter/ICCProfiles/Standard.profiles/Contents/Res ources/Epson IJ Printer.icc
       Tag 'dmnd': Tag size is not correct.
    /Library/Printers/EPSON/InkjetPrinter/PrintingModule/SPR800_Core.plugin/Contents /Resources/
    I did not know what to do next.  At the bottom of the window it said to go to www.apple.com/colorsync to find a tutorial.  I got a message saying that link does not work.  Tried to find the tutorial by searching at apple.com, but could not seem to locate it.  Does anyone know what the report above means and what I should do about it?  
    Also, how to find that tutorial?
    Re Using RGB all the way through, When I print from Photoshop Elements, I select Adobe RGB, Photoshop Manages under "Color Handling", Relative Colometric  under "Intent" and "ColorSync" i the Epson printer box.  Do you mean to do something different in this sequence?

  • Database Resource Manager

    Hello,
    We're on Oracle 10.2.0.3.
    I want the Resource Manager to map a specific machine in de 'LOW_GROUP'.
    Therefore I've used the value of 'machine' from the following query
    select sid, serial#, username, machine, resource_consumer_group
    from gv$session
    order by sid;
    BEGIN
    dbms_resource_manager.clear_pending_area();
    dbms_resource_manager.create_pending_area();
    dbms_resource_manager.set_consumer_group_mapping(
    dbms_resource_manager.client_machine,
    'CWZ\04-800-1330',
    'LOW_GROUP'
    dbms_resource_manager.submit_pending_area();
    END;
    When I connect to the database, the connection is in consumer_group 'OTHER_GROUPS'.
    What can be the reason for that ?
    Thanks for your help,
    Sjang

    Hello
    I've found the same problem when setting up the USER mapping. It doesn't work! There is a bug with the PROGRAM mapping in that dbms_resource_manager uppercases the input program name, so if you have mixed case executable names, it won't work, but it seems to extend to the other attributes too.
    To get round the problem, I've put together a logon trigger and several mapping tables and then do the switch manually i.e.
        BEGIN
            SELECT
                spm.consumer_group
            INTO
                ls_ConsumerGroup
            FROM
                resource_man.session_user_mapping spm
            WHERE
                spm.user_name = USER;
            dbms_resource_manager.switch_consumer_group_for_user
            (   USER,
                ls_ConsumerGroup
        EXCEPTION
            WHEN NO_DATA_FOUND THEN
                NULL;
        END;
        BEGIN
            SELECT
                spm.consumer_group,
                vs.sid,
                vs.serial#
            INTO
                ls_ConsumerGroup,
                ln_SessionId,
                ln_Serial
            FROM
                session_program_mapping spm,
                v$session vs
            WHERE
                vs.program = spm.program_name
            AND
                vs.audsid = TO_NUMBER(SYS_CONTEXT('USERENV','SESSIONID'));
            dbms_resource_manager.switch_consumer_group_for_sess
            (   ln_SessionId,
                ln_Serial,
                ls_ConsumerGroup
        EXCEPTION
            WHEN NO_DATA_FOUND THEN
                NULL;
        END;Not sure why the auto mapping bit doesn't work but the above code does work.
    HTH
    David

Maybe you are looking for

  • My iBooks were fine yesterday,today unable to read, message comes up; failure to load book because requested resource is missing".  What do they want?

    My iBooks were fine yesterday, today unable to get into book, message comes up, "failure to load book because requested resource missing"   It doesn't tell me what resource is missing, & why could I read this 12 hours ago fine.

  • Apps Not Showing Up on Home Screen

    I just updated to iOS 7, and upon setting up my phone, I discover all of my apps (except for the pre-loaded ones) are not on the home screen. They're definitely still on the phone as they show up in my settings, and I can access them from my control

  • Automatic batch determination in EWM

    Hi All My batch selection criterion is being replicated to EWM outbound delivery order. But, batches are not determined automatically there. I have alredy made settings for 'to check batches' for the outbound delivery order document type. Also, I hav

  • How to sign all users out of my account?!

    So I logged in to a freinds PS4 recently with my account and now I don't want them to access my PSN account anymore as it logs me out of my PS4 when they go onto my account and it's annoying me. I've tried changing my password and that didn't help as

  • Aiport Management Utility on Intel Macs

    I just downloaded the Airport Management Utility on to my Mac Book Pro. While it runs OK on an iBook G4, it refuses to run on the Mac Book Pro, giveing a message that it needs Airport 3.4 or higher. Also The accompanying Airport client monitor works