Golden Ticket error: com.appistry.fabric.TransactionException: The request was not attempted. Connect to Task Service failed
Sun, 01/18/2009 - 22:13
I have the Golden Ticket app running, and I get the test output:
bash-3.1$ fabric_ctl -d 239.255.0.1:30000 -u fabric-admin/fabric-admin fabric-version golden_ticket_java_app.fabric all
Version 2.0: 1 workers.
and also:
bash-3.1$ fabric_ctl -d 239.255.0.1:30000 -ufabric-admin/fabric-admin query all
10.10.1.112 up
bur when I try to run the "run.sh". I get:
bash-3.1$ ./run.sh 239.255.0.1 31000
Welcome to the Appistry Peer2Peer Golden Ticket Contest!
Please enter your exact Peer2Peer username: JoeBaran
com.appistry.fabric.TransactionException: The request was not attempted. Connect to Task Service failed
at com.appistry.fabric.ErrorCode.getFabricException(Unknown Source)
at com.appistry.fabric.FabricAPI.handleResults(Unknown Source)
at com.appistry.fabric.FabricAPI.handleResultsAndCleanup(Unknown Source)
at com.appistry.fabric.FabricAPI.waitCorrelated(Unknown Source)
at com.appistry.fabric.FabricAPI.execute(Unknown Source)
at com.appistry.fabric.Fabric.execute(Unknown Source)
at com.appistry.Peer2PeerContest.GoldenTicketClient.main(GoldenTicketClient.java:71)
Usage: golden_ticket_client uses the default fabric address and port
golden_ticket_client
golden_ticket_client -h yields this usage help
Running RHEL 5, firewall is disabled, selinux is disabled, etc. etc.
It is 64-bit RHEL with a 64-bit JVM - could that be a problem?
other info:
bash-3.1$ uname -a
Linux JBRHEL51 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:14 EST 2007 x86_64 x86_64 x86_64 GNU/Linux
bash-3.1$ java -version
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_09-b03, mixed mode)
bash-3.1$
Can anyone suggest what is wrong?
I ran the log monitor and got the following - it looks like a JVM problem.
===========================
bash-3.1$ log_monitor 239.255.0.1:4000
Monitor listening on: 239.255.0.1:4000
Jan 18 22:07:59 00:0C:29:A5:7C:61 FAM[I:14000] FAM Member Service started on port(s) 51130
Jan 18 22:07:59 00:0C:29:A5:7C:61 FabricWorkerManager[I:10000] Location: 10.10.1.112 FabricWorkerManager: 239.255.0.1:32000 FabricWorkerManager initialized...
Jan 18 22:07:59 00:0C:29:A5:7C:61 FabricWorkerManager[I:10001] FabricWorkerManager OS path: /sbin:/usr/sbin:/bin:/usr/bin:/usr/local/fabric/system
Jan 18 22:07:59 00:0C:29:A5:7C:61 FabricWorkerManager[I:10002] FabricWorkerManager OS ld_library_path: /usr/local/fabric/system:.
Jan 18 22:07:59 00:0C:29:A5:7C:61 FabricWorkerManager[I:10003] FabricWorkerManager Home: /usr/local/fabric/system
Jan 18 22:07:59 00:0C:29:A5:7C:61 RegionService[I:8000] Location: 10.10.1.112 Region: 239.255.0.1:32000 Services starting
Jan 18 22:08:07 00:0C:29:A5:7C:61 RegionService[I:8010] Location: 10.10.1.112 RegionLeaderRegion: Creating Region Leader for region
Jan 18 22:08:07 00:0C:29:A5:7C:61 RegionService[I:8008] Location: 10.10.1.112 RegionLeaderRegion: Creating Senior Region Leader for leader region
Jan 18 22:08:07 00:0C:29:A5:7C:61 TaskServiceManager[I:2006] App [golden_ticket_java_app] definition loaded
Jan 18 22:08:07 00:0C:29:A5:7C:61 TaskServiceManager[I:4500] Submitting start command to fabric_task_service.golden_ticket_java_app
Jan 18 22:08:07 00:0C:29:A5:7C:61 fabric_task_service.golden_ticket_java_app[I:4039] fabric_task_service.golden_ticket_java_app has LD_LIBRARY_PATH: /usr/local/fabric/system/apps/golden_ticket_java_app:/usr/local/fabric/system:.:/usr/local/fabric/system:
Jan 18 22:08:07 00:0C:29:A5:7C:61 fabric_task_service.golden_ticket_java_app[I:4026] Application classpath: /usr/local/fabric/system/apps/golden_ticket_java_app/commons-codec-1.3.jar:/usr/local/fabric/system/apps/golden_ticket_java_app/golden_ticket.jar
Jan 18 22:08:08 00:0C:29:A5:7C:61 TaskServiceManager[I:4504] Done Submitting start commands to application services
Jan 18 22:08:08 00:0C:29:A5:7C:61 ProcessService[I:2006] App [golden_ticket_java_app] definition loaded
Jan 18 22:08:08 00:0C:29:A5:7C:61 FabricProcess[I:3010] Process Flow: 'golden_ticket_java_app.golden_ticket_flow' loaded
Jan 18 22:08:08 00:0C:29:A5:7C:61 FabricProcess[I:1000] Process Service started on port 16002
Jan 18 22:08:08 00:0C:29:A5:7C:61 fabric_task_service.golden_ticket_java_app[E:4008] JavaEnvironment failed to start. Reason: JNI: Failed to get JVM environment: libjvm.so: cannot open shared object file: No such file or directory
Jan 18 22:08:08 00:0C:29:A5:7C:61 RequestService[I:2006] App [golden_ticket_java_app] definition loaded
Jan 18 22:08:08 00:0C:29:A5:7C:61 FabricRequest[I:1000] Request Service started on port(s) 16000
Jan 18 22:08:15 00:0C:29:A5:7C:61 RegionService[I:8011] Location: 10.10.1.112 Region: 239.255.0.1:32000 Heartbeat size: 1
Jan 18 22:08:18 00:0C:29:A5:7C:61 TaskServiceManager[D:0] CORE DUMP FOUND: apps/golden_ticket_java_app/core.11872
Jan 18 22:08:18 00:0C:29:A5:7C:61 RegionService[I:8011] Location: 10.10.1.112 RegionLeaderRegion: Heartbeat size: 1
Jan 18 22:08:23 00:0C:29:A5:7C:61 RegionService[I:8011] Location: 10.10.1.112 Region: 239.255.0.1:32000 Heartbeat size: 1
Jan 18 22:08:28 00:0C:29:A5:7C:61 TaskServiceManager[D:0] CORE DUMP FOUND: apps/golden_ticket_java_app/core.4465
Jan 18 22:08:28 00:0C:29:A5:7C:61 TaskServiceManager[E:4507] Service fabric_task_service.golden_ticket_java_app unexpectedly down
Jan 18 22:08:28 00:0C:29:A5:7C:61 TaskServiceManager[I:4500] Submitting start command to fabric_task_service.golden_ticket_java_app
Jan 18 22:08:28 00:0C:29:A5:7C:61 fabric_task_service.golden_ticket_java_app[I:4039] fabric_task_service.golden_ticket_java_app has LD_LIBRARY_PATH: /usr/local/fabric/system/apps/golden_ticket_java_app:/usr/local/fabric/system:.:/usr/local/fabric/system:
Jan 18 22:08:28 00:0C:29:A5:7C:61 fabric_task_service.golden_ticket_java_app[I:4026] Application classpath: /usr/local/fabric/system/apps/golden_ticket_java_app/commons-codec-1.3.jar:/usr/local/fabric/system/apps/golden_ticket_java_app/golden_ticket.jar
Jan 18 22:08:28 00:0C:29:A5:7C:61 fabric_task_service.golden_ticket_java_app[E:4008] JavaEnvironment failed to start. Reason: JNI: Failed to get JVM environment: libjvm.so: cannot open shared object file: No such file or directory
Jan 18 22:08:29 00:0C:29:A5:7C:61 RegionService[I:8011] Location: 10.10.1.112 RegionLeaderRegion: Heartbeat size: 1
Jan 18 22:08:31 00:0C:29:A5:7C:61 RegionService[I:8011] Location: 10.10.1.112 Region: 239.255.0.1:32000 Heartbeat size: 1
Jan 18 22:08:38 00:0C:29:A5:7C:61 TaskServiceManager[D:0] CORE DUMP FOUND: apps/golden_ticket_java_app/core.4539
Jan 18 22:08:38 00:0C:29:A5:7C:61 TaskServiceManager[E:4507] Service fabric_task_service.golden_ticket_java_app unexpectedly down
===========================
If this can't run with the 64-bit JVM, it should say so in the system setup requirements (or did I miss it?).
Otherwise, does anybody have any ideas????
Thanks.
Sun, 01/18/2009 - 23:33
#2
guerry
I should say that even though EAF may run in 32-bit mode, it's not supported. You're safest bet is to run it on a 32-bit box with a 32-bit OS and VM.
Thanks,
Guerry
Mon, 01/19/2009 - 08:29
#3
Wow - No 64-bit support, and not even 32-bit mode.
Unfortunately, that's a real show-stopper for us - and a severe limitation for Appistry in the Enterprise. Is there a roadmap timetable for 64-bit support?
By the way, the "System Requirements" page REALLY needs to say this - for "Supported Operating Systems", it lists the name and version but not the platform; for hardware it lists "minimums" but not "limitations".
What is says right now is just this:
---------------
System requirements
Supported Operating Systems
Red Hat Enterprise Linux 4 and 5
SUSE 10.3
Windows XP SP2 or later - also supported on VMWare Player and Virtual PC 2007
Windows Vista
Windows Server 2003 SP1 or later
All of the workers must consist of the same operating system.
Fabric Worker Minimum Requirements
Software
Sun JRE 1.5 or Sun JDK 1.5 (if running Java tasks)
.NET Framework v2.0 (if running .NET tasks)
Hardware
Intel® Pentium® III/AMD Athlon™ or later CPU
256MB RAM
10GB hard drive
A PXE-capable network card is recommended to make use of the assimilation feature
Fabric Monitor requirements
Web Service Tier
Sun JRE 1.5 or Sun JDK 1.5
Apache Tomcat 5.5
Client Tier
Flash v7+ player
HTML 3.2 compatible browser (to view help files for Appistry Fabric Monitor)
------------
P.S. Does anyone still make 32-bit servers anymore? I know that there are a lot of them still out there, but I can't remember the last time one of our customers installed one.
Mon, 01/19/2009 - 09:37
#4
guerry
JoeBaran,
I'll check on the 32-bit support while on a 64-bit platform. However, straight-up support for 64-bit is coming soon, but I do not have a release date I can share here yet.
Thanks for pointing out the docs. I thought it was in there. We'll have it fixed today.
Thanks,
Guerry
Mon, 01/26/2009 - 12:53
#5
guerry
Sorry for the late update.
Appistry EAF will run on 64-bit platforms in 32-bit mode (both Windows and Linux). For Java support under that scenario, the JDK/JRE utilized by the fabric must also be 32-bit. We have customers running in production in this mode.
I'll make sure the docs reflect this information.
Thanks,
Guerry
Mon, 03/09/2009 - 14:50
#6
It's been almost two months, and there have been no posts to this thread.
I'm new here, but I'm very interested in the 64-bit issue. Granted that you are not allowed to share a release date, can you mention a year or quarter?
Thanks,
Eric
Mon, 03/09/2009 - 15:37
#7
mark
Granted that you are not allowed to share a release date, can you mention a year or quarter?
Appistry CloudIQ Platform 4.0 will be available in Spring 2009 as a software download. That being said, I will bring this up at our next status meeting. I know there has been work on it already, but I want to find out exactly what will be included in that release as far as 64-bit. I will post an update tomorrow.
Mark
Tue, 03/10/2009 - 14:34
#8
mark
We anticipate releasing the native 64-bit version of the rhel4 and rhel5 version of the fabric when 4.0 is released. We plan on following that almost immediately with a version that is native 64-bit windows.
Therefore, we are anticipating Spring 2009 for 64-bit rhel4 and rhel5, and soon after for Windows.
Sat, 01/30/2010 - 17:59
#9
I have exactly the same problem in SUSE x64 :
fabric_task_service.monte_carlo_pi_java_app[I:4026] Application classpath: /usr/local/appistry/cloudiq/system/apps/monte_carlo_pi_java_app/monte_carlo_pi.jar
Jan 30 16:46:40 00:11:25:B9:B0:40 fabric_task_service.monte_carlo_pi_java_app[E:4008] JavaEnvironment failed to start. Reason: JNI: Failed to get JVM environment: libjvm.so: cannot open shared object file: No such file or directory
Did this problem fixed?
Mon, 02/01/2010 - 12:15
#10
mark
Yes, we now support 64-bit operating systems. Therefore, you should be able to utilize 64-bit Java on 64-bit SuSE.
It looks like there may be a mismatch of 32 and 64 bit installs on your box. Are both the fabric and the java installs 64-bit? That is likely the issue. If not, I can give you some other ideas of where to look.
Thanks,
Mark
Tue, 02/02/2010 - 16:10
#11
mark
I have exactly the same problem in SUSE x64
fabric_task_service.monte_carlo_pi_java_app[I:4026] Application classpath: /usr/local/appistry/cloudiq/system/apps/monte_carlo_pi_java_app/monte_carlo_pi.jar
Jan 30 16:46:40 00:11:25:B9:B0:40 fabric_task_service.monte_carlo_pi_java_app[E:4008] JavaEnvironment failed to start. Reason: JNI: Failed to get JVM environment: libjvm.so: cannot open shared object file: No such file or directory
Did this problem fixed?
fabric_task_service.monte_carlo_pi_java_app[I:4026] Application classpath: /usr/local/appistry/cloudiq/system/apps/monte_carlo_pi_java_app/monte_carlo_pi.jar
Jan 30 16:46:40 00:11:25:B9:B0:40 fabric_task_service.monte_carlo_pi_java_app[E:4008] JavaEnvironment failed to start. Reason: JNI: Failed to get JVM environment: libjvm.so: cannot open shared object file: No such file or directory
Did this problem fixed?
zeroprg,
I recreated the message that you displayed by installing a 32-bit version of java and a 64-bit version of the fabric on a 64-bit SuSE box. I suggest checking if you have a 32-bit version of Java installed on your SuSE x64 machine. If so, that is likely the reason why.
Mark
Tue, 02/02/2010 - 22:44
#12
I have $JAVA_HOME/jre/lib/amd64/server/libjvm.so
I fixed it by creating soft link to libjvm.so like this:
cd $JAVA_HOME/jre/lib/
ln -s $JAVA_HOME/jre/lib/amd64 i386
Please add it to your page "Configuring Java" page http://www.appistry.com/community/wiki/display/eaf38dev/Configuring+Java
and to main pdf documentation file.
Wed, 02/03/2010 - 10:57
#13
mark
I have $JAVA_HOME/jre/lib/amd64/server/libjvm.so
I fixed it by creating soft link to libjvm.so like this:
cd $JAVA_HOME/jre/lib/
ln -s $JAVA_HOME/jre/lib/amd64 i386
I fixed it by creating soft link to libjvm.so like this:
cd $JAVA_HOME/jre/lib/
ln -s $JAVA_HOME/jre/lib/amd64 i386
I have yet to recreate this issue that you are experiencing above without having a mismatch between 32-bit and 64-bit.
What version number and bit are you using for the following:
- Fabric Installation
- Java Installation
- Java fabric application (version number not necessary for this one.)
Once I get enough information, and fully understand the issue, we would be happy to add it to the documentation.
Mark
Wed, 02/03/2010 - 20:04
#14
I had this issue in SUSE v10 and v11 for AMD 64 bits. Try to reproduce it in Linux SUSE for 64 bits
Thu, 02/04/2010 - 10:32
#15
justin
What version number and bit are you using for the following:
- Fabric Installation
- Java Installation
- Java fabric application (version number not necessary for this one.)
- Fabric Installation
- Java Installation
- Java fabric application (version number not necessary for this one.)
We're happy to investigate further, but we do need this information in order to model your environment.
Tue, 02/16/2010 - 02:08
#16
- Fabric installation was last one
- Java installation JavaIce JDK1.6 (only this availabel from SUSE v11 x64) - this is key guy in issue creation I suppose
- Java fabric application "Hello word"
Sorry, but yes, our 64-bit support is forthcoming. It will need to be a 32-bit JVM, and EAF will run in 32-bit mode.
Hope that helps,
Guerry