Receiving stack trace on startup

30 views
Skip to first unread message

Scott

unread,
Aug 12, 2013, 12:04:05 PM8/12/13
to browserm...@googlegroups.com
I seem to have had something change on a system configuration which is causing me to be unable to run browsermob proxy. I was able to run things just fine on this aws instance on Friday, but today when I go to start the proxy I receive the following stack trace:

Exception in thread "main" java.lang.ExceptionInInitializerError
        at net.lightbody.bmp.proxy.guice.ConfigModule.configure(ConfigModule.java:53)
        at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
        at com.google.inject.spi.Elements.getElements(Elements.java:101)
        at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
        at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
        at com.google.inject.Guice.createInjector(Guice.java:95)
        at com.google.inject.Guice.createInjector(Guice.java:72)
        at com.google.inject.Guice.createInjector(Guice.java:62)
        at net.lightbody.bmp.proxy.Main.main(Main.java:30)
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
        at java.lang.String.substring(String.java:1949)
        at cz.mallat.uasparser.fileparser.PHPFileParser.loadFile(PHPFileParser.java:65)
        at cz.mallat.uasparser.fileparser.PHPFileParser.<init>(PHPFileParser.java:29)
        at cz.mallat.uasparser.UASparser.loadDataFromFile(UASparser.java:237)
        at cz.mallat.uasparser.CachingOnlineUpdateUASparser.<init>(CachingOnlineUpdateUASparser.java:55)
        at cz.mallat.uasparser.CachingOnlineUpdateUASparser.<init>(CachingOnlineUpdateUASparser.java:26)
        at net.lightbody.bmp.proxy.http.BrowserMobHttpClient.<clinit>(BrowserMobHttpClient.java:61)
        ... 9 more

I've downloaded the jar again, and receive that same message. Again, I'm running on a pretty vanilla aws instance. Are there any configurations which I should look for which would cause such an issue?

Scott

unread,
Aug 12, 2013, 12:48:03 PM8/12/13
to browserm...@googlegroups.com
I found the following link helpful:


I didn't even need to clear the whole temp directory. Inside of /tmp/ I had these two files:
userAgentString.properties 
userAgentString.txt

Once I removed those, I was able to startup again.
Reply all
Reply to author
Forward
0 new messages