JMS Protocol Fehler

Hi forum !
I have an J2EE Application with follow configuration:
j2eeJavaApp1.ear consisting of
j2eeJavaApp1-ejb.jar, j2eeJavaApp1-client.jar and META-INF.
In META-INF there are following files: application.xml, data-sources.xml, orion-application.xml and surely MANIFEST.MF
In application.xml are defined 2 modules:
<application>
<display-name>j2eeJavaApp1</display-name>
<module>
<ejb>j2eeJavaApp1-ejb.jar</ejb>
</module>
<module>
<java>j2eeJavaApp1-client.jar</java>
</module>
</application>
The contents of the j2eeJavaApp1-ejb.jar are:
META-INF, model.
META-INF contains ejb-jar.xml and orion-ejb-jar.xml.
The extraction from ejb-jar.xml:
<message-driven>
<description>Message Driven Bean</description>
<display-name>MessageDrivenEJB</display-name>
<ejb-name>MessageDrivenEJB</ejb-name>
<ejb-class>model.MessageDrivenEJBBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
</message-driven>
The extraction from orion-ejb-jar.xml:
<message-driven-deployment name="MessageDrivenEJB" connection-factory-location="jms/theTopicConnectionFactory" destination-location="jms/theTopic"/>
In model-directory is resided the MessageDrivenEJB-class: MessageDrivenEJBBean.
Now the contents of the j2eeJavaApp1-client.jar:
client-Directory:
MDBClient-Class (the standalone client)
META-INF-Directory:
application-client.xml:
<application-client>
<display-name>j2eeJavaApp1</display-name>
<resource-ref>
          <description>The Factory used to produce connections to the log topic...</description>
          <res-ref-name>jms/theTopicConnectionFactory</res-ref-name>
          <res-type>javax.jms.TopicConnectionFactory</res-type>
          <res-auth>Container</res-auth>
     </resource-ref>
<resource-ref>
          <description>The log topic where log events are broadcasted...</description>
          <res-ref-name>jms/theTopic</res-ref-name>
          <res-type>javax.jms.Topic</res-type>
          <res-auth>Container</res-auth>
     </resource-ref>
</application-client>
orion-application-client.xml
<orion-application-client>
<resource-ref-mapping
name="jms/theTopicConnectionFactory"
location="jms/theTopicConnectionFactory">
</resource-ref-mapping>
<resource-ref-mapping
name="jms/theTopic"
location="jms/theTopic">
</resource-ref-mapping>
</orion-application-client>
=========================================================
This Application was deployed to OC4J (10.0.3.0.0) without exceptions.
The extraction from the jms.xml from %OC4J%/j2ee/home/config directory:
<topic name="The Demo Topic" location="jms/theTopic">
          <description>The demo topic</description>
</topic>
<topic-connection-factory name="The Demo Topic Factory"
location="jms/theTopicConnectionFactory">
     <description>The demo topic connection factory</description>
</topic-connection-factory>
The extraction from the application.xml from the same directory:
<resource-provider
class="com.evermind.server.jms.Oc4jResourceProvider"
name="oc4jjms">
<description>oc4j-jms loop back resource provider</description>
</resource-provider>
=========================================================
The client attemts to create JMS-Connection and then send a message to a topic with follow code:
String TOPIC_NAME="jms/theTopic";
     String TOPIC_CONNECTION_FACTORY="jms/theTopicConnectionFactory";
     TopicConnectionFactory connectionFactory = (TopicConnectionFactory)getInitialContext().lookup( TOPIC_CONNECTION_FACTORY);
     TopicConnection connection = connectionFactory.createTopicConnection();
     connection.start();
     TopicSession topicSession = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
Topic topic = (Topic)new InitialContext().lookup( TOPIC_NAME);
     TopicPublisher publisher = topicSession.createPublisher(topic);
     Message message = topicSession.createMessage();
     message.setJMSType("theMessage");
     message.setLongProperty("time", System.currentTimeMillis());
     message.setStringProperty("subject", "Subject");
     message.setStringProperty("message", "Hello");
System.out.println("Gleich wird message abgeschickt: "+new java.util.Date());
     publisher.publish(message);
     publisher.close();
     topicSession.close();
     connection.close();
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
private static Context getInitialContext() throws NamingException
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
//env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
env.put(Context.PROVIDER_URL, "ormi://vlimar-191/j2eeJavaApp1");
return new InitialContext(env);
=========================================================
=========================================================
The line:
TopicConnectionFactory connectionFactory = (TopicConnectionFactory)getInitialContext().lookup( TOPIC_CONNECTION_FACTORY);
is performed without any troubles. But the next line:
TopicConnection connection = connectionFactory.createTopicConnection();
runs into the exception:
javax.jms.JMSException: [PROTOCOL ERROR] JMSRemoteServer[vlimar-191:9127]: "JMS protocol" error, expected "-559.038.735", got "-559.038.734".
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1853)
     at com.evermind.server.jms.JMSRemoteServer.readCheck(JMSRemoteServer.java:754)
     at com.evermind.server.jms.JMSRemoteServer.protocol(JMSRemoteServer.java:769)
     at com.evermind.server.jms.JMSRemoteServer.<init>(JMSRemoteServer.java:92)
     at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:103)
     at com.evermind.server.jms.EvermindTopicConnection.<init>(EvermindTopicConnection.java:63)
     at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicConnection(EvermindTopicConnectionFactory.java:91)
     at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicConnection(EvermindTopicConnectionFactory.java:83)
     at client.MDBClient.sendMessageDirect(MDBClient.java:86)
     at client.MDBClient.main(MDBClient.java:43)
This exception occurs with RMIInitialContextFactory as well as with ApplicationClientInitialContextFactory.
Does anyone has an idea, how to get the JMSConnection from the standalone Java Client out of the AS to the Topic inside the AS.
Thanks in advance!!

I am getting the following error.
==========================================================
C:\>java -classpath c:\ora10g\j2ee\home\oc4j.jar;c:\ora10g\j2ee\home\lib\jms.jar com.evermind.server.jms.JMSUtils -username admin -password oraadmin1 -host localhost -port 3201 stats
Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) (build "040317.1838"), OC4J JMS 1.0.2b
javax.jms.JMSException: [PROTOCOL ERROR] JMSRemoteServer[localhost:3201]: "JMS protocol" error, expected "-559,038,735", got "-485,684,723".
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1853)
at com.evermind.server.jms.JMSRemoteServer.readCheck(JMSRemoteServer.java:754)
at com.evermind.server.jms.JMSRemoteServer.protocol(JMSRemoteServer.java:769)
at com.evermind.server.jms.JMSRemoteServer.<init>(JMSRemoteServer.java:92)
at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:103)
at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:118)
at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:110)
at com.evermind.server.jms.JMSUtils.stats(JMSUtils.java:621)
at com.evermind.server.jms.JMSUtils.main(JMSUtils.java:237)
==========================================================
I only have one oc4j.jar on my system, I renamed the others. Plus, I did a search of all jars for JMSRemoteServer and it is the only one that has it. I have the 10g infrastructure installed and JDeveloper 10g.
Any ideas?
Ben

