http://www.randombugs.com Just another Bastard Operator From Hell. Everything from *nix to programming Thu, 05 Jan 2012 11:44:55 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 http://www.randombugs.com/java/glassfish/glassfish-311-workaround-denial-service-hash-table-multicollisions.html http://www.randombugs.com/java/glassfish/glassfish-311-workaround-denial-service-hash-table-multicollisions.html#comments Thu, 05 Jan 2012 11:42:48 +0000 admin http://www.randombugs.com/?p=783
This is an old bug, first discovered in 2003, but now was applied to the hash table functions from the new programming languages. The main idea behind this bug is to create hashes which collide, because collision will eat a lot more cpu cycles on your server. For a post of 2 MB is resulting in a 44 minutes of CPU time which will results in a DOS. As suggested in advisory released by nruns.com we can limit the maximum post size from several 10′s of KB. In Glassfish 3.1.1 ...]]> http://www.randombugs.com/java/glassfish/glassfish-311-workaround-denial-service-hash-table-multicollisions.html/feed 0 http://www.randombugs.com/java/glassfish/user-admin-host-null-administration-access.html http://www.randombugs.com/java/glassfish/user-admin-host-null-administration-access.html#comments Wed, 23 Nov 2011 08:24:33 +0000 admin http://www.randombugs.com/?p=771
I should admit, I didn’t read the Glassfish 3.1 Administration Manual, and I don’t know if this is documented. Anyway the main problem appeared when I tried to connect on my cluster instances with admin credentials. If I connect with VisualVM or JConsole to Domain Administration Server (DAS) on 8686 I don’t have any problem. When I’m trying to connect to my cluster instances on port 28686 with admin credentials I get from JConsole Connection Failed: Retry? The connection to admin@rb.randombugs.com:28686 did not succeed. Would you like to try again? and on server.log [#|2011-11-23T12:12:40.599+0000|INFO|glassfish3.1.1|javax.enterprise.system.tools.admin.com.sun.enterprise.container.common|_ThreadID=34;_ThreadName=Thread-2;|User [admin] ...]]> http://www.randombugs.com/java/glassfish/user-admin-host-null-administration-access.html/feed 0 http://www.randombugs.com/java/glassfish/http-transport-error-javaxnetsslsslhandshakeexception-sunsecurityvalidatorvalidatorexception-pkix-path-validation-failed-javasecuritycertcertpathvalidatorexception-signature-check-failed.html http://www.randombugs.com/java/glassfish/http-transport-error-javaxnetsslsslhandshakeexception-sunsecurityvalidatorvalidatorexception-pkix-path-validation-failed-javasecuritycertcertpathvalidatorexception-signature-check-failed.html#comments Wed, 13 Jul 2011 02:45:02 +0000 admin http://www.randombugs.com/?p=762
I switched all my Java Glassfish webservices to SSL, because I wanted to have an encrypted communication between me and my clients. Until then, all my applications worked flawlessly over the HTTP protocol, but now, after switching to SSL, I got the following error: HTTP transport error: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed That means, the client doesn’t have the certificate and cannot check response against the server certificate. The most simple solution is to export the certificate from the webserver server and import it on the webservice ...]]> http://www.randombugs.com/java/glassfish/http-transport-error-javaxnetsslsslhandshakeexception-sunsecurityvalidatorvalidatorexception-pkix-path-validation-failed-javasecuritycertcertpathvalidatorexception-signature-check-failed.html/feed 2 http://www.randombugs.com/java/glassfish/installing-glassfish-31-cluster-debian-60-command-line.html http://www.randombugs.com/java/glassfish/installing-glassfish-31-cluster-debian-60-command-line.html#comments Wed, 04 May 2011 12:48:05 +0000 admin http://www.randombugs.com/?p=729
Finlay is here. For me, Glassfish 3.1, was one of most awaited piece of software, for all it’s new features and clustering support. Glassfish 3.1 slightly changed the way to install cluster, in a much better and integrated way. This version come with a lot of new functionality, but also with improved parts related to Glassfish 2.1. The most interesting features of Glassfish 3.1 are: Clustering (100 instances per domain), SSH provisioning, Centralized management (with the help of ssh), High Availability Session Persistence, High Availability Java Message Service, RMI-IIOP Load ...]]> http://www.randombugs.com/java/glassfish/installing-glassfish-31-cluster-debian-60-command-line.html/feed 1 http://www.randombugs.com/java/glassfish/glassfish-enhanced-broker-cluster-failed-load-jdbc-driver.html http://www.randombugs.com/java/glassfish/glassfish-enhanced-broker-cluster-failed-load-jdbc-driver.html#comments Thu, 14 Apr 2011 10:44:11 +0000 admin http://www.randombugs.com/?p=721
Is not a bug, but a pretty annoying configuration thing which appear when you try to configure Enhanced Broker Cluster in Glassfish. I configured my persistent store, for Enhanced Broker Cluster, as jdbc / MySQL: [...] imq.persist.jdbc.dbVendor=mysql imq.persist.jdbc.mysql.driver=com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource imq.persist.jdbc.mysql.property.url=jdbc\:mysql\://sqlserver\:3306/jms imq.persist.jdbc.mysql.needpassword=true imq.persist.jdbc.mysql.user=jms [...] and after at restart I got the following error: [13/Apr/2011:12:12:30 CEST] [B1060]: Loading persistent data… [13/Apr/2011:12:12:30 CEST] ERROR [B3198]: Error initializing cluster manager: com.sun.messaging.jmq.jmsserver.util.BrokerException: [B3024]: Failed to load JDBC driver: com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBManager.(DBManager.java:428) at com.sun.messaging.jmq.jmsserver.persist.jdbc.DBManager.getDBManager(DBManager.java:219) at com.sun.messaging.jmq.jmsserver.persist.jdbc.JDBCStore.(JDBCStore.java:98) ...]]> http://www.randombugs.com/java/glassfish/glassfish-enhanced-broker-cluster-failed-load-jdbc-driver.html/feed 0 http://www.randombugs.com/java/glassfish/snmp-support-glassfish-211-cluster-support.html http://www.randombugs.com/java/glassfish/snmp-support-glassfish-211-cluster-support.html#comments Mon, 14 Mar 2011 11:57:21 +0000 admin http://www.randombugs.com/?p=701
Why you choose SNMP when Glassfish have strong JMX support? I presume, the answer for all who use SNMP is (almost) the same: Because the architecture of current monitoring solution is not scalable enough, and I cannot load my monitoring servers with supplementary JAVA processes. Before starting using SNMP I tried to see what solutions I have: 1. Re-design entire monitoring solution 2. Use SNMP I’m a lazy person, so I choose to add SNMP support for all our clusters . To do that you should do 3 easy steps: 1. Upload the ...]]> http://www.randombugs.com/java/glassfish/snmp-support-glassfish-211-cluster-support.html/feed 0 http://www.randombugs.com/java/sunjvmhotspotdebuggernosuchsymbolexception-find-symbol-ghotspotvmtypeentrytypenameoffset.html http://www.randombugs.com/java/sunjvmhotspotdebuggernosuchsymbolexception-find-symbol-ghotspotvmtypeentrytypenameoffset.html#comments Tue, 08 Feb 2011 14:33:58 +0000 admin http://www.randombugs.com/?p=676
This, probably, is a bug which was not spotted very often because is very obscure and the Debian guys moved very quick and fixed the problem. I know, I found a lot of bugs related to sun.jvm.hotspot.debugger.NoSuchSymbolException: Could not find symbol “gHotSpotVMTypeEntryTypeNameOffset”, but this is different. Usually was a problem of “striping symbols from libjvm.so”, but in my case wasn’t that. Also I found this error related to OpenJDK (I use Sun JDK) and the solution was to use -server flag to get the correct libjvm.so. Anyway it took me ...]]> http://www.randombugs.com/java/sunjvmhotspotdebuggernosuchsymbolexception-find-symbol-ghotspotvmtypeentrytypenameoffset.html/feed 1 http://www.randombugs.com/java/glassfish/glassfish-cluster-211-httpsessions-replication-multithread-concurrent-access.html http://www.randombugs.com/java/glassfish/glassfish-cluster-211-httpsessions-replication-multithread-concurrent-access.html#comments Wed, 03 Mar 2010 10:07:06 +0000 admin http://www.randombugs.com/?p=634
I have several clusters with Glassfish 2.1.1 in a BIG virtual environment and all worked fine … until I add new processors to this clusters. After upgrade, I started to have problems with HttpSession replication. Starting debugging JXTA, Shoal and the Web Container didn’t help at all. Until I found this page Memory Replication & Multi-threaded Concurrent Access to HttpSessions. My applications was doing multi-thread concurrent access some times (Ajax) and this was the root cause of all lost sessions. I modified sun-web.xml from my application, accordingly with the ...]]> http://www.randombugs.com/java/glassfish/glassfish-cluster-211-httpsessions-replication-multithread-concurrent-access.html/feed 3 http://www.randombugs.com/java/java-networking-problems-debian-squeezesid.html http://www.randombugs.com/java/java-networking-problems-debian-squeezesid.html#comments Tue, 16 Feb 2010 08:46:07 +0000 admin http://www.randombugs.com/?p=630
After upgrading to the latest version of Debian squeeze/sid, I was not able to use the networking in java. If you get: [2/16/10 10:39 AM] Exception occurred: java.net.SocketException: Network is unreachable at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) then you should disable ipv6. To do that ...]]> http://www.randombugs.com/java/java-networking-problems-debian-squeezesid.html/feed 1 http://www.randombugs.com/java/glassfish/upgrade-glassfish-21-211.html http://www.randombugs.com/java/glassfish/upgrade-glassfish-21-211.html#comments Tue, 29 Dec 2009 13:39:54 +0000 admin http://www.randombugs.com/?p=625
For some reasons the asupgrade tool from Sun Glassfish doesn’t work if you want to upgrade your Glassfish from 2.1 to 2.1.1. The upgrade method what I will present you in the next post, probably, is not recommended by SUN, but it will work in most cases (clustered or not). Just follow this steps: 1. Stop all domains, node agents, instances from all cluster (or only the domain if you have only 1 server) 2. Rename Glassfish folder to g2.1 3. Install glassfish 2.1.1 $ java -Xmx256m -jar glassfish-installer-v2.1.1-b31g-linux.jar $ cd glassfish $ chmod +x lib/ant/bin/ant $ ...]]> http://www.randombugs.com/java/glassfish/upgrade-glassfish-21-211.html/feed 1