Closed nbastian closed 8 years ago
I assume you understand how this plugin works (if not you could take a look at the how it works
section in README.md), in short it deploys your packages by executing jython script.
Here the exception is thrown on line 45, which indicates the appManager
is pointing to nothing.
This could be the node
name or server
name is miss configured, but I think you had already double checked it to make sure they are not.
Another possibility is you are working on a portal server or liberty profile, the behavior on portal server is not tweaked, as I never worked on a portal server, while liberty profile is not supported at all. (The log says you are not working on the liberty profile).
If you are not working on a portal server, then it could be about the version, I tested it on 7.5, 8.0 in the early stage of this plugin, but later I only worked on 8.5.
Different version of WAS might differ on how to acquire a appManager
handler.
You can debug this by running the wsadmin.sh(bat) -lang jython [-host
BTW, try to use it on a Linux server, I see some issues with WAS on Windows, which I can't explain. Cluster better than standalone, Linux better than Windows.
Hey,
I'm trying to deploy my JSF 2.0/PrimeFaces 6.0 application to my WAS 8.0 with this plugin but I'm always getting the following error:
Here's my plugin config:
Does anyone know why I always get this error? I've found some similar errors but no solution for my problem.
Thanks for your help, Nico