No Mark. We did not use a Remedy API but written a socket program to listen incoming messages on a specific port.
Thanks Pavan On 20-Sep-2017 7:29 PM, "Walters, Mark" <[email protected]> wrote: ** I had a thought – was your client developed using the Remedy API? If so try setting a client type value of AR_CLIENT_TYPE_ALERT (21) in the session configuration and see if that helps. *From:* Action Request System discussion list(ARSList) [mailto: [email protected]] *On Behalf Of *Nagidi Pavan *Sent:* 20 September 2017 11:19 *To:* [email protected] *Subject:* Re: Unable to send alerts - failed to dispatch alert message ** Sure Mark. Thanks Pavan On Wed, Sep 20, 2017 at 3:25 PM, Walters, Mark <[email protected]> wrote: ** I’m not clear on the overall process you’re using but it sounds as though there’s come change in 9.1 that’s broken your integration. Whether that’s something in your client or on BMC’s end I don’t know, I suggest you open a case with support and see what they have to say once they have all the details. Mark *From:* Action Request System discussion list(ARSList) [mailto: [email protected]] *On Behalf Of *Nagidi Pavan *Sent:* 20 September 2017 10:37 *To:* [email protected] *Subject:* Re: Unable to send alerts - failed to dispatch alert message ** Yes Mark. 9.1.03 failing to send data to client. Client server accepts the data from the AR server and process that internally. Thanks Pavan On Wed, Sep 20, 2017 at 3:01 PM, Walters, Mark <[email protected]> wrote: ** So if you send an alert to your custom client from a 7604 system it behaves as expected but a 9103 server reports the error? It sounds as though the 9103 server is trying some sort of negotiation with the client but it’s not getting what it expects. What does your client do – how was it written? Does it just accept the data sent? *From:* Action Request System discussion list(ARSList) [mailto: [email protected]] *On Behalf Of *Nagidi Pavan *Sent:* 20 September 2017 10:22 *To:* [email protected] *Subject:* Re: Unable to send alerts - failed to dispatch alert message ** Mark, Its a fresh installation. I have 7.6.04(On Linux) in another system and 9.1.03(On windows) on another system. I have installed alert client on windows machine where I have installed 9.1.03 and I can see alert tool poping up notifications. As you mentioned, it seems a problem with the server negotiating a connection with your client. What exactly you are looking for setup so that I pass that information. Thanks Pavan On Tue, Sep 19, 2017 at 4:33 PM, Walters, Mark <[email protected]> wrote: ** So you’ve written a client which registers with the server to receive alerts and have workflow generating alerts to send to this client? If that’s the case then the plugin is not used as far as I am aware, it’s a problem with the server negotiating a connection with your client. Can you provide a more detailed description of your setup? The setup is the same as you had in 7604 and you have just upgraded ARS? *From:* Action Request System discussion list(ARSList) [mailto: [email protected]] *On Behalf Of *Nagidi Pavan *Sent:* 19 September 2017 10:48 *To:* [email protected] *Subject:* Re: Unable to send alerts - failed to dispatch alert message ** Hi Mark, Thanks for your response. I have a socket program which is listening for incoming data on port xxxx. If any alert comes it receives and parse the information. I have configured the same in 7.6.04 and that worked. It's a Linux machine. Now I'm trying that on 9.1.03 ARS installed on windows machine but that's not working. Please let me know if you need any clarification! Thanks pavan On 19-Sep-2017 12:41 PM, "Walters, Mark" <[email protected]> wrote: ** What’s the client you’re sending the alerts to? The plugin you’re using is expecting to connect to a webservice when it dispatches the alert but I’m not clear on your setup. Mark *From:* Action Request System discussion list(ARSList) [mailto: [email protected]] *On Behalf Of *Nagidi Pavan *Sent:* 19 September 2017 03:32 *To:* [email protected] *Subject:* Unable to send alerts - failed to dispatch alert message ** Hi Guys, I am using alert mechanism to send alerts to an external socket which is listening on port XXXX. I have configured the alert plugin as specified in https://docs.bmc.com/docs/display/public/ars81/AR+Alert+ plug-in+configuration I am using AR - Plugin instead of webservices. When I register a user and trigger an alert I am getting the below message and my socket program is not receiving any information. Please let me know your thoughts. Tue Sep 19 00:16:43.252 2017 <ALRT> <TID: 0000000164> <RPC ID: 0000000000> <Queue: Init > <Client-RPC: 10 > <USER: ARSERVER > <Overlay-Group: 1 > /* Tue Sep 19 2017 00:16:43.2520 */ failed to dispatch alert message: java.lang.IllegalStateException: Message serializer not found for client version 0 at com.bmc.arsys.server.domain.alert.impl. SocketAlertDispatcher$SocketAlertDispatcherSession.dispatchMessage( SocketAlertDispatcher.java:386) ~[bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.domain.alert.impl. SocketAlertDispatcher$SocketAlertDispatcherSession.dispatch( SocketAlertDispatcher.java:356) ~[bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.domain.alert.impl.AlerterImpl. sendSocketBasedAlert(AlerterImpl.java:437) [bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.domain.alert.impl.AlerterImpl. sendAlertBlocking(AlerterImpl.java:353) [bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.domain.runtime.jms. AlertMessageHandler.handleMessage_aroundBody0(AlertMessageHandler.java:44) [bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.domain.runtime.jms. AlertMessageHandler$AjcClosure1.run(AlertMessageHandler.java:1) [bundlefile:9.1.03-SNAPSHOT] at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) [bundlefile:1.8.4] at com.bmc.arsys.server.internal.aspects. ARTransactionalManager.manageGeneralEntryApiTransacti on(ARTransactionalManager.java:261) [bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.internal.aspects. ARTransactionalManager.manageEntryApiTransaction( ARTransactionalManager.java:188) [bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.server.domain.runtime.jms. AlertMessageHandler.handleMessage(AlertMessageHandler.java:37) [bundlefile:9.1.03-SNAPSHOT] at com.bmc.arsys.messaging.impl.MessageSubscriberImpl. onMessage(MessageSubscriberImpl.java:125) [bundlefile:9.1.03-SNAPSHOT] at org.springframework.jms.listener. AbstractMessageListenerContainer.doInvokeListener( AbstractMessageListenerContainer.java:689) [bundlefile:na] at org.springframework.jms.listener. AbstractMessageListenerContainer.invokeListener( AbstractMessageListenerContainer.java:649) [bundlefile:na] Thanks Pavan _ARSlist: "Where the Answers Are" and have been for 20 years_ BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ BMC Software Limited Registered Office: Building E2, Eskdale Road, Winnersh, Wokingham, Berkshire, United Kingdom, RG41 5TS Registered in England No. 1927903 The content of this email is confidential. If you are not the addressee, you may not distribute, copy or disclose any part of it. If you receive this message in error, please delete this from your system and notify the sender immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
