Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here




Hi All,

I am using 4.5.2 and I want to send monitoring event when I catch some critical exception. I tired to use eventSend function using following two signatures in my JAVA collab.

1. eventSend(alertCategory, alertSubCategory, alertInfoCode, reasonCode, reasonName,
 eventInfo, additionalInfo)

2. eventSend(severityLevel, alertCategory, alertSubcategory, elemType, alertInfoCode,
 reasonCode, reasonName, eventInfo, additionalInfo)
(In 4.5.2 documentation, signature of the second method is wrong I found that out after
decompiling Alerter class, constatnts defined for elemType are also wrong )

both of them are returning true. but some how control broker is not getting this event
and nobody is throwing any exception. In our monk collab we call the event-send method and
it's sending the monitoring event successfully

Please let me know if I am missing something.


Following is some of the content from my log file.

17:04:20.738 EWY  A 12 (java_extensions.cxx:956): Failed on POST method; Exception : java.net.ConnectException: Connection timed out
17:04:20.738 EWY  I 12 (java_extensions.cxx:956): Error: SSL implementation not available!
17:04:20.788 COL  T 12 (java_extensions.cxx:311): In PostMonitorNotification
17:04:20.789 COL  T 12 (java_extensions.cxx:262): (get_handle_by_threadname) successfully retreived ThreadInfo.
17:04:20.790 API  D 12 (monitorevents.cxx:331): sending monitor event: severity [FATAL], category [User Defined], subcategory [Non standard], on behalf of [e*Way], alert info code [User], error text [HTTP(S) Post Exception at col_HTTPS_Java_Sim : ew_HTTPS_Java_Sim**** Critical Exception Processing Started at : Mon Jun 16 17:04:20 EDT 2003 ****
Document Identifier: 878542765|COP20030513142310.442|200306021212300696
Exception message: Connection timed out
Exception Stacktrace is as follows
java.net.ConnectException: Connection timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:320)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:133)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:120)
    at java.net.Socket.<init>(Socket.java:273)
    at java.net.Socket.<init>(Socket.java:100)
    at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>;([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>;([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect([DashoPro-V1.2-120198])
    at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.getOutputStream([DashoPro-V1.2-120198])
    at com.stc.eways.http.HttpClientAPI.doPostBinary(HttpClientAPI.java:1047)
    at com.stc.eways.http.HttpClientAPI.post(HttpClientAPI.java:657)
    at com.stc.eways.http.HttpClient.post(HttpClient.java:1363)
    at cr_HTTPS_Java_Sim.executeBusinessRules(cr_HTTPS_Java_Sim.java:229)
    at com.stc.jcsre.JCollaboration.translate(JCollaboration.java:121)
    at com.stc.common.collabService.JCCollabControllerImpl.translate(JCCollabControllerImpl.java:518)

**** Critical Exception Processing Ended at : Mon Jun 16 17:04:20 EDT 2003 ****
], add info text []
17:04:20.790 APIV D 1 (defeventproc.cxx:93): DefaultEventProc: STCE_CBMSG_OUTGOING (Control Broker Outgoing Message)
17:04:20.791 EWY  I 12 (java_extensions.cxx:956): Boolean return = true
17:04:20.995 API  D 13 (cbprocessing.cxx:900): DGE_P_ComposeCBMessage(): composing DGCBPV2 event message to send to CB.
17:04:20.996 CBV  T 13 (ncbtcp.c:793): CBTCP_X_WriteMsg: newmsg is NOT NULL
17:04:20.997 APIV D 1 (defeventproc.cxx:78): DefaultEventProc: Completion Event: STCE_CBMSG_OUTGOING (Control Broker Outgoing Message)
17:04:21.107 CBV  D 13 (ncbtcp.c:863): writing on socket 16
17:04:21.107 CBV  T 13 (ncbtcp.c:872): about to convert msgsize = 2434
17:04:21.108 CBV  D 13 (ncbtcp.c:882): going to write 2434 bytes.
17:04:21.108 CBV  D 13 (ncbtcp.c:885): actually wrote 2434 bytes.
17:04:21.226 EWY  I 12 (java_extensions.cxx:956): reset() has been called!

RE: eventSend

Are you getting any alerts via the monitor?
If you are getting none then maybe I have an idea, if it's just this one that is missing then I'm stuck.

RE: eventSend

yes i am getting all other alerts via monitor. This is the only one where I am not getting anythng :(

RE: eventSend

Is the Notification collaboration rules script catching this alert or just ignoring?
CB logging will show this.


RE: eventSend

I looked at CB log and found oput that it was getting this message but it wasn't able to parse it. So it was droppign it. I changed it and now it's workign fine.

Thanks for your help Stephen.

RE: eventSend

No worries.

RE: eventSend

Hi Suraj

You said you changed it(monitoring event) , and now the CB is parsing is parsing it properly. can you please elaborate on the change you did. Or can just paste the changed code here.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close