Client management with nio

Hi everyone!
I have a program based on nio which has a selector thread that handles the accepts and reads fromt he clients. Another thread, the main one, get's all the read information, handles it and sometimes has to send something back. Now I wonder how I should manage the clients so that I can send something to them based on their ip and what I have to look after to not get into dead locks or similar.
Thanks for any help in advance!
Chris

The select loop in that example I
posted passes the key to the doRead, doWrite and
doAccept methods based on what is ready, they do the
cast.I'm doing it like in your example for reading only. I thought that the trigger for the ON_WRITE select was a call to the write method of a SocketChannel so I tried to do it without the ON_WRITE stuff. Isn't the ON_WRITE select only for safety reasons when write could fail or block? I'm willing to do as you have suggested (with ON_WRITE) but I don't know how to trigger it..
I have an example of a simple NIO multiple destination
message switch (a bit like chat) that I will tidy up
and post. It addresses the issues you are concerned
with.That sounds awesome. I hope you get it up soon ;)
Thanks for your help,
Chris

Similar Messages

  • Identifying and managing clients in nonblocking NIO socket programming

    Here's my beef. When I write a Server using a thread for every new connection that comes in, I can remember everything for each client in its respective thread. I can have a table entry in a MYSQL database for each client which each thread can look up by a remembered id. I can direct packets from a different application to a specific client by passing a message to the thread associated with the client. But, in this implementation, the client-server setup will need to have a master-slave relationship where one is always reading, and can talk on the network only in response.
    I like the NIO selector way of doing things, but I do not get a memory method to deal with specific clients. How do I, for example,
    direct packets to a specific client.?
    recognize incoming packet info and make sense of its context in relation to past messages to and from the same client?
    maintain one-to-one correspondence between a MYSQL database table entry and a specific client?
    Could somebody explain this to me how I can maintain a client environment, and a client state machine with memory?
    Thanks
    Anil

    cloud9ine wrote:
    Here's my beef. When I write a Server using a thread for every new connection that comes in, I can remember everything for each client in its respective thread. I can have a table entry in a MYSQL database for each client which each thread can look up by a remembered id. I can direct packets from a different application to a specific client by passing a message to the thread associated with the client. But, in this implementation, the client-server setup will need to have a master-slave relationship where one is always reading, and can talk on the network only in response.
    I like the NIO selector way of doing things, but I do not get a memory method to deal with specific clients. How do I, for example,
    direct packets to a specific client.?
    recognize incoming packet info and make sense of its context in relation to past messages to and from the same client?
    maintain one-to-one correspondence between a MYSQL database table entry and a specific client?
    Could somebody explain this to me how I can maintain a client environment, and a client state machine with memory?
    Thanks
    AnilYou will use select() and SelectionKey when you deal with NIO. The SelectionKey has an attach method that you can use to associate the client with something, e.g. a session. Your Session class can contain all that you now have in your thread.
    Kaj

  • Streamlined Client Management and VDI with Configuration Manager 2012

    Hi, 
    There is an interesting blog about managing ConfigMgr 2012 Clients in a VDI environment. 
    http://blogs.technet.com/b/server-cloud/archive/2011/11/15/streamlined-client-management-and-vdi-with-configuration-manager-2012.aspx
    But I didn't find any way or description in the blog on how to prepare the client in the base image used for VDI. Do we still have to make the client unique before shutting down the base image? Or will this be done automatically? 
    Are these new attributes (IsVirtual, IsMachineChangesPersistent ...) enabled by default? 
    Thanks!
    Gr. Cédric.

    No this is handled by ConfigMgr post SP1 
    Are these new attributes (IsVirtual, IsMachineChangesPersistent ...) enabled by default? 
    For XenDesktop  -no you will need to enable them in the client settings (not sure for other virtual
    solutions)
    In the SCCM Console go to the Administration workspace; click Client Settings. Right click the Default Client Settings and choose Properties
    Choose Hardware Inventory and click Set Classes.
    Click the Add button and then click Connect. 
    Enter the computer name of a master image device that has the SCCM client installed.
    Enter root\ccmvdi as the WMI namespace and click Connect.
    Select CCM_DesktopMachine. Click Ok.
    Cheers
    Paul | sccmentor.wordpress.com

  • Experience with NIO client servers

    Dear Forum
    I am going to build a xml socket server and would like to use NIO rather than multi threadeding.
    What the server will do is accept client connections and run them on their own thread, these clients will then be able to send/recieve data in xml and also make simple queries to a mysql database.
    I have developed a similar system using conventional thread methods but not with NIO, the main problem that I have is i cannot see an example where a client connects a new thread is started for that client and then its reference is stored on the server allowing messages to be sent by iterating through the client vector. Is this the same for NIO?
    Any suggestions or pearls of wisdom would be great..
    Thankyou..

    If your application is basically multithreaded you are better off using the stream based sockets. If you insist on using NIO, I've posted information on multiple threads and NIO in Taming the NIO Circus. You biggest problems will come from the fact that interestOps and register block if a select is active. This forces you do do those all from the thread that does the select. You need to use a queue. Also NIO doesn't support SSL at present, maybe in 1.5.

  • How to associate an XA Resource Manager with a Corba Native Client?

    Hello,
    how is a Corba Native (C++) Client associated with an XA Resource Manager? I can't find it in the documentation.
    I believe I understand how it works in a Tuxedo native client: buildclient needs "-r <rmname>" and tpinit() needs to include the group name (ubbconfig group with TMS_ORA and OPENINFO).
    buildobjclient does not seem have anything like the "-r" option, and the bootstrap object does not seem to have any way to specify a group.
    We have a Corba client that updates the database, enqueues into /Q and invokes a transactional Corba service. All three need to be in the same transaction. I am stuck on how to get an XA DB connection.
    Thanks...
    Roger
    PS: The proper solution is to make the client's functionality a service and have the client invoke the service. But that causes other complications.

    I got part of the answer from a different thread.
    Native clients do not need a TMS_* to start a transaction. On commit/rollback they consult the Global Transaction Table (GTT) to find a TMS_* that is involved in the transaction and delegate the commit/rollback to one of those TMS_*.
    For remote clients (using IIOP) the ISH handles the request from the remote client and deals with transaction management.
    Roger

  • I'm in realestae, and i need a client manager that will sync with my iphone, ipad and mac if i make changes on one device. Any sugestions.

    I'm in realestae, and i need a client manager that will sync with my iphone, ipad and mac if i make changes on one device. Any sugestions.

    Try using icloud and that should solve your problem

  • I have windows 7 and my firefox client will not open, but it shows in task manager with 108k memory. Whats going on with my firefox?

    As stated on the question I have windows 7 and meet all the requirements. But when i launch firefox It wont start, but it shows in task manager with 108k memory.

    Got the exact same problem aswell, finally fed up with it now as i just started up firefox and 14 new windows opened because of this bug, luckily my computer can handle them but someone with a slower processor it would have been a nightmare, needs fixing ASAP.
    Reverting back to 3.6.3 until this issue is solved. (link for anyone wanting to do the same below)
    http://www.filehippo.com/download_firefox/7345/

  • Selector thread in JSSE with NIO works nor parallely?

    Hi,
    I am now studying JSSE with NIO. Most of the codes are that I looked, used the Selectable Non blocking IO model. Selector thread contains many keys(keys == client sockets nearly)
    The Selector object maintains a set of selected keys and just one key is processed at a given time in a server program. So, there is no parallel work. I wonder why this keys are not processed parallely, not in batch process model in one thread?

    wow, this reply enlightens me.I have a question for you.
    here is a samle run method of runnable selector class.
    public void run() {
        while (true) {
          doPendingTasks();
          if (closeRequested) {
            return;
          int selectedKeys = 0;
          try {
            selectedKeys = selector.select();
          } catch (IOException ioe) {      
            ioe.printStackTrace();
            continue;
          if (selectedKeys == 0) {
            continue;
          Iterator it = selector.selectedKeys().iterator();
          while (it.hasNext()) {
            SelectionKey sk = (SelectionKey)it.next();
            it.remove();
            try {
              int readyOps = sk.readyOps();
              sk.interestOps(sk.interestOps() & ~readyOps);
              SelectorHandler handler =
                 (SelectorHandler) sk.attachment();         
              if (sk.isAcceptable()) {
                ((AcceptSelectorHandler)handler).handleAccept();
              } else if (sk.isConnectable()) {     
                ((ConnectorSelectorHandler)handler).handleConnect();           
              } else {
                ReadWriteSelectorHandler rwHandler =
                  (ReadWriteSelectorHandler)handler;              
                if (sk.isReadable()) {               
                  rwHandler.handleRead();             
                if (sk.isValid() && sk.isWritable()) {
                  rwHandler.handleWrite();                             
            } catch (Throwable t) {
              Shutdown();
              t.printStackTrace();
              return;
      }in this code every operation is managed by handler named "handleXXX".for example "handleRead" does reading job and also informs the side(client or server) for the data read.
    public void handleRead() {
        try {     
          int readBytes = channel.read(inBuffer);     
          if (readBytes == -1) {
            // Closing channel...
            close();
            side.socketDisconnected(this);
            return;
          inBuffer.flip();
          processInBuffer(); //if there is parts that belongs to more than one packet, seperate them and inform side(client/server)
        } catch (IOException ex) {
          side.socketException(this, ex);
          close();
      }Finally my question is if this approach is wrong.if not ,it takes more than zero time,doesn't it?
    If it is wrong , what approach do you suggest about handling operations?
    Thanks.

  • How to install Oracle BPEL Process Manager with the BEA WebLogic

    Hi ,
    I will install Oracle BPEL Process Manager with BEA WebLogic 9.2(MP2). I have download orabpel_10133_WebLogic.zip ,then Modify the following mandatory installation properties in the orabpel_10133_WebLogic\bpelDomain.properties file:
    # BEA_HOME is the path where Weblogic is Installed
    BEA_HOME=/opt/bea
    # JAVA_HOME is the path of jdk folder inside your weblogic
    JAVA_HOME=/opt/bea/jrockit90_150_10
    # DOMAIN_HOME is the path where you wish to create your domain called BPELDomain
    DOMAIN_HOME=/opt/bea/user_projects/domains
    # APPS_HOME is the path where you wish to copy your applications and adapters that are required for oracleBPELServer
    APPS_HOME=/opt/bea/user_projects/apps
    # BEA_HOME is the path where BPEL PM is Installed
    BPEL_HOME=/home/oracle/bpel/product/10.1.3.1/OraBPEL_1/bpel
    # DRIVER_TYPE is the datasource class that installable use to create a datasources for oracleBPELServer
    DRIVER_TYPE=oracle.jdbc.xa.client.OracleXADataSource
    # DB_URL is the url to connect to orabpel schema
    DB_URL=jdbc:oracle:thin:@16.157.134.17:1521:orcl
    # DB_USER is the user Id for orabpel shema in database
    DB_USER=ORABPEL
    #DB_PASSWORD is the password for orabpel schema in database
    DB_PASSWORD=bpel
    #BPEL_SERVER_NAME is the server i.e. to be created under BPELDomain
    BPEL_SERVER_NAME=oracleBPELServer
    #PROXY_HOST is the Host name of the proxy server
    PROXY_HOST=www-proxy.us.oracle.com
    #PROXY_HOST=
    #PROXY_PORT is the Port where the proxy server is running
    PROXY_PORT=80
    #PROXY_PORT=
    #NON_PROXY_HOST is the list of non proxy hosts that are divided by a | symbol
    #NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com
    NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com|16.157.134.135
    When I run the setup.sh , it will report
    BUILD FAILED
    /opt/software/WL_Installables/build.xml:131: Traceback (innermost last):
    File "./wl_scripts/bpelDomain.py", line 22, in ?
    File "./wl_scripts/createGroupsAndUsers.py", line 4, in ?
    weblogic.management.utils.AlreadyExistsException: [Security:090267]Group BpelGroup
    Actully ,there is no BpelGroup in Weblogic. Does anybody know how to solve it ?

    MAke sure you have not set ANY environment variable related to Oracle / BEA / Java / LD_library path. Use the following script to unset / set the initial settings:
    #!/bin/sh
    unset ORACLE_BASE ORACLE_HOME ORACLE_SID ORACLE_TERM
    unset LD_LIBRARY_PATH LD_LIBRARY_PATH_64
    unset CLASSPATH JAVA_HOME
    export PATH=.:/usr/sbin:/usr/bin:/usr/local/bin:/opt/VRTS/bin
    export BEA_HOME=/appl/oracle/products/9.2/weblogic
    Marc
    http://orasoa.blogspot.com

  • 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)
              > >
              > >
              

  • Difference between nio-file-manager  and nio-memory-manager

    Hi,
    what's the difference between nio-file-manager and nio-memory-manager? The documentation doesn't really discuss the differences as far as I know. They both use nio to store memory-mapped files don't they? What are the advantages/disadvantages of both?
    When to choose the first one and when the second when storing a large amount of data? Can both be used to query data with the Filter API? Are there size limits on both?
    Best regards
    Jan

    Hi Jan,
    The difference is that one uses a memory mapped file and one uses direct nio memory (as part of the memory allocated by the JVM process) to store the data. Both allow storing cache data off heap making it possible to store more data with a single cache node (JVM) without long GC pauses.
    If you are using a 32 bit JVM, the JVM process will be limited to a total of ~3GB on Windows and 4GB on Linux/Solaris. This includes heap and off heap memory allocation.
    Regarding the size limitations for the nio-file manager Please see the following doc for more information.
    With the release of 3.5 there is now the idea of a Partitioned backing map which helps create larger (up to 8GB of capacity) for nio storage. Please refer to the following doc.
    Both can be used to query data but it should be noted that the indexes will be stored in heap.
    hth,
    -Dave

  • App-V Client, No client management console

    Running a Server 2012r2 that runs app-v version 5, and a Windows 8.1 Ent.
    Everything works fine on the server, I have a Winrar.appv added to the server, that is published.
    The problem comes on the client. The installation on the client goes fine, and after the first reboot Winrar is automatic installed, BUT I dont get any management window, where I can choose what to install! I have looked after a suitable exe file to fire
    up a GUI with, but nothing happens when I click them. I have added the HotFix to the server, and added GPO that contain the http adresses to the app-v server. I also changed
    ExecutionPolicy to to Set-ExecutionPolicy RemoteSigned. Any
    ideas? Both the AppVStreamingUX and appvclient.exe is running.
    I also want to say this is my first try on App-V, never used it before, so Im sure this is something very basic.

    Been at this for at least 9-10 hours! I have googled, and googled and tested and tested different things, and now I found this. Why cant MS just do a BIG box in the installation saying they have made a major change! Grr :) It works great now. 
    App-V 5.0 Client Management User Interface Application
    In previous versions of App-V 5.0 the Client Management User Interface (UI) was provided with the App-V 5.0 Client installation. With App-V 5.0 SP2 this is no longer the case. Administrators now have the option to deploy the App-V 5.0 Client UI
    as a Virtual Application (using all supported App-V deployment configurations) or as an installed application.
    For more information see Microsoft Application Virtualization 5.0 Client UI Application (http://go.microsoft.com/fwlink/?LinkId=386345).

  • HR Renewal: Client infotype with upload/download file functionality

    Hi Gurus,
    I am writing to you today cuz a client of mine asked me to adapt one of their client-specific infotype for HR Renewal. Now the old-legacy infotype was developed by someone else so I am just to adapt the functionality for decoupled infotype framework and front-end.
    The infotype has no subtype and record from 01.01.1800 to 31.12.9999 with a table-control listing all the pdf (or other format) file for a particular employee (such has income tax statement; SEPA bank account sheet; ID card etc... any kind of personal document relevant to employees). (that data is listed from a client Z table when opening the infotype; e.g. there is not sub-strucutrue in the pnnnn to  represent that information).
    upload, download and open file functionality is done via the infotype old-framework screen 2000 by some custom code merely replicated what is available by cl_gui_services.
    File are stored directly on the SAP system not using the GOS option;
    back-end stuff is more or less done and working at least I can do pretty much what I want in puit_ui tcode; read;modify... off course no file upload there
    front-end is another story; I have managed the FPM views for the infotype (dataset; biz card, etc) and also I have managed to list the existing file in the ATS list.
    However What I need still to do is to be able to upload from NWBC files to the back end system; and also download or open them. this seems to be a little harder than expected.
    I am now doubting if I should rather do a P&F FPM form based or if I can achieve what it is suppose to do? or maybe I should go back to the client and talk him through changing that infotype architecture? using subtype instead of a connection to a Z table and GOS services to store employee files seems way easier for me; but still I am facing the upload/download functional which I dont really no how to wrap around the FPM either it is ATS or GL2. I have checked indian-specific infotype 3743 has this uploading functionality (GOS) but no corresponding FPM I could inspire myself on!
    Also, not sure if I am missing something but when I try to change the value of one the field on the infotype pnnnn structure (that infty actually has one checkbox field) and save I end up with a dump because to BOL model does not find my entity (lo_entity). it s not the first infotype I am enabling for HR Renewal and I never had this error before.. I wonder what I am missing....
    Would you gurus oriente me a lil on how I should best proceed? should I rather use P&F? Your help and advise would greatly be appreciated!
    Thanks.

    Hello:
    So after some thinking through:
    - upload and download are handler by the FPM ATS feeder (client copy with enhanced options into to manage event method).
    - lo_entity without pointer causing dump occurred because I had inconsistently used the set automatic tag option into the FPM configuration floorplan editor.
    - PAOC_ASR_PERSONAL_FILE would be my recommendation but client want to follow on its own mini-dev for personal file hosting.
    Thank you gurus!

  • Support for Internet based client Management - SCCM 2012

    Hi There,
    My Company wants to go for Internet based client Management in SCCM 2012 SP1 R2 and here is the design I'm proposing. I'm getting a bit confused at one point and need suggestion....
    Everything would work on HTTPS ( PKI Certificate based )... LAN and Internet.
    1 Primary ( with non-client facing roles installed ) on LAN with two site systems.
    - One Site System configured for INTRANET support only with MP, DP and SUP -> To support LAN users ( Allow
    Intranet-only connections )
    - One Site System configured for INTERNET support only with MP, DP and SUP -> To support Internet users ( Allow 
        Internet-only connections )
    The INTERNET facing site system is in DMZ network connected to parent Primary via Firewall.
    We want internet clients to talk to ONLY DMZ SCCM Site System and no connection to corporate LAN. We cannot open any ports for internet based clients to LAN.
    If this is the supported scenario, then why we need to put the Internet FQDN in the Primary server Site System property. This server would not be available to internet. It should only be my DMZ SCCM server client should connect for MP, DP and SUP and only
    this DMZ server should be accessible to client over internet.
    Also, what least ports should be opened between :
    - Parent Primary and its internet facing site system kept in DMZ
    - DMZ Site system and internet clients.
    Thanks in advance for your suggestions.
    Sam

    The FQDN has only to be specified on the Internet facing site system. You can leave this field blank on the primary site Server.
    Ports to Open:
    Internet --> DMZ Site Server:
    TCP Port 443
    TCP Port 80, if Fallback Status Point is installed
    DMZ Site Server --> Primary Site:
    TCP 135, 49152-65535
    TCP 445
    TCP 135, 24158 (fixed with
    http://msdn.microsoft.com/en-us/library/bb219447(v=vs.85).aspx )
    TCP 80, 443
    If you have some other roles installed, please consult this page:
    http://technet.microsoft.com/en-us/library/hh427328.aspx
    Cheers,
    Thomas Kurth
    Netree AG, System Engineer
    Blog:
    http://netecm.netree.ch/blog | Twitter:
    | LinkedIn:
    | Xing:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Client manageability in SCCM 2012

    Hi All
    I am Planning to have test SCCM 2012 environment and for that i need few architecture suggestions. Kindly suggest me on the same so that i can implement an effective infrastructure design.
    Total Number of Clients to Support - 58000
    First Draft version of design consist of 1 Primary Site and 3 Seconadry Sites. Kindly confirm if 1 primary and 3 secondary site will be able to cater 58000 clients. As per my understanding secondary site supports 5000 clients and Primary sites can support
    25000 Clients.
    Also confirm that clients under secondary site will be considered as client of primary site (linit of 25000) or seperately counted (25k +5K).
    Regards
    Regards Suresh

    Kent's book talks about a limitation of 50 000 when using a local SQL server. 
    Kent's book does state this. 
    Note that the Technet article states the following (from the link supplied by John):
    Client group 1 includes Windows Server and client.
    Site type
    Configuration Manager version
    Client group 1
    Client group 2
    Client group 3
    Stand-alone primary site, with a local site database, or a remote site database
    System Center 2012 Configuration Manager with no service pack 1
    100,000
    50,000 4
    25,000
    System Center 2012 Configuration Manager with SP1
    100,000 2
    50,000 4
    25,000
    System Center 2012 R2 Configuration Manager
    100,000 2
    50,000 4
    25,000
    Child primary site with a local site database
    System Center 2012 Configuration Manager with no service pack 1
    50,000
    50,000 4
    25,000
    System Center 2012 Configuration Manager with SP1
    50,000 2
    50,000 4
    25,000
    System Center 2012 R2 Configuration Manager
    50,000 2
    50,000 4
    25,000
    Child primary site with a remote site database
    System Center 2012 Configuration Manager with no service pack 1
    100,000
    50,000 4
    25,000
    System Center 2012 Configuration Manager with SP1
    100,000 2, 3
    50,000 4
    25,000
    System Center 2012 R2 Configuration Manager
    100,000 2, 3
    50,000 4
    25,000
    Secondary site
    Any version 1
    5,000 5
    Cheers
    Paul | sccmentor.wordpress.com

Maybe you are looking for