1. Hung thread message in SystemOut.log when running SMP traffic with 10 Virtual Users
® Application Server provides a detection feature that attempts to locate and report on potentially hung threads in the system. Hung threads can be difficult to diagnose. The WebSphere
Application Server thread moniter architecture moniters managed threads and is enabled by default. When a thread is suspected to be hung, a notification message is written to Sysprint. False alarms do occur. When a false alarm occurs, a followup notification is sent to Sysprint.
The following warning from WebSphere Application Server may be observed in the System log:
[7/19/12 13:26:39:031 EDT] 00000033 ThreadMonitor W WSVR0605W: Thread "WorkManager.wpsDefaultWorkManager : 72" (000000ee) has been active for 682689 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
at sun.misc.Unsafe.park(Native Method)
The Social Media Publisher makes use of JMS background threads which are long running by nature. There is currently no facility for the Social Media Publisher application to pre-warn the WebSphere Portal server, or the WebSphere Application Server. As a result of this limitation, false alarms may be observed relating to JMS threads, which are used by Social Media Publisher.
Until this design limitation is corrected, warnings about potential hung threads may be observed, but can be ignored. WebSphere Application Server will report on falsely alerted threads that resume normally. It is possible, but not necessary, to adjust these intervals and thresholds. The custom properties are noted below, but please refer to the WebSphere Application Server documentation for more information:
Defaults to 180 seconds. This is the interval at which the thread pools will be polled for hung threads.
Defaults to 600 seconds. This is the length of time that a thread can be active before being marked as "potentially hung".
Defaults to 100 false alarms. This is the number of false alarms that can occur before automatically increasing the threshold by 50%.
2. Not possible to set library-scoped global settings if library name contains a space
If you have WCM libraries with spaces in the name, then you will not be able to set any library-scoped global settings as the space is not intepretted correctly by the global settings parser (which current uses a Java Properties object)
Rename the library to remove the space (the library title can still have a space)
3. Error deleting a Facebook Page Note
Attempting to delete a Facebook Page note results in an 'Unexpected error has occurred' error message. The inability to delete Facebook page notes via the Facebook API is an outstanding defect with Facebook itself. Facebook are aware of the problem, but do not have any plans to fix it at this stage.
Remove the page note from the Facebook website
4. Unable to create new Facebook Page Note
Facebook has removed the 'Page Note' feature from the v2.0 of their API which they released on April 30, 2014. Any Facebook applications created before April 30, 2014 will continue to be able to create Page Notes for a further year, however past that date (and for all applications created from April 30, 2014) the following error will be shown if you try to create a Page Note: OAuthException: (#12) notes API is deprecated for versions v2.0 and higher
None, use a Page Wall Post instead. The Social Media Publisher has officially deprecated Page Notes (given Facebook has removed the feature) and they will be removed in a future Social Media Publisher version
5. Unable post to Facebook Page
You try to post a message to a Facebook Page and encounter the following error in the logs:
EJPSJ0017E: SQL Exception occurred when trying to add a credential.com.ibm.wps.datastore.impl.DataBackendException: EJPDB0002E: Error occurred during database access.
. . .
Caused by: com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001, SQLERRMC=null, DRIVER=4.12.55
This is caused by the Portal Credential Vault 'PWD' column being too small. See this technote for resolution steps: http://www-01.ibm.com/support/docview.wss?uid=swg21662584
Parent topic: Social Media Publisher V1.0 for Web Content Manager V7.0