Category: Troubleshooting

Contract Overview Contracts allow an organization or customer group to purchase specific products from a store and a specific price for a specific time. They allow catalog filtering and price rules to be applied to products that change the items available for purchase along with the price of those items. This contract can then be…

While working on a project, a SOAP request kept failing. The page wouldn’t load, and I was getting the following lines in the logs: J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source. This is the multithreaded access detection option. Alternatively…

Failed to get the plug-in implementation, check the plug-in configuration for payment system name ThePluginName and payment configuration ID default. This FoundationApplicationException will be thrown when you add a new payment plugin in, but have an issue with the PluginDeployment.xml file. First, check you have a folder for the plugin: WC/xml/config/payments/ppc/plugins/ThePluginNamePlugin Second, verify there is…

From a recent post, you may need to restore your local RAD DB2 database, and it may or may not be a backup from another toolkit. When the database is restored, all the data you need is there, but Solr is still not returning the expected products. So you open a command prompt, and cd…

Continuing troubleshooting a payment plugin, the plugin configuration was found, but then a new error was being thrown: Error:Failed to initialize the payment plug-in ThePluginName. The reported exception is: javax.naming.NameNotFoundException: Context: localhost/nodes/localhost/servers/server1, name: ejb/com/company/payment/plugin/ThePluginNameHome: First component in name payment/plugin/ThePluginNameHome not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]. The payment plugin project was there. It was imported…