MAX 232 communication with microcontroller GUI
Hello,
I am new to embedded world and new to lab windows. I am doing one project ( Checking an errors and scrach on CD,So i divide CD area into different square blocks , i want to select some CD blocks to check ) in which i have to control two stepper motors which further control vertical and circular deflections. I am using Atmel AT mega32 microcontroller. I wanna construct one GUI in which i can select some square block for checking and some part i can leave by clicking or unclicking,further which can show serial communication parameters, postion, angle of motor deflection..I wrote a programm in atmel studio. How can i construct such a GUI in Lab Windows and how do i make a connection between these two programms.
Thanks millions.
Regards:
Singh
Hello Singh,
I'm almost sure no CVI program can run on Atmel microcontroller, but since you have already created the mc program with proprietary compiler, I suppose your problem is now in interfacing mc application with an external PC that monitors test execution.
Since you mention MAX232, I suppose you plan to perform communication between the microcontroller and the CVI program over the serial channel. CVI comes with a native RS232 library which permits you to easily configure and open a serial communication channel and write/read over it. Searching with the Example Finder (Help >> Find examples... menu item) with 'serial' keyword will return you with some basic serial communication examples that you can use to start developing your application.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?
Similar Messages
-
TCP/IP listener fucntion not communicating with Microcontroller
I am Using OEM controller CSP 2008 having Ethernet Port .
I tried Labview 8.5 programming for communicationg using TCP /IP pallette functions TCP Listener read and TCP Read but I am not getting data . I used Labview examples Data Client but it shows the "serial port buffer overflow error"
can u help me in this regardsIf you are referring to section 5.3.4.4, I believe that LabVIEW is the server and that your device is trying to connect to LabVIEW. The documentation states that the device will try to connect to the server, and then retry every 100 ms if it fails to connect.
You would want to look at the LabVIEW TCP server examples, and make sure that you match the server port value in the device and the LabVIEW example.
To make things simpler to start, try using UDP. Set the device for UDP and then use the LabVIEW UDP receiver example (again make sure to match the port numbers). UDP does not require a connection, so the testing should be much simpler. If you want to route the data over the internet, you will need to use TCP.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness -
MAX don't release LAN connction while communicating with Agilent 86122A
Dear guys,
Yesterday I met a communication issue while talking to Agilent 86122A via LAN.
It showed I cannot run MAX before launching LabVIEW; otherwise I'd have trouble in send commands in LabVIEW.
I doubt if MAX MAX don't release LAN connection while communicating with Agilent 86122A?
Please advise,thanks.
I debugged as below:
1, Ping the IP of Agilent 86122A shows internet is OK.
2, I restarted the instrument, LabVIEW reported the same error code.
3, I restarted PC, launched LabVIEW first and run the code (*IDN?), everything is OK!!!
4, Again, I send *IDN? With MAX, and it seemed to be OK.
5, hit x to close MAX and then run the same and simple code (*IDN?) in LabVIEW, but it reports error code -1073807346.Caglar,
The documents you mention ahould include the proper prcedure for using this hardware in LabVIEW. Here are my recommendations:
The version of NI-VISA you mentioned is not valid. The most recent version is 4.6.2. I would recommend ugrading if you do not have this version. After the upgrade,ensure that tulip is enabled as well as the other settings and see if this helps.
When talking about the instrument, the biggest concern that usually is relevant with 488.1 is that it will not respond to *IDN?. In your case, it looks like it does, and should work as 488.2 is backwards compatible. It seems to me, the issue is still with the 82357A, and we have not yet reached the voltmeter.
In order for NI-VISA to work with your device, NI-VISA must be the primary visa driver.
Hope this helps, let us know how the upgrade turns out. If you continue to have issues, take some screenshots of the preferences in MAX and upload them on the forum.
Regards,
Peter Flores
Applications Engineer -
Communication with motor control using RS-232
I need to use labview to communication with a stepper motor drive using the serial port RS-232. Could someone please get me started I'm not sure if a should use VISA or instrument I/O. And if I use one of those, how would I set it up?
Hi Phil,
Outside of LabView, how do you communicate with or control the motor drive? If you are able to use software like HyperTerminal or Procomm, then using the VISA serial communication tools will be the simple way of implementing your solution.
Here are some links which may provide clues on how to proceed. You can also do a search on VISA Serial communication.
Happy wiring!!
JLV
LINKS:
Link 1: Although this one talks about an error, it does provide instructions on how to setup the VISA session:
http://forums.ni.com/ni/board/message?board.id=170&message.id=99660&query.id=0#M99660
Link 2: Here are some examples: (good starting point):
http://forums.ni.com/ni/board/message?board.id=170&message.id=65873&query.id=0#M65873
Link 3: more info:
http://forums.ni.com/ni/board/message?board.id=170&message.id=86971&query.id=0#M86971 -
Help me about communicating PIC microcontroller with Labview
Hi everybody!!!!!!!!
I have a few issues about data acquisition in Labview,so i need your instruction.
Right now,I want to practise a project about the serial communication with PIC16F877A microcontroller ( a microcontroller of Microchip,40-pins,already integrated 10 bit A/D module,with 8 channels) ,developing the user interface in the Labview 8.0 software.
My goal is data acquisition from multiple sensors:such as LM35 temperature sensor and a pressure sensor,analyzing and display the data-time graph in Labview
I intend to use ANx-pins (analog input pins,having 8 pins) in PIC16F877A,connecting to data-pin from sensors,then I use the TTL outputs of the PIC in combination with a MAX232 serial driver chip.As you know,the mAX232 simple converts the TTL outputs to RS232 outputs and forword them on.
It is of no use to be able to collect various sensor readings into the PIC if there is no-way to transfer that data to a location where a user can use it.To solve this problem,I choose to implement a standard RS232 serial link between the PIC MCU and my personal computer (using DB9 COM terminal)
This meant that I would need to initialize the A/D converters each time I want to read from a different A/D sensor because the two sensor dit not share a common configuration.
My troubles is how to transfer data from sensors through PIC MCU to Labview,using RS232 standard,how to program for Labview,which I have to use:files of Serial communication in Serial.VI,or DAQ funtions in DAQ pallete?
P/Sorry,my English is not good,expecting your sympathy!
If it is impossible,you could send me an instruction or the same examples in detail,my mail:[email protected]
THANK YOU VERY MUCH!!!!!!!!It would be best if you were to re-post this to the LabVIEW forum.
Regards
Ray Farmer
Regards
Ray Farmer -
"An error occurred in the communication with the BW server"
Hi, when I open BEx Analyzer and try to connect to my BW server to run a query, I get this message, "An error occurred in the communication with the BW server".
Can someone help me.
thanks
Pat.If it's happening consistently, it could be a problem with your local m/cs MS office and/or SAP GUI.
If it was working before:
1) Uninstall SAP GUI and MS office.
2) Install MS Office and SAP GUI...then try to connect to BW.
Good luck, BB -
[Forum FAQ]How to upgrade Windows Server 2008 R2 with a GUI to Windows Server 2012 Server Core
We found that some customers willing to upgrade Windows Server 2008 R2 GUI to Windows Server 2012 Server Core recently. This article provides detailed steps to perform the upgrade.
Analysis
Upgrading from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 with Server Core directly
is not supported. If you do that, you will receive the error message below(Figure 1) in Compatibility report:
Figure 1.
In these scenario, you can upgrade to Windows Server 2012 firstly. After the upgrade process is completed, you can switch freely between Server Core and Server with a GUI modes.
Produces
You can follow the steps below to perform an upgrade from Windows Server 2008 R2 with a GUI installation to Windows Server 2012 Server Core mode:
1. Upgrade to Windows Server 2012 with a GUI mode
1) Firstly, please boot into Windows Server 2008 R2 with a Windows Server 2012 installation DVD inserted.
2) Select the operating system you want to install with a GUI mode.
We can see 2 options (Server Core Installation or Server with a GUI) for each operating system version. (Figure 2)
Figure 2.
Note: Please make sure you have enough disk space on system partition. Or you will get such an error in Compatibility report.(Figure 3)
Figure 3.
After the Compatibility check, the installation will continue. It will take several minutes until upgrading is done.(Figure 4)
Figure 4.
2. Switch the GUI mode to Server Core
Method 1: Using Server Manager
1) Open Server Manager, click
Manger and select “Remove Roles and Features” to start the
Remove Roles and Features Wizard.
2) In Features,
uncheck the box next to the “User Interfaces and Infrastructure” option, and then click “Next”. (Figure 5)
Figure 5.
Now tick the “Restart the destination Server automatically if required” box, then click “Remove”. (Figure 6)
Figure 6.
Method 2: Using Windows PowerShell
There are multiple ways to remove the GUI via Windows PowerShell, we introduce the way of using the ServerManager module.
You can also run the commands in Windows PowerShell with an administrator to remove the GUI feature:
“Import-Module ServerManager”
“Uninstall-Windowsfeature Server-Gui-Shell –Restart”
or
“Uninstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra –Restart”
It will take a period of time to remove the GUI feature and reboot. When the system boots up, you will get into the Windows Server 2012 with Server Core mode. (Figure 7)
Figure 7.
More information:
Switch between Full and Server Core in Windows Server 2012 using PowerShell 3.0
http://blogs.technet.com/b/puneetvig/archive/2012/10/16/switch-between-full-and-core-in-windows-server-2012-using-powershell-3-0.aspx
Windows Server Installation and Upgrade
http://technet.microsoft.com/en-us/windowsserver/dn527667.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.Hi,
Brian is right, for mange the Server 2008r2 sp1 we recommend use the Windows 7 or 7.1 platform.
More information:
Remote Server Administration Tools for Windows 7 with Service Pack 1 (SP1)
http://www.microsoft.com/en-us/download/details.aspx?id=7887
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
As most of us are aware xMII does not support RS-232 communication. Recently some customers have come up with requirements of interfacing weigh scales to SAP.
Most of these weigh scales have only the RS-232 interfacing option. (I am not sure if these could be OPC compliant as well.. Some higher and expensive ones come with a software version which I guess can be configured to write a file or some come even with a Database Option.)
With xMII 12 would it be possible, lets say, to write a custom action 'RS-232 Listner' which could allow this to happen?
What are SAP's thoughts on this?Yes, this is a common request. I think in part because sometimes customers get the impression that xMII can do this from the "sales force" and can do it "easily".
We had some luck with this in the past.
Sometimes what we have seen in the past, is that the rs-232 devices have a transmit or send button that sends a signal back to a pc that the device is attached to. If you use an application like WinWedge that takes the signal from the device and decodes it to text, it can be used to get the information. WinWedge typically comes with handheld USB or Serial barcode scanners. It's main purpose is to take the signal from the device and "pop" it into the active window's cursor location. So if you scan a barcode with Word open and active, the barcode scanner sends the signal to WinWedge on the PC, WinWedge translates the signal to text and throws in at the cursor location.
If your cursor is in an HTML form input box, and you can capture the data as descibed above, now you can use the data via Javascript and pass it to an applet on the page. -
i must read and write data and command from a custom card with a labview vi.
can someone send me documentation or example of serial communication
protocol that can be implemented in labview?
thanks.
davidin what site can i search example of rs 232 communication protocols or
drivers ?
david.
"PdB_Serenity_nl" ha scritto nel messaggio
news:[email protected]..
> Good examples of drivers to support RS-232 devices can be found on
> this site.
> If you bought the card, you can ask the supplier for the
> protocol/command set.
> If it is an internally developed device (we do that frequently) the
> complexity/robustness of the protocol will depend on what the task of
> the device is (and under what conditions, lab is quite different from
> plan-operation). And as long as this will not be sold as an open
> commercial system to the outside world, you can use your own protocol.
> Sorry, have no example. -
Communication with modbus devices
Hello All,
My name Peter, I am currently exploring what LabVIEW has for instrument communication. I have explored a little on NI-Visa and used it for instrument communication through USB and Ethernet. My next task just now is to see how I can communicate with Modbus devices. I have done some background reading on modbus communication protocol and now have some level of understanding of what it is about. I hope to understand more as I continue to read more materials.
I came across an NI-Tutorial titled Connect LabVIEW to any PLC with Modbus. It is about communicating with a networked PLC using modbus. I followed all the steps described for creating Modbus master I/O Server, Binding shared variables to Modbus Address through the I/O Server and writing to Modbus Addresses in LabVIEW. On running my VI to deploy the shared variable, the following error occured.
Can anyone please guide me on what to do because I do not know exactly what is going ON. I engaged in this excercise with the hope of getting to understand more about Modbus communication and then see how I can apply thesame idea to communicate with the Modbus device available in my Laboratory. Please note that I do not yet know much about modbus communication and I am just learning about it now. I do not have any PLC connected to the network. Could that be the reason for the error? If anyone has got any other relevant document to help me get started with modbus communication I will be happy to have them posted here.
Thanks very much for taking time to read through my post message. Hope to hear a quick response from you.
Regards
PeterHi SmithD,
I would like to say thank you very much for making out time to respond to my queries. I have done as directed but still not getting result. Following the wire mode port setting configuration, I stopped the process and then selected the RS485/wire4 as the wire mode. On running the VI, an error pops up with the information that the Visa resource is Valid but the port cannot be accessed. I noticed that If I undeploy the shared bound variable the error does not pop up anymore. I concluded that maybe I was not supposed to have added the VISA configure Serial port in the first place.
Kindly tell me what to do.
My task is to read the holding register from a Modbus device. I have the register map with me, and know the TCP and RTU settings for this device. After the attempts I have made so far I was forced to believe that perhaps the device was not responding. I then resolved to using the QModbusMaster which was previously used to read the holding register. For reasons I don’t not know, It worked well with the TCP communication and returned an error that read " slave threw exception > unknown error". With that, I am now sure that the device is functioning properly, at least with the TCP.
Having obtained result from the TCP using QModbusMaster application, I want to simply do the same using LabVIEW.
Some few questions for which I would want to ask for clarification are:
1.) When using the Modbus Library, do I need to create both master and slave instance to be able to read the holding register? My attempt was to create a Master instance with the RTU parameters. The starting address and number of registers were specified at the input terminals of the Read Holding Register VI. This VI immediately followed the Create Master Instance VI. I was expecting that that would read the information contained in the specified registers and output it at the register value terminal. One challenge with this attempt was that with RTU it didn't work. I tried selecting TCP as the VISA resource. But the device was not showing on the list. I went to MAX to create a new VISA TCP/IP resource under the network devices but MAX could not detect the presence of the device. I am now thinking maybe the device is not supported by NI-VISA and so it will not be possible to use the Modbus Library with it.
2.) If the device is actually not compatible with NI-VISA, can DSC I/O server be used to read the information on the holding register?
3.) Do I need an intermediate device between a Modbus device and the PC to be able to read its holding register?
Please if anybody has got a good suggestion as to what to do to get my task achieved, kindly leave me a post.
Thanks
PETER -
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 SridharHi 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 -
Using Labwindows CVI Version 10.0.1 USB communication with FTDI FT2232D to unit under test.
Communication with unit under test works fine in hypterminal after I downloaded virtual driver from FTDI site.
Never done any USB communication before in LabWindows CVI. What functions can I use in labwindows CVI?Since the device presents itself as a COM port (pretty standard with the FTDI chips) you should be able to use the RS-232 library in CVI. OpenComConfig() will open a connection to the device, ComWrt() will write data to it, and the various ComRd() functions can be used to read the responses back.
-
MAX communicates fine with GPIB Instrument, LV Standalone Exe Front Panel Control Does Not See It.
I have succesfully created a LV standalone EXE which communicated with external GPIB instruments. I used LV 7.1 for this. I upgraded DAQMx to 8.0 on the development machine and also the target which runs the Exe. The EXe runs fine on the development machine but when run on the target laptop, the front panel control fails to see the GPIB instrument. On the target, in MAX I successfully setup communication with the GPIB instrument. Is there some incompatibilty with DAQMx 8.0 and LV7.1? An additional piece of info here: when upgrading to DAQMx 8.0, I selected the installation support for LV 7, 7.1 and also 8. Could this be where the problem lies?
Thanks
PeterThe GPIB code is actually an IVI driver made for a Rhode and Schwarz TRMS meter. Its the standard VISA Read/Write, nothing out of the ordinary. I'm using a USB-GPIB-HS adapter to communicate with it. Like I mentioned, the VISA instrument control drop down list on the front panel of the Exe does not list any GPIB instruments, all that is listed is ASRL...1, ASRL...4, and ASRL...10. In the EXE that used to work, there were no ASRL... references listed. What was listed was the GPIB0...INSTR...20, COM1, and the parallel port. So something weird is going on now, somehow effected with the load of DAQMx 8.0.
Pete. -
I am having a problem communicating with the HP4194A. I get an time out error when I Querry *IDN?. The HP4194 uses HPIB.
Is there something I can do to get it to recognize it?If you are using a National Instruments GPIB board, then you should have a program called the Interactive Control on your computer (ibic.exe) that comes with the driver.
Open ibic (it looks like a dos window) and run the commands that are listed on our web site at:
http://www.ni.com/support/gpib/max/ibic.htm
If the ibln command says your device is listening, then it may just be that the device doesn't respond to the *IDN? command, but rather to some other type of identification command. -
Direct communication with SIEMENS PLC
I am trying to establish a direct connection with a SIEMENS S7 PLC. I donot want to use any card or profibus etc. I want to do it through the Serial Port.
I have used the IA server kit when communicating with SIEMENS S5 for which I used AS511 protocol. I would like to know if there is any such protocol for S7.
Please Help!!Hi.
I'll try explain it.
All Simatic S5 PLc's processors (CPU90 ,CPU100) have got serial (current loop converted to RS232) physical inteface as standard.
You can program PLC's or communicate with its by AS511 protocol.
S7 Simatics processors (CPU 3xx, CPU4xx) haven't got RS232 interface as standard. RS 232 interface occurs in forms of interface module connected to the rail (slot) and doesn't serve any protocol (simple chracters exchange).
You can program PLC, observe/modify I/O, variables, etc. only by standard RS485 interface using protocols MPI or PROFIBUS (PPI/MPI for Simatic S7-2xx CPU's).
You can try exchange data between Labview and S7 PLC by serial in characters form, but it is very difficult and inconvenient (you have to w
rite own driver for Labview and program for S7).
Another solutions:
1.PROFIBUS card for PC with drivers for Labview (I don't know if they exist)
2.connection thru OPC server (PLC->PC by PROFIBUS card->OPC server->Labview by Datasocket)
I think second solution is more comfortable.
See also:
Connecting LabVIEW to an OPC Server through a DataSocket Connection
Regards.
Romek.
Maybe you are looking for
-
When I define my R/3 system in XI SLD,I got CIM_ERR_ALREADY_EXISTS message
<b>CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_BCSystem.CreationClassName="SAP_BCSystem",Name="BRP.SystemNumber.0020270914.SystemHome.sapprddb"</b> Before I defined R/3 system in XI SLD wrongly, after that I delete from Business and technica
-
Button on SWF to export it in PDF
Hello All, We have created XCelsisus dashboard and have published the SWF of this dashboard to InfoView in BO. The Users want that they should be able to execute the SWF and at the same time, they should be able to download a PDF version of this SWF
-
O.k. I can recieve and send AOL on my HP just fine. BUT on my 4S, Ipad and IMAC, no go. Cannot recieve AOL messages or send out to AOL members. Itouch without an ios5 update works fine. It has to be Ios5 problem. Genius could not help but said look o
-
Hello: I need to send emails by groups including some magazine with Director, like magazine GamaSutra Daily. It seems like a web page inserted in the client mailing software (outlook Express,...) Can you tell me how to do this with Lingo, please? Tha
-
How can I select multiple clips in the event browser?
I can't seem to figure out how to do something that should be pretty simple. I want to select multiple clips in the event browser that aren't next to each other. Right now it's only letting me select the two clips with every other clip in between. Is