The average decent servletcontainer itself flushes the stream by default every ~2KB. You should really not have the need to explicitly call flush() on the OutputStream of the HttpServletResponse at intervals when sequentially streaming data from the one and same source. In for example Tomcat (and Websphere!) this is configureable as bufferSize attribute of the … Read more
If you are only deploying the WAR file itself you can’t control this, but if you have your WAR file in an EAR file you can use the deployment.xml solution. The deployment.xml file would look something like this: <?xml version=”1.0″ encoding=”UTF-8″?> <appdeployment:Deployment xmi:version=”2.0″ xmlns:xmi=”http://www.omg.org/XMI” xmlns:appdeployment=”http://www.ibm.com/websphere/appserver/schemas/5.0/appdeployment.xmi” xmi:id=”Deployment_1347529484613″> <deployedObject xmi:type=”appdeployment:ApplicationDeployment” xmi:id=”ApplicationDeployment_1347544766353″ startingWeight=”99″ warClassLoaderPolicy=”SINGLE”> <modules xmi:type=”appdeployment:WebModuleDeployment” xmi:id=”WebModuleDeployment_1347543866613″ startingWeight=”1″ … Read more
Following information is for Websphere 6.1 on Windows. First of all, the magic URL to connect to the MBean server is: service:jmx:iiop://<host>:<port>/jndi/JMXConnector If you have a default Websphere installation, the JNDI port number will likely be 2809, 2810, … depending on how many servers there are installed on one system and the specific one you … Read more
SSL certificates are bound to a ‘common name’, which is usually a fully qualified domain name but can be a wildcard name (eg. *.example.com) or even an IP address, but it usually isn’t. In your case, you are accessing your LDAP server by a hostname and it sounds like your two LDAP servers have different … Read more
I share what worked for me. Me and my team were able to deploy our application with Spring 4.2.4, Hibernate 5.1 and Hibernate JPA 2.1 in Websphere 8.5.5 and Websphere 7. The key to do this is to extract all the hibernate libraries and put them in a shared library folder in your server, create … Read more
This will happen if the client side state is encrypted by one server and decrypted by other server and the servers don’t use the same AES key for this. Normally, you should also have seen below warning in server log: ERROR: MAC did not verify You need to ensure that you have set jsf/ClientSideSecretKey in … Read more
The problem might be that WebSphere 6.1 uses Jakarta Commons Logging (JCL) internally, and if any of your code or 3rd-party libraries also use JCL, WebSphere’s configuration conflicts with your application trying to use log4j. If this is happening, you’ll see exactly what you’re seeing. There are multiple references and blog posts that describe ways … Read more
You need to do the following steps: Disable built in JAX-RS via JVM property com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine=true see description here. You can set this property via web admin console in Servers > WebSphere Application Servers > yourServerName. Then in Server Infrastructure section Java and Process Management > Process definition > Java Virtual Machine > Custom properties. Create … Read more
I had the same issue with WebSphere 6.1. As Ceki pointed out, there were tons of jars that WebSphere was using and one of them was pointing to an older version of slf4j. The No-Op fallback happens only with slf4j -1.6+ so anything older than that will throw an exception and halts your deployment. There … Read more