Product webMethods Integration Server
Version 9.5.1.0
Updates IS_9.5_SP1_Core_Fix3
TNS_9.5_SP1_Fix4

Build Number 202
SSL Strong (128-bit)

MWS Version:

Version: 9.5.1.0.172
Build Date: 2013-09-16
Installed Fixes: MWS_9.5_SP1_Fix2

When trying to access Processing Rules under Administration\Integration\B2B\ProcessingRules, we are receiving following exception:

2014-07-18 09:32:46 EDT (Framework:WARN) [RID:917] - Failed to evaluate binding expression: “#{Wm_tn_procrules_searchresultsDefaultviewView.filteredProcRuleList}”
javax.faces.el.EvaluationException: javax.el.ELException: java.lang.NullPointerException
at com.sun.faces.application.ValueBindingValueExpressionAdapter.getValue(ValueBindingValueExpressionAdapter.java:116)
at com.webMethods.caf.faces.application.CAFValueBinding.getValue(CAFValueBinding.java:57)
at com.webMethods.caf.faces.bean.BaseFacesBean.resolveExpression(BaseFacesBean.java:106)
at com.webMethods.caf.faces.bean.BaseFacesBean._resolveDataBinding(BaseFacesBean.java:354)
at com.webMethods.caf.faces.bean.BaseFacesBean.resolveDataBinding(BaseFacesBean.java:239)
at com.webMethods.caf.wm_tn_procrules_searchresults.Wm_tn_procrules_searchresultsDefaultviewView.getProcessingRuleListProvider(Wm_tn_procrules_searchresultsDefaultviewView.java:454)
at sun.reflect.GeneratedMethodAccessor3492.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Where are you seeing this error on the MWS B2B/Integration for TN pages and does this error in the specific page you are looking or any thing related to the TN views?

Also raise a ticket with SAG support and they can peek in your IS/MWS setup.

HTH,
RMG

Yes, I am seeing this error in MWS page under B2BIntegration Processing rules. Rest of the TN views are working as expected.

Please advise, we just migrated from 8.2 to 9.5.

Could be a migration related issue with the rules.

After you applied any MWS fixes are you doing -s update and then restarting MWS (startup.sh)?

HTH,
RMG

Opened a ticket with softwareAG… and they suggested to set wsclient-socketTimeout property in Trading Networks \ Environment entries under MWS (sysadmin) login. This didnt help to resolve the issue. Still working with support.

Any suggestions, why processing rules in MWS taking long time or some times get failed with Error message mentioned in subject of this topic.

May be you need to tune up the timeout property or some thing…

SAG should point you in the right direction pertaining to your environment.

Also are you having lot of data in the TN DB and is your archiving process going on?

HTH,
RMG