Open topic with navigation

TIBCO GridServer® 7.1.0

# Deployment Issues

The GridServer Manager is responsible for deploying application resources to Engines. The Manager periodically generates a checksum list of every file in its resources area. If any checksums have changed (or have been deleted or added) since the last time the list was generated, it notifies the Engines.

Don’t deploy resource files that only differ by case in UNIX. Resource files names must be different. If you deploy different files named `hello.zip` and `Hello.zip`, they collide on Windows machines. Also, you can’t deploy files that contain `#` or end in `.tmp`.

For more information about resource deployment and Grid Libraries, see Deploying Services.

## Grid Library Issues

If you have a `GridLibraryException` failure when deploying a Grid Library, check your `grid-library.xml` for incorrect file names; also ensure that files and file reference in `grid-library.xml` are of the correct case. Also check that the `jar-path`, `lib-path`, `assembly-path`, and `command-path` are correctly specified.

## .Net GridLib - DLL Missing

When deploying a .NET assembly, all DLL libraries in `win32/lib` and all other directories specified in Engine Configuration are not used. Put all related DLL files into the same Grid Library, or another Grid Library that this Grid Library depends on. A missing DLL causes a log message similar to the following:

    INFO  DSForward Message DD7C5440-D3B9-42D6-9201-F7E7CE3AE847 submitted
    DSHandler Service invocation 0 failed for DD7C5440-D3B9-42D6-9201-F7E7CE3AE847
    Exception: DataSynapse.GridServer.Client.ServiceInvocationException
    Message: spri12d10052
    Source: GridServerNETClient

## Service Failures

If a Service is not defined in the Services > Services > Service Types page, a message similar to the following is produced in the Driver log:

    Service Type not found in the Service Type Registry: JavaCalculator

If the JAR file containing the class of the Service has not been loaded into the correct library, a message in the Driver log is produced:

    Info: [TaskDispatcher$DispatcherJob] Canceling due to task failure and AutoCancel.LIBRARY_LOAD, Exception type: java.lang.ClassNotFoundException

If a Service fails, an error is returned to the Callback method; check your code for errors.

    Info: [ServiceEvent] SubmittedTask:3393405147689298243-3393405147689298243-1
    CalculatorCallback::handleResponse : Result for task [B@c713d2
    Info: [ServiceEvent] CompletedTask:3393405147689298243-3393405147689298243-0:Total:2
    CalculatorCallback ::handleError : Id = 1, Exception : java.lang.Exception: service failed [java.lang.Exception: service failed

If a Service fails to run even if there are available Engines, check that Service or Engine discrimination is not preventing the Service task from running. Also check for usage of dependencies in the application. The Service or task might be waiting for a Service or task it is dependent on.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO GridServer®

Copyright © 2001-2022. TIBCO Software Inc. All Rights Reserved.