[jira] Commented: (SMX4-200) Startup hangs occasionally

["Chris Custine (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SMX4-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49057#action_49057 ] 

Chris Custine commented on SMX4-200:
------------------------------------

If you are using 4.0-m1, you might want to download a more recent nightly snapshot of 4.0-m2 from [here|http://people.apache.org/repo/m2-snapshot-repository/org/apache/servicemix/features/apache-servicemix/4.0-m2-SNAPSHOT/].  There have been a lot of changes since 4.0-m1 so if you could test this issue on 4.0-m2 and give an update here that would be great.

> Startup hangs occasionally
> --------------------------
>
>                 Key: SMX4-200
>                 URL: https://issues.apache.org/activemq/browse/SMX4-200
>             Project: ServiceMix 4
>          Issue Type: Bug
>    Affects Versions: 4.0-m1
>         Environment: JDK:
> java version "1.6.0_02"
> Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_02-b05, mixed mode)
> OS: Win XP x64 Pro Version 2003 Service Pack 2
>            Reporter: Sakke Wiik
>             Fix For: 4.0-m2
>
>         Attachments: diff_folder_structure.html, servicemix_fail.log
>
>
> Start with servicemix.bat fails approximately every second time. The process doesn't die, but uses a high amount of CPU forever.
> The data folders between a failing and a success start shows differences (full folder diff in attached file "diff_folder_structure.html"). Repeated failed starts proved that all failing cases have identical data folders:
> differing files (except log and bundle.lasmodified):
> <apache-servicemix-4.0-m1>\failing_start\cache\bundle78\data\config\org\apache\servicemix\activemq.config
> <apache-servicemix-4.0-m1>\successful_start\cache\bundle78\data\config\org\apache\servicemix\activemq.config
> <apache-servicemix-4.0-m1>\failing_start\cache\bundle78\data\config\org\apache\servicemix\features.config
> <apache-servicemix-4.0-m1>\successful_start\cache\bundle78\data\config\org\apache\servicemix\features.config
> <apache-servicemix-4.0-m1>\failing_start\cache\bundle78\data\config\org\apache\servicemix\management.config
> <apache-servicemix-4.0-m1>\successful_start\cache\bundle78\data\config\org\apache\servicemix\management.config
> <apache-servicemix-4.0-m1>\failing_start\cache\bundle78\data\config\org\apache\servicemix\shell.config
> <apache-servicemix-4.0-m1>\successful_start\cache\bundle78\data\config\org\apache\servicemix\shell.config
> <apache-servicemix-4.0-m1>\failing_start\cache\bundle78\data\config\org\apache\servicemix\transaction.config
> <apache-servicemix-4.0-m1>\successful_start\cache\bundle78\data\config\org\apache\servicemix\transaction.config
>      
> The difference is that property service.bundleLocation is missing from config-files in the failing case.
> The bundle with id 78 has location org.apache.felix.configadmin-1.0.0.jar
> Other differences:
>       
> The folder <apache-servicemix-4.0-m1>\failing_start\cache\bundle81\data (org.apache.felix.prefs-1.0.2.jar) is missing. The bundle81 is the bundle with the highest id.
> Other missing folders: <apache-servicemix-4.0-m1>\failing_start\amq, <apache-servicemix-4.0-m1>\failing_start\jbi

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.