Using REST services to communicate with a BSV on same server

[RLJB]

Has anyone done this?

We don't "think" you can. We tried doing it, things seemed ok for a day and then stuff started getting funky, Java spiked to 200%, server kept falling over, strange errors in logs (see below) which we "think" was due to this. Why? Because we deleted the BSV and it stopped.

Anyone got any experience on this?

2020-05-07 21:35:17,069 org.apache.activemq.broker.TransportConnection.Transport -Transport Connection to: tcp://127.0.0.1:34868 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:34868
2020-05-07 21:35:17,069 org.apache.activemq.broker.TransportConnection.Transport -Transport Connection to: tcp://127.0.0.1:34828 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:34828
TRACE: org.openadaptor.adaptor.jms.JMSListener - closing JMS connection
TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop()
TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop: JMSException: [org.apache.activemq.ConnectionFailedException: The JMS connection has failed: Channel was inactive for too (>30000) long: tcp://127.0.0.1:61616 [org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:61616]]
TRACE: org.openadaptor.adaptor.jms.JMSListener - connection.stop: JMSException: [ - during cleanup after - JMSException: org.apache.activemq.ConnectionFailedException: The JMS connection has failed: Channel was inactive for too (>30000) long: tcp://127.0.0.1:61616 [org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://127.0.0.1:61616]]
TRACE: org.openadaptor.adaptor.jms.JMSListener - consumer.close()

[aware_support]

It IS possible and it can and should be used. We use it all the time in our applications. Maybe you have done something wrong or the problem has nothing to do with services.

[Jaymer]

It IS possible and it can and should be used. We use it all the time in our applications. Maybe you have done something wrong or the problem has nothing to do with services.

Just to clarify, you "do it all the time", but this is calling AwareIM REST from a Process with REQUEST SERVICE, not from the UI via a URL?

And to help us all out here expand our thinking... could you explain some uses of this where its beneficial to do this?

[aware_support]

Yes, this is calling REST using REQUEST SERVICE.

Typical scenario. You have a SaaS system in the Cloud and you deploy multiple business spaces - one for each client. You also have a Sales System (special BSV) that keeps track of the clients and handles periodic payments based on the amount of work that each client does. The clients have limited access to the Sales System - they can view their account and see they payment history.

The best way to handle communication between client business spaces and the Sales System is using services (REST or SOAP). You can put the Sales System on the same machine or on a separate one.

[RLJB]

We have a BSV that logs all outgoing SMS form other BSVs (for billing purposes) and then processes replies back from the SMS provider and directs them to the correct install - it uses REST, all BSVs here are on the same server. It's a good set-up.

However, the setup we have caused issues as described above. It might be that our web services didn't have a Reply (guess?). But this set-up definitely caused CPU issues. We removed the BSV and moved it to another server and instantly the issues stopped.