Task #8447 (closed)
Opened 12 years ago
Closed 12 years ago
BUG: poluted session/thread while using CLI
Reported by: | atarkowska | Owned by: | cblackburn |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-4.4 |
Component: | Bin-Services | Version: | n.a. |
Keywords: | n.a. | Cc: | cxallan, jamoore |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | 2012-04-24 (13) |
Description
I was trying to import set of files from two different location. For the first time it went smoothly. When I picked second location I got the following error:
bin/omero import -m -d 51 /OMERO/ManagedRepository/MY_PATH/ Using session 50f8d98f-7472-4d41-a43b-1c8626524992 (user@localhost:4064). Idle timeout: 10.0 min. Current group: group Exception in thread "main" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:640) at java.util.Timer.<init>(Timer.java:154) at java.util.Timer.<init>(Timer.java:122) at java.util.prefs.FileSystemPreferences.<clinit>(FileSystemPreferences.java:413) at java.util.prefs.FileSystemPreferencesFactory.userRoot(FileSystemPreferencesFactory.java:24) at java.util.prefs.Preferences.userRoot(Preferences.java:434) at java.util.prefs.Preferences.userNodeForPackage(Preferences.java:348) at ome.formats.importer.ImportConfig.prefs(ImportConfig.java:141) at ome.formats.importer.ImportConfig.<init>(ImportConfig.java:169) at ome.formats.importer.ImportConfig.<init>(ImportConfig.java:155) at ome.formats.importer.cli.CommandLineImporter.main(CommandLineImporter.java:239)
bin/omero logout
solved the problem
Change History (3)
comment:1 Changed 12 years ago by atarkowska
- Summary changed from BUG: poluted session while using CLI to BUG: poluted session/thread while using CLI
comment:2 Changed 12 years ago by jburel
- Sprint changed from 2012-04-10 (12) to 2012-04-24 (13)
comment:3 Changed 12 years ago by cblackburn
- Resolution set to fixed
- Status changed from new to closed
This was a failure to logout of the session/close services. This had the knock on effect seen in #8525.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moved from sprint 2012-04-10 (12)