and this is the project that I have tried to debug https://github.com/redhat-developer-demos/microspringboot1/blob/master/pom.xml#L80
if you wait a few minutes, it sometimes works. so, i did demo this live (might have been a different java project, can't remember) at JavaOne but skipped it for JavaDay as it was too unreliable. still unreliable. perhaps something mis-configured in that project and I need to find another one. On Mon, Nov 6, 2017 at 9:20 PM, Burr Sutter <[email protected]> wrote: > made it to hotel room and horrible internet connectivity but trying to > make this work > > even fabric8:deploy now presents the end-user will lots of these messages > > [INFO] F8: > {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container > \"sti-build\" in pod \"microspringboot3-s2i-1-build\" is waiting to > start: PodInitializing","reason":"BadRequest","code":400} > > [INFO] Current reconnect backoff is 1000 milliseconds (T0) > > [INFO] Current reconnect backoff is 2000 milliseconds (T1) > > [INFO] Current reconnect backoff is 4000 milliseconds (T2) > > [INFO] Current reconnect backoff is 8000 milliseconds (T3) > > [INFO] Current reconnect backoff is 16000 milliseconds (T4) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > [INFO] Current reconnect backoff is 32000 milliseconds (T5) > > On Mon, Nov 6, 2017 at 2:52 PM, Pradeepto Bhattacharya < > [email protected]> wrote: > >> + Hrishikesh >> >> On Mon, Nov 6, 2017 at 3:19 PM, Burr Sutter <[email protected]> wrote: >> >>> Currently running through airports. Will check again tonight. >>> >>> Could it be “memory”? My 6G minishift VM is running the 3.7rc and lots >>> of JVMs, at least 10. >>> >>> free -m says that there is some memory available but I have notice that >>> deployments hang in general until I delete some previous projects. >>> >>> I think fabric:debug is starting a new pod which taking a long time. >>> >>> On Mon, Nov 6, 2017 at 10:54 AM James Strachan <[email protected]> >>> wrote: >>> >>>> any clues as to what's not working? Its pretty hard to diagnose "not >>>> working" >>>> >>>> Does the command listen on the debug port? Does the pod have the >>>> JAVA_ENABLE_DEBUG env var enabled? I've seen DeploymentConfig's be >>>> changed and that change never actually do anything on OpenShift - I wonder >>>> if you just need to manually click "Deploy" on the DeploymentConfig? >>>> >>>> On Sun, Nov 5, 2017 at 8:45 AM, Burr Sutter <[email protected]> wrote: >>>> >>>>> I believe the Fabric8:debug is broken. >>>>> >>>>> It could be that my cluster is under too much strain but the debug has >>>>> been taking several minutes and I had to just give up. >>>>> >>>>> Has anyone else had recent success with fabric8:debug? >>>>> >>>>> _______________________________________________ >>>>> Devtools mailing list >>>>> [email protected] >>>>> https://www.redhat.com/mailman/listinfo/devtools >>>>> >>>>> >>>> >>>> >>>> -- >>>> James >>>> ------- >>>> Red Hat >>>> >>>> Twitter: @jstrachan >>>> Email: [email protected] >>>> Blog: https://medium.com/@jstrachan/ >>>> >>>> fabric8: https://fabric8.io/ >>>> open source development platform >>>> >>> >>> _______________________________________________ >>> Devtools mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/devtools >>> >>> >> >> >> -- >> Pradeepto Bhattacharya >> >> >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
