Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://blog.nashcom.de/nashcomblog.nsf/feed.rss

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0"
  3. xmlns:dc="http://purl.org/dc/elements/1.1/"
  4. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  5. xmlns:admin="http://webns.net/mvcb/"
  6. xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  7. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  8. xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  9. <channel>
  10. <title>Daniel Nashed&#8217;s Blog</title>
  11. <description>Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...</description>
  12. <link>http://blog.nashcom.de/nashcomblog.nsf/</link>
  13. <language>en-us</language>
  14. <lastBuildDate>Wed, 17 Jan 2018 04:41:02 +0200</lastBuildDate>
  15. <item>
  16. <title>ROBOT SSL/TLS Attack</title>
  17. <pubDate>Wed, 17 Jan 2018 04:41:02 +0200</pubDate>
  18. <description>
  19. <![CDATA[
  20. This has not been widely discussed yet. But since SSL Labs will start reporting it with a rating of F beginning of February let me explain some background and what you could do. The issue has been t ...
  21. ]]>
  22. </description>
  23. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/robot-ssltls-attack.htm</link>
  24. <category>Security</category>
  25. <dc:creator>Daniel Nashed</dc:creator>
  26. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/robot-ssltls-attack.htm?opendocument&amp;comments</comments>
  27. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/robot-ssltls-attack.htm</guid>
  28. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">This has not been widely discussed yet. But since SSL Labs will start reporting it with a rating of F beginning of February let me explain some background and what you could do.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> The issue has been there in a similar way before and is back. You can read the details here --> https://robotattack.org/</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Affected are the older ciphers that are not widely used by current browsers/client. You could disable those ciphers until the issue is fixed.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> But on the other side most browsers/clients do support higher secure ciphers. And because by default the server cipher order is used, a client should not choose a weaker cipher.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> In addition because of Secure Renegotiation which is supported by Domino and most browsers/clients support it, no weaker cipher will be used than the best common cipher between client and server.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> That means that only a very small fraction of connections might use those affected ciphers and if you disable those the client cannot connect at all.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> A fix for the ROBOT Attack is planned for FP10. </span><span style=" font-size:12pt"><br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> So IMHO there is no need right now to disable those affected older RSA ciphers unless you have very high security requirements or if you are concerned about your SSL labs rating ..</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> If you disable those affected ciphers the warning on the SSL Labs test side goes away.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Here is a more paranoid configuration of TLS ciphers that you could use:</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> set config SSLCipherSpec&Agrave;30009FC02F009EC028006BC0140039C02700670033C013</strong></span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> restart task http</strong></span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> If you look into the compatibility report, there is no current client that could not connect any more (even older IE versions would connect). <br /> The other positive effect would be that you would only support DHE and ECDHE ciphers which is a good idea in general..</span><span style=" font-size:12pt"><br /> <br /> </span><span style=" font-size:12pt;font-family:sans-serif">UPDATE 17.01.2018 </span> <br /> <br /><span style=" font-size:12pt;font-family:sans-serif">Andy Brunner had an interesting comment. In my cipher list I am still having 0033 which is rated as a weak cipher which is not enabled by default.</span> <br /><span style=" font-size:12pt;font-family:sans-serif">I have a cipher configuration database where I still had that cipher listed. </span> <br /> <br /><span style=" font-size:12pt;color:#800000;font-family:sans-serif">TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) </span> <br /> <br /><span style=" font-size:12pt;font-family:sans-serif">If you still have this cipher listed and did not allow weak ciphers the server will give you a hint:</span> <br /> <br /><span style=" font-size:12pt;font-family:sans-serif">SSLDisableExportCiphers> Disabling weak cipher </span><span style=" font-size:12pt;color:#800000;font-family:sans-serif">DHE_RSA_WITH_AES_128_CBC_SHA</span><span style=" font-size:12pt;font-family:sans-serif">. Set notes.ini "USE_WEAK_SSL_CIPHERS=1" to re-enable. </span> <br /> <br /><span style=" font-size:12pt;font-family:sans-serif">So the better fitting cipher liste in this case would be</span> <br /> <br /><span style=" font-size:12pt;font-family:sans-serif"><strong>set config SSLCipherSpec&Agrave;30009FC02F009EC028006BC0140039C0270067C013 </strong></span> <br /><span style=" font-size:12pt;font-family:sans-serif"><strong>restart task http </strong></span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">The mentioned cipher is rated as weak by Domino because it is a cipher that internally uses "SHA".</span> <br /> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Daniel</span><span style=" font-size:12pt;font-family:sans-serif"> </span><span style=" font-size:12pt"><br /> <br /> <br /> <br /> <br /> </span><img  alt="Image:ROBOT SSL/TLS Attack" border="0" src="http://blog.nashcom.de/nashcomblog.nsf/dx/robot-ssltls-attack.htm/content/M2?OpenElement" />  ]]></content:encoded>
  29. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/robot-ssltls-attack.htm</wfw:commentRss>
  30. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/robot-ssltls-attack.htm?opendocument&amp;comments</wfw:comment>
  31. </item>
  32. <item>
  33. <title>Meltdown and Spectre Exploit</title>
  34. <pubDate>Fri, 5 Jan 2018 00:44:30 +0200</pubDate>
  35. <description>
  36. <![CDATA[
  37. There is a new security issue for most modern CPUs. Intel and AMD is affected in different ways. It's not something that is application specific. It's a CPU and OS level issue. Which affects also vi ...
  38. ]]>
  39. </description>
  40. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/meltdown-and-spectre-exploit.htm</link>
  41. <category>Security</category>
  42. <dc:creator>Daniel Nashed</dc:creator>
  43. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/meltdown-and-spectre-exploit.htm?opendocument&amp;comments</comments>
  44. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/meltdown-and-spectre-exploit.htm</guid>
  45. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif"><br /> There is a new security issue for most modern CPUs. Intel and AMD is affected in different ways. <br /> It's not something that is application specific. It's a CPU and OS level issue. Which affects also virtualization hosts.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> Here is the best website to get details --> </span><a href=https://meltdownattack.com/><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://meltdownattack.com</u></span></a><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> And there are already some patches for some platforms. <br /> <br /> I have just installed the current kernel patches for CentOS (kernel 2.6.32-696.18.7).</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> Here is the info from RHEL about the first patches </span><a href="https://access.redhat.com/errata/RHSA-2018:0008"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://access.redhat.com/errata/RHSA-2018:0008</u></span></a><span style=" font-size:10pt;font-family:sans-serif">.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> We will probably see patches for other platforms including virtualization platforms like ESX.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> Those are the first fixes. And we will probably see more followup fixes.<strong><br /> <br /> Update 06.01.2018: </strong><br /> <br /> There is an interresting article describing some of the background and what hardware and software vendors are doing against it with different approaches.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-heres-what-intel-apple-microsoft-others-are-doing-about-it/<br /> <br /> From what I see the applications with the biggest exposure to those bugs are web-browsers because they execute active code from remote (e.g. JavaScript).</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Here is also a current statement from Mozilla: </span><span style=" font-size:12pt"><br /> </span><span style=" font-size:12pt;color:blue"><u><br /> </u></span><a href="https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/</u></span></a><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> And there is the status page for Chrome and other Google technologis:</span><span style=" font-size:12pt"> <br /> <br /> </span><span style=" font-size:12pt;color:blue"><u><br /> </u></span><a href=https://support.google.com/faqs/answer/7622138#chrome><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://support.google.com/faqs/answer/7622138#chrome</u></span></a><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> -- Daniel</span><span style=" font-size:12pt"> </span>  ]]></content:encoded>
  46. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/meltdown-and-spectre-exploit.htm</wfw:commentRss>
  47. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/meltdown-and-spectre-exploit.htm?opendocument&amp;comments</wfw:comment>
  48. </item>
  49. <item>
  50. <title>DOMINO NETWORK PERFORMANCE OPTIMIZATION WINDOWS 2008 R2 VERSUS 2012</title>
  51. <pubDate>Sun, 31 Dec 2017 10:19:26 +0200</pubDate>
  52. <description>
  53. <![CDATA[
  54. There is a new APAR which describes a performance issue on Windows 2008 and earlier. The APAR is based on a PMR which I had open with IBM. So I want give you the full detail about what we found out in ...
  55. ]]>
  56. </description>
  57. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-network-performance-optimization-windows-2008-r2-versus-2012.htm</link>
  58. <category>Network</category>
  59. <dc:creator>Daniel Nashed</dc:creator>
  60. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-network-performance-optimization-windows-2008-r2-versus-2012.htm?opendocument&amp;comments</comments>
  61. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/domino-network-performance-optimization-windows-2008-r2-versus-2012.htm</guid>
  62. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">There is a new APAR which describes a performance issue on Windows 2008 and earlier.<br /> The APAR is based on a PMR which I had open with IBM. So I want give you the full detail about what we found out instead of the summary described in &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> LO93355: DOMINO NETWORK PERFORMANCE OPTIMIZATION WINDOWS 2008 R2 VERSUS 2012 --> </span><span style=" font-size:9pt;color:blue;font-family:Default MultiLingual">https://www-01.ibm.com/support/entdocview.wss?uid=swg1LO93355</span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> We had a situation where we needed to replicate databases from an existing Domino 8.5.3 FP6 Windows 2008 environment to a new Domino 9.0.1 FP9 Linux 64 environment. &nbsp;<br /> The replication was quite slow and we tried all kind of optimization on Domino, Windows and Linux. <br /> Beside increasing the sending/receiving buffer and memory we have been looking into ways to optimize the the Domino configuration. <br /> <br /> It turned out that Domino NRPC network compression was not always helpful depending on the configuration. So we ended up to disable network compression in our particular case. But this might not help in your configuration. It's something that needs testing.<br /> Between the Domino application sending the data and the IP-Stack sending the actual data there is a layer called the "NTI" layer which is responsible for actually coordinating sending the data. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> The buffer size can not be modified and depending on the transaction higher latency networks take some time for the round-trip between sending and receiving side. <br /> But the main issue we have seen was that sending attachments which have a bigger chunk size that is send over the network was also slow. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> <br /> Windows 2008 TCP/IP Issue</strong> &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> The issue we found on the Windows IP stack only had impact in network environments which have higher latency than a local network where the latency is around 1 ms. &nbsp;<br /> Our environment had 1 GBit and around 6 ms latency which is already great for a wide area connection . If you are having higher latency the performance might be even lower! <br /> We also reproduced the slow performance also with a faster connection with similar latency (10 GBit network with 5-6 ms latency). So it is the latency that has impact! &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> For transferring attachments with my own written C-API test application we have seen <strong>2,5 MB/sec</strong> transferring data from Win2008. <br /> In contrast Windows 2012 did not have the same issue and that was very strange for us. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> After discussion with the network team and a lot of tests we found the following tuning parameters. <br /> Both parameter do not exist by default on Win2008 R2 but the DefaultSendWindow exists for example on Win7 (which hare &nbsp;comparable network stack) with a smaller value. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> <br /> &#91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AFD\Parameters&#93; &nbsp;<br /> "DefaultSendWindow"=dword:00080000 &nbsp;<br /> "DefaultReceiveWindow"=dword:00080000 &nbsp;</strong></span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> Those settings ensures that the much more chunk sizes are send over the network before the IP-stack waits for the ACK from the other side. By default it was around 12 KB of data which was quite small! <br /> The first tests on our internal environment after the change showed <strong>35 MB/sec</strong>! </span> <br /><span style=" font-size:10pt;font-family:sans-serif"><br /> But that does not mean that normal replication will have the same performance because it is a mix of different transactions! We only tested object write transactions which had the biggest impact in our case.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> <br /> Object Write Chunk-Size is 256 KB</strong> &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> In discussions with IBM we also found out that the documentation for changing the chunk size for sending attachment data was wrong. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> The WIKI documentation say that the chunk size ist 64 KB and can be increased with a Notes.ini parameter up to 1 MB. &nbsp;<br /> But it turns out that the parameter was only implemented as a test for a customer and the fix had never been added to the code. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> Here is the technote describing <strong>Notes.ini SERVER_SEND_OBJECT_CHUNK_SIZE.</strong> &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> This is the only documentation for the parameter that should be corrected. The parameter does currently not exist and the default is<strong> 256 KB</strong>instead of 64 KB. &nbsp;</span><span style=" font-size:12pt"><br /> </span><span style=" font-size:12pt;color:blue"><u><br /> </u></span><a href="https://www-10.lotus.com/ldd/dominowiki.nsf/dx/Optimising_NRPC_Bandwidth_Consumption_for_attachment"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://www-10.lotus.com/ldd/dominowiki.nsf/dx/Optimising_NRPC_Bandwidth_Consumption_for_attachment</u></span></a><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> I have been testing different chunk sizes between 64KB and 1 MB with a low level C-API application which writes attachments.<br /> And I found out that 256KB is a good balanced value. So there would be no need to change this parameter. <strong><br /> <br /> Conclusion and some additional tips for AdminP</strong></span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> When you are running on Win20012 or higher you don't need to change anything. &nbsp;<br /> For Windows 2008 you should really set the registry parameter, because this will be a big boost for your replication performance. &nbsp;</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> On the other side the nature of replication is that document level replication will always take some time even in a local network.<br /> That's why Domino provides accelerated replica which uses a different transaction type.<br /> It's a kind of backup restore over the network. But that does only work if the database is not DAOS enabled. <br /> For DAOS enabled databases the replicator is used and it takes benefit of storage optimization. <br /> It will only send the attachment if it isn't yet on the remote side. But this might be still slower compared to an accelerated replica.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> To better utilize the bandwidth of your 1 GBit line we ended up having multiple AdminP threads leveraging the replicator code to push databases in parallel.<br /> There is ab enhancement in the 9.0.1 codestream (we got it backported to 8.5.3 FP6) which allows one process with multiple threads to replicate in parallel.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> <br /> And if you want AdminP to create the replica immediately instead of just creating a replica stub you need the following notes.ini parameter: <strong>ADMINP_EXCHANGE_ALL_UNREAD_MARKS=1</strong>.<br /> <br /> When you set this parameter Adminp actually pushes the database instead of creating a replica stub and also syncs all unread marks for the database. <br /> Note: &nbsp;The admin4.nsf the request type will look like accelerated replica copy even DAOS is enabled on the database and the status of the request also looks a bit different.<br /> You should not be worried about that. It will use the normal replicator code including unread mark sync.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br />  &nbsp;</span>  ]]></content:encoded>
  63. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/domino-network-performance-optimization-windows-2008-r2-versus-2012.htm</wfw:commentRss>
  64. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-network-performance-optimization-windows-2008-r2-versus-2012.htm?opendocument&amp;comments</wfw:comment>
  65. </item>
  66. <item>
  67. <title>Domino 9.0.1 FT Index Hang and potential crash</title>
  68. <pubDate>Sun, 10 Dec 2017 06:08:37 +0200</pubDate>
  69. <description>
  70. <![CDATA[
  71. We ran into a hang situation multiple times during FT indexing. It turned out that this is a regression introduced in FP9 due to changes in the FT index area. In certain situations the FTIndex update ...
  72. ]]>
  73. </description>
  74. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-ft-index-hang-and-potential-crash.htm</link>
  75. <category>FP9</category>
  76. <dc:creator>Daniel Nashed</dc:creator>
  77. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-ft-index-hang-and-potential-crash.htm?opendocument&amp;comments</comments>
  78. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-ft-index-hang-and-potential-crash.htm</guid>
  79. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">We ran into a hang situation multiple times during FT indexing. It turned out that this is a regression introduced in FP9 due to changes in the FT index area.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">In certain situations the FTIndex update does hang getting document data and will cause one CPU core to be maxed out for this thread.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">The description of the SPR says it is a "spike" but it more looks like the thread permanently uses CPU.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">This can happen with updall, DBMT and also other tasks updating the FT index.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">The process cannot be stopped and this will also cause that the server cannot be shutdown cleanly.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">We got a hotfix which will will be included in IF3. After applying the hotfix we had no new server hangs.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">I am including the call-stack for the hang to this blog post to have it searchable for others who might run into the same issue.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">If you have not installed FP9 you should wait for IF3. If you are on FP9 and run into this issue, take a full NSD, open a PMR and reference the mentioned SPR numbers to get the fix.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Daniel</span> <br /> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Fixed SPRs --</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif"><strong>SPR #SVEM9SLCL7 </strong></span> <br /><span style=" font-size:10pt;font-family:sans-serif">J3 server crashed on DBMT task, while full text indexing the database </span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif"><strong>SPR #TDOOAT6LK9 </strong></span> <br /><span style=" font-size:10pt;font-family:sans-serif">CPU spike when running dbmt (or updall/update task) and creating full text index. </span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Call Stack --</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Thread 3 (Thread 0x7f2c5da71700 (LWP 17594)): </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#0 &nbsp;ODSToOrFromHost (toHost=32769, type=0, vbuffer=0x7f2c5da6e8e0, iterations=1) at ods.c:824 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#1 &nbsp;0x00007f2cba7ef8fe in ODSReadItem (src=0x7f2c54466d96, type=<value optimized out>, dest=0x7f2c5da6e8e0) at ods.c:1420 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#2 &nbsp;0x00007f2cbab635e2 in GetChar(STREAM_CTX*, STREAM_DATA*) () from /opt/ibm/domino/notes/latest/linux/libnotes.so </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#3 &nbsp;0x00007f2cbab64932 in <strong>FTGetDocStream</strong> () from /opt/ibm/domino/notes/latest/linux/libnotes.so </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#4 &nbsp;0x00007f2c5d390919 in NotesStreamReadChar (arg=<value optimized out>) at ftg_dstr.cpp:1412 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#5 &nbsp;0x00007f2cbab5ca7c in FTLexMatch () from /opt/ibm/domino/notes/latest/linux/libnotes.so </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#6 &nbsp;0x00007f2c5d39296c in FTGCreateIndex (pFTGCtx=0x7f2c4c00abf8) at ftg_dstr.cpp:1839 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#7 &nbsp;0x00007f2c5d38bac0 in CFTNoteIndexer::ProcessDoc(FTG_CTX *, struct {...} &amp;) (this=<value optimized out>, pFTGCtx=0x7f2c4c00abf8, docIndexerInfo=...) at ftgindex.cpp:2074 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#8 &nbsp;0x00007f2c5d38c5d1 in FTGIndexIDProc (Parameter=<value optimized out>, NoteID=207326) at ftgindex.cpp:1685 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#9 &nbsp;0x00007f2cb999285d in IDEnumerate (hTable=536872571, Routine=0x7f2c5d38c343 <FTGIndexIDProc(void*, DWORD)>, Parameter=0x7f2c4c00abf8) at idtable.c:2216 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#10 0x00007f2c5d38e252 in <strong>FTGIndex</strong>(FT_THREAD *, struct {...} *, WORD, char *) (pftt=0x7f2cb41004d0, pFTStreamCtx=0x7f2c4c00abf8, Options=392, StopFile=<value optimized out>) at ftgindex.cpp:1146 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#11 0x00007f2cbab5adce in FTCallIndex () from /opt/ibm/domino/notes/latest/linux/libnotes.so </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#12 0x00007f2cbab5c3a3 in FTIndexExt2 () from /opt/ibm/domino/notes/latest/linux/libnotes.so </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#13 0x00007f2cb93e8485 in UpdateFullTextIndex (hDB=1154, Pathname=0x7f2cb4101648 "mail/c1/xn06451.nsf", Flags=201342976, fullTextStatus=8) at update.c:1239 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#14 0x00007f2cb93ea78f in UpdateCollectionsExt (_hModule=<value optimized out>, Pathname=0x7f2cb4101648 "mail/c1/xn06451.nsf", Type=2, Flags=201342976, Flags2=0, mSecs=0, ViewNoteID=0, ContainerObjectID=0, ViewTitle=0x40a360 "", retDbTitle=0x0, fSrchSite=0, QueuedRequest=0, retbLater=0x0, fullTextStatus=8, wantsFulltext=0x0) at update.c:660 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#15 0x00007f2cb93ea957 in UpdateCollections (_hModule=32769, Pathname=0x0, Flags=<value optimized out>, ViewNoteID=<value optimized out>, ContainerObjectID=<value optimized out>, ViewTitle=<value optimized out>, retDbTitle=0x0, fSrchSite=0, QueuedRequest=0, retbLater=0x0, fullTextStatus=8, wantsFulltext=0x0) at update.c:106 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#16 0x0000000000405238 in UpdallThread (threadparam=<value optimized out>) at dbmt.c:2108 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#17 0x00007f2cb98e7be3 in ThreadWrapper (Parameter=<value optimized out>) at thread.c:1183 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#18 0x0000003aae007aa1 in start_thread () from /lib64/libpthread.so.0 </span> <br /><span style=" font-size:10pt;font-family:sans-serif">#19 0x0000003aadce8bcd in clone () from /lib64/libc.so.6 </span> <br />  ]]></content:encoded>
  80. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/domino-9.0.1-ft-index-hang-and-potential-crash.htm</wfw:commentRss>
  81. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-ft-index-hang-and-potential-crash.htm?opendocument&amp;comments</wfw:comment>
  82. </item>
  83. <item>
  84. <title>End of Service for JVM 1.6</title>
  85. <pubDate>Sat, 25 Nov 2017 13:34:30 +0200</pubDate>
  86. <description>
  87. <![CDATA[
  88. IBM uses the Oracle JVM as their base for their IBM JVM platform which is used in IBM products like Notes, Domin and Traveler. JVM 6.0 has been around for almost 10 years and is now discontinued si ...
  89. ]]>
  90. </description>
  91. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/end-of-service-for-jvm-1.6.htm</link>
  92. <category>Java</category>
  93. <dc:creator>Daniel Nashed</dc:creator>
  94. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/end-of-service-for-jvm-1.6.htm?opendocument&amp;comments</comments>
  95. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/end-of-service-for-jvm-1.6.htm</guid>
  96. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif"><br /> IBM uses the Oracle JVM as their base for their IBM JVM platform which is used in IBM products like Notes, Domin and Traveler.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> JVM 6.0 has been around for almost 10 years and is now discontinued since Sep 2017. <br /> Oracle discontinued their support for JVM 1.6 so IBM cannot support JVM 1.6 on their side.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> That also means for IBM platforms that there is no patch support for JVM 1.6!</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> For Notes and Domino means you have to update to 9.0.1 FP8/FP10 for JVM 1.8 and hopefully FP10 will bring compile time for JVM 1.8 as well (current planning).</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> If you are running on Notes/Domino 8.5.3 or an earlier 9.0.1 FP don't panic. Most Java applications on Domino are not directly accessible over the network. There is at least the Domino HTTP stack between the client and the Java application.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> On the client side you might have direct connection from the client to the internet. And for encrypted connections there have been limitations before in the SSL/TLS area as posted before. <br /> For example there is just very limited TLS 1.2 support in JVM 1.6 with just one chiper.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> I personally would still wait for Feature Pack 10 and have the full JVM 1.8 support also at compile time. But you should be aware that it is time to move to a current release.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> If you are on 9.0.1 you are just a "FP" install away. If you are on 8.5.3 there are another good reasons to move to a current 9.0.1 release from security point of view. For example missing SHA-256 support and no TLS 1.2 support - not just for JVM.</span><span style=" font-size:12pt"> <br /> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Here is a link to the support cycle for the IBM JVM</span><span style=" font-size:12pt"> </span><span style=" font-size:12pt;color:blue"><u><br /> </u></span><a href=https://developer.ibm.com/javasdk/support/lifecycle/><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://developer.ibm.com/javasdk/support/lifecycle/</u></span></a><span style=" font-size:12pt"> <br /> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Daniel</span><span style=" font-size:12pt"> </span>  ]]></content:encoded>
  97. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/end-of-service-for-jvm-1.6.htm</wfw:commentRss>
  98. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/end-of-service-for-jvm-1.6.htm?opendocument&amp;comments</wfw:comment>
  99. </item>
  100. <item>
  101. <title>Traveler 9.0.1.20 Released</title>
  102. <pubDate>Sat, 18 Nov 2017 14:44:58 +0200</pubDate>
  103. <description>
  104. <![CDATA[
  105. Traveler 9.0.1.20 has been released and I installed it already. As usual, if you are not waiting for an urgent open issue that is listed in the fix list, it might make sense to wait before installing ...
  106. ]]>
  107. </description>
  108. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.20-released.htm</link>
  109. <category>Traveler</category>
  110. <dc:creator>Daniel Nashed</dc:creator>
  111. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.20-released.htm?opendocument&amp;comments</comments>
  112. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.20-released.htm</guid>
  113. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">Traveler 9.0.1.20 has been released and I installed it already. </span> <br /><span style=" font-size:10pt;font-family:sans-serif">As usual, if you are not waiting for an urgent open issue that is listed in the fix list, it might make sense to wait before installing a new version in production asap.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">I have installed it already befor the weekend and it looks good for my small environment.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Beside the fixes listed below there is a new feature:</span> <br /> <ul> <li><span style=" font-size:10pt;font-family:sans-serif">Support for invitee availability search from Calendar on Exchange ActiveSync clients.</span></li></ul> <br /><span style=" font-size:10pt;font-family:sans-serif">Still trying to test it. Not sure the iOS native calendar does support it. </span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">I did not have this on the radar and also never tested with the Verse app. Don't see it working here.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">Maybe someone has an idea?</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">I did not testing but without luck on any of my clients.</span> <br /><span style=" font-size:12pt"><br /> </span> <table width=689 style="border-collapse:collapse;"> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt"><strong>APAR #</strong></span> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt"><strong>Abstract</strong></span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93044"><span style=" font-size:12pt;color:blue"><u>LO93044</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Slow sync due to prime sync thread looping over large number of child documents.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93067"><span style=" font-size:12pt;color:blue"><u>LO93067</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Better handling of encrypted mail when syncing to mobile device.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93070"><span style=" font-size:12pt;color:blue"><u>LO93070</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Traveler cleanup bind command may fail when using MS SQL Server.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93084"><span style=" font-size:12pt;color:blue"><u>LO93084</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Better handling of Notes Doc Links when syncing to mobile devices.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93196"><span style=" font-size:12pt;color:blue"><u>LO93196</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Traveler "did not respond in time" messages on the console log.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93217"><span style=" font-size:12pt;color:blue"><u>LO93217</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Additional HTML to plain text conversion options to improve generated plain text content.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93221"><span style=" font-size:12pt;color:blue"><u>LO93221</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Do not include previous attachments on reply mails from MaaS Secure Mail client.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93236"><span style=" font-size:12pt;color:blue"><u>LO93236</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Improve crash prevention on Traveler server when processing documents.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">L</span><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93238"><span style=" font-size:12pt;color:blue"><u>O93238</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Phone messages with HTML content may not display correctly on mobile device.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93258"><span style=" font-size:12pt;color:blue"><u>LO93258</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Traveler server may be unresponsive due to logging thread deadlock.</span> <tr valign=top height=8> <td width=104 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO93319"><span style=" font-size:12pt;color:blue"><u>LO93319</u></span></a> <td width=576 style="border-style:ridge ridge ridge ridge;border-color:#000000;border-width:1px 1px 1px 1px;padding:1px 1px;"><span style=" font-size:12pt">Support for Domino 9.0.1 FP10.</span></table> <br />  ]]></content:encoded>
  114. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/traveler-9.0.1.20-released.htm</wfw:commentRss>
  115. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.20-released.htm?opendocument&amp;comments</wfw:comment>
  116. </item>
  117. <item>
  118. <title>VIEW_REBUILD_DIR changed to /dev/shm/view_rebuild</title>
  119. <pubDate>Tue, 14 Nov 2017 14:35:22 +0200</pubDate>
  120. <description>
  121. <![CDATA[
  122. We just discovered an interesting configuration issue, which generates quite some logging and is a bit annoying. When you specify the view_rebuild_dir without the trailing slash / back-slash, the serv ...
  123. ]]>
  124. </description>
  125. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/view_rebuild_dir_changed_to</link>
  126. <category></category>
  127. <dc:creator>Daniel Nashed</dc:creator>
  128. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/view_rebuild_dir_changed_to?opendocument&amp;comments</comments>
  129. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/view_rebuild_dir_changed_to</guid>
  130. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">We just discovered an interesting configuration issue, which generates quite some logging and is a bit annoying.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">When you specify the view_rebuild_dir without the trailing slash / back-slash, the server will internally append the slash.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">But if you configured the view_rebuild_dir in the config document without the (back) slash the server will tell you every couple of minutes that the server changed the setting.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">This happens why the internal path is always stored with the trailing (back) slash and the notes.ini check to update the parameter compares against the config doc entry without the (back) slash.</span> <br /> <br /><span style=" font-size:10pt;color:red;font-family:sans-serif"><strong>VIEW_REBUILD_DIR changed to /dev/shm/view_rebuild</strong></span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">So you have a constant changing parameter -- even it looks the same in the notes.ini </span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">The correct notes.ini entry would be </span> <br /> <br /><span style=" font-size:10pt;color:#008000;font-family:sans-serif"><strong>VIEW_REBUILD_DIR changed to /dev/shm/view_rebuild/ </strong></span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">including the trailing slash.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">This avoids the log messages.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Daniel</span> <br />  ]]></content:encoded>
  131. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/view_rebuild_dir_changed_to</wfw:commentRss>
  132. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/view_rebuild_dir_changed_to?opendocument&amp;comments</wfw:comment>
  133. </item>
  134. <item>
  135. <title>Erster DNUG &quot;Domino Next&quot; Event 23.11.2017</title>
  136. <pubDate>Thu, 9 Nov 2017 13:44:18 +0200</pubDate>
  137. <description>
  138. <![CDATA[
  139. Nach den Ankündigungen zu Domino 10, der IBM &amp; HCL Kooperation und Domino 2025 haben wir die Agenda für den DNUG Domino Day am 23.11.2017 in Düsseldorf umgestellt. Teil des Domino Days wird ein ...
  140. ]]>
  141. </description>
  142. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/erster-dnug-domino2025-jam-event.htm</link>
  143. <category>DNUG</category>
  144. <dc:creator>Daniel Nashed</dc:creator>
  145. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/erster-dnug-domino2025-jam-event.htm?opendocument&amp;comments</comments>
  146. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/erster-dnug-domino2025-jam-event.htm</guid>
  147. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">Nach den Ankündigungen zu Domino 10, der IBM &amp; HCL Kooperation und Domino 2025 haben wir die Agenda für den DNUG Domino Day am 23.11.2017 in Düsseldorf umgestellt.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Teil des Domino Days wird ein Domino Next Feedback Richtung Domino 10 und beyond. </span> <br /><span style=" font-size:10pt;font-family:sans-serif">Neben Uffe Sorensen wir auch ein Kollege von HCL mit dabei sein.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Es wird &nbsp;im Vortrag von Uffe u.A. um die aktuellen Informationen zur Kooperation gehen. <br /> Ihr könnt alle eure Fragen mitbringen und im "Feedback" Teil geht es dann um Feedback für Wünsche für Domino 10 und beyond.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Dieser Teil ist bewußt ans Ende gelegt, damit genügend Zeit für Fragen ist ...</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Ich bin sehr gespannt. </span><span style=" font-size:12pt"><br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> PS: Der Event ist für DNUG Mitglieder kostenlos! Gegen eine Gebühr können auch nicht Mitglieder teilnehmen...</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br />  </span><span style=" font-size:12pt">&nbsp;<br /> </span><span style=" font-size:12pt;color:blue"><u><br /> </u></span><a href="https://www.eventbrite.de/e/dnug-fachgruppentag-domino-day-fachgruppe-verse-und-notesdomino-tickets-35785282744"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>https://www.eventbrite.de/e/dnug-fachgruppentag-domino-day-fachgruppe-verse-und-notesdomino-tickets-35785282744</u></span></a><span style=" font-size:12pt"> <br /> <br /> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> 09:00 - 09:10 <br /> <strong>Begrüßung </strong><br /> Daniel Nashed - CEO (Nash!Com) <br /> Manfred Lenz - Technical Sales Professional, IBM Collaboration and Talent Solutions (IBM Software Sales) <br /> <br /> 09:10-10:05 <br /> <strong>UPDATE: IBM Notes/Domino Feature Packs </strong><br /> Daniel Nashed - CEO (Nash!Com)</span> <br /><span style=" font-size:10pt;font-family:sans-serif">&nbsp;<br /> 10.05-11:05 <br /> <strong>ApplicationInsights &amp; IBM Domino Doublecheck - Der Weg um richtige Entscheidungen treffen zu können </strong><br /> Christoph Adler - Senior Consultant (panagenda) <br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">11:05-12:00 <br /> <strong>SSL Zertifikate unter Domino - Allgemeine Einführung und Vorstellung der kostenfreien CA Let's Encrypt </strong><br /> Detlev Poettgen - Geschäftsführer (midpoints) <br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">12:00-13:00 <br /> <strong>Mittagspause</strong></span><span style=" font-size:12pt"><strong> </strong></span><span style=" font-size:10pt;font-family:sans-serif"><br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">13:00-13:45 <br /> <strong>Domino Application Cloud (DAC) &amp; Domino on Docker </strong><br /> Michael Finkenbrink - Certified Senior Architect, IBM Collaboration Solutions (IBM Software Services) <br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">13:45-14:15 <br /> <strong>Kaffeepause </strong><br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">14:15-15:15 <br /> <strong>Keynote: IBM Notes/Domino and Verse On-Premises - News/Strategy/Roadmaps incl. Notes Domino 10 </strong><br /> Uffe Sorensen - Messaging &amp; Collaboration Director (IBM Software Sales) <br /> n.n. - HCL Industries <br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">15:15 - 17:00 <br /> <strong>Notes/Domino Next Feedback" - Workshop in Form eines Knowledge Cafes zum Thema "Anforderungen an Verse Notes Domino 10 und danach</strong><br /> Uffe Sorensen - Messaging &amp; Collaboration Director (IBM Software Sales) <br /> Peter Schütt - Leader IBM Collaboration Solutions Strategy D-A-CH (IBM Software Sales) <br /> Manfred Lenz - Technical Sales Professional, IBM Collaboration and Talent Solutions (IBM Software Sales)</span><span style=" font-size:12pt"> </span> <br />  ]]></content:encoded>
  148. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/erster-dnug-domino2025-jam-event.htm</wfw:commentRss>
  149. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/erster-dnug-domino2025-jam-event.htm?opendocument&amp;comments</wfw:comment>
  150. </item>
  151. <item>
  152. <title>Domino on Linux Start Script 3.1.3 with changed way to request it</title>
  153. <pubDate>Mon, 30 Oct 2017 05:43:05 +0200</pubDate>
  154. <description>
  155. <![CDATA[
  156. Just updated the start script to a new version with some minor changes. There was one issue with systemd on shutdown and I made a change in the way config files are used. Most of the new features are ...
  157. ]]>
  158. </description>
  159. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-on-linux-start-script313.htm</link>
  160. <category>Start Script</category>
  161. <dc:creator>Daniel Nashed</dc:creator>
  162. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-on-linux-start-script313.htm?opendocument&amp;comments</comments>
  163. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/domino-on-linux-start-script313.htm</guid>
  164. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">Just updated the start script to a new version with some minor changes.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">There was one issue with systemd on shutdown and I made a change in the way config files are used.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Most of the new features are coming in either thru projects or when I want something for my own environment.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">I don't get much feedback or feature requests beside that.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">One change triggered by a project was how config files apply. We wanted to use the same configuration for all servers.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">But we wanted special settings for the Traveler servers. So I changed the way the config files apply. </span> <br /><span style=" font-size:10pt;font-family:sans-serif">Now you can use a general config and additional or changed parameters for individual servers.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">That way you can have a general config that you deploy automatically and you keep a server specific file with changes.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">So in that case the general config would be /etc/sysconfig/rc_domino_config.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">And the specific config would be for example: /etc/sysconfig/rc_domino_config_notes.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">This would also work in partitioned environments where each server has a basic configuration and you want additional parameters for a partition.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">On the other side even on partitioned servers you could use variables which depend on variables like the DOMINO_USER.</span> <br /> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif"><strong>Changed way to request the start script</strong></span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">I am also changing the way you can request the new version. Until now I had a request form.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">Now you just send a mail to <strong>dominostartscript</strong> &nbsp;at <strong>nashcom.de</strong> with the subject "<strong>script</strong>".</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">The old implementation was a servertask which read the data posted in database.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">I switched to a pre-delivery agent with some additional logic to check the message.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">So for example I am not triggering an automatic reply if the message is a reply or is an autosubmitted message.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">I am not yet updating the start script page and want to see first how this works with requests coming in thru the blog.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">And I hope you like the new way to request the start script? Any feedback is welcome.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Daniel</span> <br /> <br /> <br /> <br /><tt><span style=" font-size:9pt">--------------</span></tt> <br /><tt><span style=" font-size:9pt">Change History</span></tt> <br /><tt><span style=" font-size:9pt">--------------</span></tt> <br /> <br /><tt><span style=" font-size:9pt">V3.1.3 30.10.2017</span></tt> <br /> <br /><tt><span style=" font-size:9pt">Problems Solved</span></tt> <br /><tt><span style=" font-size:9pt">---------------</span></tt> <br /> <br /><tt><span style=" font-size:9pt">Fixed an issue with systemd in combination with server controller. </span></tt> <br /><tt><span style=" font-size:9pt">Now the server controller correctly shutsdown when the service is stopped</span></tt> <br /> <br /> <br /><tt><span style=" font-size:9pt">New Features</span></tt> <br /><tt><span style=" font-size:9pt">------------</span></tt> <br /> <br /><tt><span style=" font-size:9pt">listini -- displays server's notes.ini</span></tt> <br /> <br /><tt><span style=" font-size:9pt">Changes</span></tt> <br /><tt><span style=" font-size:9pt">-------</span></tt> <br /> <br /><tt><span style=" font-size:9pt">Changed sample rc_domino_config_notes setting DOMINO_PRE_SHUTDOWN_COMMAND to "tell traveler shutdown"</span></tt> <br /> <br /> <br /><tt><span style=" font-size:9pt">V3.1.2 01.09.2017</span></tt> <br /> <br /><tt><span style=" font-size:9pt">New Features</span></tt> <br /><tt><span style=" font-size:9pt">------------</span></tt> <br /> <br /><tt><span style=" font-size:9pt">New check if Domino ".res" files exist and readable to generate warnings</span></tt> <br /> <br /><tt><span style=" font-size:9pt">New short cut command "res" for "resources" </span></tt> <br /> <br /><tt><span style=" font-size:9pt">Changes</span></tt> <br /><tt><span style=" font-size:9pt">-------</span></tt> <br /> <br /><tt><span style=" font-size:9pt">In previous version either the server specific config file was used or the default config file.</span></tt> <br /> <br /><tt><span style=" font-size:9pt">The config files are now used in the following order to allow more flexible configurations:</span></tt> <br /> <br /><tt><span style=" font-size:9pt">- First the default config-file is loaded if exists (by default: /etc/sysconfig/rc_domino_config)</span></tt> <br /><tt><span style=" font-size:9pt">- In the next step the server specifc config-file (by default: /etc/sysconfig/rc_domino_config_notes) is included.</span></tt> <br /><tt><span style=" font-size:9pt">- The server specific config file can add or overwrite configuration parameters.</span></tt> <br /> <br /><tt><span style=" font-size:9pt">This allows very flexible configurations. You can specify global parameters in the default config file and have specific config files &nbsp;per Domino partition.</span></tt> <br /><tt><span style=" font-size:9pt">So you can now use both config files in combination or just one of them.</span></tt> <br />  ]]></content:encoded>
  165. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/domino-on-linux-start-script313.htm</wfw:commentRss>
  166. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-on-linux-start-script313.htm?opendocument&amp;comments</wfw:comment>
  167. </item>
  168. <item>
  169. <title>Great news Notes Domino 10 and beyond </title>
  170. <pubDate>Wed, 25 Oct 2017 20:03:05 +0200</pubDate>
  171. <description>
  172. <![CDATA[
  173. We got great news today. There will be a Notes &amp; Domino 10 in 2018. And IBM also announced that with joined efforts with HCL Technologies they are working on a strategy for #Domino2025. This isn' ...
  174. ]]>
  175. </description>
  176. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/great-news-notes-domino-10-and-beyond.htm</link>
  177. <category>#Domino2025</category>
  178. <dc:creator>Daniel Nashed</dc:creator>
  179. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/great-news-notes-domino-10-and-beyond.htm?opendocument&amp;comments</comments>
  180. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/great-news-notes-domino-10-and-beyond.htm</guid>
  181. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">We got great news today. There will be a Notes &amp; Domino 10 in 2018. And IBM also announced that with joined efforts with HCL Technologies they are working on a strategy for #Domino2025.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">This isn't a new partnership. IBM and HCL are already working together for Tivoli and Rational software. But is was still a big surprise today.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Notes and Domino 9.0.1 FP10 is committed for 2017 and I am looking forward to hear more about the Notes &amp; Domino Strategy planned for 2018 with Notes and Domino 10.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">And I am really looking forward actively giving feedback for future directions that IBM is asking customers and partners for.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif"><br /> See details in this official links</span> <br /> <br /><a href="https://www.ibm.com/blogs/social-business/2017/10/25/ibm-announces-investment-notes-domino-version-10-beyond/"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://www.ibm.com/blogs/social-business/2017/10/25/ibm-announces-investment-notes-domino-version-10-beyond/</span></a> <br /> <br /><a href="https://www.ibm.com/social-business/us-en/announce/domino-jam2025/"><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://www.ibm.com/social-business/us-en/announce/domino-jam2025/</span></a> <br /> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">What a coincident. Tomorrow I am part of a Notes &amp; Domino strategy workshop for a customer and I bet some of the slides of one of the co-speakers need some updates tonight :-)</span> <br /> <br /> <br /> <br /> <br /><img  alt="Image:Great news Notes Domino 10 and beyond " border="0" src="http://blog.nashcom.de/nashcomblog.nsf/dx/great-news-notes-domino-10-and-beyond.htm/content/M2?OpenElement" /> <br />  ]]></content:encoded>
  182. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/great-news-notes-domino-10-and-beyond.htm</wfw:commentRss>
  183. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/great-news-notes-domino-10-and-beyond.htm?opendocument&amp;comments</wfw:comment>
  184. </item>
  185. <item>
  186. <title>Correctly Stopping a Traveler Server</title>
  187. <pubDate>Tue, 24 Oct 2017 15:02:57 +0200</pubDate>
  188. <description>
  189. <![CDATA[
  190. This is not new but I ran into this a couple of times on customer site. Specially on a Traveler HA server this becomes important. Shutting down the Traveler servertask when the Domino server/service ...
  191. ]]>
  192. </description>
  193. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/correctly-stopping-a-traveler-server.htm</link>
  194. <category>Traveler</category>
  195. <dc:creator>Daniel Nashed</dc:creator>
  196. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/correctly-stopping-a-traveler-server.htm?opendocument&amp;comments</comments>
  197. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/correctly-stopping-a-traveler-server.htm</guid>
  198. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">This is not new but I ran into this a couple of times on customer site. Specially on a Traveler HA server this becomes important.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Shutting down the Traveler servertask when the Domino server/service is stopped might lead to hang situations of the HTTP task.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> The better way would be to shutdown the Traveler servertask first. But even that might lead to undesired results.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> There is a special Traveler shutdown command "<strong>tell traveler shutdown</strong>" that can be used to let Traveler finish it's work and not accept any new requests before cleanly shutting down.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> When you configured <strong>NTS_AUTOSTART_HTTP=true</strong> the Traveler task did start the HTTP task automatically but by default the HTTP task will not be shutdown automatically when you just shutdown the Traveler servertask.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> If you configure <strong>NTS_AUTOSTOP_HTTP=true</strong> the Traveler servertask will automatically take care of shutting down the HTTP task in the right moment.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> This is important for Traveler HA environments because the Traveler OSGi servlet will only connect to the local Traveler servertask which will than either process the request or forward it to another Traveler server (if another server holds the master monitor for the user).</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> So if you don't shutdown the HTTP task your load-balancer might still send requests to the Traveler server which reports back that the Traveler Server is not available ("<strong>IBM Traveler server is not available</strong>.").</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> That's an undesirable result for a load-balancer because usually the load-balance does not check for this status and might continue to send devices to that Traveler server.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> It makes sense to configure the server to be either fully available or to not respond to HTTPS requests if the Traveler service is not available.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> This is true if you shutdown the Traveler task or also during shutdown of the whole server.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> My Domino start script for Linux allows to configure a pre-shutdown command which can be used to shutdown Traveler before you shutdown the whole server.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> -- /etc/sysconfig/rc_domino_config --</strong></span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> # -- Command to execute before shutting down the Domino server --</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> DOMINO_PRE_SHUTDOWN_COMMAND="tell traveler shutdown"</strong></span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> # -- Delay before shutting down the Domino server after invoking the pre-shutdown command --</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><strong><br /> DOMINO_PRE_SHUTDOWN_DELAY=10</strong></span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> There is no simple solution for Windows because Domino is started as a Windows service. <br /> But if you shutdown your server manually, you should shutdown the Traveler server and also use the notes.ini setting.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Sadly if you shutdown the whole server all processed will receive the quit command at the same time and will start to shutdown. <br /> This means it could come to undesired timing issues when HTTP and Traveler do their shutdown at the same time.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> A controlled Traveler server shutdown would be the cleaner solution.</span><span style=" font-size:12pt"> <br /> </span> <br /><span style=" font-size:10pt;font-family:sans-serif">Update to make it more clear:</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Yes there is a big difference between using <strong>tell traveler quit</strong> and <strong>tell traveler shutdown</strong>!</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">If you quit a servertask the task has only limited time to continue to work with full resources available.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">If a task or a server is in pending shutdown some resources are not available any more and cannot fully controlled terminate pending work.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Here is the decumentation for the shutdown command:</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">Shutdown &#91;command&#93; &nbsp; &nbsp; - Stop accepting new work requests, allow current work to complete, and then Quit. &nbsp;</span> <br /><span style=" font-size:10pt;font-family:sans-serif">If you specify a &#91;command&#93;, then this command will be run after the server is idle but before it quits.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">So it makes a lot of sense to use shutdown instead of quit.</span> <br /><span style=" font-size:10pt;font-family:sans-serif"><br /> ------------</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Another tip that might be still new for some customers. If your load-balancer or other monitoring software support authenticated (with user credentials), SSL enabled probes, there is a very nice feature in Traveler to allow an end to end check for your Traveler server availability.</span><span style=" font-size:12pt"> <br /> </span><span style=" font-size:12pt;color:blue"><u><br /> </u></span><a href="http://blog.nashcom.de/nashcomblog.nsf/dx/HTTPS://traveler.acme.com/traveler?action=getStatus"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>HTTPS://traveler.acme.com/traveler?action=getStatus</u></span></a><span style=" font-size:10pt;font-family:sans-serif"> </span><span style=" font-size:12pt"><br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> Depending on your language settings you either get</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br /> <br /> a.) IBM Notes Traveler server is available.</span><span style=" font-size:10pt"> </span><span style=" font-size:10pt;font-family:Arial"><br /> <br /> b.) IBM Notes Traveler server is not available.</span><span style=" font-size:10pt"> </span><span style=" font-size:10pt;font-family:Arial"><br /> Or an error message for the end to end check for the user you specified. The user must be allowed to user Traveler and have a proper mailfile for this end to end test.</span><span style=" font-size:12pt"> </span><span style=" font-size:10pt;font-family:Arial"><br /> c.) The IBM Notes Traveler server cannot connect to your mail database mail/jdoe.nsf on server CN=domino.acme.com/OU=Srv/O=Acme. &nbsp;Verify that your mail server mail database grants access to server CN=domino.acme.de/OU=Srv/O=Acme and is operational. &nbsp;If this does not resolve the problem, your administrator may need to verify the network connection between the servers and that the IBM Notes Traveler server is allowed to access your mail server.</span><span style=" font-size:10pt"> </span><span style=" font-size:12pt"><br /> </span><span style=" font-size:10pt;font-family:sans-serif"><br /> So I would recommend to</span><span style=" font-size:12pt"> </span> <ul> <li><span style=" font-size:10pt;font-family:sans-serif">always use the "</span><span style=" font-size:10pt;color:#008000;font-family:sans-serif"><strong>tell traveler shutdown</strong></span><span style=" font-size:10pt;font-family:sans-serif">" command first</span><span style=" font-size:12pt"> </span> </li><li><span style=" font-size:10pt;font-family:sans-serif">enable HTTP Auto shutdown -> notes.ini </span><span style=" font-size:10pt;color:#008000;font-family:sans-serif"><strong>NTS_AUTOSTOP_HTTP=true</strong></span><span style=" font-size:12pt"> </span> </li><li><span style=" font-size:10pt;font-family:sans-serif">use the options in my start script if you are running on Linux </span> </li><li><span style=" font-size:10pt;font-family:sans-serif">have a look into the </span><span style=" font-size:10pt;color:#008000;font-family:sans-serif"><strong>?action=getStatus</strong></span><span style=" font-size:10pt;font-family:sans-serif"> command if you didn't use that before</span></li></ul><span style=" font-size:10pt;font-family:sans-serif">-- Daniel</span><span style=" font-size:12pt"> <br /> </span>  ]]></content:encoded>
  199. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/correctly-stopping-a-traveler-server.htm</wfw:commentRss>
  200. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/correctly-stopping-a-traveler-server.htm?opendocument&amp;comments</wfw:comment>
  201. </item>
  202. <item>
  203. <title>Notes Client 9.0.1 FP9 F1 released</title>
  204. <pubDate>Sat, 14 Oct 2017 19:31:24 +0200</pubDate>
  205. <description>
  206. <![CDATA[
  207. There is also a client IF1 for 9.0.1 FP9 which fixes one part of the issue that I reported. Depending on your configuration MIME messages sent did show up with different fonts on Notes clients. It hap ...
  208. ]]>
  209. </description>
  210. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/notes-client-901-fp9-if1</link>
  211. <category>FP9</category>
  212. <dc:creator>Daniel Nashed</dc:creator>
  213. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/notes-client-901-fp9-if1?opendocument&amp;comments</comments>
  214. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/notes-client-901-fp9-if1</guid>
  215. <content:encoded><![CDATA[ <span style=" font-size:10pt;font-family:sans-serif">There is also a client IF1 for 9.0.1 FP9 which fixes one part of the issue that I reported.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">Depending on your configuration MIME messages sent did show up with different fonts on Notes clients.</span> <br /><span style=" font-size:10pt;font-family:sans-serif">It happened in edit mode or when the embedded MIME browser was disabled.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">What has been fixed is that the IF1 client shows correct fronts. But earlier clients still shows different fonts (for example if you send a mail with sans serif it will show up in serif).</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">I don't know if that can be fixed at all but IBM is aware of it and is looking into it.</span> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">-- Daniel</span> <br /> <br /> <br /> <br /><span style=" font-size:10pt;font-family:sans-serif">AYAVAQF7WZ &nbsp; &nbsp; &nbsp; &nbsp; Fix an issue where sent internet mail shows as "serif" font instead of "san serif" &nbsp; &nbsp; &nbsp; &nbsp; </span> <br /><span style=" font-size:10pt;font-family:sans-serif">JVEKARBEP2 &nbsp; &nbsp; &nbsp; &nbsp; Fixed an issue where the contents are not displayed after editing if a Richtext field contains an image and "Store contents as HTML and MIME" is enabled</span> <br /><span style=" font-size:10pt;font-family:sans-serif">YNABANLSUB &nbsp; &nbsp; &nbsp; &nbsp; Fix an error 4399 "Value Is Out Of Range" when running deleteuser lotusscript &nbsp; &nbsp; &nbsp; &nbsp; </span>  ]]></content:encoded>
  216. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/notes-client-901-fp9-if1</wfw:commentRss>
  217. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/notes-client-901-fp9-if1?opendocument&amp;comments</wfw:comment>
  218. </item>
  219. <item>
  220. <title>Domino 9.0.1 FP 9 IF2 available with important fixes</title>
  221. <pubDate>Fri, 13 Oct 2017 11:09:53 +0200</pubDate>
  222. <description>
  223. <![CDATA[
  224. Two of the issues fixed in IF2 have been discussed before in my blog. But there are also two other critical issues fixed. Some of my customers reported DBMT and updall hangs which have been fixed wit ...
  225. ]]>
  226. </description>
  227. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp-9-if2-available-with-important-fixes.htm</link>
  228. <category>Domino</category>
  229. <dc:creator>Daniel Nashed</dc:creator>
  230. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp-9-if2-available-with-important-fixes.htm?opendocument&amp;comments</comments>
  231. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp-9-if2-available-with-important-fixes.htm</guid>
  232. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Two of the issues fixed in IF2 have been discussed before in my blog.</font> <br /><font size=2 face="sans-serif">But there are also two other critical issues fixed.</font> <br /> <br /><font size=2 face="sans-serif">Some of my customers reported DBMT and updall hangs which have been fixed with <strong>TDOOAREP8W</strong>.</font> <br /><font size=2 face="sans-serif">And the Private on first use folder issue also has been reported before.</font> <br /> <br /><font size=2 face="sans-serif">If you have installed 9.0.1 FP 9 you should update to IF2!</font> <br /> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /><font size=2 face="sans-serif"><strong>JPAIAQ5SKW</strong></font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; PANIC: DbMarkCorrupt! (d:\notefile\admin4.nsf Dbiid: 0x3D91E116 0x3C07FE17) &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>JVEKAQSGCC</strong></font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Shared, Private on First Use Folder not working as expected in 9.0.1 FP9. It is not possible to view the folder in Designer. &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>TDOOAREP8W</strong></font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Performances issue (deadlock) with long held lock after update to Domino 9.0.1 FP9. &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif"><strong>YNABANLSUB</strong></font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Error 4399 (Value Is Out Of Range) When Running Deleteuser Lotusscript. &nbsp; &nbsp; &nbsp; &nbsp; </font>  ]]></content:encoded>
  233. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/domino-9.0.1-fp-9-if2-available-with-important-fixes.htm</wfw:commentRss>
  234. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-9.0.1-fp-9-if2-available-with-important-fixes.htm?opendocument&amp;comments</wfw:comment>
  235. </item>
  236. <item>
  237. <title>IBM Champion Program Nominations are open</title>
  238. <pubDate>Tue, 10 Oct 2017 20:05:55 +0200</pubDate>
  239. <description>
  240. <![CDATA[
  241. The IBM champion nominations have just started today. You can nominate your favorite persons in the community to appreciate what they are doing for the community (-- https://developer.ibm.com/dwblog/ ...
  242. ]]>
  243. </description>
  244. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-program-nominations-are-open.htm</link>
  245. <category>IBM Champion</category>
  246. <dc:creator>Daniel Nashed</dc:creator>
  247. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-program-nominations-are-open.htm?opendocument&amp;comments</comments>
  248. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-program-nominations-are-open.htm</guid>
  249. <content:encoded><![CDATA[ <font size=2 face="sans-serif">The IBM champion nominations have just started today.</font> <br /> <br /><font size=2 face="sans-serif">You can nominate your favorite persons in the community to appreciate what they are doing for the community (--> </font><a href="https://developer.ibm.com/dwblog/2017/ibm-champion-program-nominations/"><font size=2 color=blue face="sans-serif">https://developer.ibm.com/dwblog/2017/ibm-champion-program-nominations/</font></a><font size=2 face="sans-serif">)</font> <br /> <br /><font size=2 face="sans-serif">Libby just expressed it in short words what a champion makes stand out. Let me quote instead of just passing a link!</font> <br /> <p><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /><font size=2 face="sans-serif"><strong>"You may know an IBM Champion if…</strong></font> <p><font size=2 face="sans-serif">The best way to understand the IBM Champions program is to know an IBM Champion. Do you think you know a Champion? Here are 7 questions to ask yourself about your technical community. Do these sound familiar?</font> <ul> <li><font size=2 face="sans-serif">Someone freely gives you advice in person, on Twitter, on forums…</font> </li><li><font size=2 face="sans-serif">You regularly read the blog of someone for help or shared code…</font> </li><li><font size=2 face="sans-serif">Someone in your organization knows everything there is to know about your IBM software or hardware and makes it all work together and is always the one answering questions…</font> </li><li><font size=2 face="sans-serif">There is someone whose presentations you enjoy and learn from…</font> </li><li><font size=2 face="sans-serif">Someone is putting their own time into organizing an event you value…</font> </li><li><font size=2 face="sans-serif">Someone has positively influenced your choices of what to deploy and when…</font> </li><li><font size=2 face="sans-serif">There is someone whose contribution you would miss if they were to stop…</font></li></ul><font size=2 face="sans-serif">If you put a name or a face to those 7 questions, you may know an IBM Champion… or someone who should <em>become</em> an IBM Champion!"</font> <p><font size=2 face="sans-serif">See this link for more details about IBM Champions --> </font><a href="https://developer.ibm.com/dwblog/2017/ibm-champion-program-nominations/"><font size=2 color=blue face="sans-serif">https://developer.ibm.com/dwblog/2017/ibm-champion-program-nominations/</font></a> <p> <p>  ]]></content:encoded>
  250. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/ibm-champion-program-nominations-are-open.htm</wfw:commentRss>
  251. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/ibm-champion-program-nominations-are-open.htm?opendocument&amp;comments</wfw:comment>
  252. </item>
  253. <item>
  254. <title>Installing C-API Applications on Linux</title>
  255. <pubDate>Wed, 4 Oct 2017 12:51:45 +0200</pubDate>
  256. <description>
  257. <![CDATA[
  258. When installing binaries on Linux you have to be aware of the directory structure for the files installed in the opt directory. For installing a servertask the recommended way is to copy it to the Do ...
  259. ]]>
  260. </description>
  261. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/installing-c-api-applications-on-linux.htm</link>
  262. <category>Linux</category>
  263. <dc:creator>Daniel Nashed</dc:creator>
  264. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/installing-c-api-applications-on-linux.htm?opendocument&amp;comments</comments>
  265. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/installing-c-api-applications-on-linux.htm</guid>
  266. <content:encoded><![CDATA[ <font size=2 face="sans-serif">When installing binaries on Linux you have to be aware of the directory structure for the files installed in the opt directory.</font> <br /> <br /><font size=2 face="sans-serif">For installing a servertask the recommended way is to copy it to the Domino binary directory and create a start link.</font> <br /> <br /><font size=2 face="sans-serif">For myself I created a script that handles installation of servertasks and extension managers because I don't want to do those steps manually and my script comes with a wrapper script that benefits of sudo when installing binaries on my development environment.</font> <br /><font size=2 face="sans-serif">Also you have to take care that binaries are not running when replacing them.</font> <br /> <br /><font size=2 face="sans-serif">Linux does not prevent you from replacing the file but the Domino server might crash after your replaced the binary. This is true for extension managers and also servertasks.</font> <br /><font size=2 face="sans-serif">In addition the script does check if the file changed at all before replacing the binary.</font> <br /> <br /><font size=2 face="sans-serif">So I will add this new script into the "extras" directory of my start script. But let me quickly describe what you would do in general to install a binary correctly and post the first official version of my script.</font> <br /> <br /> <br /><font size=2 face="sans-serif">In general Domino is usually installed by default today in</font> <br /> <br /><font size=2 face="sans-serif"><strong>/opt/ibm/domino</strong></font> <br /> <br /><font size=2 face="sans-serif">Below that directory there is another directory &nbsp;<strong>/opt/ibm/domino/notes</strong>.</font> <br /> <br /><font size=2 face="sans-serif">Inside that directory we have the latest major version installed (linke 90010 in my case) and a link to the latest version</font> <br /> <br /> <br /><tt><font size=2>drwxr-xr-x 4 root root 4096 Apr 24 &nbsp;2014 90010</font></tt> <br /><tt><font size=2>lrwxrwxrwx 1 root root &nbsp; &nbsp;5 Sep 26 &nbsp;2015 latest -> 90010</font></tt> <br /> <br /><font size=2 face="sans-serif">Best practice is always to use the "latest" directory</font> <br /> <br /><font size=2 face="sans-serif">So the actual directory the binaries located is:</font> <br /> <br /><font size=2 face="sans-serif"><strong>/opt/ibm/domino/notes/latest/linux</strong></font> <br /> <br /><font size=2 face="sans-serif">This directory contains all the binaries and is the place where you should copy new binaries and make them executable:</font> <br /> <br /><font size=2 color=#008000 face="sans-serif"><strong>cp mybinary &nbsp;/opt/ibm/domino/notes/latest/linux</strong></font> <br /><font size=2 color=#008000 face="sans-serif"><strong>chmod 755 /opt/ibm/domino/notes/latest/linux/mybinary</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif">For an extension manager there is nothing else to do. But for a servertask you have to create a startup-link in</font> <br /> <br /><font size=2 face="sans-serif"><strong>/opt/ibm/domino/bin</strong></font> <br /> <br /><font size=2 face="sans-serif">The directory contains startup links pointing to a startup script for each servertask (OK not all IBM installed servetasks have a startup link so the installer is missing to create the links).</font> <br /><font size=2 face="sans-serif">If you environment is setup correctly with the right path settings (for example when running my start-script) that's usually not an issue.</font> <br /> <br /> <br /><tt><font size=2>lrwxrwxrwx 1 root root 33 Sep 26 &nbsp;2015 server -> /opt/ibm/domino/bin/tools/startup</font></tt> <br /> <br /> <br /><font size=2 face="sans-serif">This symbolic link points to another symbolic link which finally points to the internal startup script in the binary directory:</font> <br /> <br /><tt><font size=2>lrwxrwxrwx 1 root root &nbsp; 42 Sep 26 &nbsp;2015 startup -> /opt/ibm/domino/notes/latest/linux/startup</font></tt> <br /> <br /> <br /><font size=2 face="sans-serif">Invoking the following commands generates your link for the servertask. Domino creates absolute links. But I prefer relative links.</font> <br /> <br /> <br /><font size=2 color=#008000 face="sans-serif"><strong>cd /opt/ibm/domino/bin</strong></font> <br /><font size=2 color=#008000 face="sans-serif"><strong>ln -s tools/startup mybinary</strong></font> <br /> <br /> <br /><font size=2 face="sans-serif">So what finally happens when you invoke the file on your own or if you are using the load command on the server console, is that Linux starts the internal script leveraging the symbolic link which will set the right environment for your servertask etc and than start the actual binary.</font> <br /> <br /><font size=2 face="sans-serif">I hope this helps a bit to understand the structure and how to install binaries on Linux.<br /> </font> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br /> <br /> <br /> <br /> <br /><tt><font size=2>#!/bin/sh</font></tt> <br /> <br /> <br /><tt><font size=2>check_binary_busy()</font></tt> <br /><tt><font size=2>{</font></tt> <br /><tt><font size=2>&nbsp; if &#91; ! -e "$1" &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; return 0</font></tt> <br /><tt><font size=2>&nbsp; fi</font></tt> <br /> <br /><tt><font size=2>&nbsp; TARGET_REAL_BIN=`readlink -f $1`</font></tt> <br /><tt><font size=2>&nbsp; FOUND_TARGETS=`lsof | awk '{print $9}' | grep "$TARGET_REAL_BIN"`</font></tt> <br /> <br /><tt><font size=2>&nbsp; if &#91; -n "$FOUND_TARGETS" &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; return 1</font></tt> <br /><tt><font size=2>&nbsp; else</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; return 0</font></tt> <br /><tt><font size=2>&nbsp; fi</font></tt> <br /><tt><font size=2>}</font></tt> <br /> <br /> <br /><tt><font size=2>install_binary()</font></tt> <br /><tt><font size=2>{</font></tt> <br /><tt><font size=2>&nbsp; SOURCE_BIN=$1</font></tt> <br /> <br /><tt><font size=2>&nbsp; if &#91; -z "$SOURCE_BIN" &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; echo "no file specified"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; return 0</font></tt> <br /><tt><font size=2>&nbsp; fi</font></tt> <br /> <br /><tt><font size=2>&nbsp; INSTALL_BIN_NAME=`basename $SOURCE_BIN`</font></tt> <br /> <br /><tt><font size=2>&nbsp; if &#91; -z "$INSTALL_BIN_NAME" &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; echo "no file specified"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; return 0</font></tt> <br /><tt><font size=2>&nbsp; fi</font></tt> <br /> <br /><tt><font size=2>&nbsp; TARGET_BIN=$Notes_ExecDirectory/$INSTALL_BIN_NAME</font></tt> <br /> <br /><tt><font size=2>&nbsp; if &#91; -e "$TARGET_BIN" &#93;; then</font></tt> <br /> <br /><tt><font size=2>&nbsp; &nbsp; cmp -s "$SOURCE_BIN" "$TARGET_BIN"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; if &#91; $? -eq 0 &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; echo "File did not change -- No update needed"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; return 0</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; fi</font></tt> <br /> <br /><tt><font size=2>&nbsp; &nbsp; if &#91; ! -w "$TARGET_BIN" &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; echo "Error - Can not update binary '$TARGET_BIN' -- No write permissions"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; return 1</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; fi</font></tt> <br /> <br /> <br /><tt><font size=2>&nbsp; &nbsp; check_binary_busy "$TARGET_BIN"</font></tt> <br /> <br /><tt><font size=2>&nbsp; &nbsp; if &#91; $? -eq 1 &#93;; then</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; echo "Error - Can not update binary '$TARGET_BIN' -- Binary in use"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; return 1</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; fi</font></tt> <br /><tt><font size=2>&nbsp; fi</font></tt> <br /><tt><font size=2>&nbsp; </font></tt> <br /><tt><font size=2>&nbsp; cp -f "$SOURCE_BIN" "$TARGET_BIN"</font></tt> <br /><tt><font size=2>&nbsp; chmod 755 "$TARGET_BIN"</font></tt> <br /> <br /><tt><font size=2>&nbsp; case "$INSTALL_BIN_NAME" in</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; *.so)</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; echo "Installed '$INSTALL_BIN_NAME' Extension-Manager"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; ;;</font></tt> <br /> <br /><tt><font size=2>&nbsp; &nbsp; *)</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; cd $LOTUS/bin</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; ln -f -s tools/startup "$INSTALL_BIN_NAME"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; echo "Installed '$INSTALL_BIN_NAME' Servertask"</font></tt> <br /><tt><font size=2>&nbsp; &nbsp; &nbsp; ;;</font></tt> <br /> <br /><tt><font size=2>&nbsp; esac</font></tt> <br /> <br /><tt><font size=2>&nbsp; return 0</font></tt> <br /><tt><font size=2>}</font></tt> <br /> <br /> <br /><tt><font size=2>export LOTUS=/opt/ibm/domino</font></tt> <br /><tt><font size=2>export Notes_ExecDirectory=$LOTUS/notes/latest/linux</font></tt> <br /> <br /><tt><font size=2>install_binary "$1"</font></tt> <br /> <br /><tt><font size=2>exit 0</font></tt>  ]]></content:encoded>
  267. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/installing-c-api-applications-on-linux.htm</wfw:commentRss>
  268. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/installing-c-api-applications-on-linux.htm?opendocument&amp;comments</wfw:comment>
  269. </item>
  270. <item>
  271. <title>Known issues with Domino 9.0.1 FP9</title>
  272. <pubDate>Wed, 27 Sep 2017 05:38:56 +0200</pubDate>
  273. <description>
  274. <![CDATA[
  275. A couple of customers and partners asked me about current known issues with FP9 in my blog and offline. Beside the issue with the garbage chars fixed in IF1 there are 3 other issues that could preven ...
  276. ]]>
  277. </description>
  278. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/known-issues-with-domino-9.0.1-fp9.htm</link>
  279. <category>FP9</category>
  280. <dc:creator>Daniel Nashed</dc:creator>
  281. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/known-issues-with-domino-9.0.1-fp9.htm?opendocument&amp;comments</comments>
  282. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/known-issues-with-domino-9.0.1-fp9.htm</guid>
  283. <content:encoded><![CDATA[  <br /><font size=2 face="sans-serif">A couple of customers and partners asked me about current known issues with FP9 in my blog and offline.</font> <br /><font size=2 face="sans-serif">Beside the issue with the garbage chars fixed in IF1 there are 3 other issues that could prevent you from upgrading to FP9.</font> <br /><font size=2 face="sans-serif"><br /> There is an issue with private on first use views and folders on the server side which prevents those views and folders to be created.</font> <br /><font size=2 face="sans-serif">IBM has a hotfix for this as Sascha already reported in my blog comments.</font> <br /><font size=2 face="sans-serif"><br /> <strong>SPR# JVEKAQSGCC / LO92948: SHARED, PRIVATE ON FIRST USE FOLDER NOT WORKING AS EXPECTED IN 9.0.1 FP9. IT IS NOT POSSIBLE TO VIEW THE FOLDER IN DESIGNER </strong><br /> </font> <br /><font size=2 face="sans-serif">In addition some customers ran into a hang during view update with DBMT where IBM is working on a solution. One customer already got a test hotfix but I have no confirmed status yet if this finally solved the regression.</font> <br /><font size=2 face="sans-serif"><br /> <strong>SPR TDOOAREP8W Performances issue with long held lock after update to Domino 9.0.1 FP9 </strong><br /> <br /> <br /> IMHO both SPRs are good candidates for an IF2.</font> <br /> <br /><font size=2 face="sans-serif">I keep you posted what I hear.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br />  ]]></content:encoded>
  284. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/known-issues-with-domino-9.0.1-fp9.htm</wfw:commentRss>
  285. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/known-issues-with-domino-9.0.1-fp9.htm?opendocument&amp;comments</wfw:comment>
  286. </item>
  287. <item>
  288. <title>Fix Available: SMTP regression issue in Domino 9.0.1 FP9 can cause malformed headers </title>
  289. <pubDate>Sat, 16 Sep 2017 00:43:31 +0200</pubDate>
  290. <description>
  291. <![CDATA[
  292. Finally we got IF1 for 9.0.1 FP9 for the issue I reported in an earlier blog post . The regression was introduced by a fix that IBM has removed in IF1 (and I got a hotfix earlier as mentioned in an ea ...
  293. ]]>
  294. </description>
  295. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/fix-available-smtp-regression-issue-in-domino-9.0.1-fp9-can-cause-malformed-headers-.htm</link>
  296. <category>Domino</category>
  297. <dc:creator>Daniel Nashed</dc:creator>
  298. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/fix-available-smtp-regression-issue-in-domino-9.0.1-fp9-can-cause-malformed-headers-.htm?opendocument&amp;comments</comments>
  299. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/fix-available-smtp-regression-issue-in-domino-9.0.1-fp9-can-cause-malformed-headers-.htm</guid>
  300. <content:encoded><![CDATA[ <font size=2 face="sans-serif">Finally we got IF1 for 9.0.1 FP9 for the issue I reported in an earlier blog post</font> <br /><font size=2 face="sans-serif">.</font> <br /><font size=2 face="sans-serif">The regression was introduced by a fix that IBM has removed in IF1 (and I got a hotfix earlier as mentioned in an earlier blog post).</font> <br /> <br /><font size=2 face="sans-serif">The root cause is an issue with malformed headers &nbsp;-- specially the from header that are generated at message itemization. </font> <br /> <br /><font size=2 face="sans-serif">Depending on your configuration this causes garbage chars in your headers. In any case some functionality like SMTPVerifyAuthenticatedSender=1 or capturing mail for certain recipients via SMTPSaveImportErrors=3 and SMTPSaveFileFrom=sender &nbsp;did not work any more.</font> <br /> <br /><font size=2 face="sans-serif">This is not the final fix. IBM is working on resolving the regression. So this fix along with another agent bug fix is really just a quick fix to allow you to deploy FP9.</font> <br /> <br /><font size=2 face="sans-serif">I installed the fix on my Linux64 machine which shows up as 9.0.1 FP9 HF 63 and it resolves the regression.</font> <br /> <br /><font size=2 face="sans-serif">See details here:</font> <br /> <br /><font size=2 face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg22008327</font> <br /> <br /><font size=2 face="sans-serif">IF1 contains the two fixes:</font> <br /> <br /><font size=2 face="sans-serif">KBRNAQKKK9</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Domino agents crash in the backend in FP8 with a memory overwrite &nbsp; &nbsp; &nbsp; &nbsp; </font> <br /> <br /><font size=2 face="sans-serif">JCARAQSJB6</font> <br /><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; SMTP regression issue in Domino 9.0.1FP9 can cause malformed headers &amp; prevent Internet mail delivery with SMTPVerifyAuthenticatedSender=1 (technote 2008327) &nbsp; &nbsp; &nbsp; &nbsp; </font> <br />  ]]></content:encoded>
  301. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/fix-available-smtp-regression-issue-in-domino-9.0.1-fp9-can-cause-malformed-headers-.htm</wfw:commentRss>
  302. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/fix-available-smtp-regression-issue-in-domino-9.0.1-fp9-can-cause-malformed-headers-.htm?opendocument&amp;comments</wfw:comment>
  303. </item>
  304. <item>
  305. <title>Domino Performance issue on some Linux Versions</title>
  306. <pubDate>Thu, 14 Sep 2017 12:13:17 +0200</pubDate>
  307. <description>
  308. <![CDATA[
  309. When working on a larger Domino migration and consolidation project I ran into an new Linux specific performance issues that might hit some of you depending on your Linux version. I have tested with ...
  310. ]]>
  311. </description>
  312. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-performance-issue-on-some-linux-versions.htm</link>
  313. <category>Performance</category>
  314. <dc:creator>Daniel Nashed</dc:creator>
  315. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/domino-performance-issue-on-some-linux-versions.htm?opendocument&amp;comments</comments>
  316. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/domino-performance-issue-on-some-linux-versions.htm</guid>
  317. <content:encoded><![CDATA[ <font size=2 face="sans-serif">When working on a larger Domino migration and consolidation project I ran into an new Linux specific performance issues that might hit some of you depending on your Linux version.</font><font size=3> </font><font size=2 face="sans-serif"><br /> I have tested with current RHEL 7 servers which are not affected.</font><font size=3> </font><font size=2 face="sans-serif"><br /> But on customer site we are using the latest patch level of RHEL 6.9 and I have also seen it with SLES 11 SP2/3. I did not yet test with SLES 12 (maybe someone volunteers to do some testing).</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> There has been an issue in the 8.5.3 code stream which has been fixed in 8.5.3 FP2. </font><font size=3><br /> </font><font size=2 face="sans-serif"><strong><br /> SPR# PHEY8RJHXR - Fixed a performance issue where creating multiple documents with attachments led to high NETIO delays on Linux, Mac, and IBM i, resulting in slower transactions for other users accessing other databases.</strong></font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> The old issue has been a timing issue between the Domino network stack/listener and the scheduling of the kernel.</font><font size=3> </font><font size=2 face="sans-serif"><br /> The change was to use native pthread semaphores in the Domino network layer.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> But already at that time we saw some performance issues with the standard kernel tuning</font><font size=3> </font><font size=2 face="sans-serif"><br /> (see --> </font><a href="http://blog.nashcom.de/nashcomblog.nsf/dx/runfaster1-for-domino-on-linux.htm"><font size=2 color=blue face="sans-serif"><u>http://blog.nashcom.de/nashcomblog.nsf/dx/runfaster1-for-domino-on-linux.htm</u></font></a><font size=2 face="sans-serif"> for details).</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> Over time some other changes in the kernel made the default settings used for the CFS process scheduler to not work nicely with Domino in some kernel versions.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> I discovered this slow down specially for attachment write transactions when troubleshooting some Windows related issues on the sending side (working on another blog post for the Windows 2008 issue).</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> But at least on RHEL 6.x and some SLES versions the receiving side can and should be optimized.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> For testing I wrote a simple servertask which &nbsp;creates attachments in a remote database from memory to benchmark the performance.</font><font size=3> </font><font size=2 face="sans-serif"><br /> It turned out that with standard kernel settings for server in a local network we have been able to write with <strong>25 MB/sec</strong>.</font><font size=3> </font><font size=2 face="sans-serif"><br /> With the kernel tuning changes we have been able to write with over <strong>100 MB/sec</strong>.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> Attachment write operations are just one part of the communication but specially when consolidating servers all attachments have to be transferred which will be the bigger part of the data that has to be transferred.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> The setting I found is responsible for the CFS scheduler behavior for process scheduling. It specially hits larger transfer operations like attachments (I did not test other transactions types).</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> By default the setting is set to 12 ms on RHEL 6.9 &nbsp;(take care it is specified in nano seconds). This is causing some timing issues with the Domino network layer.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> I have found a recommendation for SAP on Linux which suggested to reduce the value to 1 ms. But in my testing already reducing it to 6 ms did help.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> My suggestion would be to set the value to 4 ms.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> You can change the parameter via:</font><font size=3> <br /> </font><font size=2 face="sans-serif"><strong><br /> echo 4000000 > &nbsp;/proc/sys/kernel/sched_latency_ns </strong></font><font size=3><br /> </font><font size=2 face="sans-serif"><br /> OR you can permanently set it in <strong>/etc/sysctl.conf</strong></font><font size=3> <br /> </font><font size=2 face="sans-serif"><strong><br /> kernel.sched_latency_ns = 4000000</strong></font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> Automatically set after boot or run once <strong>sysctl -p </strong></font><font size=3><br /> <br /> </font><font size=2 face="sans-serif"><br /> Again this setting might not be needed for all Linux versions and should be Domino release independent (I have tested the lates 8.5.3 FP6 versions and 9.0.1 FP8/9).</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> So you could either set it as a best practice or use my test tool to check you current performance. <br /> My tests with the latest RHEL 7 version did show that even setting the value much higher there, did not have any performance impact.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> I am happy to send over the test tool for Windows or Linux. I cannot make it available for download because I don't want to spead the binaries uncontrolled.</font><font size=3> </font><font size=2 face="sans-serif"><br /> But feel free to contact me by mail and I am also interested to see your results, when you test it.</font><font size=3> </font><font size=2 face="sans-serif"><br /> The tool can create documents in any target database and you can specify the number of documents (default is 10).</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> See detailed test results below.</font><font size=3> <br /> </font><font size=2 face="sans-serif"><br /> -- Daniel</font><font size=3> <br /> <br /> </font><font size=2 face="sans-serif"><strong><br /> -- Test with Default Settings --</strong></font><font size=3> <br /> </font><tt><font size=2><br /> cat /proc/sys/kernel/sched_latency_ns</font></tt><font size=3> </font><tt><font size=2><br /> 12000000<br /> <br /> /local/notesdata $ /opt/ibm/domino/bin/nshobj dsim012\!\!admin/nshobj.nsf</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Local Notes/Domino Release 9.0 QMR:1 QMU:9 Hotfix: 0 Fixpack: 0 (0)</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Remote Notes/Domino Release 9.0 QMR:1 QMU:9 Hotfix: 0 Fixpack: 0 (0)</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Database: &nbsp; 'dsim012!!admin/nshobj.nsf'</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Att-Size: &nbsp; 2097152</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Chunk-Size: 262144</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Count: &nbsp; &nbsp; &nbsp;10</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Total: &nbsp; &nbsp; &nbsp;814</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Minimum: &nbsp; &nbsp;19</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Maximum: &nbsp; &nbsp;194</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Average: &nbsp; &nbsp;81</font></tt><tt><font size=3> </font></tt><tt><font size=2><strong><br /> MB/Sec: &nbsp; &nbsp; 25,3</strong></font></tt><tt><font size=3><strong> </strong><br /> </font></tt><font size=3><br /> </font><font size=2 face="sans-serif"><strong><br /> -- Test with Modified Settings --</strong></font><tt><font size=2><br /> <br /> echo 4000000 > &nbsp;/proc/sys/kernel/sched_latency_ns</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> <br /> /local/notesdata $ /opt/ibm/domino/bin/nshobj dsim012\!\!admin/nshobj.nsf</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Local Notes/Domino Release 9.0 QMR:1 QMU:9 Hotfix: 0 Fixpack: 0 (0)</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Remote Notes/Domino Release 9.0 QMR:1 QMU:9 Hotfix: 0 Fixpack: 0 (0)</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Database: &nbsp; 'dsim012!!admin/nshobj.nsf'</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Att-Size: &nbsp; 2097152</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Chunk-Size: 262144</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Count: &nbsp; &nbsp; &nbsp;10</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Total: &nbsp; &nbsp; &nbsp;192</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Minimum: &nbsp; &nbsp;16</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Maximum: &nbsp; &nbsp;35</font></tt><tt><font size=3> </font></tt><tt><font size=2><br /> Average: &nbsp; &nbsp;19</font></tt><tt><font size=3> </font></tt><tt><font size=2><strong><br /> MB/Sec: &nbsp; &nbsp; 107,8</strong></font></tt><tt><font size=3><strong> </strong></font></tt><font size=3><br /> </font>  ]]></content:encoded>
  318. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/domino-performance-issue-on-some-linux-versions.htm</wfw:commentRss>
  319. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/domino-performance-issue-on-some-linux-versions.htm?opendocument&amp;comments</wfw:comment>
  320. </item>
  321. <item>
  322. <title>How to resolve synchronization issues that start after upgrading to IBM Traveler 9.0.1.18 (or higher)</title>
  323. <pubDate>Sat, 9 Sep 2017 11:21:53 +0200</pubDate>
  324. <description>
  325. <![CDATA[
  326. If you are running on Traveler 9.0.1.18 and higher you should read the following support flash technote in detail. http://www.ibm.com/support/docview.wss?uid=swg22005703 You must read this technote ...
  327. ]]>
  328. </description>
  329. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/how-to-resolve-synchronization-issues-that-start-after-upgrading-to-ibm-traveler-9.0.1.18-or-higher.htm</link>
  330. <category>Traveler</category>
  331. <dc:creator>Daniel Nashed</dc:creator>
  332. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/how-to-resolve-synchronization-issues-that-start-after-upgrading-to-ibm-traveler-9.0.1.18-or-higher.htm?opendocument&amp;comments</comments>
  333. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/how-to-resolve-synchronization-issues-that-start-after-upgrading-to-ibm-traveler-9.0.1.18-or-higher.htm</guid>
  334. <content:encoded><![CDATA[ <font size=2 face="sans-serif">If you are running on Traveler 9.0.1.18 and higher you should read the following support flash technote in detail.</font> <br /> <br /><a href="http://www.ibm.com/support/docview.wss?uid=swg22005703"><font size=2 color=blue face="sans-serif">http://www.ibm.com/support/docview.wss?uid=swg22005703</font></a> <br /> <br /><font size=2 face="sans-serif">You must read this technote if you are running on 9.0.1.18 and higher. </font> <br /><font size=2 face="sans-serif">And with this new information it makes a lot of sense to move to this new version soon.</font> <br /> <br /><font size=2 face="sans-serif">As mentioned before, IBM changed the default security mode for Traveler. <br /> Traveler uses a run as user feature to ensure that all functionality is invoked in the name of the user.</font> <br /> <br /><font size=2 face="sans-serif">Therefore Traveler server has to be listed in the trusted server on the security tab of the mail-server (which already caused a yellow status warning on your servers in earlier versions in preparation).</font> <br /> <br /><font size=2 face="sans-serif">But there are additional requirements for each mail-database to correctly sync with this new security modeil.</font> <br /><font size=2 face="sans-serif">Some of them have not been documented in detail before this technote was available. And Traveler 9.0.1.19 has more detailed checking/logging if capabilities in access for a database is missing.</font> <br /><font size=2 face="sans-serif">Also there is a fallback per user to the old mode, if not all requirements are full filled for a mail-database.</font> <br /><font size=2 face="sans-serif">For example Maximum Internet Access for a mail-database needs to be set to Editor or higher.</font> <br /> <br /><font size=2 face="sans-serif">The technote describes the requirements and the new error logging in very detail. And also all options that you have to disable the new access mode for the server or per user.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /> <br />  ]]></content:encoded>
  335. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/how-to-resolve-synchronization-issues-that-start-after-upgrading-to-ibm-traveler-9.0.1.18-or-higher.htm</wfw:commentRss>
  336. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/how-to-resolve-synchronization-issues-that-start-after-upgrading-to-ibm-traveler-9.0.1.18-or-higher.htm?opendocument&amp;comments</wfw:comment>
  337. </item>
  338. <item>
  339. <title>Traveler 9.0.1.19 with important fixes</title>
  340. <pubDate>Fri, 8 Sep 2017 09:15:12 +0200</pubDate>
  341. <description>
  342. <![CDATA[
  343. We have been waiting for Traveler 9.0.1.19 for some important fixes and also updates SQL server support and push certificate update: Support for MS SQL Server 2016 Enterprise Edition. Updated ...
  344. ]]>
  345. </description>
  346. <link>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.19-with-important-fixes.htm</link>
  347. <category>Traveler</category>
  348. <dc:creator>Daniel Nashed</dc:creator>
  349. <comments>http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.19-with-important-fixes.htm?opendocument&amp;comments</comments>
  350. <guid isPermaLink="true">http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.19-with-important-fixes.htm</guid>
  351. <content:encoded><![CDATA[ <font size=2 face="sans-serif">We have been waiting for Traveler 9.0.1.19 for some important fixes and also updates SQL server support and push certificate update:</font> <br /><font size=2 face="sans-serif">&nbsp; <br /> &nbsp; </font> <ul> <li><font size=2 face="sans-serif">Support for MS SQL Server 2016 Enterprise Edition. </font> </li><li><font size=2 face="sans-serif">Updated APNS Certificates with expiration 8/1/2018. </font> </li><li><font size=2 face="sans-serif">Improvements for the Run as User Feature.</font></li></ul> <br /><font size=2 face="sans-serif">But the most important changes are for the "Run as User" Feature which has been introduced in 9.0.1.18.</font> <br /><font size=2 face="sans-serif">Some of my customers and issues with Traveler profiles which could not be read correctly in some cases.</font> <br /> <br /><font size=2 face="sans-serif">Beside this fix there are a couple of minor enhancements listed below.</font> <br /> <br /><font size=2 face="sans-serif">-- Daniel</font> <br /><font size=2 face="sans-serif"><strong><br /> Fixlist:</strong> </font> <table width=1381 style="border-collapse:collapse;"> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">APAR # </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Abstract </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92524"><font size=2 color=blue face="sans-serif"><u>LO92524</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Sync performance impacted if syncing a large repeating calendar event. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92525"><font size=2 color=blue face="sans-serif"><u>LO92525</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Reply notice sent from an FYI recipient for a calendar event when processed on a mobile device. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92557"><font size=2 color=blue face="sans-serif"><u>LO92557</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Cancelled event may appear ghosted after the cancel on the iOS Native Calendar application. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92638"><font size=2 color=blue face="sans-serif"><u>LO92638</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Add invitee from native iOS Calendar application and the recipient may be added twice to the meeting. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92645"><font size=2 color=blue face="sans-serif"><u>LO92645</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Error reading some policy documents when Run as User feature is enabled. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92713"><font size=2 color=blue face="sans-serif"><u>LO92713</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">User unable to sync when sync request is internally routed from an older server to a 9.0.1.18 or later server. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92728"><font size=2 color=blue face="sans-serif"><u>LO92728</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">DB Connection exception during migration from Derby to an Enterprise database. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92783"><font size=2 color=blue face="sans-serif"><u>LO92783</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Android user incorrectly denied access if specific set of administration settings are enabled. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92829"><font size=2 color=blue face="sans-serif"><u>LO92829</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Handle comma character in display name for mail sent from an Outlook client. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92881"><font size=2 color=blue face="sans-serif"><u>LO92881</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">High CPU may be seen on the database server for one particular SQL query. </font> <tr valign=top height=8> <td width=138 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><a href="http://www.ibm.com/support/docview.wss?uid=swg1LO92897"><font size=2 color=blue face="sans-serif"><u>LO92897</u></font></a><font size=2 face="sans-serif"> </font> <td width=1238 style="border-style:none none none none;border-color:#000000;border-width:0px 0px 0px 0px;padding:1px 1px;"><font size=2 face="sans-serif">Update APNS Certificates, new expiration is 8/1/2017.</font></table> <br /> <br />  ]]></content:encoded>
  352. <wfw:commentRss> http://blog.nashcom.de/nashcomblog.nsf/dxcomments/traveler-9.0.1.19-with-important-fixes.htm</wfw:commentRss>
  353. <wfw:comment> http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.19-with-important-fixes.htm?opendocument&amp;comments</wfw:comment>
  354. </item>
  355. </channel></rss>
  356.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//blog.nashcom.de/nashcomblog.nsf/feed.rss

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda