Removing Standard Output Messages from Console Window - coded-ui-tests

I'm using vstest to execute tests on local.
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe\" "C:\Debug\Solution.dll /Tests:VerifyTest1,VerifyTest2 /Logger:trx"
And over console i receive output something like this -
Passed VerifyTest1
Failed VerifyTest2
Standard Output Messages:
TestContext Messages:
1/29/2016 21:50:00 - START - START : [VerifyTest2]
1/29/2016 21:50:00 - INFO - Operating System - Microsoft Windows 10 Enterprise
1/29/2016 21:50:00 - INFO - Test Environment - Test1
1/29/2016 21:50:00 - INFO - Test Environment - Test1
1/29/2016 21:50:00 - INFO - File updated
1/29/2016 21:50:02 - INFO - Login Complete! via UI API's
1/29/2016 21:50:03 - INFO - eb481527-49f6-49bc-a9ca-9ccf4e10d12a submitted successfully.
1/29/2016 21:50:11 - PASS - Return created through UI
1/29/2016 21:50:11 - INFO - Checking Process launched or NOT
1/29/2016 21:50:11 - INFO - Process: My.CommonUIFramework.Shell is launched
1/29/2016 21:50:11 - INFO - Terminating the Process: My.CommonUIFramework.Shell
1/29/2016 21:50:11 - INFO - Checking Process launched or NOT
1/29/2016 21:50:11 - INFO - Process: My.Xion.DataMigration.UI is NOT launched
1/29/2016 21:50:12 - INFO - Launched the Application : My.CommonUIFramework.Shell
1/29/2016 21:50:12 - INFO - Checking Process launched or NOT
Now, i don't want the debug trace with all the info when a test fails on Console. I just want passed or failed result on Console. Is there a way to do that. I know that i can see the result on trx file but i just wanted to know is there a way to suppress the debug trace or Standard Output Messages on Console.

You May Want to Disable your trace Logs. You can do it thru multiple channels. Try as mentioned in here based on ur VSTS & .Net version. https://msdn.microsoft.com/en-us/library/jj159363(v=vs.120).aspx
0 is the setting for disabling traces.

Using MSTest instead of VSTest solved the purpose of my problem.

Related

Experiencing difficulties running a gatsby project on yarn

I am trying to help a friend with its gatsby template, each time I tried to run the gatsby project, I get several errors.
C:\Users\Thosyn Pax\Desktop\Project\Sarvesh\Sarvesh\Superprops\Superprops>yarn gatsby-dev
yarn run v1.22.4
$ yarn workspace gatsby-landing run dev
$ gatsby develop
success open and validate gatsby-configs - 0.474s
success load plugins - 99.856s
success onPreInit - 0.400s
success initialize cache - 0.175s
success copy gatsby files - 1.584s
success onPreBootstrap - 3.519s
success createSchemaCustomization - 0.129s
success source and transform nodes - 16.371s
success building schema - 13.086s
success createPages - 0.022s
success createPagesStatefully - 2.229s
success onPreExtractQueries - 0.010s
success update schema - 0.379s
success extract queries from components - 39.358s
success write out requires - 0.879s
success write out redirect data - 0.019s
warn The icon(src/images/favicon.png) you provided to 'gatsby-plugin-manifest' is not
square.
The icons we generate will be square and for the best results we recommend you
success Build manifest and related icons - 2.713s
success onPostBootstrap - 2.757s
⠀
info bootstrap finished - 266.442s
⠀
ERROR
Processing C:/Users/Thosyn Pax/Desktop/Project/Sarvesh/Sarvesh/Superprops/Superprops/packages/common/src/assets/image/agency/blog/blog-img1.png failed
Original error:
WorkerError: Processing C:/Users/Thosyn Pax/Desktop/Project/Sarvesh/Sarvesh/Superpr ops/Superprops/packages/common/src/assets/image/agency/blog/blog-img1.png failed
Original error:
- jobs-manager.js:316 exports.enqueueJob
[Superprops]/[gatsby]/dist/utils/jobs-manager.js:316:23
- runMicrotasks
- task_queues.js:97 processTicksAndRejections
internal/process/task_queues.js:97:5
not finished run queries - 2.861s
not finished Generating image thumbnails - 2.512s
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
Exit code: 1
Command: C:\Program Files\nodejs\node.exe
Arguments: C:\Program Files (x86)\Yarn\lib\cli.js run dev
Directory: C:\Users\Thosyn Pax\Desktop\Project\Sarvesh\Sarvesh\Superprops\Superprops\packages\landing-gatsby
Output:
info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Setting up a Selenium node on Linux

