Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • claudiobosticco
    replied
    Originally posted by Isomorphic View Post
    Still working on the JSON issue.
    any update on this issue?

    Leave a comment:


  • claudiobosticco
    replied
    Hello, I've just tested the rabbitmq-jms-1.8.1.jar and it seems that there isn't the original issue with queues growing every 2 minutes. And the remoteDebug is working.

    But I've noticed some warnings in the developer console, so I want to report it.

    I'm using this build:
    SmartClient Version: v11.1p_2017-12-02/Enterprise Deployment (built 2017-12-02)
    with Chrome on High Sierra
    Note that when I open the dev console, 3 queues are created, and this are the tomcat logs:
    Code:
    2017-12-04 17:08:20,095 INFO  RequestContext URL: '/Legend/isomorphic/DataSourceLoader', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:20,149 DEBUG FileDownload Registered expires mapping - text/javascript: 31104000 seconds 
    2017-12-04 17:08:20,149 DEBUG FileDownload Registered expires mapping - image/gif: 31104000 seconds 
    2017-12-04 17:08:20,149 DEBUG FileDownload Registered expires mapping - image/png: 31104000 seconds 
    2017-12-04 17:08:20,149 DEBUG FileDownload Registered expires mapping - image/jpeg: 31104000 seconds 
    2017-12-04 17:08:20,149 DEBUG FileDownload Registered expires mapping - image/x-icon: 31104000 seconds 
    2017-12-04 17:08:20,149 DEBUG FileDownload Registered expires mapping - text/css: 31104000 seconds 
    2017-12-04 17:08:20,149 INFO  RequestContext URL: '/Legend/isomorphic/skins/Enterprise/load_skin.js', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:20,161 INFO  Download File /opt/tomcat/webapps/Legend##0800/isomorphic/skins/Enterprise/load_skin.js not found, sending 404 
    2017-12-04 17:08:20,694 INFO  RequestContext URL: '/Legend/isomorphic/skins/Enterprise/load_skin.js', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:20,696 INFO  Download File /opt/tomcat/webapps/Legend##0800/isomorphic/skins/Enterprise/load_skin.js not found, sending 404 
    2017-12-04 17:08:20,766 INFO  RequestContext URL: '/Legend/tools/adminConsoleOperations.jsp', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:20,776 INFO  Compression /Legend/tools/adminConsoleOperations.jsp: 32 -> 68 bytes 
    2017-12-04 17:08:20,810 INFO  RequestContext URL: '/Legend/tools/developerConsoleOperations.jsp', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:20,818 INFO  Compression /Legend/tools/developerConsoleOperations.jsp: 109 -> 127 bytes 
    2017-12-04 17:08:21,088 INFO  RequestContext URL: '/Legend/tools/developerConsoleOperations.jsp', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:21,092 DEBUG XML Parsed XML from (in memory stream): 2ms 
    2017-12-04 17:08:21,092 DEBUG PoolableDataSourceFactory Tried to create DataSource  of type 'transaction' but null was returned 
    2017-12-04 17:08:21,092 DEBUG PoolableDataSourceFactory Created DataSource 516 of type 'Object' and assigned it to thread https-jsse-nio-8443-exec-9 
    2017-12-04 17:08:21,093 DEBUG PoolableDataSourceFactory Created DataSource 517 of type 'List' and assigned it to thread https-jsse-nio-8443-exec-9 
    2017-12-04 17:08:21,093 DEBUG PoolableDataSourceFactory Tried to create DataSource  of type 'elem' but null was returned 
    2017-12-04 17:08:21,093 DEBUG RPCManager Processing 1 requests. 
    2017-12-04 17:08:21,093 DEBUG RPCManager Request #1 (RPCRequest) data: {
        appID:"isc_builtin",
        className:"builtin",
        methodName:"getAvailableScriptEngines",
        arguments:[
        ],
        is_ISC_RPC_DMI:true
    } 
    2017-12-04 17:08:21,096 DEBUG XML Parsed XML from jar:file:/opt/tomcat/webapps/Legend%23%230800/WEB-INF/lib/isomorphic_core_rpc.jar!/isc_builtin.app.xml: 1ms 
    2017-12-04 17:08:21,096 DEBUG PoolableDataSourceFactory Created DataSource 518 of type 'Application' and assigned it to thread https-jsse-nio-8443-exec-9 
    2017-12-04 17:08:21,097 DEBUG PoolableDataSourceFactory Created DataSource 519 of type 'ServerObject' and assigned it to thread https-jsse-nio-8443-exec-9 
    2017-12-04 17:08:21,097 DEBUG PoolableDataSourceFactory Created DataSource 520 of type 'Method' and assigned it to thread https-jsse-nio-8443-exec-9 
    2017-12-04 17:08:21,107 DEBUG RPCDMI rpc returned data 
    2017-12-04 17:08:21,108 DEBUG RPCManager Content type for RPC transaction: text/plain; charset=UTF-8 
    2017-12-04 17:08:21,108 INFO  Compression /Legend/tools/developerConsoleOperations.jsp: 96 -> 99 bytes 
    2017-12-04 17:08:21,272 INFO  RequestContext URL: '/Legend/isomorphic/messaging', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:08:21,385 INFO  JMSMessageDispatcher Initializing JMS connection - JMS API version: 1.1 - provider: RabbitMQ version 4.3.0 
    2017-12-04 17:08:21,385 INFO  JMSMessageDispatcher JMS Connection started. Using json encoding  
    2017-12-04 17:08:21,396 INFO  JMSMessageDispatcher Destination for channel 'F654BA4B-CE82-4850-8EF1-EE08A157DB5C' not available via JNDI - dynamically creating 
    2017-12-04 17:08:21,436 INFO  JMSMessageDispatcher Destination for channel '08867DC2-4DDA-4EAF-A7E8-5EF5AE6ABBCD' not available via JNDI - dynamically creating 
    2017-12-04 17:08:21,441 INFO  JMSMessageDispatcher Destination for channel 'isc_DebugMaster' not available via JNDI - dynamically creating 
    2017-12-04 17:08:21,444 DEBUG MessagingConnectionHandler Sending connectCallback 
    2017-12-04 17:08:21,445 DEBUG MessagingConnectionHandler Entering event loop with ttl: 120000 
    2017-12-04 17:08:24,445 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:08:27,446 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:08:30,447 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:08:33,447 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:08:36,448 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:08:39,449 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:08:42,449 DEBUG MessagingConnectionHandler Sending keepalive 
    ....[CUT]
    2017-12-04 17:10:09,471 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:10:12,471 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:10:15,472 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:10:18,473 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:10:21,466 DEBUG MessagingConnectionHandler terminating connection 
    2017-12-04 17:10:21,515 INFO  RequestContext URL: '/Legend/isomorphic/messaging', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:10:21,549 DEBUG MessagingConnectionHandler Sending connectCallback 
    2017-12-04 17:10:21,550 DEBUG MessagingConnectionHandler Entering event loop with ttl: 120000 
    2017-12-04 17:10:23,466 DEBUG MessagingConnectionHandler inClientReconnectWindow - breaking out of event processing loop 
    2017-12-04 17:10:23,466 DEBUG MessagingConnectionHandler calling cleanup() 
    2017-12-04 17:10:23,466 DEBUG JMSMessageDispatcher closing session 
    2017-12-04 17:10:23,476 DEBUG MessagingConnectionHandler clientReconnectWindow expired 
    2017-12-04 17:10:23,476 DEBUG MessagingConnectionHandler calling cleanup() 
    2017-12-04 17:10:24,550 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:10:27,551 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:10:30,551 DEBUG MessagingConnectionHandler Sending keepalive
    I see that the number of queues doubles after 2 minutes (updating the RabbitMQ admin console every 5sec), but at the next refresh of the RabbitMQ admin console there are only 3 queues.
    So far so good.

    Then I access my application with ?isc_remoteDebug=true, and I see the usual two queues created on the broker, and this in the dev console:
    Code:
    17:15:30.156:TMR2:DEBUG:Messaging:proceeding to connect
    17:15:30.157:TMR2:DEBUG:Messaging:Using EventSource for comm
    17:15:30.553:DEBUG:Messaging:connection conn_1 established
    17:15:30.554:DEBUG:Messaging:persistent server connection open - ttl: 120000ms, keepaliveDelay: 4000ms, connectTimeout: 4000ms.
    17:15:33.416:DEBUG:Messaging:keepalive on conn: conn_1
    17:15:36.420:DEBUG:Messaging:keepalive on conn: conn_1
    17:15:39.421:DEBUG:Messaging:keepalive on conn: conn_1
    and this in tomcat logs:
    Code:
    2017-12-04 17:15:09,983 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:12,983 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:15,984 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:18,985 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:21,985 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:24,986 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:27,987 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:30,311 INFO  RequestContext URL: '/Legend/isomorphic/messaging', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-12-04 17:15:30,321 INFO  JMSMessageDispatcher Destination for channel 'DC7E5277-8290-43D0-81F2-04C5E9C5138C' not available via JNDI - dynamically creating 
    2017-12-04 17:15:30,391 DEBUG MessagingConnectionHandler Sending connectCallback 
    2017-12-04 17:15:30,401 DEBUG MessagingConnectionHandler Entering event loop with ttl: 120000 
    2017-12-04 17:15:30,577 DEBUG JMSMessageDispatcher Message: {"payload":{"methodName":"targetAvailable","args":[{"GUID":"DC7E5277-8290-43D0-81F2-04C5E9C5138C","receiveChannel":"DC7E5277-8290-43D0-81F2-04C5E9C5138C","discoverableOnChannel":"isc_DebugTarget","generatedDate":"$$DATESTAMP$$:1512404130555","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36","platform":"MacIntel","vendor":"Google Inc.","visibleMethods":[],"documentTitle":"Gestione Terzo Livello Palchi","URL":"https://mydomain.com/Legend/?isc_remoteDebug=true","formFactor":"Desktop","browserVersion":62,"browserMinorVersion":62}]},"sequence":4,"originChannel":"DC7E5277-8290-43D0-81F2-04C5E9C5138C","expectsReply":false} 
    2017-12-04 17:15:30,579 DEBUG JMSMessageDispatcher Decoded jmsMessage for channel: isc_DebugMaster data: {
        payload:{
            methodName:"targetAvailable",
            args:[
                {
                    GUID:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
                    receiveChannel:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
                    discoverableOnChannel:"isc_DebugTarget",
                    generatedDate:"$$DATESTAMP$$:1512404130555",
                    userAgent:"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36",
                    platform:"MacIntel",
                    vendor:"Google Inc.",
                    visibleMethods:[
                    ],
                    documentTitle:"Gestione Terzo Livello Palchi",
                    URL:"https://mydomain.com/Legend/?isc_remoteDebug=true",
                    formFactor:"Desktop",
                    browserVersion:"62",
                    browserMinorVersion:"62"
                }
            ]
        },
        sequence:"4",
        originChannel:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
        expectsReply:"false"
    } 
    2017-12-04 17:15:30,579 DEBUG MessagingConnectionHandler Sending message: ID:2bbc58e1-981b-4b76-918b-7d7c9224cffa:{
        payload:{
            methodName:"targetAvailable",
            args:[
                {
                    GUID:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
                    receiveChannel:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
                    discoverableOnChannel:"isc_DebugTarget",
                    generatedDate:"$$DATESTAMP$$:1512404130555",
                    userAgent:"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36",
                    platform:"MacIntel",
                    vendor:"Google Inc.",
                    visibleMethods:[
                    ],
                    documentTitle:"Gestione Terzo Livello Palchi",
                    URL:"https://mydomain.com/Legend/?isc_remoteDebug=true",
                    formFactor:"Desktop",
                    browserVersion:"62",
                    browserMinorVersion:"62"
                }
            ]
        },
        sequence:"4",
        originChannel:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
        expectsReply:"false"
    } 
    2017-12-04 17:15:33,401 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:33,580 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:36,413 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:36,581 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:39,414 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:39,582 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:42,415 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-12-04 17:15:42,583 DEBUG MessagingConnectionHandler Sending keepalive
    Then I open another browser window, access the application and open the dev console, and I see this in tomcat logs:
    Code:
    2017-12-04 17:25:11,077 INFO  JMSMessageDispatcher Initializing JMS connection - JMS API version: 1.1 - provider: RabbitMQ version 4.3.0 
    2017-12-04 17:25:11,077 INFO  JMSMessageDispatcher JMS Connection started. Using json encoding  
    2017-12-04 17:25:11,285 DEBUG JMSMessageDispatcher Message: {"payload":{"GUID":"DC7E5277-8290-43D0-81F2-04C5E9C5138C","receiveChannel":"DC7E5277-8290-43D0-81F2-04C5E9C5138C","discoverableOnChannel":"isc_DebugTarget","generatedDate":"$$DATESTAMP$$:1512404711221","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36","platform":"MacIntel","vendor":"Google Inc.","visibleMethods":[],"documentTitle":"Gestione Terzo Livello Palchi","URL":"https://mydomain.com/Legend/?isc_remoteDebug=true","formFactor":"Desktop","browserVersion":62,"browserMinorVersion":62},"originChannel":"DC7E5277-8290-43D0-81F2-04C5E9C5138C","sequence":13,"inResponseTo":{"originChannel":"A6AB93E8-9AEE-4B33-8F58-01B287D6DE8F","sequence":"1"}} 
    2017-12-04 17:25:11,287 DEBUG JMSMessageDispatcher Decoded jmsMessage for channel: A6AB93E8-9AEE-4B33-8F58-01B287D6DE8F data: {
        payload:{
            GUID:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
            receiveChannel:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
            discoverableOnChannel:"isc_DebugTarget",
            generatedDate:"$$DATESTAMP$$:1512404711221",
            userAgent:"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36",
            platform:"MacIntel",
            vendor:"Google Inc.",
            visibleMethods:[
            ],
            documentTitle:"Gestione Terzo Livello Palchi",
            URL:"https://mydomain.com/Legend/?isc_remoteDebug=true",
            formFactor:"Desktop",
            browserVersion:"62",
            browserMinorVersion:"62"
        },
        originChannel:"DC7E5277-8290-43D0-81F2-04C5E9C5138C",
        sequence:"13",
        inResponseTo:{
            originChannel:"A6AB93E8-9AEE-4B33-8F58-01B287D6DE8F",
            sequence:"1"
        }
    }
    Then I select in this 2nd dev console the first browser instance for remote debug, and I see this logs in the (2nd) developer console

    Code:
    17:28:04.887:TMR9:DEBUG:Messaging:proceeding to connect
    17:28:04.888:TMR9:DEBUG:Messaging:Using EventSource for comm
    17:28:04.936:DEBUG:Messaging:connection conn_8 established
    17:28:04.936:DEBUG:Messaging:Destroying connection: conn_7
    17:28:04.938:DEBUG:Messaging:persistent server connection open - ttl: 120000ms, keepaliveDelay: 4000ms, connectTimeout: 4000ms.
    17:28:05.183:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Unable to find originating request for response packet: {originChannel: "55029E68-4554-4340-BA8A-074B965C6FAF",
    sequence: "3",
    inResponseTo: Obj}
    17:28:05.184:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Outstanding requests: [Obj
    ]
    17:28:05.203:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Unable to find originating request for response packet: {originChannel: "55029E68-4554-4340-BA8A-074B965C6FAF",
    sequence: "4",
    inResponseTo: Obj}
    17:28:05.204:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Outstanding requests: [Obj
    ]
    17:28:05.333:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Unable to find originating request for response packet: {payload: "734",
    originChannel: "55029E68-4554-4340-BA8A-074B965C6FAF",
    sequence: "5",
    inResponseTo: Obj}
    17:28:05.335:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Outstanding requests: [Obj
    ]
    17:28:06.324:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Unable to find originating request for response packet: {payload: "735",
    originChannel: "55029E68-4554-4340-BA8A-074B965C6FAF",
    sequence: "6",
    inResponseTo: Obj}
    17:28:06.326:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Outstanding requests: [Obj
    ]
    17:28:07.326:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Unable to find originating request for response packet: {payload: "736",
    originChannel: "55029E68-4554-4340-BA8A-074B965C6FAF",
    sequence: "7",
    inResponseTo: Obj}
    17:28:07.328:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Outstanding requests: [Obj
    ]
    17:28:08.347:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Unable to find originating request for response packet: {payload: "737",
    originChannel: "55029E68-4554-4340-BA8A-074B965C6FAF",
    sequence: "8",
    inResponseTo: Obj}
    17:28:08.349:WARN:MessagingDMISocket:isc_MessagingDMISocket_3:Outstanding requests: [Obj
    ]
    Are they expected?

    Leave a comment:


  • Isomorphic
    replied
    Patched and pull request submitted to author.

    Leave a comment:


  • claudiobosticco
    replied
    great, thank you!

    Leave a comment:


  • Isomorphic
    replied
    I've also reproduced this. Updated [url]https://github.com/rabbitmq/rabbitmq-jms-client/pull/35[/code] to try to get a fix in before it exits RC status.

    Leave a comment:


  • claudiobosticco
    replied
    Hello, thanks for the update.

    I've just tried the rabbitmq-jms-1.8.0.RC1.jar, using the cleanUpServerNamedQueuesForNonDurableTopicsOnSessionClose="true" as you suggested.

    I'm using this build of SmartClient:
    SmartClient Version: v11.1p_2017-11-16/Enterprise Deployment (built 2017-11-16)

    and Chrome browser on High Sierra.

    But I'm still seeing the queues growing.
    I'm accessing my application with ?isc_remoteDebug=true, so I see immediately two queues created on the broker, and then two more queues every 2 minutes.
    In the tomcat logs I see the cleanup call
    MessagingConnectionHandler calling cleanup()
    Code:
    2017-11-23 10:53:17,394 DEBUG MessagingConnectionHandler Sending connectCallback 
    2017-11-23 10:53:17,395 DEBUG MessagingConnectionHandler Entering event loop with ttl: 120000 
    2017-11-23 10:53:17,912 DEBUG MessagingConnectionHandler inClientReconnectWindow - breaking out of event processing loop 
    2017-11-23 10:53:17,912 DEBUG MessagingConnectionHandler calling cleanup() 
    2017-11-23 10:53:17,912 DEBUG JMSMessageDispatcher closing session 
    2017-11-23 10:53:17,917 DEBUG MessagingConnectionHandler clientReconnectWindow expired 
    2017-11-23 10:53:17,917 DEBUG MessagingConnectionHandler calling cleanup() 
    2017-11-23 10:53:17,917 DEBUG ExceptionTranslationFilter Chain processed normally 
    2017-11-23 10:53:17,917 DEBUG SecurityContextPersistenceFilter SecurityContextHolder now cleared, as request processing completed 
    2017-11-23 10:53:20,396 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:23,396 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:26,397 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:29,398 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:32,398 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:35,399 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:38,400 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:41,400 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:44,401 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:47,401 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:50,402 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:53,402 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:56,403 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:53:59,404 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:02,404 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:05,405 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:08,406 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:11,407 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:14,408 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:17,408 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:20,409 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:23,409 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:26,410 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:29,411 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:32,412 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:35,412 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:38,416 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:41,417 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:44,417 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:47,418 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:50,418 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:53,419 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:56,420 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:54:59,420 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:02,421 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:05,422 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:08,422 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:11,423 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:14,424 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:17,415 DEBUG MessagingConnectionHandler terminating connection 
    2017-11-23 10:55:18,245 INFO  RequestContext URL: '/Legend/isomorphic/messaging', User-Agent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36': Safari with Accept-Encoding header 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy Converted URL to lowercase, from: '/isomorphic/messaging'; to: '/isomorphic/messaging' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy Candidate is: '/isomorphic/messaging'; pattern is /images/*; matched=false 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy Converted URL to lowercase, from: '/isomorphic/messaging'; to: '/isomorphic/messaging' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy Candidate is: '/isomorphic/messaging'; pattern is /isomorphic/resthandler*; matched=false 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy Converted URL to lowercase, from: '/isomorphic/messaging'; to: '/isomorphic/messaging' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy Candidate is: '/isomorphic/messaging'; pattern is /**; matched=true 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 1 of 10 in additional filter chain; firing Filter: 'ChannelProcessingFilter' 
    2017-11-23 10:55:18,246 DEBUG DefaultFilterInvocationSecurityMetadataSource Converted URL to lowercase, from: '/isomorphic/messaging'; to: '/isomorphic/messaging' 
    2017-11-23 10:55:18,246 DEBUG DefaultFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /*.jsp; matched=false 
    2017-11-23 10:55:18,246 DEBUG DefaultFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /monitoring*; matched=false 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 2 of 10 in additional filter chain; firing Filter: 'ConcurrentSessionFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 3 of 10 in additional filter chain; firing Filter: 'SecurityContextPersistenceFilter' 
    2017-11-23 10:55:18,246 DEBUG HttpSessionSecurityContextRepository Obtained a valid SecurityContext from SPRING_SECURITY_CONTEXT: 'org.springframework.security.core.context.SecurityContextImpl@15948c65: Authentication: org.springframework.security.cas.authentication.CasAuthenticationToken@15948c65: Principal: org.springframework.security.ldap.userdetails.InetOrgPerson@f74a983f: Dn: mail=claudio.bosticco@juventus.com,o=JUVENTUSFC; Username: claudio.bosticco@juventus.com; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; CredentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: ROLE_ADMIN, ROLE_SALES, ROLE_CONTROLLO_GEST; Credentials: [PROTECTED]; Authenticated: true; Details: org.springframework.security.web.authentication.WebAuthenticationDetails@0: RemoteIpAddress: 172.16.2.26; SessionId: 0591E6629107CB5799E503F99D35F504.srvubuntu6; Granted Authorities: ROLE_ADMIN, ROLE_SALES, ROLE_CONTROLLO_GEST Assertion: org.jasig.cas.client.validation.AssertionImpl@493a4f44 Credentials (Service/Proxy Ticket): ST-28-iCYBXNgO2zdueDCAnNiK-cas' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 4 of 10 in additional filter chain; firing Filter: 'LogoutFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 5 of 10 in additional filter chain; firing Filter: 'CasAuthenticationFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 6 of 10 in additional filter chain; firing Filter: 'RequestCacheAwareFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 7 of 10 in additional filter chain; firing Filter: 'SecurityContextHolderAwareRequestFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 8 of 10 in additional filter chain; firing Filter: 'SessionManagementFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 9 of 10 in additional filter chain; firing Filter: 'ExceptionTranslationFilter' 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true at position 10 of 10 in additional filter chain; firing Filter: 'FilterSecurityInterceptor' 
    2017-11-23 10:55:18,246 DEBUG ExpressionBasedFilterInvocationSecurityMetadataSource Converted URL to lowercase, from: '/isomorphic/messaging'; to: '/isomorphic/messaging' 
    2017-11-23 10:55:18,246 DEBUG ExpressionBasedFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /*.jsp; matched=false 
    2017-11-23 10:55:18,246 DEBUG ExpressionBasedFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /isomorphic/idacall*; matched=false 
    2017-11-23 10:55:18,246 DEBUG ExpressionBasedFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /tools/*.jsp; matched=false 
    2017-11-23 10:55:18,246 DEBUG ExpressionBasedFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /tools/visualbuilder/*.jsp; matched=false 
    2017-11-23 10:55:18,246 DEBUG ExpressionBasedFilterInvocationSecurityMetadataSource Candidate is: '/isomorphic/messaging'; pattern is /monitoring*; matched=false 
    2017-11-23 10:55:18,246 DEBUG FilterSecurityInterceptor Public object - authentication not attempted 
    2017-11-23 10:55:18,246 DEBUG FilterChainProxy /isomorphic/messaging?ts=1511430918240&type=connect&connectionID=conn_3&subscribedChannels=%7B%0A%20%20%20%20%22F347BB79-C374-421C-B047-6B7F3C65D8F3%22%3A%7B%0A%20%20%20%20%7D%2C%20%0A%20%20%20%20isc_DebugTarget%3A%7B%0A%20%20%20%20%7D%0A%7D&eventStream=true reached end of additional filter chain; proceeding with original chain 
    2017-11-23 10:55:18,267 DEBUG MessagingConnectionHandler Sending connectCallback 
    2017-11-23 10:55:18,267 DEBUG MessagingConnectionHandler Entering event loop with ttl: 120000 
    2017-11-23 10:55:19,416 DEBUG MessagingConnectionHandler inClientReconnectWindow - breaking out of event processing loop 
    2017-11-23 10:55:19,416 DEBUG MessagingConnectionHandler calling cleanup() 
    2017-11-23 10:55:19,416 DEBUG JMSMessageDispatcher closing session 
    2017-11-23 10:55:19,418 DEBUG MessagingConnectionHandler clientReconnectWindow expired 
    2017-11-23 10:55:19,418 DEBUG MessagingConnectionHandler calling cleanup() 
    2017-11-23 10:55:19,419 DEBUG ExceptionTranslationFilter Chain processed normally 
    2017-11-23 10:55:19,419 DEBUG SecurityContextPersistenceFilter SecurityContextHolder now cleared, as request processing completed 
    2017-11-23 10:55:21,268 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:24,268 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:27,269 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:30,270 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:33,270 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:36,271 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:39,271 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:42,272 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:45,273 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:48,273 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:51,274 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:54,284 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:55:57,285 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:00,285 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:03,286 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:06,287 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:09,287 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:12,288 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:15,289 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:18,289 DEBUG MessagingConnectionHandler Sending keepalive 
    2017-11-23 10:56:21,290 DEBUG MessagingConnectionHandler Sending keepalive
    But immediately after every call I see two more queues.

    The client logs are like this:
    Code:
    10:52:57.939:DEBUG:Messaging:keepalive on conn: conn_1
    10:53:00.939:DEBUG:Messaging:keepalive on conn: conn_1
    10:53:03.940:DEBUG:Messaging:keepalive on conn: conn_1
    10:53:06.940:DEBUG:Messaging:keepalive on conn: conn_1
    10:53:09.941:DEBUG:Messaging:keepalive on conn: conn_1
    10:53:12.941:DEBUG:Messaging:keepalive on conn: conn_1
    10:53:17.366:TMR0:DEBUG:Messaging:proceeding to connect
    10:53:17.367:TMR0:DEBUG:Messaging:Using EventSource for comm
    10:53:17.422:DEBUG:Messaging:connection conn_2 established
    10:53:17.422:DEBUG:Messaging:Destroying connection: conn_1
    10:53:17.424:DEBUG:Messaging:persistent server connection open - ttl: 120000ms, keepaliveDelay: 4000ms, connectTimeout: 4000ms.
    10:53:20.422:DEBUG:Messaging:keepalive on conn: conn_2
    10:53:23.422:DEBUG:Messaging:keepalive on conn: conn_2
    10:53:26.423:DEBUG:Messaging:keepalive on conn: conn_2
    10:53:29.424:DEBUG:Messaging:keepalive on conn: conn_2
    10:53:32.424:DEBUG:Messaging:keepalive on conn: conn_2
    10:53:35.424:DEBUG:Messaging:keepalive on conn: conn_2
    Am I missing something?

    Leave a comment:


  • Isomorphic
    replied
    Still working on the JSON issue. But wanted to make sure you saw the update on https://github.com/rabbitmq/rabbitmq-jms-client/pull/35 wherein the next stable release of the RMQ JMS client will require a special flag to auto-delete temporary broker queues. The context.xml that ships with our SDK includes a commented out RMQ factory JNDI block with this flag - here's a copy for reference:

    Code:
      <Resource name="jms/ConnectionFactory"
                type="javax.jms.ConnectionFactory"
                factory="com.rabbitmq.jms.admin.RMQObjectFactory"
                username="guest"
                password="guest"
                virtualHost="/"
                host="localhost"
                cleanUpServerNamedQueuesForNonDurableTopicsOnSessionClose="true"            
      />

    Leave a comment:


  • Isomorphic
    replied
    Hey - yes, the JNDI lookup code has been modified. The purpose was to provide some resiliency and consistency for lookups, so the intent was to have the ConnectionFactory (and other) lookups work with or without the jndiPrefix so that people arrive at a working configuration faster even if they don't read all the docs super closely.

    We'll patch the behavior where having the jndiPrefix set to an empty string creates a problem - previously this was treated as null and that behavior will be restored in tomorrow's build.

    Will take a look at the JSON encoding issue. The boolean issue is not immediately explicable, but the dates look like they're using our internal format - which works client to client, but obviously wouldn't work cross-platform with some arbitrary JSON parser consuming what we send. Will get this taken care of asap.

    Leave a comment:


  • claudiobosticco
    replied
    SmartClient Version: v11.1p_2017-11-16/Enterprise Deployment (built 2017-11-16)

    Chrome on OSX

    Hello, I'm trying the
    messaging.jms.encoding: json
    setting, but I've found a problem.
    In the messaging callback, I see that every data field is a string, ie:
    - booleans are "true" and "false" (as a string)
    - numbers (as ids or others) are also strings, so 2979574 became "2979574"
    - dates are rendered as "$$DATESTAMP$$:1511725500000"

    Obviously strings are correct.

    Leave a comment:


  • claudiobosticco
    replied
    Hello, I'm trying today (Nov 16) build, with
    messaging.jms.encoding: json
    setting.
    Did you change something in the jndi lookup?
    I've got this exception:
    Code:
    2017-11-16 14:51:01,761 ERROR [claudio.bosticco@juventus.com ] MessagingServlet com.isomorphic.messaging.MessagingServlet top-level exception
    java.lang.Exception: Failed to lookup JNDI object javax.jms.ConnectionFactory - tried: /ConnectionFactory, and: ConnectionFactory
        at com.isomorphic.naming.JNDI.lookup(JNDI.java:299)
        at com.isomorphic.messaging.JMSMessageDispatcher.connect(JMSMessageDispatcher.java:117)
        at com.isomorphic.messaging.JMSMessageDispatcher.<init>(JMSMessageDispatcher.java:80)
        at sun.reflect.GeneratedConstructorAccessor100.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at java.lang.Class.newInstance(Class.java:383)
        at com.isomorphic.base.Reflection.newInstance(Reflection.java:213)
        at com.isomorphic.base.Reflection.instantiateClass(Reflection.java:185)
        at com.isomorphic.base.Reflection.instantiateClass(Reflection.java:161)
        at com.isomorphic.messaging.ISCMessageDispatcher.instance(ISCMessageDispatcher.java:58)
        at com.isomorphic.messaging.ISCMessageDispatcher.instance(ISCMessageDispatcher.java:72)
        at com.isomorphic.messaging.MessagingConnectionHandler.process(MessagingConnectionHandler.java:132)
        at com.isomorphic.messaging.MessagingServlet.doPost(MessagingServlet.java:115)
        at com.isomorphic.messaging.MessagingServlet.doGet(MessagingServlet.java:131)
    -------------------------------------------------
    Edit: I managed to get it working using:
    messaging.jms.jndiPrefix: jms
    messaging.jms.topicConnectionFactory: ConnectionFactory
    instead of:
    messaging.jms.jndiPrefix:
    messaging.jms.topicConnectionFactory:jms/ConnectionFactory
    nevertheless I'm interested in understanding what has changed.

    Note: I've found another problem, I'll write a new post.
    Last edited by claudiobosticco; 16 Nov 2017, 07:40.

    Leave a comment:


  • Isomorphic
    replied
    Ok, looks like our patch is in to the RabbitMQ JMS broker. Tomorrow's (Nov 16) build of SC/SGWT will have the json encoding option. It may not be doc'd yet, but you can enable it by setting this server.properties value:

    Code:
    messaging.jms.encoding: json
    On server startup, you should see a message like the following:

    Code:
    === 2017-11-15 10:56:10,388 [ec-1] INFO  JMSMessageDispatcher - JMS Connection started. Using json encoding

    Leave a comment:


  • Isomorphic
    replied
    Patch submitted. It may have to go through a few rounds before it's accepted, but ultimately it looks like this should be resolved in the jms connector code so we won't have to provide a sub-optimal workaround like cycling connections.

    Leave a comment:


  • claudiobosticco
    replied
    Originally posted by claudiobosticco View Post
    ok, thanks, I've subscribed to receive notifications.
    and they've just replied!

    Leave a comment:


  • claudiobosticco
    replied
    Originally posted by Isomorphic View Post
    I've posted a question about this to the RabbitMQ community - check it out here: https://groups.google.com/forum/#!to...rs/0zXgBh-nX28. Let's see where this goes.
    ok, thanks, I've subscribed to receive notifications.
    Originally posted by Isomorphic View Post
    In terms of the amqp thing: I think the issue is we're relying on Java serialization because we send our messages as type ObjectMessage. What we'll do is provide a config flag that switches to the TextMessage type which is consumable by things other than Java - which is often the whole point of using a broker. We'll probably just encode the payload via JSON to the String datatype that TextMessage requires and doc that. What do you think?
    Sounds great! Thank you very much.

    Leave a comment:


  • Isomorphic
    replied
    Just to clarify on the JSON encoding: if the consumer on the other side of the SmartClient/SGWT send is also a SmartClient/SGWT server, then the JSON encoding will be totally transparent - you won't need to do any deserialization yourself. But if you're writing to a topic/queue that e.g. gets read by some arbitrary C++ client, then it'll need to parse the JSON, but these days there's a drop-in library for that in just about every language.

    Leave a comment:

Working...
X