- This topic has 16 replies, 8 voices, and was last updated 16 years, 2 months ago by
.
-
Posts
-
I installed Glassfish V2.1, and am able to start it via the command line using asadmin. I configured the MyEclipse connector, so that it looks like:
https://www.genuitec.com/forums/topic/glassfish-2-what-does-a-configured-connector-look-like/
I configured it to use the same jdk6 as I have set in JAVA_HOME.When I try to start the glassfish server via MyEclipse, I get the error:
recursive call into SystemOutandErrhandler java.lang.RuntimeException: recursivecall at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:359) at java.io.PrintStream.write(PrintStream.java:432) at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.write(SystemOutandErrHandler.java:293) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:263) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:106) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) at java.io.Writer.write(Writer.java:140) at java.util.logging.StreamHandler.publish(StreamHandler.java:192) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88) at java.util.logging.Logger.log(Logger.java:472) at java.util.logging.Logger.doLog(Logger.java:494) at java.util.logging.Logger.log(Logger.java:517) at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:368) at java.io.PrintStream.write(PrintStream.java:432) at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.write(SystemOutandErrHandler.java:293) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272) at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212) at java.util.logging.StreamHandler.flush(StreamHandler.java:225) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:89) at java.util.logging.Logger.log(Logger.java:472) at java.util.logging.Logger.doLog(Logger.java:494) at java.util.logging.Logger.log(Logger.java:558) at com.sun.enterprise.server.ApplicationServer.printStartupInfo(ApplicationServer.java:618) at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:170) at com.sun.enterprise.server.ondemand.OnDemandServer.onInitialization(OnDemandServer.java:103) at com.sun.enterprise.server.PEMain.run(PEMain.java:399) at com.sun.enterprise.server.PEMain.main(PEMain.java:336) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.enterprise.server.PELaunch.main(PELaunch.java:415)Does the MyEclipse connector work with Glassvish V2.1? Should I be using 2.0 instead?
This is the first time I have seen this error being reported on the forums. You should be able to run Glassfish V2.1 with MyEclipse. Have you tried cross posting this question on the GlassFish forums as well?
Does 2.0 work for you without issues ?
Yes, I tried 2.0, and it works fine; I strongly suspect it’s a problem with the MyEclipse connector, given that 2.1 works fine from the command line.
I’ll just keep using 2.0, as there is nothing in 2.1 that I need right now. But it’s probably something the MyEclipse team should have a look at.
Brian
I have a similar problem:
recursive call into SystemOutandErrhandler
java.lang.RuntimeException: recursivecallI use MyEclipse 7.0.1 or MyEclipse 6.0.1 and GlassFish 2.1 or SailFin 1.0
I can start the server via command line using asadmin.bat
But I received the RuntimeException when I try to start the server via MyEclipse(connector configured correctly and I use JDK 1.5.0_09, not JRE, like command line mode)
I’m having exactly the same problem using MyEclipse 7.0 and GlassFish 2.1.
But the problem seems to affect log output, not server start: server works fine, it just doesn’t log anything to my console apart from the above error message?!I also tried using
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
as optional Java VM argument, resulting in no log output at all, not even the error message above?!
Hi,
Im sorry you ran into this issue. I have already filed a PR for the dev team and they are looking into this issue.themanbenstout,
Inconvinience caused is sincerely regretted. Dev team are investigating this issue. I don’t have a workaround for this right now, you can try to deploy your application on GlassFish 2.0 or directly through the GlassFish 2.1 admin console. Can you please check if you are able to run your application even though the error console displays the error “recursive call into SystemOutandErrhandler …..”?
support-joy,
yes, GlassFish 2.1 server and deployed applications work fine. Console just doesn’t log anything apart from the above server startup error message “recursive call into SystemOutandErrhandler …..”.
appreciate any news on this, thanks.
Hey rubberxduck,
Thank you for the info. I will have to push this to the dev team. I don’t have any workaround on this right now, sorry for the inconvinience caused.
@support-joy wrote:
Hey rubberxduck,
Thank you for the info. I will have to push this to the dev team. I donDo we have the solution
Sekhar
All,
A PR is filed for the dev team and they are currently investigating this issue. Sorry for the inconvinience caused.
Got the same error with Sailfin (based on glassfish 2.1) so it it pretty consistent error here.
To test just download the sailfin : https://sailfin.dev.java.net/downloads/
select the beta 08 (the one including glashfish 2.1)follow the simple startup guide ( an ant config installer)
add the server using MyEclipse glassfish preference
add a new eb project and deploy it
see it run well on glashfish alone (deployment made using MyEclipse)then the fun part, try to start a debug (or just click start) the server
and you get this same infamous stack trace !!! :recursive call into SystemOutandErrhandler
java.lang.RuntimeException: recursivecall
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:359)
at java.io.PrintStream.write(PrintStream.java:414)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.write(SystemOutandErrHandler.java:293)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136)
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146)
at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
at java.io.Writer.write(Writer.java:126)
at java.util.logging.StreamHandler.publish(StreamHandler.java:192)
at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88)
at java.util.logging.Logger.log(Logger.java:452)
at java.util.logging.Logger.doLog(Logger.java:474)
at java.util.logging.Logger.log(Logger.java:497)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:368)
at java.io.PrintStream.write(PrintStream.java:414)
at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingPrintStream.write(SystemOutandErrHandler.java:293)
at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)
at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)
at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
at java.util.logging.StreamHandler.flush(StreamHandler.java:225)
at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:89)
at java.util.logging.Logger.log(Logger.java:452)
at java.util.logging.Logger.doLog(Logger.java:474)
at java.util.logging.Logger.log(Logger.java:538)
at com.sun.enterprise.server.ApplicationServer.printStartupInfo(ApplicationServer.java:618)
at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:170)
at com.sun.enterprise.server.ondemand.OnDemandServer.onInitialization(OnDemandServer.java:103)
at com.sun.enterprise.server.PEMain.run(PEMain.java:399)
at com.sun.enterprise.server.PEMain.main(PEMain.java:336)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:415)vincent.nonnenmacher,
I have replied to your post here https://www.genuitec.com/forums/topic/glassfish-run-server-got-exception/#post-297227 Let me also clarify that MyEclipse doesn’t provide and integrated support for Sailfin. Listed here are the features supported by MyEclipse – http://www.myeclipseide.com/module-htmlpages-display-pid-1.html. GlassFish 2.1 issue is fixed and will be released as part of ME 7.5.