I am currently trying to set up a Selenium node on a Linux VM (headless). The hub is being run from a Windows device on port 5786 (4444 was in use).
I initiate the hub using the following code:
java -jar selenium-server-standalone-
2.53.0.jar -role node –hub http://<myIP>:5786/grid/register -port 5558
When i execute this, it returns the following error messages:
13:42:12.765 INFO - Launching a Selenium Grid node
13:42:13.435 WARN - error getting the parameters from the hub. The node may
end up with wrong timeouts.Connect to 10.146.48.80:4444 [/10.146.48.80]
failed: Connection refused
13:42:13.445 INFO - Java: Oracle Corporation 24.60-b09
13:42:13.445 INFO - OS: Linux 3.10.0-514.21.1.el7.x86_64 amd64
13:42:13.450 INFO - v2.53.0, with Core v2.53.0. Built from revision 35ae25b
13:42:13.521 INFO - Driver provider
org.openqa.selenium.ie.InternetExplorerDriver registration is skipped:
registration capabilities Capabilities [{platform=WINDOWS,
ensureCleanSession=true, browserName=internet explorer, version=}] does not
match the current platform LINUX
13:42:13.521 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver
registration is skipped:
registration capabilities Capabilities [{platform=WINDOWS,
browserName=MicrosoftEdge, version=}] does not match the current platform
LINUX
13:42:13.521 INFO - Driver class not found:
com.opera.core.systems.OperaDriver
13:42:13.521 INFO - Driver provider com.opera.core.systems.OperaDriver is not
registered
13:42:13.522 INFO - Driver provider org.openqa.selenium.safari.SafariDriver
registration is skipped:
registration capabilities Capabilities [{platform=MAC, browserName=safari,
version=}] does not match the current platform LINUX
13:42:13.523 INFO - Driver class not found:
org.openqa.selenium.htmlunit.HtmlUnitDriver
13:42:13.523 INFO - Driver provider
org.openqa.selenium.htmlunit.HtmlUnitDriver is not registered
13:42:13.552 INFO - Version Jetty/5.1.x
13:42:13.553 INFO - Started HttpContext[/selenium-server/driver,/selenium-
server/driver]
13:42:13.553 INFO - Started HttpContext[/selenium-server,/selenium-server]
13:42:13.553 INFO - Started HttpContext[/,/]
13:44:03.596 INFO - Started
org.openqa.jetty.jetty.servlet.ServletHandler#188fd321
13:44:03.596 INFO - Started HttpContext[/wd,/wd]
13:44:03.599 INFO - Started SocketListener on 0.0.0.0:5555
13:44:03.599 INFO - Started org.openqa.jetty.jetty.Server#a01330f
13:44:03.599 INFO - Selenium Grid node is up and ready to register to the hub
13:44:03.630 INFO - Starting auto registration thread. Will try to register
every 5000 ms.
13:44:03.630 INFO - Registering the node to the hub:
http://10.146.48.80:4444/grid/register
13:44:03.638 INFO - Couldn't register this node: Error sending the
registration request: Connect to 10.146.48.80:4444 [/10.146.48.80] failed:
Connection refused
In the command that you shared viz.,
java -jar selenium-server-standalone-2.53.0.jar -role node –hub http://<myIP>:5786/grid/register -port 5558
You have a copy paste problem. The - before the parameter hub doesn't seem to be a hyphen character.
I was able to deduce this as a possible root cause because the value of -hub is completely being ignored and the default hub port of 4444 is being attempted to use. The stacktrace that you shared re-iterates this
13:42:13.435 WARN - error getting the parameters from the hub. The node may
end up with wrong timeouts.Connect to 10.146.48.80:4444 [/10.146.48.80]
failed: Connection refused
As you can see, even though you are providing your Hub's registration URL to include a port number of 5786, its still picking up 4444 and complaining Connection refused.
Please try typing out the entire command for starting the hub and try again. That should work.

Intellij Idea 14 on Arch Linux opening to grey screen

