Article ID: 120317, created on Feb 26, 2014, last review on Aug 12, 2014

  • Applies to:
  • Business Automation 5.5

Symptoms

Limit notifications are not sent to the customers even though the resource usage reached the limit configured.

In the MESSAGE.log an exception of the method FindNotifiableResources can be seen:

Execution Failed: [../../../../../usr/local/stellart/include/stlrt/type/numeric.hpp:48] cast to numeric type on NULL value
Backtrace:
/usr/local/stellart/lib64/libstlrt.so(+0x7f3f1) [0x7f5e007fb3f1]
/usr/local/stellart/lib64/libstlrt.so(_ZN9ExceptionC2EPKciS1_ii+0xba) [0x7f5e007fbdba]
/usr/local/stellart/lib64/libstlrt.so(_ZN5STLRT4Type9ExceptionC2EPKciRKN9Exception4CodeE+0x19) [0x7f5e008128e9]
/usr/local/bm/bin/MESSAGE_Container(_ZNK5STLRT4Type7NumericIdE6c_typeEv+0x4b) [0x40a321]
/usr/local/bm/lib64/libMESSAGElib.so(_ZN7MESSAGE23FindNotifiableResourcesEv+0x2d0d) [0x7f5e0b4178d1]
/usr/local/bm/lib64/libMESSAGElib.so(_ZN10MESSAGERPC25__FindNotifiableResourcesEPN5STLRT9ComponentER10DataPacketRK7Address+0x6a) [0x7f5e0b195202]
/usr/local/stellart/lib64/libMW.so(_ZN5STLRT9Component3RPCERKNS0_13RPC_SIGNATUREER10DataPacketRK7Address+0x294) [0x7f5dffbf9e74]
/usr/local/stellart/lib64/libCOM.so(_ZN12ServerObject16UnsafeMethodCallER12RemotePacketb+0x35b) [0x7f5e0011bccb]
/usr/local/stellart/lib64/libCOM.so(_ZN17TransactionServer16UnsafeMethodCallER12RemotePacketb+0x33) [0x7f5e000fecd3]
/usr/local/stellart/lib64/libCOM.so(_ZN12ServerObject17ProcessMethodCallER12RemotePacket+0x15f) [0x7f5e0011a7ff]
/usr/local/stellart/lib64/libCOM.so(_ZN17TransactionServer14ProcessMessageER12RemotePacket+0x1ae) [0x7f5e000fe39e]
/usr/local/stellart/lib64/libCOM.so(_ZN10CommObject13processPacketER12RemotePacket+0xa2) [0x7f5e000f8b52]
/usr/local/stellart/lib64/libCOM.so(_ZN17TransactionServer11packetCycleEv+0x225) [0x7f5e000fd535]
/usr/local/stellart/lib64/libCOM.so(_ZN10CommObject6GoWorkEv+0x148) [0x7f5e000f9988]
/usr/local/stellart/lib64/libstlrt.so(_ZN7AThread3runEPS_+0xd7) [0x7f5e007c84c7]
/lib64/libpthread.so.0(+0x7851) [0x7f5dfef9d851]
/lib64/libc.so.6(clone+0x6d) [0x7f5dfeceb90d]

Cause

There is a limit notification configured for the composite resource, but attaching the resource limit notification to the composite resource is useless (usage is not collected for composite resources, no limit notifications will ever be sent). The issue was reported as bug #PBA-54802 ("No limit notification should be sent to customers in case of some limit notification attached to the composite resource"), which was fixed in PBA-E 5.5.5.

Resolution

Please upgrade to the latest version of PBA. Incorrect composite resource configuration will automatically be detected and corrected, the possibility to attach limit notification to the composite resource - deleted (no more option in GUI).

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF