The Connection Server

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators. Symptom With an Active Directory Authenticator configured, if a user logs in once with incorrect credentials further attempts to log in will fail, even with the correct username and password (until the server is restarted). If the user continues to login with correct credentials, WebLogic will eventually lockout the account. Cause This is a known bug for WebLogic 10 MP1. During authentication the AD provider binds twice using the same LDAP connection, once with the username password being authenticated, and once with the credentials supplied when you configure the LDAP provider. If authentication fails, the second binding doesn’t happen, and the unauthenticated LDAP connection is returned to the internal LDAP connection pool. This poses a problem when later trying to authenticate and the unauthenticated LDAP connection is retrieved from the pool... -Cobb...

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators. Symptom The WebLogic admin or managed server is running, but telnetting to it fails, with an error like: Trying 10.123.123.123... telnet: connect to address 10.123.123.123: Connection refused Cause You may be using a development/limited license. These restrict WebLogic to accept connections from up to 5 different IP addresses and then stop accepting connections from any other IP. If you have multiple interfaces on the server, WebLogic may be listening on one of the others. If you do not specify a listen address for a admin or managed server, it will listen on all interfaces. Solution Replace the dev license with a purchased one, or restart the server to clear the 5 IPs that it accepts connection from. Change the listen address, or telnet to the correct address.

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators. Symptom On Red Hat Enterprise Linux 4 (and possibly other flavours and versions) all weblogic processes are disappearing and there are no errors in the server logs. Upon closer inspection the processes are being killed by the OS. The Linux "dmesg" command shows log messages like: Out of Memory: Killed process 22043 Cause The processes are using up too much low- (under 640k) or high-memory and the Linux OOM-Killer is killing the processes. Solution Either disable OOM-killer, or make it work more aggresively. To disable, run this command: echo "0" > /proc/sys/vm/oom-kill To make more aggressive: echo "250" > /proc/sys/vm/lower_zone_protection References http://en.wikipedia.org/wiki/Out_of_memory http://www.linux-archive.org/red-hat-linux/39907-out-memory-issue.html

The Connection Server is the name of this site. That's right, there is no technology officially called a 'connection server'. However it could describe any number of technologies that we use everyday in the corporate sys admin world. Any type of server must accept connections from clients in order to respond, so whether its a HTTP server, JEE server or sql/database server, its pretty much a connection server too. The articles at this site will touch on all these types of technologies. In case you were wondering... HTTP Servers , which handle HTTP connections, accept and process requestsand return HTML code which is processed by an internet browser (Eg. Internet Explorer, Firefox, Chrome, Safari and Opera). The internet browser renders the HTML code as formatted text and graphics. Common HTTP servers include Apache and IIS. Application Servers , such as WebLogic, WebSphere, JBoss and Tomcat, usually include a basic HTTP server, but are also able to run JEE (Java Enterprise...

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators. Symptom Getting the following exception (regularly) in the Admin server logs. HTTPClntLogin: Login rejected with code: 'Failed', reason: java.net.ProtocolException: HTTP tunneling is disabled at weblogic.rjvm.http.HTTPServerJVMConnection.acceptJVMConnection(HTTPServerJVMConnection.java:88) at weblogic.rjvm.http.TunnelLoginServlet.service(TunnelLoginServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.WebAppServletContext$ServletInvocation...

The Connection Server is an informal blog about a range of professional server-related topics, with a focus on the everyday tasks of a corporate IT infrastructure administrator. Articles range from hard-core technical tips to more business-oriented discussions. What technologies do I cover? Potentially anything used in the corporate IT world, but to name a few big ones: Java (J2EE, J2SE and J2ME) Oracle WebLogic (previously BEA WebLogic) WebSphere and JBoss Oracle DB Apache and IIS Windows, AIX, Solaris and Red Hat Although a few articles are aimed at helping beginners become more advanced administrators or developers, most articles assume at least a medium level of technical knowledge.

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators. Symptom There is no license.bea, UpdateLicense.cmd or UpdateLicense.sh files in the BEA_HOME directory of WebLogic 10.3. Cause When Oracle bought BEA they decided to do away with this approach to licensing. Solution When you download WebLogic 10.3, you are getting the full version. That is, you do not need to do anything to fully enable the product. Although technically you do not need to do anything to use this product, legally you will need to purchase a license from Oracle. Contact an Oracle sales person for this. Previous versions of WebLogic, including 10.0, have not been changed, so you still require the license.bea file for these.