I have not closed the bug because there is still the question of why it works on glassfish 4.0 but not in 4.1 and derived works. Removing this line allows us to run with payara41, glassfish 4.1.1 and glassfish 4.0. This line was inserted in the script some years ago to fix some other problem which I don't remember. I found that our setup script for glassfish servers includes:Īsadmin set -service.enable-implicit-cdi=false
While trying to build a simple example to show up the bug. If anyone has succeeded with glassfish 4.1, it would be good to know (especially if they found the same problem and resolved it). On this basis, I recommend not using glassfish 4.1 for ICAT, though as this is based on a single example, your experience may vary. I haven't tried 4.1 with any other ICAT components. I replaced glassfish 4.1 with 4.0 (and re-ran the installation scripts) this time testicat worked OK. I see reports that suggest that there may be a bug with CDI in glassfish 4.1, e.g. : Could not find an implementation of ClassAnalyzer with name CdiInjecteeSkippingClassAnalyzer
Suds.WebFault: Server raised fault: ': : Could not create stateless EJB'Ĭaused by: A MultiException has 1 exceptions. Print "ICAT version", service.getApiVersion()įile "/usr/lib/python2.6/site-packages/suds/client.py", line 542, in _call_įile "/usr/lib/python2.6/site-packages/suds/client.py", line 602, in invokeįile "/usr/lib/python2.6/site-packages/suds/client.py", line 657, in sendįile "/usr/lib/python2.6/site-packages/suds/client.py", line 712, in failedįile "/usr/lib/python2.6/site-packages/suds/bindings/binding.py", line 265, in get_fault However, testicat failed with:įile "/home/br54/bin/testicat", line 35, in
When installing ICAT on a CentOS VM, I downloaded the current version of Glassfish, which turned out to be 4.1. There may be a problem with glassfish 4.1 (which was released in September and is now the current version) that prevents ICAT from working.
0 kommentar(er)