I am trying to run Intellij Idea 14 on my Macbook which I have loaded with Arch Linux. I have installed both Idea and the Oracle JDK8 installed from AUR.
When I run idea.sh, the splashscreen shows up and after it finishes loading it opens to this screen.
Here is idea.log:
2015-10-29 17:02:33,298 [ 0] INFO - #com.intellij.idea.Main - ------------------------------------------------------ IDE STARTED ------------------------------------------------------
2015-10-29 17:02:33,312 [ 14] INFO - #com.intellij.idea.Main - IDE: IntelliJ IDEA (build #IC-141.2735.5, 22 Sep 2015 00:00)
2015-10-29 17:02:33,312 [ 14] INFO - #com.intellij.idea.Main - OS: Linux (4.2.3-1-arch, amd64)
2015-10-29 17:02:33,312 [ 14] INFO - #com.intellij.idea.Main - JRE: 1.8.0_66-b17 (Oracle Corporation)
2015-10-29 17:02:33,312 [ 14] INFO - #com.intellij.idea.Main - JVM: 25.66-b17 (Java HotSpot(TM) 64-Bit Server VM)
2015-10-29 17:02:33,314 [ 16] INFO - #com.intellij.idea.Main - JVM Args: -Xbootclasspath/a:./../lib/boot.jar -Xms128m -Xmx750m -XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=225m -XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 -ea -Dsun.io.useCanonCaches=false -Djava.net.preferIPv4Stack=true -Dawt.useSystemAAFontSettings=on -Djb.vmOptionsFile=./idea64.vmoptions -XX:ErrorFile=/home/noah/java_error_in_IDEA_%p.log -Djb.restart.code=88 -Didea.paths.selector=IdeaIC14 -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel
2015-10-29 17:02:33,341 [ 43] INFO - #com.intellij.idea.Main - JNA library loaded (64-bit) in 27 ms
2015-10-29 17:02:33,424 [ 126] INFO - .intellij.idea.IdeaApplication - WM detected: bspwm
2015-10-29 17:02:34,174 [ 876] INFO - llij.ide.plugins.PluginManager - 29 plugins initialized in 612 ms
2015-10-29 17:02:34,174 [ 876] INFO - llij.ide.plugins.PluginManager - Loaded bundled plugins: Android Support (10.1.1.0), Ant Support (1.0), Bytecode Viewer (0.1), CVS Integration (11), Copyright (8.1), Coverage, Eclipse Integration (3.0), EditorConfig (1.0), Git Integration (8.1), GitHub, Gradle, Groovy (9.0), I18n for Java, IDEA CORE, IntelliLang (8.0), JUnit (1.0), Java Bytecode Decompiler (0.1), JavaFX (1.0), Maven Integration, Plugin DevKit (1.0), Properties Support, Subversion Integration (1.1), Task Management (1.0), Terminal (0.1), TestNG-J (8.0), UI Designer, XPathView + XSLT Support (4), XSLT-Debugger (1.4), hg4idea (10.0)
2015-10-29 17:02:34,790 [ 1492] INFO - ellij.util.io.PagedFileStorage - lower=100; upper=200; buffer=10; max=739246080
2015-10-29 17:02:34,814 [ 1516] INFO - api.vfs.impl.local.FileWatcher - Starting file watcher: /usr/share/intellijidea-ce/bin/fsnotifier64
2015-10-29 17:02:34,822 [ 1524] INFO - api.vfs.impl.local.FileWatcher - Native file watcher is operational.
2015-10-29 17:02:35,539 [ 2241] INFO - lij.diagnostic.DebugLogManager - Set DEBUG for the following categories: []
2015-10-29 17:02:35,977 [ 2679] INFO - rains.ide.BuiltInServerManager - built-in server started, port 63342
2015-10-29 17:02:36,557 [ 3259] INFO - TestNG Runner - Create TestNG Template Configuration
2015-10-29 17:02:36,622 [ 3324] INFO - ellij.project.impl.ProjectImpl - 20 project components initialized in 409 ms
2015-10-29 17:02:36,622 [ 3324] INFO - le.impl.ModuleManagerComponent - 0 module(s) loaded in 0 ms
2015-10-29 17:02:36,865 [ 3567] INFO - pl.stores.ApplicationStoreImpl - 83 application components initialized in 2621 ms
2015-10-29 17:02:36,870 [ 3572] INFO - .intellij.idea.IdeaApplication - App initialization took 4204 ms
2015-10-29 17:06:05,892 [ 212594] INFO - org.jetbrains.io.BuiltInServer - web server stopped
2015-10-29 17:06:05,893 [ 212595] INFO - Types.impl.FileTypeManagerImpl - FileTypeManager: 0 auto-detected files
Elapsed time on auto-detect: 0 ms
2015-10-29 17:06:05,907 [ 212609] INFO - dea.ddms.adb.AdbService$Ddmlib - DDMLib terminated
2015-10-29 17:06:05,907 [ 212609] INFO - il.indexing.FileBasedIndexImpl - START INDEX SHUTDOWN
2015-10-29 17:06:05,927 [ 212629] INFO - il.indexing.FileBasedIndexImpl - END INDEX SHUTDOWN
2015-10-29 17:06:05,927 [ 212629] INFO - stubs.SerializationManagerImpl - START StubSerializationManager SHUTDOWN
2015-10-29 17:06:05,927 [ 212629] INFO - stubs.SerializationManagerImpl - END StubSerializationManager SHUTDOWN
2015-10-29 17:06:06,002 [ 212704] WARN - api.vfs.impl.local.FileWatcher - Watcher terminated with exit code 0
2015-10-29 17:06:06,003 [ 212705] INFO - newvfs.persistent.PersistentFS - VFS dispose started
2015-10-29 17:06:06,003 [ 212705] INFO - newvfs.persistent.PersistentFS - VFS dispose completed
2015-10-29 17:06:06,007 [ 212709] INFO - #com.intellij.idea.Main - ------------------------------------------------------ IDE SHUTDOWN ------------------------------------------------------
Any help would be greatly appreciated.
This is most likely due to your window manager, bspwm. If you set the following environment variable before starting IntelliJ, it should work.
_JAVA_AWT_WM_NONREPARENTING=1
As #thomas pointed out, the missing environment variable is causing this issue
Here're the steps to do that.
Copy this -> _JAVA_AWT_WM_NONREPARENTING=1
If you have nano installed:
Run sudo nano /etc/environment on terminal and enter the password if prompted
Scroll to the bottom
Paste by pressing Shift + Insert
Save by pressing Ctrl + O and confirm the path with Enter
Quit by pressing Ctrl + X
If you have vim installed:
Run sudo vim /etc/environment on terminal and enter the password if prompted
Scroll to the bottom
Enter insert mode by pressing i
Paste by pressing Shift + Insert
Exit the insert mode by pressing Esc
Save and exit by typing :wq and Enter
The error should be resolved. This is apparently documented along with Android Studio on the wiki

