cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Punith s <punit...@cloudbyte.com>
Subject Re: Which DevCloud2 Usage Mode is good for Development and Debugging ????
Date Wed, 09 Oct 2013 05:14:05 GMT
it was the /etc/hosts script i had to modify, i had change my ip from dhcp
to static, so had to include my ip in the hosts file.


On Mon, Oct 7, 2013 at 11:25 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:

> Interesting...I see you have another e-mail out on this, as well.
>
> I'd be curious if the recommendation solved your problem.
>
>
> On Mon, Oct 7, 2013 at 1:58 AM, Punith s <punith.s@cloudbyte.com> wrote:
>
> > hi mike ,
> >
> > today i rebuilt the ACS with the new 4.2 official release, but while
> > debugging the CS in eclipse its popping up an error saying ,
> > Failed to connect to remote VM. Connection refused.
> > Connection refused
> >
> >
> > i have shut down the firewall by service iptables stop,
> >
> > also if i do netstat -nap | grep 8787 , the port is shown listening
> > tcp        0      0 127.0.0.1:8787              127.0.0.1:51909
> > ESTABLISHED 14862/java
> >
> > ps -auxx | grep jetty shows that i have exported the following
> > export="-Xmx1024m
> > -XX:MaxPermSize=800m -Xdebug
> > -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
> >
> > ps -auxx | grep jetty
> > root 14862 12.2 6.1 5758204 969372 pts/1 Sl+ 13:01 2:11
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java -Xmx1024m
> > -XX:MaxPermSize=800m -Xdebug
> > -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -classpath
> > /usr/local/apache-maven-3.1.0/boot/plexus-classworlds-2.4.2.jar
> > -Dclassworlds.conf=/usr/local/apache-maven-3.1.0/bin/m2.conf
> > -Dmaven.home=/usr/local/apache-maven-3.1.0
> > org.codehaus.plexus.classworlds.launcher.Launcher -pl :cloud-client-ui
> > jetty:run
> >
> > also # jmap 14862 shows,
> >
> > [root@mycloudstack home]# jmap 14862
> > Attaching to process ID 14862, please wait...
> > Debugger attached successfully.
> > Server compiler detected.
> > JVM version is 23.7-b01
> > 0x0000000000400000 9K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/bin/java
> > 0x000000310fa00000 153K /lib64/ld-2.12.so
> > 0x000000310fe00000 54K
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/jli/libjli.so
> > 0x0000003110200000 1877K /lib64/libc-2.12.so
> > 0x0000003110600000 22K /lib64/libdl-2.12.so
> > 0x0000003110a00000 142K /lib64/libpthread-2.12.so
> > 0x0000003110e00000 88K /lib64/libz.so.1.2.3
> > 0x0000003111200000 45K /lib64/librt-2.12.so
> > 0x0000003112e00000 12K /usr/lib64/libXau.so.6.0.0
> > 0x0000003113200000 121K /usr/lib64/libxcb.so.1.1.0
> > 0x0000003113a00000 1269K /usr/lib64/libX11.so.6.3.0
> > 0x0000003114600000 79K /usr/lib64/libXext.so.6.4.0
> > 0x0000003114e00000 61K /usr/lib64/libXi.so.6.1.0
> > 0x0000003115600000 41K /usr/lib64/libXrender.so.1.3.0
> > 0x000000311ba00000 91K /lib64/libgcc_s-4.4.7-20120601.so.1
> > 0x000000311ca00000 966K /usr/lib64/libstdc++.so.6.0.13
> > 0x0000003126600000 25K /usr/lib64/libXtst.so.6.1.0
> > 0x00007fc0524b9000 347K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/xawt/libmawt.so
> > 0x00007fc052711000 698K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libawt.so
> > 0x00007fc053df8000 31K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libmanagement.so
> > 0x00007fc060c3e000 92K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnet.so
> > 0x00007fc060e55000 68K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnio.so
> > 0x00007fc06166c000 16K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libdt_socket.so
> > 0x00007fc071f94000 31K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libzip.so
> > 0x00007fc07219c000 64K /lib64/libnss_files-2.12.so
> > 0x00007fc0723c0000 12K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libnpt.so
> > 0x00007fc0725c3000 234K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjdwp.so
> > 0x00007fc0727fe000 168K
> > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libjava.so
> > 0x00007fc072a28000 58K
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/libverify.so
> > 0x00007fc072d38000 584K /lib64/libm-2.12.so
> > 0x00007fc072fbc000 10975K
> >
> >
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/lib/amd64/server/libjvm.s
> >
> > any suggestions ?? thanks.
> >
> > regards,
> > punith s
> >
> >
> >
> > On Sun, Sep 15, 2013 at 5:43 PM, Rohit Yadav <bhaisaab@apache.org>
> wrote:
> >
> > > #3 is best and also since devcloud2 was created to provide host-only
> mode
> > > so that it could be used a throw away appliance for a faster CloudStack
> > > development.
> > >
> > > #3: CloudStack will run on your host OS so debugging becomes easier.
> > >
> > > HTH.
> > >
> > >
> > > On Thu, Sep 12, 2013 at 2:49 PM, Punith s <punith.s@cloudbyte.com>
> > wrote:
> > >
> > > > hi folks,
> > > >
> > > > i'm using Devcloud2 to build cloudstack 4.2 , currently i'm using
> *full
> > > > sandbox mode* ,
> > > >
> > > > devcloud allows following modes ,
> > > > *1.full sandbox mode - *build and deploy inside devcloud
> > > > *2.deployment mode - *build code in localhost and deploying in
> devcloud
> > > > *3.host only mode - *using devcloud only as host
> > > >
> > > >
> > > > which mode do you think its feasible for development and  interactive
> > > > debugging ?
> > > > can you elaborate more on setting up remote debugging in Devcloud2
> > > > (fullsandbox mode) using eclipse ??
> > > >
> > > > thanks,
> > > > punith s
> > > >
> > >
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message