Hi Vageesha,
all that I can do is to point you to the change history and the optional dependencies. Especially if you have the version running in one environment, but not in the other.
Regards,
Jörg
On Wednesday, 2. February 2022, 15:53:02 CET Vageesha Basutkar wrote:
> Hi Team,
>
> We are hitting a roadblock while the loading of xstream-1.4.18.jar version
> in our application, requesting support / suggestions.
>
> Issue - After Application deployment in Production Environment,
> xstream-1.4.18.jar is found in the deployment path but not loaded in to the
> Application Class path causing feature failure in the Application.
>
> Same build having xstream-1.4.18.jar version, working fine in other Test
> Environments but not working only in Production Environment.
> Test and Prod Environments configurations are same.
>
> We created the new build with old version xstream-1.4.16.jar, it went
> through without any hiccups in both Test and Prod Environments.
>
> We need help to understand what are the dependencies to take care for
> xstream-1.4.18.jar usage.
>
> Application is on WAS version - 8.5.5.19 with the JAVA 1.8.
>
> Steps tried below on WAS Server but still situation remains same - Xstream
> 1.4.18 jar not loaded on Application Classpath only in Production
> Environment,
>
> 1) Synchronized all nodes and restarted all JVMs
>
> 2) Reviewed the path / permission / ownership and compared with other env.
>
> 3) Added classpaths to all JVMs
>
> 3) Added classpath to only one JVM
>
> 4) Full WAS restart
>
> 5) Redeployed same build.
>
> 6) Synchronized DMgrs on WAS Servers.
>
> 7) Added xstream jar to manifest file Classpath to the Services component
> of the Application
>
>
>
> Regards,
> Vageesha