My there! My name is Steve Kwan. User experience design is my passion.

The message: "The asynchonous CPIP message failed" will turn up whenever a CPIP request generates a Java exception that isn't the result of timing out. In this case it's probably happening because of the convergence of two factors:

1) SCT Authenticator was probably stopped and restarted while Luminis stayed up.

2) Recent builds of Luminis have conditionalized the CORBA ping operation (to check the authentication service) and disabled it by default to improve performance. This is fine as long as you never restart the authenticator independently of Luminis. If that happens, we may end up holding an invalid object reference.

This issue can be fixed by setting the following parameter to true and then restarting the Web server for the change to take effect:

configman -s com.pipeline.sdk. cpip.SCTExternal SystemV1.should_ ping true

This assumes, of course, that you have rights to modify the database.........

One again, your article is very nice

Nice content. Thank you for your information.

it's so good

I think a programmable Y-cable is also an option your brave

Great sharing this.

Do you remeber me?

Thanks for this

information