I have good news. After deploying various GeoServer releases in WebSphere
8.5.5, I found that I can successfully login to GeoServer 2.8.5 when it's
deployed in WebSphere.
However, I did have to make one change to the web.xml file to fix garbage
character display on the admin site. I commented out compression types (I
believe WebSphere must already provide compression so double compression
was producing funny characters):
compressed-types
* *
FYI, I had to repackage the war with the jar utility and redeploy to fix
the character issue. It appears that WebSphere ignores changes to the
web.xml file after deployment, even if the servers are restarted.
>From testing newer GeoServer releases in WebSphere 8.5.5, I concluded that
everything from 2.9 onwards produces the following message in the browser:
Error 500: javax.servlet.ServletException: Filter [filterChainProxy]: could
not be initialized
According to the logs there is an issue with casting an XML document
builder factory object:
java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to
javax.xml.parsers.DocumentBuilderFactory
Since GeoServer 2.9 is the first release built with Java 8, my guess would
be that the XML parsing libraries that come with the standard Java 8 JDK
differ from the Java 8 libraries installed in WebSphere. The issue could
likely be fixed by installing the correct libraries as shared libraries in
WebSphere and ensuring that they are loaded before the WebSphere Java
libraries.
Thanks,
Juanita
On Wed, Oct 16, 2019 at 9:02 AM Juanita Dahlin <
juanita.av...@concept-solutions.com> wrote:
> Thank you for the recommendations, Jody. I will do some research into
> changing the XML parser. I'm going to test a few more versions of GeoServer
> to see if any supported versions produce the same login issue as 2.2.4.
>
> Thanks for your help,
> Juanita
>
> On Tue, Oct 15, 2019 at 7:07 PM Jody Garnett
> wrote:
>
>> I would be far more comfortable if you work on a supported version of
>> GeoServer and focus on getting that working (2.2.4 was released in 2013!)
>> Can you check the xml parsers available in web sphere? It looks like the
>> parser provided by your environment is not supported?
>>
>> You have quite the work cut out for you Juanita, although we ask for
>> testing each release cycle you are the first to provide feedback in ...
>> quite some time.
>>
>>
>>
>> --
>> Jody Garnett
>>
>>
>> On Tue, 15 Oct 2019 at 12:51, Juanita Dahlin <
>> juanita.av...@concept-solutions.com> wrote:
>>
>>> Hello GeoServer Team,
>>>
>>> I've been tasked with porting GeoServer 2.2.4 from GlassFish to
>>> WebSphere 8.5.5. GeoServer runs fine under WebSphere except for login to
>>> the admin site.
>>>
>>> When I attempt to login to the GeoServer admin site, I am directed to a
>>> blank /j_spring_security_check page. If I tail the geoserver.log or the
>>> WebSphere SystemOut.log absolutely no messages are logged. It's as if the
>>> Spring login filter is not invoked at all.
>>>
>>> I've tried various WebSphere tweaks including class load order and
>>> custom Web Container properties. Evidently the invokefilterscompatibility
>>> property used to solve similar issues in older versions of WebSphere, but
>>> it's no longer available in WebSphere 8.5.5:
>>>
>>> com.ibm.ws.webcontainer.invokefilterscompatibility = true
>>>
>>> Has anyone else had success getting GeoServer login to work in WebSphere
>>> 8.5.5?
>>>
>>> FYI, I also have the option of upgrading to a newer version of
>>> GeoServer. However, I've tried 2.16.0 and 2.14.4 and cannot even get the
>>> admin site to come up. With newer versions of GeoServer, I see this message
>>> in the browser:
>>>
>>> Error 500: javax.servlet.ServletException: Filter [filterChainProxy]:
>>> could not be initialized
>>>
>>> And this message in the logs:
>>>
>>> java.lang.ClassCastException:
>>> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl cannot be cast to
>>> javax.xml.parsers.DocumentBuilderFactory
>>>
>>> Thanks for your help,
>>> Juanita Dahlin
>>>
>>> --
>>>
>>> *Juanita Avila Dahlin*
>>>
>>> Software Developer for the FAA AIM-SAA program
>>>
>>> ConceptSolutions, LLC
>>>
>>> www.concept-solutions.com
>>>
>>>
>>> www.concept-solutions.com
>>>
>>> *An Equal Opportunity Employer*
>>> CONFIDENTIALITY NOTICE: The information and/or documents contained in
>>> this transmission may contain confidential or proprietary information. The
>>> information is solely for the use of the addressee named above. If you are
>>> not the intended recipient, you are hereby notified that any disclosure,
>>> copying, distribution, any action in reliance or other use of the contents
>>> of this transmission is strictly prohibited.
>>>
>>> ___
>>> Geoserver-users mailing list
>>>
>>> Please make sure you read the following two resources before posting to
>>> this list:
>>> - Earning your support instead of buying it, but
