Closed GoogleCodeExporter closed 9 years ago
Are there any errors in the zap.log file when it fails to start?
Original comment by psii...@gmail.com
on 19 Apr 2013 at 3:28
Sorry, I'm pretty new to ZAP and just downloaded and attempted to try it out.
Where would I find the zap.log file? I don't see anything like that in the app
package. I only saw a /Contents/Java/log/dummy.txt file there.
Original comment by Daniel.J...@gmail.com
on 19 Apr 2013 at 3:49
I think its in ~/Library/Application Support/ZAP on Macs (I dont have one)
Original comment by psii...@gmail.com
on 19 Apr 2013 at 3:53
Ok, I found the log file. I tailed the file and watched to see if anything was
being written to it when I tried to launch the application using the osx
package. The icon still just bounces on the dock but nothing is being written
to the logs. However, when I run the zap shell script in the app package, it
writes to the logs(which is fine since I can run the application using that
shell script).
Maybe it has something to do with the osx package I downloaded and it's not
compatible with my version of OSX or something?
Anyway, here's the attached log file.
Original comment by Daniel.J...@gmail.com
on 19 Apr 2013 at 6:04
Attachments:
Ok, I tried to launch the same application on my macbook I use at home(earlier
I was trying to run the application on the macbook I use at work) and I am
still getting the same situation. I can run it using the zap.sh shell script
but it doesn't work when I try to run by double clicking the app package(and no
logs being written).
Original comment by Daniel.J...@gmail.com
on 20 Apr 2013 at 12:48
Original comment by psii...@gmail.com
on 20 Apr 2013 at 9:56
Issue 648 has been merged into this issue.
Original comment by psii...@gmail.com
on 21 Apr 2013 at 8:12
I can confirm that I have the same issue.
I have MAC OS X 10.8.3
Java 7 update 21 , Java Update was last run at 18:43 on 24/04/13.
Downloaded version: OWASP_ZAP_2.1.0_OSX
Is there any solution for this problem?
Original comment by donseedp...@gmail.com
on 24 Apr 2013 at 5:44
Hi all,
I can confirm the issue on my Mac OS X 10.8.3, Java 7 update 21.
The necessary stacktrace can be found via the Console.app:
4/24/13 9:17:59.282 PM JavaAppLauncher[818]: failed to JNI_CreateJavaVM (-1):
CFBundle 0x100116a30 </Applications/OWASP
ZAP.app/Contents/PlugIns/jre1.7.0_21.jre> (framework, loaded): (
0 CoreFoundation 0x00007fff90253b06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff907653f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff902538dc +[NSException raise:format:] + 204
3 JavaAppLauncher 0x000000010000326f JavaAppLauncher + 12911
4 Foundation 0x00007fff88ef4cd2 __NSThread__main__ + 1345
5 libsystem_c.dylib 0x00007fff8efc27a2 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff8efaf1e1 thread_start + 13
)
4/24/13 9:18:12.839 PM Dock[260]: no information back from LS about running
process
4/24/13 9:18:45.933 PM com.apple.launchd.peruser.501[247]:
([0x0-0x50050].org.zaproxy.zap.ZAP[818]) Exited: Terminated: 15
4/24/13 9:20:10.688 PM Dock[260]: no information back from LS about running
process
Original comment by hugo.v...@gmail.com
on 24 Apr 2013 at 7:22
I see the following in system.log via the Console app:
Apr 24 21:36:58 mac-georger [0x0-0x11ea1e9].org.zaproxy.zap.ZAP[84415]: Error:
could not find libjava.dylib
Apr 24 21:36:58 mac-georger [0x0-0x11ea1e9].org.zaproxy.zap.ZAP[84415]: Failed
to GetJREPath()
Apr 24 21:36:58 mac-georger JavaAppLauncher[84415]: failed to JNI_CreateJavaVM
(-1): CFBundle 0x100302af0 </Applications/OWASP
ZAP.app/Contents/PlugIns/jre1.7.0_21.jre> (framework, loaded): (
0 CoreFoundation 0x00007fff8ec1ef56 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff8a53bdee objc_exception_throw + 43
2 CoreFoundation 0x00007fff8ec1ed8a +[NSException raise:format:arguments:] + 106
3 CoreFoundation 0x00007fff8ec1ed14 +[NSException raise:format:] + 116
4 JavaAppLauncher 0x000000010000326f JavaAppLauncher + 12911
5 Foundation 0x00007fff9128372a -[NSThread main] + 68
6 Foundation 0x00007fff912836a2 __NSThread__main__ + 1575
7 libsystem_c.dylib 0x00007fff8dc248bf _pthread_start + 335
8 libsystem_c.dylib 0x00007fff8dc27b75 thread_start + 13
)
Mac OS X 10.7.5
$ java -version
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
Original comment by George.V...@gmail.com
on 25 Apr 2013 at 4:40
I am having the same issue loading the program. I did update my Java
installation using the V7 JDK.
Mac OSX 10.7.5
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b12)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
Original comment by bob.ches...@nhsoftwerks.com
on 27 Apr 2013 at 5:09
Hi guys,
just wanted to let you know that i am already trying to fix the issue.
So far i was not able to reproduce it, since it is working like a charm on
my testing instances. Nevertheless, i'll try to find out what's wrong with
the Java starter.
Please be patient a little bit longer.
Original comment by a.c.neumann
on 29 Apr 2013 at 9:04
Same Problem here. Posting in hope of getting an email on new postings.
Original comment by ricki.my...@gmail.com
on 30 Apr 2013 at 10:33
Have the same problem as you guys, but if you want to play around with I found
that I could start it up with the zap.sh script found in OWASP
ZAP.app/Contents/Java/
Original comment by christer...@gmail.com
on 3 May 2013 at 6:52
Same issue.
Original comment by mich...@mbcarlson.org
on 14 May 2013 at 4:59
After rummaging through the source code of JavaAppLauncher, it seems that the
problem is that it could not find the library that exports the symbol
"JNI_CreateJavaVM". I think I even saw somewhere that JNI_CreateJavaVM is being
deprecated.
Anyway, in the meantime, instead of relying on the fancy launcher system, one
should simply just invoke zap.sh from the command line as
"/Applications/OWASP ZAP.app/Contents/Java/zap.sh"
Note the quote "..." above because of the space in the name. If you installed
ZAP elsewhere, modify your path accordingly.
Original comment by dayo.res...@gmail.com
on 15 May 2013 at 4:40
OK. On further investigation the problem seems to lie with the version of JRE
bundled with ZAP. After fiddling about a bit, I found a working solution that
uses the JDK I already have installed.
The following two commands removed the JRE bundled with ZAP and created a
symbolic link to my JDK. I could then launch ZAP as usual afterwards.
rm -rf /Applications/OWASP\ ZAP.app/Contents/PlugIns/jre1.7.0_21.jre
ln -s /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk /Applications/OWASP\
ZAP.app/Contents/PlugIns/jre1.7.0_21.jre
Original comment by dayo.res...@gmail.com
on 15 May 2013 at 5:48
`./zap.sh`
Exiting: ZAP 2.0.0 requires a minimum of Java 7 to run.
`java -version`
java version "1.6.0_43"
Java(TM) SE Runtime Environment (build 1.6.0_43-b01-447-11M4203)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01-447, mixed mode)
I installed the latest JRE 7 for mac and it didn't seem to affect the java
version installed.
What else am I missing?
Original comment by bsoa...@gmail.com
on 17 May 2013 at 1:15
@#18
You might need to set your JAVA_HOME environment variable by adding the
following line to your ~/.bash_profile
export JAVA_HOME=$(/usr/libexec/java_home -v 1.7)
Original comment by dayo.res...@gmail.com
on 17 May 2013 at 10:21
@#18
Download and install JDK 7 by yourself.
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.h
tml
Original comment by riot...@gmail.com
on 21 May 2013 at 8:29
@#17
Thanks for the info. I attempted the fix and it works just fine now :).
Original comment by Daniel.J...@gmail.com
on 21 May 2013 at 1:06
[deleted comment]
All,
I am having the same problem - very frustrating!
@#17 - Tried this, but it didn't work.
@#19 - Tried this too, but am getting the following message: Unable to find any
JVMs matching version "1.7", even though I installed 7.
I'm totally at a loss what to do...
Original comment by r.den...@gmail.com
on 21 May 2013 at 6:16
[deleted comment]
Hi guys,
i've prepared another ZAP testing build using the latest openjdk code for
building the included JRE. Could you please test and report back if it
fixed the problems? Testing ZAP with different Java Runtimes in a virtual
machine is almost impossible for me because of existing Java/VMWare
incompatibilities/issues, such as
http://communities.vmware.com/docs/DOC-22830 ...
Zap 2.1.0 Testing Build:
http://goo.gl/sKNsm
Original comment by a.c.neumann
on 23 May 2013 at 1:29
I've tried using the new testing build and it seems to be working now(at least
the application loads up correctly without having to do the #17 hack).
Thanks!
Original comment by Daniel.J...@gmail.com
on 23 May 2013 at 4:27
2.1.0 was throwing the same console log as comment #10 here on 10.7.5 / Java 7
Update 21.
I've tried the test build from comment #25 - still doesn't work but throws a
different set of errors to the console:
24/05/2013 11:54:23.481 [0x0-0x13b13b].org.zaproxy.zap.ZAP: 486 [main] INFO
org.zaproxy.zap.ZAP - OWASP ZAP 2.1.0 started.
24/05/2013 11:54:23.528 [0x0-0x13b13b].org.zaproxy.zap.ZAP: [LaunchRunner
Error] org.zaproxy.zap.ZAP.main(String[]) threw an exception:
24/05/2013 11:54:23.529 [0x0-0x13b13b].org.zaproxy.zap.ZAP:
java.lang.UnsatisfiedLinkError: /Applications/OWASP ZAP
openjdk.app/Contents/PlugIns/jre1.7.0.jre/Contents/Home/lib/lwawt/liblwawt.dylib
: dlopen(/Applications/OWASP ZAP
openjdk.app/Contents/PlugIns/jre1.7.0.jre/Contents/Home/lib/lwawt/liblwawt.dylib
, 1): Library not loaded:
/System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
24/05/2013 11:54:23.529 [0x0-0x13b13b].org.zaproxy.zap.ZAP: Referenced from:
/Applications/OWASP ZAP
openjdk.app/Contents/PlugIns/jre1.7.0.jre/Contents/Home/lib/lwawt/liblwawt.dylib
24/05/2013 11:54:23.529 [0x0-0x13b13b].org.zaproxy.zap.ZAP: Reason: image not
found
...
24/05/2013 11:54:23.532 [0x0-0x13b13b].org.zaproxy.zap.ZAP:
JavaAppLauncherFailure CallStaticVoidMethod() threw an exception
24/05/2013 11:54:23.532 [0x0-0x13b13b].org.zaproxy.zap.ZAP: Exception in thread
"main" java.util.MissingResourceException: Can't find bundle for base name
appLauncherErrors, locale en_US
...
If I run zap.sh directly from within the package then it works but is using
1.7.0_13 (which I assume is the bundled JRE) rather than the system installed
copy.
Original comment by liam.jon...@gmail.com
on 24 May 2013 at 10:59
Sorry if my messing around with comment #27 sent multiple notifications to
people. I had JRE 1.7.0_21 on my Mac but JDK 1.7.0_13 - I wanted to check that
wasn't causing issues.
Having updated to JDK 1.7.0_21 the behaviour is still the same in all
instances. Both builds fail via the launcher (with the differing messages
mentioned before) but both work via zap.sh.
Original comment by liam.jon...@gmail.com
on 24 May 2013 at 12:57
My machine is using the 1.7.0_21 JDK and it seems to work fine.
It does take awhile for it to load up but it does start.
Original comment by Daniel.J...@gmail.com
on 24 May 2013 at 2:28
#17 - worked for me
#25 - worked for me
Original comment by matthewd...@gmail.com
on 30 May 2013 at 11:01
i give up, dont works.... :(
i have mac os lion 10.7.5 with last java jdk 7.21 and nothing happen, even from
zap.sh :(
with the link in the comment #25 says "Successfully tested with OS X 10.8.3
(12D78) and Java 7 Update 17 (build 1.7.0_17-b02). Does not work for OS X
10.7.x guests at this time: The patch applies and prevents the crash, but Java
windows/frames do not display any content." fck!! :)
i cant update the mac os x by the moment, any other idea? or version of zap?
appreciate
Original comment by neo...@gmail.com
on 8 Jun 2013 at 4:44
Yes, the 'Linux' release is actually cross platform - its just a tar.
It will work on Linux, Mac and Windows.
The weekly releases are the same.
I'm hoping to get access to a Mac box soon so will make getting ZAP working on
Macs a priority.
Original comment by psii...@gmail.com
on 8 Jun 2013 at 10:30
Issue 679 has been merged into this issue.
Original comment by psii...@gmail.com
on 8 Jun 2013 at 10:30
in linux release, running the zap.sh on terminal says...
Unable to find any JVMs matching version "1.7".
:(
Original comment by neo...@gmail.com
on 8 Jun 2013 at 3:09
Do you have java 7 on your path?
zap.sh is a text file that you can easily edit.
The following lines check to see if java appears to be on the path:
#Check the java version (min java 7)
JAVAV=`java -version 2>&1 |awk 'NR==1{ gsub(/"/,""); print $3 }'`
if [[ $JAVAV == 1.7* ]]; then
# OK
echo "Using Java version: $JAVAV"
else
echo "Exiting: ZAP 2.0.0 requires a minimum of Java 7 to run."
exit 1
fi
If you do have java 7 on your path, could you run:
java -version 2>&1 |awk 'NR==1{ gsub(/"/,""); print $3 }'
and let me know what it returns?
You could always try commenting those lines out, but it would be very useful to
fix the underlying problem.
Many thanks
Original comment by psii...@gmail.com
on 8 Jun 2013 at 3:15
returns 1.6.0_45
but why? on panel control says... java 7 update 21
access path
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
Original comment by neo...@gmail.com
on 8 Jun 2013 at 9:23
This will be an OS 'path' issue.
Unfortunately I dont have a Mac OS right now so I cant give any specific advice.
However on *nix systems you can typically do things like:
# Show the path you are using
echo $PATH
# Show which java you are using
which java
Can anyone else offer some advice?
Original comment by psii...@gmail.com
on 10 Jun 2013 at 8:47
So, the 1.6.0_45 is probably the last version of Java that Apple supported
before they stopped supporting it.
Apple used to provide support for Java on their OS and had Java already
installed. So that version you are seeing is probably what Apple had already
on your Macbook.
What you can do is try to override your $JAVA_HOME variable for your user. So,
under your /Users/{username} directory, create/modify the file .bash_profile
and add a JAVA_HOME variable in the file. Then, close your terminal and re-open
it. Here's part of my .bash_profile looks like:
export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home
Incase you are wondering, I've installed JDK 1.7.21 on my machine and that's
why the path looks different from your control panel for Java(the control panel
application I believe only manages a JRE installation...I'm a java web
developer so I need to use the JDK installation).
Original comment by Daniel.J...@gmail.com
on 10 Jun 2013 at 12:46
17# works fine!!! users install before 1.7 jdk and automatic update your jdk of
mountain lion!! and try to patch with #17 answers... works fine!!!
Original comment by rocco.sp...@gmail.com
on 10 Jun 2013 at 5:45
I'm running Mountain Lion and here is what worked for me:
1. Download and install Java JDK 7_u21
2. rm -rf /Applications/OWASP\ ZAP.app/Contents/PlugIns/jre1.7.0_21.jre
3. ln -s /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk /Applications/OWASP\
ZAP.app/Contents/PlugIns/jre1.7.0_21.jre
4. mkdir "/var/root/Library/Application Support/"
5. mkdir "/var/root/Library/Application Support/ZAP"
Launch OWASP ZAP.
Original comment by ara1...@gmail.com
on 12 Jun 2013 at 9:04
I _may_ have a fix for this issue.
If you have a Mac can you try this release:
http://code.google.com/p/zaproxy/downloads/detail?name=ZAP_2.1.0b_Mac_OS_X.zip
Its flagged as Deprecated, but thats just so that it doesnt show up for most
people until we've had a chance to try it out on various systems.
Please let us know if it works or not, and what system you tested it on.
Cheers,
Simon
Original comment by psii...@gmail.com
on 17 Jun 2013 at 1:24
So far had confirmation that this works on:
15" Retina MacBook Pro - 10.9
Mac Mini - 10.8.4
Original comment by psii...@gmail.com
on 17 Jun 2013 at 2:28
works like a charm! :) thanks!
Mac OS X - 10.7.5
Original comment by neo...@gmail.com
on 17 Jun 2013 at 3:04
This is believed to be fixed by the latest Mac download.
Original comment by psii...@gmail.com
on 24 Jun 2013 at 1:39
Original issue reported on code.google.com by
Daniel.J...@gmail.com
on 19 Apr 2013 at 3:25