Qualys vulnerability Scanner caused JMS Server to reset connection
Hi
Our customer is doing vulnerability scanning for our product. We are using Oracle AS 10.1.2.0.2.
When customer ran Qualys vulnerability scanner, our application stopped working. While debugging we found that Oracle JMS server closed its connections.
We got following error in jms.log under OC4J
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:173)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at java.io.DataInputStream.readInt(DataInputStream.java:443)
at com.evermind.server.jms.JMSRequestHandler.readCheck(JMSRequestHandler.java:269)
at com.evermind.server.jms.JMSRequestHandler.protocol(JMSRequestHandler.java:282)
at com.evermind.server.jms.JMSRequestHandler.run(JMSRequestHandler.java:124)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
09/09/08 02:08:16 protocol
javax.jms.JMSException: [PROTOCOL ERROR] JMSRequestHandler[2:10.129.246.48:33729]: "JMS protocol" error, expected "-559,038,735", got "1,735,489,335".
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1854)
at com.evermind.server.jms.JMSRequestHandler.readCheck(JMSRequestHandler.java:272)
at com.evermind.server.jms.JMSRequestHandler.protocol(JMSRequestHandler.java:282)
at com.evermind.server.jms.JMSRequestHandler.run(JMSRequestHandler.java:124)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
This shows that JMS server is prone to denial of service problem. Can any one have any idea, is this is some known issue. Or how to debug the issue.
HI,
Have a look into SAP Notes 804124, 807000
Check the JMS drivers are installed or not?
Thnx
Chirag Gohil
Similar Messages
-
Vulnerability Scanner causes Flash Remoting Status Description to return null
I'm having an issue with Flash Remoting that we have been able to track down as being cause by our vulnerability scanner. About 2 minutes into the scan process it causes flash remoting to fail and it does not recover until the ColdFusion Application Service is restarted. What's worse is that I'm not seeing any errors in the log to identify that there is a problem and it's a error the end user is seeing and reporting to notify me of the issue.
Any thoughts of what might be causing this? Is there any logging I can enable to help troubleshoot / identify when I have a problem?
Bellow is a modified snippet of the code we are using to do the call. In alert("Error while calling cfc:" + stat.description); is where we are seeing the error.
function getCurrentDate()
mx.managers.CursorManager.setBusyCursor();
var connection:mx.remoting.Connection = mx.remoting.NetServices.createGatewayConnection("http://#cgi.HTTP_HOST#/flashservices/gateway/");
var zService:mx.remoting.NetServiceProxy;
var responseHandler = {};
var dmLAST_MOD_DATE= dmLAST_MOD_DATE;
responseHandler.onResult = function( results: Object ):Void
mx.managers.CursorManager.removeBusyCursor();
_root.sessionTime = 0;
_root.realSessionTime = 0;
responseHandler.onStatus = function( stat: Object ):Void
mx.managers.CursorManager.removeBusyCursor();
alert("Error while calling cfc:" + stat.description);
zService = connection.getService("X.Y.z_dao", responseHandler);
zService.getToday();
I am runnning ColdFusion 11 on Win Server 2012 R2 and IIS 8.5.Did you get a resolution to this? I'm having the same
issue. -
Hi Cisco Experts,
Good day! We preparing to implement the Qualy Vulnerability Scanner to our VoIP network. However, we need to verify what Cisco UC devices are supported. The currently UC devices installed on our VoIP network are Cisco IP phones, Routers (2821/2811/2921) and Cisco Unified Communication Manager (CUCM).
Thank you.
Best regards,
RJThe description of the vulnerability specifies IKE aggressive mode. So my first question would be whether you are using IKE in aggressive mode or in main mode? In my experience most router based site to site VPN use main mode (though aggressive mode is an option) while many Remote Access VPN use aggressive mode. So which mode are you using?
The second part of my response goes back to what I said in my earlier response. What kind of key are you using? How long is it and how strong is it? When you think about it any time we authenticate using shared keys there is some degree of vulnerability to brute force attack. The longer the key and the stronger the key the more you have mitigated the risk.
HTH
Rick -
Foreign JMS Server Persistance\Retry in case Remote JMS Provider goes down
Hi All
I would need more clarity on this. How does the Foreign JMS Server behave in case the remote JMS provider goes down. Does it take the message from the Publishing Proxy Service and retries\persists the JMS Message till the remote provide is up?
Please let us know. This would effect our design as retrial is very important here. ThanksIf you want to provide guaranteed delivery with automatic retries when using remote JMS implementations, there are multiple ways to implement it:
1. While reading from a foreign JMS destination
Create a Foreign JMS server using transactional drivers (use XA in case of JMS). The messages remain on remote server JMS queue and OSB proxy polls the message directly on remote server. So if Remote Server is down OSB will not be able to read the message. Once remote server is up OSB will pick up the message (as long as foreign JMS server provides persistence and maintains the messages in the queue during a server restart). In case of error in OSB foreign queue can do retry if it provides a retry mechanism.
2. While writing the message to a foreign JMS destination
a. Use a foreign JMS server using transactional connection. Put the retry mechanism in OSB Business service which writes to the foreign JMS/MQ queue. In case of failure Business Service can retry based on configuration. If you want to provide guaranteed delivery then create a local JMS queue to store the messages. So when remote destination is down for a long time undelivered messages will be rolled back to the local queue. You can put retry mechanism on the local queue.
b. Use a messaging bridge which will write the messages to the remote destination. You can configure retry delivery rules in messaging bridge so once busienss service writes the message to the bridge, a SAF agent will ensure the delivery to remote destination whenever it is up. -
The connection to the server was reset while the p...
For the past week i keep getting the below error page every minute or so--->
"The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web."
When i refresh the page it usually goes through as normal or does it again and needs to refresh again. Seems like every 1-2 mins i get a period of 15-20 secs of this.
Is this the connection droppping or another error altogether?? If its not actually the connection dropping will this affect gaming online (xbox 360, Battlefield 3)?
I believe Infinity is rolling out in my village (ST8 7__) (Biddulph Moor) next month. Could this be the reason? Its not the sites/pages im visiting as its happening no matter what site i visit.
I have done the quiet line test (17070) and thats fine. My hub details and speedtest is below. As far as i know we connected to the master socket.
Any advice will be greatly appreciated
I cant do the btspeedtest as the bill payer is away so i cant find out the Serice ID. I have done a test on speedtest.net if thAt is any good
[URL=http://www.speedtest.net][IMG]http://www.speedtest.net/result/1862765754.png[/IMG][/URL]
ADSL line status Connection information
Line state
Connected
Connection time
2 days, 15:46:50
Downstream
2,643 Kbps
Upstream
1,031 Kbps
ADSL settings
VPI/VCI
0/38
Type
PPPoA
Modulation
ITU-T G.992.5
Latency type
Interleaved
Noise margin (Down/Up)
10.1 dB / 5.3 dB
Line attenuation (Down/Up)
55.5 dB / 35.1 dB
Output power (Down/Up)
0.0 dBm / 12.8 dBm
Loss of Framing (Local)
0
Loss of Signal (Local)
0
Loss of Power (Local)
0
FEC Errors (Down/Up)
0 / 13
CRC Errors (Down/Up)
3101 / N/A
HEC Errors (Down/Up)
N/A / 11
Error Seconds (Local)
1281I dont believe so no. And the speed isnt an issue for me. I live in a village in the sticks so never had over 2.5mb. The issue is the error i get all the time. Ive had problems in the past where my connection would drop and i would have to wait to connect again before continuing. That was along time ago. This seems a different error. And is instantly fixed a refresh.
So if my connection doesnt actually drop will this affect online gaming?
Could this error be due to infinity coming to my area next month?
The reasn its an issue for me at the moment is because im a memeber of a few survey sites where i get paid to take surveys. This error causes me so much trouble. I i click a survey and this error occurs then i lose that survey.... so its actually preventing me from making money :-(
I think we will be getting infinity at the end of april. But if this isnt anything to do with inifinty and is actually a problem with my line then im concerned this will continue.
Since i heard a week or so ago inifinity was rolling out in my village in april this problem seems to have started. So im guessing its due to infinty.
Could it be? and when infinity is running in my village could this problem cease? -
I get the following message when trying to connect to firefox:
"The connection to the server was reset while the page was loading." I have to click on "try again" and then it connects.Did you check your security software (firewall)?
A possible cause is security software (firewall) that blocks or restricts Firefox without informing you about that, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox.
See [[Server not found]] and [[Firewalls]] and http://kb.mozillazine.org/Firewalls -
I've been working on our church website and all of a sudden this week, my computer will not connect to the site. I keep getting a message saying that the the connection to the server was reset while the page was loading. Does anyone have any ideas of how I can fix this?
The "The connection was reset" error message can be caused by a bug fix for the BEAST (Browser Exploit Against SSL/TLS) attack that the server doesn't handle.
*[[/questions/918127]]
*[[/questions/918028]] -
Opening attachments gives the error : "The connection was reset. The connection to the server was reset. I tried clearing cookies and cache, but it doesnot work. 8 out of 10 times this is happenning. It's reproducible, and happening only after the latest update.
A possible cause is security software (firewall,anti-virus) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.
See:
*https://support.mozilla.org/kb/Server+not+found
*https://support.mozilla.org/kb/Firewalls
You can also try to reset (power off/on) the router. -
How the JMS client detect if the JMS server is still running?
I have a JMS server running on Weblogic and a JMS client running as a standalone application on my local machine. I ran into the problem that if the JMS server is down for a period of time and then get re-started, the JMS client will lose its connection to the server. Since JMS client is just passively listening to the topic it subscribes, it will have no information about the status of the JMS server. Therefore it will not be able to receive any new message if the JMS server is restarted.
I wonder if there is a way I can have the JMS client automatically detect if the connection to the server is lost or reset. I tried to use a while loop in JMS client that does a JNDI loopup every minute to check if the JMS server is up. But if the WL server is down, the JMS client will just catch an exception and crash.Hi,
You should use an exception listener that allows a client to be notified of a problem asynchronously. As your client only consumes messages, it would have no other way to learn that its connection has failed.
Hence, you should implement the interface ExceptionListener (let says MyExceptionListener) and define your reconnection logic in the method onException(JMSException exception). MyExceptionListener has to be registered with your connection with the method:
public void setExceptionListener(ExceptionListener listener) throws JMSException
Hope it helps,
Arnaud
www.arjuna.com -
ORA-25228 error occurs when Foreign JMS Server connecting to the Oracle AQ
Hi,
I configure of a Foreign JMS Server that uses the Oracle JDBC Driver to connect to the AQ Topic. I use OSB messaging proxy service as a JMS client to connect the Foreign JMS Server. After the launch, I get the following error:
####<Jan 30, 2013 4:51:49 AM MSK> <Error> <EJB> <EPRUSARW0520> <osb_server1> <RequestEJB7826682746890400115XX35047bed.13c85602eea.X7f53> <<anonymous>> <> <0000Jm8w2Es6qI_5xRh8iW1H1sMk0001sD> <1359507109078> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed
Nested exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)
at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)
at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)
at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:201)
at weblogic.ejb.container.internal.JMSMessagePoller$1.run(JMSMessagePoller.java:262)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)
at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:257)
at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:351)
at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:483)
at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:499)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
at oracle.jdbc.driver.T4Caqdq.processError(T4Caqdq.java:497)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)
at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4704)
at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)
at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)
at oracle.jdbc.OracleConnectionWrapper.dequeue(OracleConnectionWrapper.java:1624)
at weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)
at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)
... 13 moreHowever, when I put message to AQ topic, the OSB proxy receives and processes it. But SQLException occurs every five seconds and pollute logs.
Request help to resolve this.
Thanks in advance.
Regards
Alexander.Maybe this can help: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::p11_question_id:4018285967344
-
MDBs failed to connect to remote JMS server
Hi,
We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
<weblogic-enterprise-bean>
<ejb-name>MyBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>MyTopic</destination-jndi-name>
<provider-url>t3://myhost:19009,myhost:19011</provider-url>
<connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
di-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
(t3://myhost:19009) but got the same result.
When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
Any help would be greatly appreciated.
Thanks,
ThaoI'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?). I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
>>> Could you elaborate on the known problem?
9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
>>> What else I can try?
Beyond contacting customer support, I'm not sure.
Tom -
What does "each JMS server needs to have its own unique store" mean?
Does this mean that each JMS server needs it's own table? I found this info here:
http://forums.bea.com/bea/message.jspa?messageID=200022411&tstart=0
I'm attempting to find the root cause of why we're crashing the OS on a highly clustered (14 managed server) implementation whenever a JMS queue (through BEA's JMS JDBC Store) is being hit.
Thanks!JDBC stores must be configured to use different database tables (by configuring a different "prefix" for each). Otherwise, they will corrupt each-others data. But I've never heard of this causing an O/S crash. Perhaps you are using native code JDBC drivers that have problems. You might want to try switching drivers, or even simply try switching from JDBC stores to file stores (temporarily) to see if that fixes the problem. You might want to check if you're using a supported JVM, etc. I'm curious about what versions of O/S, driver, JVM, and WebLogic are you using.
Tom, BEA -
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 -
I get an exception in starting OC4J (oc4j_extended_1013_dp4.zip file, version 10.1.3)
java -jar oc4j.jar
(SEVERE) Failed to set the internal configuration of the OC4J JMS Server with:
XMLJMSServerConfig[file:/C:/oc4j_1013/j2ee/home/config/jms.xml]
Error starting JMS-Server...
On my computer I succeeded to start the same OC4J ok, but on other 2 computers I get the same exception.
What can be the problem?
Thanks.The OC4J instance that is having the problem may have .lock file issues. Some quotes from the JMS chapter of the services guide:
If OC4J terminates normally, then the lock files are cleaned up automatically. However, if OC4J terminates abnormally, for example, a kill -9 command, then the lock files remain in the file system. OC4J can usually recognize leftover lock files. If not, you must manually remove lock files before restarting OC4J after abnormal termination.
JMS persistence lock files are tagged with (contain) server and persistence directory location info. If the lock file exists when the JMS server starts, and the lock file was created by the same server (having the same ip address) and using the same persistence directory location, then the JMS server will assume control of the lock file and start up successfully.
If, for some reason, the jms.state file itself is corrupted, then the only recourse is to delete it, with the attendant loss of all pending transactions - that is, transactions that have been committed, but the commits not yet performed by all individual destination objects participating in the transactions.
Note that the use of an IP address can cause issues if you have abnormal terminations and are using DHCP (so next time you start OC4J you also have a new IP address). There was also an issue in the dev preview versions if you are running on MS-Windows where the .lock files would not be automatically deleted on normal shut down - even if you have since moved to the release version, the old .lock files may still be there. -
Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server
Hi,
I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
<Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
nect to the JMS destination: FMAContractOutboundQueue. The Error was:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
:weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
-SreekanthI recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
* The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
* The connection factory doesn't exist.
* The object in JNDI with the specified connection factory name isn't actually a connection factory.
* The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
Tom
Maybe you are looking for
-
How to load flat file in existing Architecture.
Hi everyone! There is an existing architecture that I have to upload data into. There is a cube on top, followed below by an ODS and its update rules to the cube, followed below by an Infosource and its corresponding update rule to the ODS above it,
-
How to create the log file in remote system using log4j.
Hi, How to create the log file in remote system using log4j. please give me a sample code or related links.The below example i used for create the log file in remote system but it return the below exception.Is there any authandication parameter for a
-
How to tace the change no for a certain BOM?
I have a BOM(bill of material).and from time to time,engineer like to change the BOM by using "Change Number" ,so it is clear in the menu of T.C cs03, you can find the "change no.",but this T.C is only down to the second lower level and not down to t
-
Itunes (11.2.2 for Macbook Pro 2012) I can drag and drop in finder and other applications. However, I can't select and then drag and drop individual (or groups) of songs, or playlists in Itunes. For example, when I want to drag a song from one playl
-
Where are custom equalizer settings saved on windows pc
Where are iTunes custom equalizer settings saved on my Windows 7 hard drive? I always backup the entire iTunes folder and use that to restore everything after reformatting my hard drive. Everything restores EXCEPT the custom equalizer settings. Which