Dealing with failure of JMS server

I'd like to build some fault tolerance into my application using JMS, and I was wondering if a J2EE server with registered topics were to crash, is there the ability to migrate the topics to another J2EE server without the application (publishers/subscribers) knowing?

You can use fault tolerance functionality provided by various JMS vendors.
I have tried out FioranoMQ which contains a dispatcher component to cluster a set of JMS Servers.
Client always sends the connection request to the Dispatcher which forwards it to the Least loaded server in the cluster.
The data on various topics in JMS Servers in the cluster can be synchronised using the Repeater component.
In order to avoid the single point of failure of the Dispatcher, a backup dispatcher can also be configured.
You can find more details and documentation in the developer zone of FioranoMQ on www.fiorano.com

Similar Messages

  • How to deploy a MDBean into cluster with only one JMS server instance running on one of the cluster servers

              I am trying to deploy a MDBean in my cluster ( two servers). The MDBean requires
              the destinestion has to each cluster server. It means that I have to deploy my
              JMS server over the cluster. This will result multiple destinations (queue or
              topic) are created.
              Is there a way to run one JMS server with a clustered MDBean?
              Thanks,
              Taohe
              

    Check out my posting from 4-3 in this thread.
    http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=5&jump=true
    I think I may have answered your question before you asked it.
    In that example I use the picture control to manipulate a bunch of rectangular images of booleans.
    I hope this helps,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • PasswordSync with a Sun JMS Server: javax.jms.QueueConnectionFactory

    Hi,
    I have installed Sun IDM 8.1 and Sun DSEE7 and uses Active Directory as source for identities.
    I then added a resource for the JMS Listener, but when I tried to do Test Connection I got this message:
    Test connection failed for resource:
    java.lang.ClassCastException: com.sun.messaging.ConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory
    Can anybody help me with this.
    rgds
    Crimson
    Edited by: Crimson on May 3, 2010 4:46 AM

    Hi Sean,
    it's better to ask this question at Sun Java System Messaging Server forum:
    http://swforum.sun.com/jive/forum.jspa?forumID=15

  • Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server

    Hi,
    I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
    <Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
    nect to the JMS destination: FMAContractOutboundQueue. The Error was:
    [EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
    ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
    :weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
    -Sreekanth

    I recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
    * The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
    * The connection factory doesn't exist.
    * The object in JNDI with the specified connection factory name isn't actually a connection factory.
    * The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
    Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
    Tom

  • Oracle 10g R2 jms server

    Hi All
    i want to know , how can create more than one jms server, because our application now run on the weblogic 8.1 and 9.1 as well,for weblogic configaration we configee more than one jms server,what i really want to know how i can do that using oracle ...
    and also i like to know what is good information source about the weblogic 8.1 to oracle migration ...
    Thankx
    Asnaka Priyanjith

    The only way to start more than one JMS server is to start up multiple OC4J JVMs, each with its own JMS server.

  • Do I need a Foreign JMS Server?

              Initially, I had an exploded web application, an ejb jar, a jms server, a connection
              factory and a queue all deployed under one weblogic instance. I am now trying
              to move the jms configuration to another machine running weblogic. However, I
              am unsure whether I need to configure a Foreign JMS Server on the initial weblogic
              instance. I have tried to do so and I cannot successfully start the connection
              from my web/ejb app (i.e., myQueueConnection.start() throws an exception - weblogic.jms.common.JMSException:
              Connection not found).
              I saw a thread here about changing the names of the JMS Servers, so I configured
              my web server with a foreign jms server (ForeignMessageServer) and I configured
              one foreign connection factory and one foreign destination. The local jndi names
              of these are unique and different from the remote jndi name. The remote jndi names
              match the names of the connection/destination on the app server (my 2nd server).
              I am using the url of the web server as my provider url and the foreign connection
              factory local jndi name to look up the connection.
              I have two questions:
              Is it necessary to use a foreign jms server configuration to implement this structure?
              If a foreign jms server configuration is necessary, am I going about this correctly?
              Thanks,
              John
              

    It certainly will work. Basically, all it does is move information like the
              JNDI provider name and URL from your deployment descriptors into config.xml.
              For a lot of applications, that's a big help. You can use the "Foreign JMS
              Provider" support anywhere you want to create a JNDI entry on your local
              server that points to something else. You can even use it to point to a JMS
              queue, topic, or connection factory in the same cluster, or the same WLS
              server if you want. I do this for testing so I don't have to have different
              versions of my EJB for different environments.
              As for the bridge, it depends on whether you need to interact with the JMS
              provider synchronously or asynchronously. When you use the bridge, you first
              put the message on one JMS queue or topic, and the bridge copies it to the
              other. So, if the foreign provider is down, you can still send messages.
              However, using the bridge adds an extra "hop" which will slow performance.
              greg
              <[email protected]> wrote in message news:[email protected]...
              > Hi Tom,
              >
              > If I have 2 WLS servers: server1 and server2 and they are NOT in the same
              > cluster. server1 wants to send a JMS message to server2. I know I can
              > achieve the desired result using your 3 suggestions below but would
              using
              > foreign JMS server works as well? When should I use foreign JMS server
              > instead of a messaging bridge?
              >
              > Thanks,
              >
              > Vincent
              >
              >
              >
              > "Tom Barnes" <[email protected]> wrote in message
              > news:[email protected]...
              > > If both weblogic servers participate in the same cluster
              > > there is no additional configuration needed.
              > > All servers in cluster share the same JNDI
              > > name space. Simply specifying a JNDI name
              > > (as you already must have done) is enough
              > > for any server in the cluster, or any client connected
              > > to the cluster, to find a JNDI resource that is hosted
              > > on any server in the cluster (such as queue).
              > > This location transparency is one of the primary
              > > benefits of using clusters.
              > >
              > > If the MDB is in a different cluster than its
              > > source destination, then you have three choices
              > > (1) Change the MDB weblogic descriptor to specify
              > > a URL that resolves to any one of the
              > > addresses of a WL server in the remote cluster.
              > > I don't recall the name of the URL field,
              > > but it is in the weblogic descriptor, and
              > > is documented in the EJB (MDB) programmer's
              > > guide.
              > > (2) Configure wrappers that refer to the
              > > remote JMS resources in the cluster, and change
              > > the MDB descriptors to point to the jndi
              > > locations you configured for the wrapped
              > > connection factory and wrapped destination.
              > > (3) Configure a messaging bridge that
              > > moves from the remote destination to
              > > a local destination (which, in turn,
              > > the MDB consumes from).
              > >
              > > Tom
              > >
              > > John Owen wrote:
              > >
              > > > Initially, I had an exploded web application, an ejb jar, a jms
              server,
              > a connection
              > > > factory and a queue all deployed under one weblogic instance. I am now
              > trying
              > > > to move the jms configuration to another machine running weblogic.
              > However, I
              > > > am unsure whether I need to configure a Foreign JMS Server on the
              > initial weblogic
              > > > instance. I have tried to do so and I cannot successfully start the
              > connection
              > > > from my web/ejb app (i.e., myQueueConnection.start() throws an
              > exception - weblogic.jms.common.JMSException:
              > > > Connection not found).
              > > >
              > > > I saw a thread here about changing the names of the JMS Servers, so I
              > configured
              > > > my web server with a foreign jms server (ForeignMessageServer) and I
              > configured
              > > > one foreign connection factory and one foreign destination. The local
              > jndi names
              > > > of these are unique and different from the remote jndi name. The
              remote
              > jndi names
              > > > match the names of the connection/destination on the app server (my
              2nd
              > server).
              > > > I am using the url of the web server as my provider url and the
              foreign
              > connection
              > > > factory local jndi name to look up the connection.
              > > >
              > > > I have two questions:
              > > >
              > > > Is it necessary to use a foreign jms server configuration to implement
              > this structure?
              > > > If a foreign jms server configuration is necessary, am I going about
              > this correctly?
              > > >
              > > > Thanks,
              > > > John
              > >
              >
              >
              

  • JMS Server JNDI not being replicated? (clustered environment)

    Hello,
    First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
    My current production and test environments consist, each one of them, of
    clusters with one admin server (ProdAdmin) and two managed servers (Prod1
    and Prod2). One of the managed servers (Prod1) is the server to which the
    JMS server is deployed and everything works fine.
    Now I'm trying to add another managed server to the cluster. The idea is to
    target the JMS Server (and nothing else) to this node. We don't want the JMS
    server to be running in Prod1 and the new server, named ProdJMS, won't even
    have any deployed beans or the startup class targeted to it. Just the JMS
    server. Here our problems start.
    I'm able to start this ProdJMS node with no problems. However, when I start
    Prod1 it seems that the JMS server is not binded. This is the exception
    we're getting when a message-driven bean is being deployed (I get the same
    exception trying to create other):
    ------- snip -------------
    <May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
    CacheUpdateBean is unable to connect to the JMS
    destination: securityChanges. The EJB container will automatically attempt
    to re-establish the connection with the JMS s
    erver. This warning may occur during WebLogic Cluster start-up if the JMS
    destination is located on another WebLogic Ser
    ver instance. When the JMS server connection is re-established, the
    Message-Driven EJB will again receive JMS messages.
    The Error was:
    weblogic.jms.common.JMSException: Error creating session
    Start server side stack trace:
    weblogic.jms.common.JMSException: Error creating session
    at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ----------- Linked Exception -----------
    weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
    Prod1, javax.naming.NameNotFoundException: Un
    able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
    Unresolved:'S:Prod1' ; remaining name ''
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
    .java:260)
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
    anager.java:307)
    at weblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ------- snip -------------
    If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
    exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
    actually able to see "weblogic.jms.S:Prod1", which is the name that seems
    not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
    everything works fine. If I deploy the JMS server to a server with only the
    JMS server I get the mentioned JNDI exception.
    I would appreciate if you could give me help me solving this problem.
    Thanks in a dvance for any help.
    Andre Mendonca

    First of all, my envinronment is Weblogic 6.1 sp2, JDK 1.3.1, Windows
    My current production and test environments consist, each one of them, of
    clusters with one admin server (ProdAdmin) and two managed servers (Prod1
    and Prod2). One of the managed servers (Prod1) is the server to which the
    JMS server is deployed and everything works fine.
    Now I'm trying to add another managed server to the cluster. The idea isto
    target the JMS Server (and nothing else) to this node. We don't want theJMS
    server to be running in Prod1 and the new server, named ProdJMS, won'teven
    have any deployed beans or the startup class targeted to it. Just the JMS
    server. Here our problems start.
    I'm able to start this ProdJMS node with no problems. However, when Istart
    Prod1 it seems that the JMS server is not binded. This is the exception
    we're getting when a message-driven bean is being deployed (I get the same
    exception trying to create other):1. Make sure that you are using a dif multicast address for each cluster
    2. Remove the JMS from Prod1 -- double check this!
    3. Stop Prod1 and Prod2
    4. Start the ProdJMS
    5. Restart Prod1 and Prod2
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Andre Mendonca" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    ------- snip -------------
    <May 21, 2002 12:11:42 PM EDT> <Warning> <EJB> <The Message-Driven EJB:
    CacheUpdateBean is unable to connect to the JMS
    destination: securityChanges. The EJB container will automatically attempt
    to re-establish the connection with the JMS s
    erver. This warning may occur during WebLogic Cluster start-up if the JMS
    destination is located on another WebLogic Ser
    ver instance. When the JMS server connection is re-established, the
    Message-Driven EJB will again receive JMS messages.
    The Error was:
    weblogic.jms.common.JMSException: Error creating session
    Start server side stack trace:
    weblogic.jms.common.JMSException: Error creating session
    atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:121)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ----------- Linked Exception -----------
    weblogic.jms.dispatcher.DispatcherException: Dispatcher not found in jndi:
    Prod1, javax.naming.NameNotFoundException: Un
    able to resolve weblogic.jms.S:Prod1. Resolved: 'weblogic.jms'
    Unresolved:'S:Prod1' ; remaining name ''
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager
    .java:260)
    at
    weblogic.jms.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherM
    anager.java:307)
    atweblogic.jms.backend.BEManager.sessionCreate(BEManager.java:117)
    at weblogic.jms.backend.BEManager.invoke(BEManager.java:219)
    at
    weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:510)
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:149
    at
    weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.jav
    a:300)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
    Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ------- snip -------------
    If I deploy the CacheUpdateBean bean to ProdJMS itself, I don't have this
    exception. The weird thing is that when I check the JDNI tree of Prod1 I'm
    actually able to see "weblogic.jms.S:Prod1", which is the name that seems
    not to be binded. Again, if I deploy the JMS Server to Prod1, for example,
    everything works fine. If I deploy the JMS server to a server with onlythe
    JMS server I get the mentioned JNDI exception.
    I would appreciate if you could give me help me solving this problem.
    Thanks in a dvance for any help.
    Andre Mendonca

  • How to deal with deadlock on wwv_flow_data table when http server times out

    There are some threads about a deadlock on the wwv_flow_data table. None of them contain a real explanation for this behaviour. In my case I will try to explain what I think is happening. Maybe it helps somebody who is hitting the same matter.
    In my case with APEX 3.2.1 I am navigating from one page to another. Doing this APEX will lock the table wwv_flow_data. As soon as the other page is shown the lock will be released. But now this other page contains a bad performing query (standaard report region). After 5 minutes the http server (modplsql) will time out and present the message "No response from the application server" on the screen. In the meanwhile the query is still running on the database server and the lock stays on the wwv_flow_data table.
    Normal user behaviour will be that the user will use the back button to return to the previous page and tries it again to navigate to the other page or
    the user will try to refresh the page with the bad performing query.
    And voila now you will have a deadlock on the wwv_flow_data table since a second session is trying to do the same thing while the first hasn't finished yet.
    How to deal with it?
    First of all. Have a good look at the bad performing query. Maybe you can improve it that it will succeed before the http server will timeout.
    In my case the 11gr1 optimizer couldn't handle a subquery factoring clause in the best way. After changing it back to a classical inline query the problem was solved.
    Secondly you could increase the timeout parameter of the http server. Although this not the best way.
    Maybe it would better if APEX in a next version would release the lock on the table wwv_flow_date earlier or do a rollback just before the moment that the http server is timing out.
    regards,
    Mathieu Meeuwissen

    Hello Shmoove,
    I saw your reply here and you probably understand the problems the HTTP 100 response may cause.
    I am trying to send image that was taken by getSnapshot. The problem is that the server respond with this HTTP 100 message.
    I suspect that the reason that my server doesn't recognize the file that I'm sending from J2me is that the "server to client" response to the 100 message comes after the second message of (see what the TCPIP viewer shows down here):
    POST /up01/up02.aspx HTTP/1.1
    Content-Type: multipart/form-data; boundary=xxxxyyyyzzz
    Connection: Keep-Alive
    Content-length: 6294
    User-Agent: UNTRUSTED/1.0
    Host: szekely.dnsalias.com:80
    Transfer-Encoding: chunked
    400: Client to Server (126 bytes)
    78
    --xxxxyyyyzzz
    Content-Disposition: form-data; name="pic"; filename="david.jpg"
    Content-Type: application/octet-stream
    400: Connected to Server
    400: Server to Client (112 bytes)
    HTTP/1.1 100 Continue
    Server: Microsoft-IIS/5.1
    Date: Wed, 23 Mar 2005 00:47:02 GMT
    X-Powered-By: ASP.NET
    Any help will be appreciated,
    David

  • It says that "there was a problem connecting to the server". What's wrong with this, and how can I deal with this problem?

    I just got my new iPad Mini2, and when I choose "sign in with your apple ID", it says that "there was a problem connecting to the server". What's wrong with this, and how can I deal with this problem?

    1. Turn router off for 30 seconds and on again
    2. Settings>General>Reset>Reset Network Settings

  • How do I delete a Gmail message on my phone, but keep it on the server so I can deal with it on my iMac?  What settings are required, or is this impossible?

    How do I delete a message in my gmail account, but keep it on the server so I can see it on my iMac when I log into gmail.com?  I set up the gmail account on my iphone NOT through the colored "gmail button" but through "add account."  And I've enabled IMAP in the settings when I log in on my computer to gmail.com.
    Thanks!

    Gmail uses IMAP. It's designed to keep all of your devices in sync. If you delete on one, it will be deleted on all of them. However, deleted means that it's in the trash. You could always retrieve it when you're using your Mac. Or, just create a folder that you move things to to deal with later.
    Best of luck.

  • SQL Server Express 2014 Installation Completes with Failures and Repair Does Nothing to Help

    I am attempting to install SQL Server Express 2014 on a development machine and as usual old versions of SQL and the remnants of them are a plague to the installation.
    I have used to Revo Uninstaller to scrub the old installations and with my first attempt after some additional work on the registry I was able to get an instance to install and remarkably I was able to connect to the instance. However, I removed an application
    reference to SQL Server 2008 after the SQL Express 2014 installation (through Control Panel > Programs > Programs and Features) and it stopped working immediately.
    So I removed (uninstalled using Revo Uninstaller) every reference to any SQL Server application as well as removed all of the registry references (using Revo) and I can now install SQL Server Express 2014 with 
    "Feature" failures [Reporting Services, Database Engine Services, Full-Text and Semantic Extractions for Search and SQL
    Server Replication]  and of course it doesn't work.
    Now when I attempt "Repair" the installation the process ends normally (no errors) and reports  "Success" however SQL still has no instance and the services are not running nor are they visible when I open the "SQL Server Configuration
    Manager".
    This is the "Repair" log:
    Overall summary:
    Final result: Passed
    Exit code (Decimal): 0
    Start time: 2014-12-21 17:21:37
    End time: 2014-12-21 17:29:10
    Requested action: Repair
    Machine Properties:
    Machine name: EDWARD-PC2
    Machine processor count: 4
    OS version: Windows 7
    OS service pack: Service Pack 1
    OS region: United States
    OS language: English (United States)
    OS architecture: x86
    Process architecture: 32 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2014 Management Tools - Basic 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Management Tools - Complete 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools Connectivity 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools Backwards Compatibility 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools SDK 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
    Package properties:
    Description: Microsoft SQL Server 2014
    ProductName: SQL Server 2014
    Type: RTM
    Version: 12
    SPLevel: 0
    Installation location: C:\Users\Edward\Downloads\SQLEXPRADV_x86_ENU\x86\setup\
    Installation edition:
    User Input Settings:
    ACTION: Repair
    AGTDOMAINGROUP: <empty>
    AGTSVCACCOUNT: <empty>
    AGTSVCPASSWORD: <empty>
    AGTSVCSTARTUPTYPE: Manual
    ASCONFIGDIR: Config
    ASSVCACCOUNT: <empty>
    ASSVCPASSWORD: <empty>
    CLTSTARTUPTYPE: 0
    CLTSVCACCOUNT: <empty>
    CLTSVCPASSWORD: <empty>
    CONFIGURATIONFILE:
    CTLRSTARTUPTYPE: 0
    CTLRSVCACCOUNT: <empty>
    CTLRSVCPASSWORD: <empty>
    ENU: true
    FAILOVERCLUSTERGROUP: <empty>
    FAILOVERCLUSTERNETWORKNAME: <empty>
    FTSVCACCOUNT: <empty>
    FTSVCPASSWORD: <empty>
    HELP: false
    IACCEPTSQLSERVERLICENSETERMS: false
    INDICATEPROGRESS: false
    INSTANCENAME: <empty>
    ISSVCACCOUNT: NT AUTHORITY\Network Service
    ISSVCPASSWORD: <empty>
    ISSVCSTARTUPTYPE: Automatic
    QUIET: false
    QUIETSIMPLE: false
    SQLSVCACCOUNT: <empty>
    SQLSVCPASSWORD: <empty>
    UIMODE: AutoAdvance
    X86: false
    Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\ConfigurationFile.ini
    Detailed results:
    Feature: Management Tools - Complete
    Status: Passed
    Feature: Client Tools Connectivity
    Status: Passed
    Feature: Client Tools SDK
    Status: Passed
    Feature: Client Tools Backwards Compatibility
    Status: Passed
    Feature: Management Tools - Basic
    Status: Passed
    Feature: SQL Browser
    Status: Passed
    Feature: Documentation Components
    Status: Passed
    Feature: SQL Writer
    Status: Passed
    Feature: LocalDB
    Status: Passed
    Feature: SQL Client Connectivity
    Status: Passed
    Feature: SQL Client Connectivity SDK
    Status: Passed
    Feature: Setup Support Files
    Status: Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\SystemConfigurationCheck_Report.htm
    However this is what the "SQL Sever Configuration Manager" look like:
    Why does this appear to not be working properly? I can not connect the the "local" instance and I would guess that the service either does not exist or is not running.
    Edward Walker

    Hello,
    To my knowledge, Revo is not a supported way to uninstall SQL Server.
    Please try to uninstall all you can using Control Panel -> Programs and Features, then perform a manual uninstall to
    remove remnants. Try the following procedure:
    1. Uninstall all SQL Server 2012 components you can using Control Panel -> Programs and Features
    2. Backup the registry.
    3. Delete the following keys in regedit:
    --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
    --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
    4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing
    SQL Server.
    5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
    6. Rename all the SQL Server folders in the computer like C:\Program Files\Microsoft SQL Server and subfolders.
    After performing above procedure, try to reinstall SQL Server again.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • What is the best way to deal with memory leak issue in sql server 2008 R2

    What is the best way to deal with memory leak issue in sql server 2008 R2.

    What is the best way to deal with memory leak issue in sql server 2008 R2.
    I have heard of memory leak in OS that too because of some external application or rouge drivers SQL server 2008 R2 if patched to latest SP and CU ( may be if required) does not leaks memory.
    Are you in opinion that since SQL is taking lot of memory and then not releasing it is a memory leak.If so this is not a memory leak but default behavior .You need to set proper value for max server memory in sp_configure to limit buffer pool usage.However
    sql can take more memory from outside buffer pool if linked server ,CLR,extended stored procs XML are heavily utilized
    Any specific issue you are facing
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Dealing with two different sets of users but same OAM/SSO/OID Server?

    In our application server's (OAS 10.1.2.) ssl.conf, we need to have the following as following since it's part of the requirement,
    to ask for the user's Cert (CAC, SMARTCARD, X509). We have OAM 10.1.4.2.
    SSLVerifyClient require
    However, using the same exact OAS 10.1.2.3 server, for only a specific URL containing
    /web_html/ as a part of the URL, we need to bypass the SSLVerifyClient require and only
    a server based SSL handshake is required when the SSO resource*(/sso/auth, or /pls/orasso/..)* is hitting
    the OID server that is configured with the SSLVerifyClient.
    SAME OID Server has to deal with two different organizations:
    org1 ---> SSO ---> Client based X509 Cert Based Auth
    org2 ---> SSO ---> Server Based SSL Handshake only
    The SSLClientVerify does have the optional option to use and the users
    can just click on CANCEL but the customer thinks is not very user friendly.
    The screen that is displayed as a result of the SSLVerifyClient (Choose a Digital Certificate) seems to be
    operating system dependent.
    I hope, we won't need to have anther server just for this other organization.
    Thx for your time in advance.
    KA
    Thanks in advance,
    KA

    Daniel,
    We have OAM and it's performing the authentication.
    The SSLVerifyClient is bring up the Choose a Digitial Cert screen and by selecting Cancel, everything works for userlogin/password users. The problem is the screen user friendliness.*
    We are just trying to customize this screen so there is additional message or a different screen would be displayed instead of the generic screen from MicroSoft with OK OR CANCEL.
    Thx for your time,
    KA

  • Communication with JMS server failed

    Hi All,
    We created the Third Party Product,SWC,TS and Business System in SLD.
    While importing S/W component versions from SLD it giving the following error.
    Communication with JMS server failed Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service.
    Pls help me in this.
    Regards,
    Goli Sridhar

    Hi Prateek,
    This is the Error log.
    #11 10:42:19 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.throwRootCause(PvcTransport.java:448)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:197)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Serialized server exceptions:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.server.propagation.XIPropagationException: Communication with JMS server failed
         at com.sap.aii.ib.server.propagation.XIPropagationException.createFromException(XIPropagationException.java:48)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:272)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
         at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         ... 19 more
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
         at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
         at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:189)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: javax.jms.JMSSecurityException (serialized)
    javax.jms.JMSSecurityException: You do not have permissions: action produce and instance jms topic xi PostIntegrate.
         at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
         at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2613)
         at com.sap.jms.client.session.Session.createProducer(Session.java:2396)
         at com.sap.jms.client.session.TopicSession.createPublisher(TopicSession.java:46)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendJMSMessage(MessageReceiverFactory.java:210)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:170)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #10 10:42:19 [Pool-Thread-3] ERROR com.sap.aii.ib.gui.tools.transport.ConcurrentProgressDialog: Execution failed
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.throwRootCause(PvcTransport.java:448)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:197)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Serialized server exceptions:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.server.propagation.XIPropagationException: Communication with JMS server failed
         at com.sap.aii.ib.server.propagation.XIPropagationException.createFromException(XIPropagationException.java:48)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:272)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
         at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         ... 19 more
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
         at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
         at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:189)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: javax.jms.JMSSecurityException (serialized)
    javax.jms.JMSSecurityException: You do not have permissions: action produce and instance jms topic xi PostIntegrate.
         at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
         at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2613)
         at com.sap.jms.client.session.Session.createProducer(Session.java:2396)
         at com.sap.jms.client.session.TopicSession.createPublisher(TopicSession.java:46)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendJMSMessage(MessageReceiverFactory.java:210)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:170)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
         at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
         at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
         at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
         at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
         at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #9 10:36:08 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.ibrep.client.swc.ExtSwcServiceException: Communication with JMS server failed
         at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:120)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
         at java.lang.Thread.run(Unknown Source)
    Root cause:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
         at com.sap.aii.ib.clsif.extobjects.EOAServiceDelegatorImpl.importExtObject(EOAServiceDelegatorImpl.java:127)
         at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:112)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
         at java.lang.Thread.run(Unknown Source)
    Root cause:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.ib.core.extobjects.ExternalOasProcessCSException: Communication with JMS server failed
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:102)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Serialized server exceptions:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:108)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:272)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed
         at com.sap.aii.ib.core.clmgmt.ChangeListMgmtException.createFromException(ChangeListMgmtException.java:35)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:227)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
         at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:104)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
         at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendSynchronousMessage(MessageReceiverFactory.java:278)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:379)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:86)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: javax.jms.JMSSecurityException (serialized)
    javax.jms.JMSSecurityException: You do not have permissions: action consumer and instance jms topic xi PostIntegrate.
         at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
         at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2613)
         at com.sap.jms.client.session.Session.createConsumer(Session.java:2172)
         at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.getJmsReceiver(MessageReceiverFactory.java:673)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.startMessageReceivers(MessageReceiverFactory.java:140)
         at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendSynchronousMessage(MessageReceiverFactory.java:263)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:379)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:86)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #8 10:36:08 [Thread-64] ERROR com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog: Unable to import HARISWC, 1.0 of haritest
    Thrown:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.ibrep.client.swc.ExtSwcServiceException: Communication with JMS server failed
         at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:120)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
         at java.lang.Thread.run(Unknown Source)
    Root cause:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
         at com.sap.aii.ib.clsif.extobjects.EOAServiceDelegatorImpl.importExtObject(EOAServiceDelegatorImpl.java:127)
         at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:112)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
         at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
         at java.lang.Thread.run(Unknown Source)
    Root cause:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
    com.sap.aii.ib.core.extobjects.ExternalOasProcessCSException: Communication with JMS server failed
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:102)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Serialized server exceptions:
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:108)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:272)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed
         at com.sap.aii.ib.core.clmgmt.ChangeListMgmtException.createFromException(ChangeListMgmtException.java:35)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:227)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
         at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:104)
         at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
         at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
         at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
         at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
         at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
         at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
    com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
         at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
         at com.sap.aii.ib.server.notification.Mes

  • Can anyone help me how to work with jms server in osb?

    Hi,
    I am new in osb. I have requirement in osb listeners.
    I want to put some data in to jms server using osb in one project and then consume that data using osb in diffrent projects.
    how to configure jms server to work above scenario?
    how to construct business and proxy sevices?
    jms protocal format?
    My requirement is topic in jms server
    Regards,
    Raju..

    Hi,
    The below link will help you to create simple JMS in weblogic
    https://blogs.oracle.com/soaproactive/entry/how_to_create_a_simple
    How to push message and consume message
    http://rangarb.wordpress.com/2012/04/18/working-with-jms-in-osb-11g/
    Another example of subscription of jms
    http://oraclesoaandoim.blogspot.co.uk/2012/04/oracle-service-11116-consume-jms.html
    Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.
    Thanks,
    Vijay

