On 3/22/13 12:49 PM, "Chip Childers" <chip.child...@sungard.com> wrote:
> > >After running through the steps, I get this error: > > mvn -Pdeveloper,marvin -Dmarvin.config=setup/dev/advanced.cfg -pl >:cloud-marvin integration-test > ERROR: transport error 202: bind failed: Address already in use > ERROR: JDWP Transport dt_socket failed to initialize, >TRANSPORT_INIT(510) > JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports >initialized [../../../src/share/back/debugInit.c:741] > FATAL ERROR in native method: JDWP No transports initialized, >jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) > [1] 28712 abort (core dumped) mvn -Pdeveloper,marvin >-Dmarvin.config=setup/dev/advanced.cfg -pl > > >I think that running the jetty server from mvn may be problematic, if >steps >afterward are also going to require maven. Is there a config to get >around this? It looks like two java processes are being started up, and each want to bind to the same debug port. Both probably have something like - -Xrunjdwp:transport=dt_socket,address=8787, Perhaps leave it out of MAVEN_OPTS?