Similar Messages

  • Using socket and JMS protocol in the same logic for OSB

    Hi frnds,
    In my organization...the only communication protocol used is "socket" protocol. However, I want to use JMS protocol to process incoming messages. Can somebody help me figuring out how to go about it.
    Using some nice OSB blogs, I am able to create the JMS connection factory and JMS queues in weblogic. And that works fine when I select the communication protocol as JMS while creating the BS and PS.
    What should be my message flow when the communication protocol used is "socket" for both BS and PS.
    salil

    Hi,
    Make the BS as JMS and the PS as socket, in the PS's flow do a route for the BS... Then if an external call is made to the PS via socket, it will send a messages to a JMS queue...
    Hope this helps...
    Cheers,
    Vlad

  • Jms Protocol error

    Hi ,
    I am using Oracle 10g version 10.1.3 and Oracle AS JMS Server
    I have a java client that is using the following configuration for JNDI conext.
    // set the environment properties
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.evermind.server.rmi.RMIInitialContextFactory");
    env.put(Context.PROVIDER_URL,"opmn:ormi://vtun-lap.us.oracle.com:6003:home");
    env.put(Context.SECURITY_PRINCIPAL,"oc4jadmin");
    env.put(Context.SECURITY_CREDENTIALS,"apps10g");
    QueueConnectionFactory queueConnectionFactory =util.getQueueConnectionFactory();
    When I execute the following statement
    QueueConnection queueConnection = queueConnectionFactory.createQueueConnection();
    I am getting the following error:
    [PROTOCOL ERROR] JMSRemoteServer[vtun-lap:12601]: "JMS protocol" error, expected "-559,038,735", got
    Object Address: 0x529EDEC4
    Thank you
    Van Sioung

    Your client is using old OC4J JMS classes - you need to set up your client's class-path to point to the .jar files that came with 10.1.3. The exact set of .jar files required for looking up and using OC4J JMS connection factories and destinations over RMI is covered in the 10.1.3 version of the Services Guide - in the JMS Chapter.

  • Creating connection for AQ using JMS protocol

    Hi,
    Could you please provide me the steps to configure custom AQ using JMS protocol.
    Thanks,
    Geetha S

    There's aq backed jms queue creation sample available as part of this thread please use the same to create AQ.
    Re: Creating JMS internal delivery channel ?
    To enable, aq as jms please refer oc4j documentation. There are good pointers here OJMS (AQ JMS) and RAC FAQ (or Best practises guide)
    Please let us know if you need more information.

  • JMS protocol details: How opens connection?

    Hello,
    as for some protocol details of existing JMS vendor implementations, what are your experiences with certain vendors?
    I suppose most vendors use (mainly for performance reasons) a custom (plain vanilla) TCP/IP connection to communicate (compared to higher-level protocols like HTTP or SMTP). Compared to the JMS architecture of message delivery from queues to consumers, does this mean that the consumer opens up a connection (periodically) to the queue to check for new messages, or does the queue server contact (and therby initiate the connection) the consumer of a message?
    I suppose that vendors are implementing this differently (as this is not an issue for the JMS spec). But what are your expriences with JMS vendors on this protocol detail?
    Thanks for any input/feedback.

    As you assert, the underlying protocol is not covered by the spec so each vendor has the abiliy to do as they wish. Some use RMI (which means the JRMP or IIOP protocol), but many write thier own protocol over straight TCP sockets to eliminate the overhead of RMI. Most of these are simply going to be writing objects back and forth over the stream. Many vendors have pluggable transports like HTTP.
    As for your second question, most vendors I'm aware of open persistant connections. However, I know at least one can operate in "off-line" mode.

  • JMS protocol with AXIS Adapter

    Hi,
    I need to configure the sender AXIS adapter to access SonicMQ JMS queues via Open LDAP. I looked at the AXIS Adapter documentation and no examples are provided to access SonicMQ via OpenLdap.
    I do see the documentation to access the JMS providers directly by specifying the URL as "jms://ABCD"
    but what i am looking for is to access the JMS objects via LDAP. The standard SAP JMS Adapter has the functionality to access JMS via LDAP. but i need to use AXIS adapter for WS-Security
    Any help is greatly appreciated
    Thanks
    Chandra

    Hi Chandra,
    As far as I know, this is not directly supported via SOAP Axis Adapter. But one question which I would like to ask is are you trying to configure WS Security using Axis Handlers or you are trying to use the WS Security provided by SAP PI i.e. configuring Security Profile in the Sender Channel?
    If you are trying to do it with Axis Handlers may be you can try using the Adapter modules specified in this link which can be used tto call Axis Handlers. <http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm>. Although documentation says that this is supported for SOAP adapter but you can still try as the message returned is still a valid AF message.
    Best Regards,
    Pratik

  • XI 7.0 NW 2004s install - JMS Errors in applications.log & defaultTrace

    We just installed XI 7.0 NW 2004s.  The installation of XI 7.0 NW 2004s is a lot simpler than XI 3.0 NW 2004 since the Template installer runs most of the post installation steps.
    However, there are a few issues that I am encountering that i did not see with XI 3.0 installations.  The installation is on Windows 2003 server and SQL server 2005.
    Checking the applications.log file through Visual Administrator LogViewer, I see that the Applications log is filing up every few seconds with the following repeating errors:
    Message -
    Exception on server occured! Internal error.
    Additional Information -
    Category : /Applications/JMS
    Message ID : 001422B146E800750000070D0000013000041A845FCB659B
    Source Name : /Applications/JMS
    Thread : SAPEngine_Application_Thread[impl:3]_26
    Application :
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : d16ec30026fd11dbb450001422b146e8
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : com.sap.jms.client.session.Session
    Resource Bundlename :
    Session : 0
    Source : /Applications/JMS
    ThreadObject : SAPEngine_Application_Thread[impl:3]_26
    Transaction :
    User : J2EE_GUEST
    Message -
    Exception on server occured! Cannot write to transaction log TXf48.tx.
    Additional Information -
    Category : /Applications/JMS
    Message ID : 001422B146E800750000070A0000013000041A845FCB4CC8
    Source Name : /Applications/JMS
    Thread : SAPEngine_Application_Thread[impl:3]_26
    Application :
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : d16ec30026fd11dbb450001422b146e8
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : com.sap.jms.client.session.Session
    Resource Bundlename :
    Session : 0
    Source : /Applications/JMS
    ThreadObject : SAPEngine_Application_Thread[impl:3]_26
    Transaction :
    User : J2EE_GUEST
    In the defaultTrace.trc file, i see the JMS error too:
    Message -
    Error From List = javax.jms.JMSException: Internal error.
         at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
         at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:1808)
         at com.sap.jms.client.session.Session.rollback(Session.java:300)
         at com.sap.jms.client.session.Session.close(Session.java:158)
         at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
         at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
         at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
         at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:262)
         at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:361)
         at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
         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:95)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
    Additional Information -
    Category : /Version
    Message ID : 001422B146E8008B000007340000013000041A847A0F6CB9
    Source Name : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
    Thread : SAPEngine_Application_Thread[impl:3]_98
    Application :
    Argument Objs :
    Arguments :
    Dsr Component :
    Dsr Transaction : d815880126fe11db9edc001422b146e8
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 0
    Relatives : /Version
    Resource Bundlename :
    Session : 0
    Source : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
    ThreadObject : SAPEngine_Application_Thread[impl:3]_98
    Transaction :
    User : J2EE_GUEST
    This is filing up both the applications.log and defaultTrace files.  I cannot find any information through Service Marketplace.  Has anyone encountered this issue?  This is new installation - no messages are running on it so I am not sure why there is a JMS error.
    Regards,
    Jay

    Hi Jay,
    The exception means that the JMS Provider is not able to write to the transaction log file upon close of a transacted session. In NW04s, JMS transactions are stored as files on the local file system. The location of the root folder where the transactions are persisted is configured by the JMS service property "transactionStorePath". You can check its value through the Visual Administrator -> Services-> JMS Provider -> Properties. Please check if it contains a correct directory path and that nothing prevents the server from writing to this path - access rights, enough disk space, etc. If there is something wrong with the path, you can change it, save the change and restart the JMS provider service for the change to become effective.
    You can also have a closer look at the server trace file: the root cause of the above exception is some other exception, probably I/O one, and it should be logged somewhere in adjacency to the JMS exception.
    There is ongoing JMS communication even in a new server installation - in this case (judging from the stack trace) the component that performs this JMS activity is the timeout service.
    Hope this helps,
    Stoyan

  • Trouble with a JMS proxy listening to a distributed topic

    Hi all,
    I've setup an ALSB cluster with 1 admin instance and 2 managed instances (m01 and m02).
    I've also configured 1 distributed topic A and defined the two below proxies:
    - proxy P1 is a http proxy that publishes a message into the distributed topic A. The proxy uses a business service with jms protocol and endpoint uri:
    jms://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303/my.ConnectionFactory/DistributedTopicA
    - proxy P2 is a JMS proxy listening to
    jms://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303/my.ConnectionFactory/DistributedTopicA
    that logs the received message and writes it to file.
    The strange behaviour is that on the managed m01 log file I see the message received from P2 but also on the managed m02 log file I see the message received from P2.
    So I'm sending out 1 message and receiving 1 x managed that is total = 2.
    This strange behaviour is also confirmed from the fact that I see on the file system 2 files and not only 1.
    I thought it was a problem concerning the config of business service that publishes message into the distributed topicA; but I tried with an external 'normal' java JMS subscriber that listens to t3://wasdv1r3n1.dev.b-source.net:7301,wasdv1r3n1.dev.b-source.net:7303 and it works properly: it receives only 1 message.
    I'm trying to understand where is my fault.
    Do you have any idea ?
    Thanks in advance
    Patrizio

    If you publish a message to a topic, all the proxy that subscribed to this topic will receive the message. If you want the message to be processed by only one managed server you can publish to a queue instead.
    Gregory Haardt
    ALSB Prg. Manager
    [email protected]

  • Oracle Service Bus 10.3.1 proxy consuming jms (AQJMS)

    Hi,
    I need to use AQJMS with Oracle Service Bus proxy.
    We have an installation with WLS 10.3 and OSB 10.3.1 and another with WLS 10.3.1 where I defined a JMS Foreign Server like appears in the documentation http://download.oracle.com/docs/cd/E12839_01/web.1111/e13738/aq_jms.htm#JMSAD565.
    I need support to how to define the URI at the OSB configuration.. jms://server:port/XAQueueConnectionFactory/QueueName... because I tried a lot of ways and can't make it work.
    Thank You in Advance...
    Juan Pablo

    Hi,
    Because I want to use the jms protocol... because if I change AQJMS with another JMS Provider the only thing that I must change in OSB is jms://server:port/CF/Q
    In SOA Suite 10.1.3.x I use JMS Adapter for this...
    Thank You.
    JP

  • OSB JMS Transport configuration

    I have a need to pass a reply-to destination from one external process (the producer) to a second external process (the consumer), with the design supporting flexibility for changing destinations within the OSB pipeline at a future time. To enable this functionality, the following jms transport was designed on the OSB 10gR3:
    external producer--->|---q1--->jmsTransProxy---->q2---|--->external consumer
    The jmsTransProxy is configured with request/response text message types, jms protocol, Get All Headers yes, Is Response Required enabled, and Response Correlation Pattern CorrelationID.
    In the Request pipeline of jmsTransProxy, a single stage is configured to Pass All Headers through Pipeline.
    In the Response pipeline of jmsTransProxy, a single stage is configured to Pass All Headers through Pipeline.
    When the external producer sets the JMSReplyTo header, I expected that this header would be passed from q1 to q2 so that the external consumer would receive it. The message payload is correctly received by the external consumer along with the JMSCorrelationID, but not the JMSReplyTo header information. By examining the logs, I can see the header information is received correctly in the request pipeline, but is not available from q2.
    What is the correct solution to have the JMSReplyTo information pass through to the external consumer?

    Thank-you for your tips.
    I have revised the pipeline as you indicated and more of the headers pass through, but not the JMSReplyTo header. Because the user headers are passed through, I can use get/setObjectProperty on the message to realize the functionality required (though this is a workaround).
    current configuration:
    external producer--->q1--->jmsProxy--->jmsBusiness--->q2---> external consumer
    jmsProxy parameters:
    service type: messaging service
    request message type: text
    response message type: none
    protocol: jms
    endpoint uri: q1
    get all headers: yes
    destination type: queue
    is reposnse required: disabled
    etc.
    jmsProxy request pipeline:
    publish to [ jmsBusiness ]
    request actions: set transport headers for [ outbound request ] (pass all headers)
    jmsBusiness parameters:
    service type: messaging service
    request message type: text
    response message type: none
    protocol: jms
    endpoint uri: q2
    destination type: queue
    is reposnse required: disabled
    etc.

  • Oracle Service Bus - Alert Destination on JMS Queue

    Hi Guys, I have been trying to create Alert destination with email destinations and have been successful. The problem that I am facing now is when I am trying to create an Alert Destination to a JMS Queue. I am using the correct format that you generally use for a JMS URI. -- jms://<host>:port/<factoryJNDIName>/<QueueJNDIName>
    This, is the scenario. I have an Alert Rule specified in one of my proxy services, which basically sends out the fault to the Alert Destination as configured above. This alert will be triggered
    when the error count in the Proxy Service exceeds 3. But I do not seem to be getting the messages into my queue which I am monitoring from weblogic console.
    However, I do get all the messages that I trigger from a separate biz service that I had made just to test the authenticity of my JMS Configuration.
    Any one experienced this before? Specifically related to SLA Alerts/Alert Destinations configuration on JMS Queues?

    Thank you for your response. Well, Let me see if I can explain in a clearer way.
    As you already know, Alert Destination (used for SLA Alerting for example) in OSB have two destinations that you can configure. One - an email recipient(s), who will get the email when the alert (configured in your proxy service and bounded to this alert destination is triggered) . Two - a jms queue, where the same "alert" can be pushed to.
    My question is - I have configured the JMS Destination on the Alert Destination configuration page as such - jms://localhost:7001/testConnFact/testQueue
    (testConnFact and testQueue being the JNDI names of the connection factory and queue respectively configured in weblogic server)
    When the alert (configured in the proxy service) is triggered, (like maybe, due to the error count being more than 3), I should be getting the message pushed into the queue, because, that's the destination I have set in this ALERT DESTINATION.
    I am NOT getting it however.
    On a diff note, when I am creating a business service in OSB on a JMS protocol giving the URI of the queue created in weblogic, I AM getting the messages into the Queue. This, I had done, to test whether my configuration for the queue is correct or not.
    So it seems that Queue configuration on weblogic is correct, however, the alert destination is simply not pushing the messages to the queue.
    Hope this was clear.

  • 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

  • Osb jms query

    Hi,
    I have generic jms client code as part of my web application sits on weblogic 11g, which publishes the text message file to different jms providers based on configuration (set the file path to be published, connection factory and destination info etc). Currently it works fine with weblogic JMS and websphere mq. Now I need to test with OSB.
    So how can I use osb here? Do I need to use osb proxy service to publish the message to either weblogic JMS or MQ?
    Can I configure osb in some way so that my generic jms provider will publish the message using osb?
    Does OSB has default JMS Provider or we need to always plug in the external jms provider like mq?
    As I am new to osb it will be very helpful your inputs on this. Appreciate your inputs.
    Thanks,
    Sri.

    Hi-
    I have generic jms client code as part of my web application sits on weblogic 11g, which publishes the text message file to different jms providers  I assume you clinet posts the msg to weblogic queue
    So how can I use osb here? Do I need to use osb proxy service to publish the message to either weblogic JMS or MQ?You have configure a Business Service with JMS protocol providing the end point URL.
    refer this doc for the same http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html
    Does OSB has default JMS Provider or we need to always plug in the external jms provider like mq?OSB supports JMS transactions
    As I am new to osb it will be very helpful your inputs on this. Appreciate your inputs. These docs could help you to explain about OSB
    http://www.oracle.com/technology/pub/articles/jumpstart_for_osb_development_page_3.html
    http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15020/toc.htm

  • SOAP over JMS sample BPEL Process

    Hi ,
    Does any one has the sample BPEL Process code for SOAP/JMS protocol bindings on Oracle Weblogic server ?
    This is very urgent , any help is appreciated !
    Regards,
    Sam

    Have the same requirement.

  • Suggested JMS configuration

    Hello, experts.
    We recently started using JMS rather extensively and had bumped into a strange problem with our J2EE app running on SAP WebAS. After a while all JMS queue processing stops and we see JMS buffer overflow exception in the logs:
    com.sap.jms.protocol.BufferOverflowException: BufferOverflow
         at com.sap.jms.protocol.message.MessageRequest.setJMSRedelivered(MessageRequest.java:733)
         at com.sap.jms.server.destinationcontainer.messagequeue.impl.ptp.QueueConsumerViewImpl.peek(QueueConsumerViewImpl.java:138)
         at com.sap.jms.server.destinationcontainer.agent.QueueAgent.processConsumer(QueueAgent.java:119)
         at com.sap.jms.server.destinationcontainer.agent.QueueAgent.run(QueueAgent.java:92)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:140)
    However, messages delivered to the topic subscribers seem to continue to work fine. Only queues stop working.
    Should I tune up some JMS Provider parameter to fix this problem?
    Here is the code snippet on how we take messages off the queue:
    if(qreceiver==null)
      qreceiver = qsess.createReceiver(q,receiveString);
    message=(BytesMessage) qreceiver.receiveNoWait();
    if(message!=null) {
    message.acknowledge();
    final Serializable obj=processMessage(message);

    Follow the below procedure for creating a connection factory/queue/topic
    Visual Administrator->Services->JMS Provider
    Then  create a connection factory and queue .
    Get back in case of some issues.
    Regards.

Maybe you are looking for

  • New music skipping

    I've had my iPod for a while now. It's a 30GB. Recently, I've had a problem - with all of my recently uploaded music (uploaded from CD to iTunes, then to iPod), it jumps to the next track when there's still 10 seconds left in my current track. It's o

  • Can't create a sign in seal

    Afternoon all XP SP3 I downloaded some microsoft updates this morning, including IE8. After updating I ran ccleaner to tidy up the registry. My sign in seal on BTY has disappeared and I don't seem to be able to create a new one. Any suggestions? TIA

  • After upgrading my 4s to iOS 7.0.2 I can't receive iMessages.  Help?

    I've seen all people talk about turning iMessages off and back on...doesn't fix it.  I've seen the recommendation to reset the network settings...doesn't fix it.  I've seen the recommendation to turn the phone off for 3-5 minutes and turn it back on.

  • Publication and commentaires

    i have a formulaire , i want if i click 'post comment' i have this ??

  • Integrated SD/mmc card reader

    I have a strange problem with the integrated sd/mmc card reader on my laptop. I know I have everything correctly configured and the needed modules loaded because I can use a 16MB and a 128MB SD cards without any problem. When I insert any of them ude