Thursday, 3 June 2010

Lotus Connections Portlets - Blogging Problems

Hmmm, one of the two Blogs portlets (Blogs rather than Blogs Summary) is generating the following exception in SystemOut.log ( on WP node ): -

....
java.lang.StringIndexOutOfBoundsException
...
ava.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at com.bowstreet.webapp.engine.actions.MethodAction.callAction(MethodAction.java:90)
        at com.bowstreet.webapp.engine.WebAppAccessImpl.callMethod(WebAppAccessImpl.java:405)
        at com.bowstreet.webapp.engine.WebAppAccessImpl.processAction(WebAppAccessImpl.java:1063)
        at com.bowstreet.webapp.engine.WebAppAccessImpl.processAction(WebAppAccessImpl.java:1163)
        at genjava.lcaccelerator.portlets._BlogPortlet.catchError_Wrapper(_BlogPortlet.java:508)


I've removed and redeployed the portlets from the WAR file snor.pf.portlets.war and checked/double-checked the configuration between the portlet and Connections: -

bpf_config.lcaccelerator.ServiceProperties:blogs_homepage home
bpf_config.lcaccelerator.ServiceProperties:profiles_url http://connections.demo.uk.ibm.com:82/profiles
bpf_config.lcaccelerator.ServiceProperties:service_url http://connections.demo.uk.ibm.com:82/blogs
isPortletConfigured true

but to no avail.

More testing .....

2 comments:

Unknown said...

Did you ever find a solution to this? I'm seeing the same error now and your blog seems to be the only search result. ;)

Regards,
Brian

Dave Hay said...

@Brian, sadly not, and I've not seen the problem again since, so put it down to a misconfiguration.

One possible consideration is mix of HTTP and HTTPS.

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...