Maybe you are looking for

  • 2TB Time Capsule and Time Machine on Snow Leopard 10.6.1 slooooooow

    I have a 2TB Time Capsule on a 100Mps LAN that is shared by my Mac Pro and an iMac G5. No USB devices are connected to the Time Capsule. The Time Capsule and both computers are connected to the LAN through a LinkSys 8-port Cable/Router/DHCP. While in

  • Short Dump while entering data in VF01

    Runtime Errors         SAPSQL_INVALID_FIELDNAME Except.                    CX_SY_DYNAMIC_OSQL_SEMANTICS Program                               SAPLV61Z Include                                 LV61ZU01 Error analysis     An exception occurred that is e

  • ITunes could not connect to this iPhone. The device is no longer connected

    A few days ago, my iPad 3 A1430 screen turned black. Siri was still there but very slow to respond. The following day, the screen display returned (the usual green background colour but a much smaller display and not a single icon present). Siri was

  • Sort Column Date - DataGrid - Flex 4.5.1

    Hi I made download the function (below)  to sort column date in DateGrid, but is not working private function date_sortCompareFunc(itemA: Object, itemB:Object):int    var dateA:Date=new Date(Date.parse(itemA.dob));     var dateB:Date=new Date(Date.pa

  • How to create 3D bar?

    I want to draw 3D bar,it's top level is smaller than bottom level,and there is many levels in this bar, and there is effect graphics: http://www.soulbath.com/intro.html,I think I shoud use some math models to create 3D bar,anyone could tell me which