Selenium test execution via jenkins on linux machine without GUI (CLI-only) - HEADLESS MODE

This is regarding Selenium Automation Testing. I have a Jenkins job setup for some test executions.Jenkins is setup on a Ubuntu machine without GUI (CLI Only).
So when I run the scripts seems like it can't find the web browser obviously.
This job is working perfectly fine in windows. In Windows I get like this result.
Window Successful Result
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
06/08/2015 00:04:47,996 INFO [main] (BasicTestObject.java:251) - ======BEGIN Test workflow============
06/08/2015 00:04:48,002 INFO [main] (BasicTestObject.java:252) - BEGIN Test: MlpBvt
06/08/2015 00:04:48,002 INFO [main] (BasicTestObject.java:253) - ======BEGIN Test workflow============
06/08/2015 00:04:58,862 DEBUG [main] (DefaultUIDriver.java:300) - Opened url: http://mlpdemo.qaprod.ecollege.com/
06/08/2015 00:04:58,912 INFO [main] (BasicTestObject.java:296) - -------------BEGIN Test Method-------------------
06/08/2015 00:04:58,913 INFO [main] (BasicTestObject.java:297) - BEGIN Test Method: verifyAdminLogin
06/08/2015 00:04:58,913 INFO [main] (BasicTestObject.java:298) - -------------BEGIN Test Method-------------------
06/08/2015 00:04:58,969 DEBUG [main] (DefaultUIElement.java:980) - Waiting 60000ms for element to be displayed [Locator = {By.xpath: //input[#id='clientname']}]
06/08/2015 00:04:59,058 DEBUG [main] (DefaultUIElement.java:538) - Element is displayed [Locator = {By.xpath: //input[#id='clientname']}]
06/08/2015 00:04:59,059 DEBUG [main] (DefaultUIElement.java:992) - After 89ms, element is displayed [Locator = {By.xpath: //input[#id='clientname']}]
On Linux I get like this
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
06/08/2015 00:18:46,834 INFO [main] (BasicTestObject.java:251) - ======BEGIN Test workflow============
06/08/2015 00:18:46,839 INFO [main] (BasicTestObject.java:252) - BEGIN Test: MlpBvt
06/08/2015 00:18:46,839 INFO [main] (BasicTestObject.java:253) - ======BEGIN Test workflow============
06/08/2015 00:18:46,998 DEBUG [main] (CapturePageOnFailureListener.java:186) - CapturePageOnFailure found 2 parameters
06/08/2015 00:18:47,002 WARN [main] (DebugUIDriver.java:311) - Called quit() on debugDriver containing null uiDriver
06/08/2015 00:18:47,025 INFO [main] (BasicTestObject.java:304) - -------------END Test Method-------------------
06/08/2015 00:18:47,026 INFO [main] (BasicTestObject.java:305) - END Test Method: verifyAdminLogin
06/08/2015 00:18:47,026 INFO [main] (BasicTestObject.java:306) - -------------END Test Method-------------------
06/08/2015 00:18:47,031 INFO [main] (BasicTestObject.java:304) - -------------END Test Method-------------------
06/08/2015 00:18:47,032 INFO [main] (BasicTestObject.java:305) - END Test Method: VerifyProfessorLogin
06/08/2015 00:18:47,032 INFO [main] (BasicTestObject.java:306) - -------------END Test Method-------------------
06/08/2015 00:18:47,036 INFO [main] (BasicTestObject.java:304) - -------------END Test Method-------------------
06/08/2015 00:18:47,036 INFO [main] (BasicTestObject.java:305) - END Test Method: VerifyStudentLogin
06/08/2015 00:18:47,037 INFO [main] (BasicTestObject.java:306) - -------------END Test Method-------------------
06/08/2015 00:18:47,038 INFO [main] (BasicTestObject.java:283) - ======END Test workflow============
06/08/2015 00:18:47,038 INFO [main] (BasicTestObject.java:284) - END Test: MlpBvt
06/08/2015 00:18:47,040 INFO [main] (BasicTestObject.java:285) - ======END Test workflow============
06/08/2015 00:18:47,100 DEBUG [main] (ProcessTool.java:36) - Getting current tool for LINUX
06/08/2015 00:18:47,100 WARN [main] (ProcessTool.java:40) - Could not find ProcessTool for LINUX
06/08/2015 00:18:47,101 WARN [main] (ProcessTool.java:88) - There was no ProcessTool for LINUX
06/08/2015 00:18:47,101 DEBUG [main] (ProcessTool.java:115) - process count for There was no ProcessTool for LINUX:1
Tests run: 12, Failures: 1, Errors: 0, Skipped: 11, Time elapsed: 1.976 sec <<< FAILURE!
Results :
Failed tests:
It is mentioned as
06/08/2015 00:18:47,002 WARN [main] (DebugUIDriver.java:311) - Called quit() on debugDriver containing null uiDriver
Please provide me some technical specialities regarding this matter. Can I run this job in linux ? Please help me out
Well for unix systems you have to use Xvfb to run tests in headless mode, for jenkins you can use xvfb plugin
Simple example how to open firefox in headless mode
from xvfbwrapper import Xvfb
from selenium import webdriver
xf = Xvfb() # xf = Xvfb(1920, 1080) - will create virtual display with 1920x1080 size
xf.start()
# browser won't appear
driver = webdriver.Firefox()
driver.get("http://google.com")

Rexster refuses to start with extension but does not display errors

I have a small Rexster/Titan cluster using Cassandra. A Rexster extension is used to query the graph. I did some benchmarking and did start and stop Rexster/Titan many times. But now I run into a strange issue: Rexster refuses to start but does not display any error message.
I tried to figure out what is causing this and reduced the cluster to a single node 192.168.0.4.
If I remove my extension Rexster manages to start up.
# console output
Forking Cassandra...
Running `nodetool statusthrift`..... OK
(returned exit status 0 and printed string "running").
Forking Titan + Rexster...
Connecting to Titan + Rexster (127.0.0.1:8184)...... OK
(connected to 127.0.0.1:8184).
Run rexster-console.sh to connect.
but when I place my extension uber JAR in the ext folder Rexster refuses to start.
# console output
Forking Cassandra...
Running `nodetool statusthrift`..... OK
(returned exit status 0 and printed string "running").
Forking Titan + Rexster...
Connecting to Titan + Rexster (127.0.0.1:8184)............................
timeout exceeded (60 seconds): could not connect to 127.0.0.1:8184
See /var/lib/titan/bin/../log/rexstitan.log for Rexster log output.
If I now check rexstitan.log, as suggested by the console output, I can not find any error message.
# rexstitan.log
0 [main] INFO com.tinkerpop.rexster.Application - .:Welcome to Rexster:.
73 [main] INFO com.tinkerpop.rexster.server.RexsterProperties -
Using [/var/lib/titan/rexhome/../conf/rexster-cassandra-cluster.xml]
as configuration source.
78 [main] INFO com.tinkerpop.rexster.Application - Rexster is watching
[/var/lib/titan/rexhome/../conf/rexster-cassandra-cluster.xml] for change.
244 [main] INFO com.netflix.astyanax.connectionpool.impl.ConnectionPoolMBeanManager -
Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,
name=ClusterTitanConnectionPool,ServiceType=connectionpool
252 [main] INFO com.netflix.astyanax.connectionpool.impl.CountingConnectionPoolMonitor -
AddHost: 192.168.0.4
537 [main] INFO com.netflix.astyanax.connectionpool.impl.ConnectionPoolMBeanManager -
Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,
name=KeyspaceTitanConnectionPool,ServiceType=connectionpool
538 [main] INFO com.netflix.astyanax.connectionpool.impl.CountingConnectionPoolMonitor -
AddHost: 192.168.0.4
1951 [main] INFO com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration -
Set cluster.partition=false from store features
1971 [main] INFO com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration -
Set default timestamp provider MICRO
2019 [main] INFO com.thinkaurelius.titan.graphdb.configuration.GraphDatabaseConfiguration -
Generated unique-instance-id=7f0000012902-node1
2045 [main] INFO com.netflix.astyanax.connectionpool.impl.ConnectionPoolMBeanManager -
Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,
name=ClusterTitanConnectionPool,ServiceType=connectionpool
2046 [main] INFO com.netflix.astyanax.connectionpool.impl.CountingConnectionPoolMonitor -
AddHost: 192.168.0.4
2053 [main] INFO com.netflix.astyanax.connectionpool.impl.ConnectionPoolMBeanManager -
Registering mbean: com.netflix.MonitoredResources:type=ASTYANAX,
name=KeyspaceTitanConnectionPool,ServiceType=connectionpool
2054 [main] INFO com.netflix.astyanax.connectionpool.impl.CountingConnectionPoolMonitor -
AddHost: 192.168.0.4
2228 [main] INFO com.thinkaurelius.titan.diskstorage.Backend -
Initiated backend operations thread pool of size 4
6619 [main] INFO com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog -
Loaded unidentified ReadMarker start time Timepoint[1423479705116000 μs]
into com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog$MessagePuller#212f3ff1
6625 [main] INFO com.tinkerpop.rexster.RexsterApplicationGraph -
Graph [graph] - configured with allowable namespace [*:*]
The only entry that looks strange to me is the one concerning the log:
6619 [main] INFO com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog -
Loaded unidentified ReadMarker start time Timepoint[1423479705116000 μs]
into com.thinkaurelius.titan.diskstorage.log.kcvs.KCVSLog$MessagePuller#212f3ff1
My exception uses the logger for debugging. You can see the instantiation an usage on github: https://github.com/sebschlicht/titan-graphity-kribble/blob/master/src/main/java/de/uniko/sebschlicht/titan/extensions/GraphityExtension.java#L22
Though Rexster failed to start there is a process with the PID displayed in the console but curl fails to connect to Rexster:
$ curl 192.168.0.4:8182
curl: (7) Failed to connect to 192.168.0.4 port 8182: Connection refused
Why doesn't Rexster throw an exception? How can I debug this situation?
edit:
I removed any log messages in my code. I removed all exceptions that may be thrown during startup. Still Rexster refuses to start with my extension and the only hint in the log files is the unidentified read marker. I have to clue what prevents Rexster from starting.
The log message is nothing to worry about.
After rebuilding the application in another project step-by-step Rexster is now able to start with the extension. During this rebuild I noticed two situations, that can cause the behaviour described:
Missing dependency
If your project depends on a second project you might use Maven to inject it as a dependency. However, if you use
mvn clean package
to build the extension's JAR file it does not contain this dependency by default. You need to use a Maven plugin (e.g. maven-shade-plugin) to create a shaded JAR that contains all the dependencies your extension needs. Set the dependency scope to provided for all Titan/Rexster/Blueprints related dependencies. Use the shaded uber-JAR to deploy the extension to Rexster.
However, this was not new to me and should not have caused the problem in my case. There might be more situations that cause this problem or maybe there was a problem with Maven that messed up the shaded JAR. Feel free to browse the commit on github to catch this voodoo.
Missing extension
Another cause of this behaviour is a missing extension.
If you specify an extension in the com.tinkerpop.rexster.extension.RexsterExtension resource file, that is not present on startup, Rexster does neither log nor throw an exception, but refuses to start.

Resources