You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Harroot <ha...@gmail.com> on 2009/01/16 17:22:20 UTC

maven jetty problem

Hi all
I am using maven 2.0.9, when i try to execute any command of maven(mvn, mvn
-Prun, mvn package) i got this message {Listening for transport dt_socket at
address: 4000} and nothing else. Firstly i think that jetty is running yet,
but it is not. And now I can't run eny maven command.

What can I do, to fix this proble.

Regards Harroot.
-- 
View this message in context: http://www.nabble.com/maven-jetty-problem-tp21502964p21502964.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: maven jetty problem

Posted by Harroot <ha...@gmail.com>.
Hi Ralf,

Thank's for your reply:), before your mail I remember that I was debuging
shindig via eclipse end set MAVEN_OPTS to listen 4000 port, so I fix that
problem, enyway thank's for your answer:)

Best regards 
Harroot. 

Ralf Fischer-2 wrote:
> 
> Hi Harroot,
> 
> Am 16.01.2009 um 17:22 schrieb Harroot:
>> Hi all
>> I am using maven 2.0.9, when i try to execute any command of  
>> maven(mvn, mvn
>> -Prun, mvn package) i got this message {Listening for transport  
>> dt_socket at
>> address: 4000} and nothing else. Firstly i think that jetty is  
>> running yet,
>> but it is not. And now I can't run eny maven command.
>>
>> What can I do, to fix this proble.
> 
> IMO this is a little OT, but anyway...
> 
> I'm no expert in maven but this sounds pretty much like a plain java  
> problem. My guess would be you have either modified your maven start  
> script or have set an environment variable which is used by the  
> scripts' call of the JVM, like $MAVEN_OPTS in my version. By any  
> chance, did you ever debug a JVM remotely via port 4000?
> 
> This message is usually produced by the JVM when it's configured to  
> wait with the execution of the entry point (main(String[]...) for a  
> remote debugger to connect.
> 
> Cheers,
> -Ralf
> 
>> Regards Harroot.
>> -- 
>> View this message in context:
>> http://www.nabble.com/maven-jetty-problem-tp21502964p21502964.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/maven-jetty-problem-tp21502964p21513554.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: maven jetty problem

Posted by Ralf Fischer <th...@googlemail.com>.
Hi Harroot,

Am 16.01.2009 um 17:22 schrieb Harroot:
> Hi all
> I am using maven 2.0.9, when i try to execute any command of  
> maven(mvn, mvn
> -Prun, mvn package) i got this message {Listening for transport  
> dt_socket at
> address: 4000} and nothing else. Firstly i think that jetty is  
> running yet,
> but it is not. And now I can't run eny maven command.
>
> What can I do, to fix this proble.

IMO this is a little OT, but anyway...

I'm no expert in maven but this sounds pretty much like a plain java  
problem. My guess would be you have either modified your maven start  
script or have set an environment variable which is used by the  
scripts' call of the JVM, like $MAVEN_OPTS in my version. By any  
chance, did you ever debug a JVM remotely via port 4000?

This message is usually produced by the JVM when it's configured to  
wait with the execution of the entry point (main(String[]...) for a  
remote debugger to connect.

Cheers,
-Ralf

> Regards Harroot.
> -- 
> View this message in context: http://www.nabble.com/maven-jetty-problem-tp21502964p21502964.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org