[ 
https://issues.apache.org/jira/browse/SOLR-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914429#comment-13914429
 ] 

Uwe Schindler commented on SOLR-5733:
-------------------------------------

bq. If you do find that you're using one of the known bad Java versions, please
come back and close this JIRA.

The list is here: http://wiki.apache.org/lucene-java/JavaBugs

In general, if you really want to use Java 6 (which is no longer supported by 
Oracle), update to at least 1.6.0 u45 (latest available). In addition, OpenJDK 
1.6 has major performance problems because of missing patches from official JDK 
6. If you want to use OpenJDK, use OpenJDK 7, which is identical on the 
patch-level and features for server applications with Oracle JDK 7.

> Solr 4.5.0, 4.5.1, and 4.6.1 spontaneously chashes within first 10min of 
> their life
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-5733
>                 URL: https://issues.apache.org/jira/browse/SOLR-5733
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.5, 4.5.1, 4.6.1
>         Environment: Linux solrssd2 2.6.32-5-amd64 #1 SMP Fri May 10 08:43:19 
> UTC 2013 x86_64 GNU/Linux
> java version "1.6.0_18"
> OpenJDK Runtime Environment (IcedTea6 1.8.13) (6b18-1.8.13-0+squeeze2)
> OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
>            Reporter: Marcus Engene
>             Fix For: 4.6.1
>
>
> tien@solrssd2:/solr461stem/example$ cat start.sh
> #!/bin/sh
> java -Xms9G -Xmx22G -Djetty.host=0.0.0.0 -Djetty.port=9993 -DhostPort=9993 
> -jar start.jar 2>/dev/null 1>/dev/null
> Solr crashes spontaneously about every 2nd start within the first 10min of 
> the process life.
> tien@solrssd2:/solr461stem/example/solr/collection1$ du -ks data
> 5405556       data
> Machine is not heavily used
> Tasks: 317 total,   1 running, 316 sleeping,   0 stopped,   0 zombie
> Cpu(s):  1.3%us,  0.0%sy,  0.0%ni, 98.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
> Mem:  264660644k total, 227656492k used, 37004152k free,   544848k buffers
> Swap:  4000144k total,   102940k used,  3897204k free, 204332940k cached
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND          
>                                                                             
>  7700 tien      20   0 32.4g 3.3g 1.2g S   13  1.3   2:23.15 java             
>                                                                              
>  8208 tien      20   0 27.6g 3.9g 805m S   10  1.5   0:56.45 java             
>                                                                              
>  7785 tien      20   0 26.7g 5.6g 2.2g S    2  2.2   3:42.94 java             
>                                                                              
>  6102 tien      20   0 27.6g 9.9g 4.3g S    0  3.9  61:03.26 java             
>                                                                              
>  8337 tien      20   0 19204 1552 1016 R    0  0.0   0:00.02 top              
>                                                                              
>     1 root      20   0  8356  796  664 S    0  0.0   0:12.90 init             
>                                                                              
>     2 root      20   0     0    0    0 S    0  0.0   0:00.00 kthreadd         
>                                                                              
>     3 root      RT   0     0    0    0 S    0  0.0   0:05.30 migration/0      
>                                                                              
>     4 root      20   0     0    0    0 S    0  0.0   0:13.17 ksoftirqd/0      
>                                                                              
>     5 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/0    
> I'll try to attach the hs-dump.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to