- This topic has 17 replies, 5 voices, and was last updated 19 years, 7 months ago by
.
-
Posts
-
I’m running ME 3.8.4 with SUN Java AS 8.1 platform Ed on Win2K. Whenever I start the app server inside MyEclipse I get all the console log entries repeated 4 times 😕
Starting the app server outside of ME, results in single log entries in the AS log file.
Has anyone seen similar behaviour or have any idea where I might start looking to resolve this?
any help or pointers greatfully accepted.
Colin.
Colin,
This sounds very odd indeed… almost like you have a log configuration file somewhere in your path that the app server is picking up and using? (e.g. multiple console appenders configured or something of that nature).If you download a brand new copy of Sun Java AS and install it somewhere temporarily like C:\Temp\SunAS and run it, does that happen still?
rkalla, thanks for the quick reply. I tried doing a fresh JAS install but I still see the same behaviour. I have closed all ME projects and removed all options from the JAS81 connector config. Now only the first page detailing locations are spec’ed.
I double checked the console output and found the following error on JAS startup. After the error, the log entries start being repeated. I searched for this error and found another similar one on the ME forums. That was resolved after he set the JAS server name correctly. I have checked this and it is set to the virtual server name (‘server’) being used by the JAS domain.
I am not deploying any applications to this JAS instance, it is out-of-box from the clean install.
I’ve checked the win process list and cannot see any JAS releated processes or services running after it has been shutdown.
Any clues ?
thanks, Colin
Top of console log output:
====================Mar 22, 2005 9:06:58 AM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\temp\Sun\AppServer\imq\bin]. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Mar 22, 2005 9:06:58 AM com.sun.enterprise.jms.JmsProviderLifecycle checkProvider recursive call into SystemOutandErrhandler java.lang.RuntimeException: recursivecall at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189) at java.io.PrintStream.write(PrintStream.java:260) 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:191) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:87) at java.util.logging.Logger.log(Logger.java:424) at java.util.logging.Logger.doLog(Logger.java:446) at java.util.logging.Logger.log(Logger.java:469) at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198) at java.io.PrintStream.write(PrintStream.java:260) 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:224) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88) at java.util.logging.Logger.log(Logger.java:424) at java.util.logging.Logger.doLog(Logger.java:446) at java.util.logging.Logger.log(Logger.java:510) at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:433) at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54) at com.sun.enterprise.server.PEMain.run(PEMain.java:274) at com.sun.enterprise.server.PEMain.main(PEMain.java:220) Mar 22, 2005 9:06:58 AM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\temp\Sun\AppServer\imq\bin]. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Mar 22, 2005 9:06:58 AM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\temp\Sun\AppServer\imq\bin]. Mar 22, 2005 9:06:58 AM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\temp\Sun\AppServer\imq\bin]. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Mar 22, 2005 9:06:58 AM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\temp\Sun\AppServer\imq\bin]. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices INFO: CORE5098: AS Socket Service Initialization has been completed. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Mar 22, 2005 9:06:58 AM com.sun.e Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices INFO: CORE5098: AS Socket Service Initialization has been completed. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices INFO: CORE5098: AS Socket Service Initialization has been completed. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices INFO: CORE5098: AS Socket Service Initialization has been completed. Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: Mar 22, 2005 9:06:58 AM com.sun.enterprise.server.ss.ASLazyKernel startASSocketServices INFO: CORE5098: AS Socket Service Initialization has been completed. ..snip..– System Setup ——————————-
Operating System and version:
Eclipse version: 3.0.1
Eclipse build id: 200409161125
Fresh Eclipse install (n):
If not, was it upgraded to its current version using the update manager? Yes
Other installed external plugins: None
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 14 (7 for 3.0.0 / 7 for 3.0.1)
MyEclipse version: 3.8.4 Build id: 200501171200-3.8.4
Eclipse JDK version: j2re1.4.2_06
Application Server JDK version: j2sdk1.4.2_06
Are there any exceptions in the Eclipse log file? noSun Java System Application Server Platform Edition 8.1 (build b41-fcs)
This is from the sjsas_pe-8_1_2005Q1-windows release.Hmm, it seems you aer not the only one with this issue:
http://forum.java.sun.com/thread.jspa?threadID=530249&tstart=225
http://swforum.sun.com/jive/thread.jspa?threadID=24623&messageID=62479 (Using Java Studio Creator)Does this happen with the 8.0 release? I wonder if something broken in the most recent release… also you could try a different JDK (1.4.2_07 or 1.5.0_02) just incase… sometimes it is the smallest thing…
Hi RKalla, I had a look at the other posts and it looks like they are both running on AS 8.0. I tried 1.4.2_07 and no change. I also tracked down the JMS log file (IMQ broker) to check for errors but could find no difference to the log output when I start AS8.1 inside or outside of ME.
I’ll give 1.5.x a go and also try to find a way to disable the JMS lifecycle module – this seems to be the one that tries to do the logging that cuases the recursive call.
Any other ideas ?
cheers, Colin
Colin those sound like good starts, honestly at this point you know more about AS than I do, so I don’t have any other suggestions.
Try reading the links provided, it is not an uncommen problem and seems to be occuring with users using AS as standalone.
Well, I read the links above. A.S 8.1 starts and works perfect through command-line, but doesn’t in MyEclipse. Also in the links above there hasn’t been any additions posts in resolving this issue since last year…Scary.
I continue to get this.
May 26, 2005 3:15:24 PM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/usr/local/sunapp/imq/bin]. May 26, 2005 3:15:24 PM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: May 26, 2005 3:15:24 PM com.sun.enterprise.jms.JmsProviderLifecycle checkPro recursive call into SystemOutandErrhandler java.lang.RuntimeException: recursivecall at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:189) at java.io.PrintStream.write(PrintStream.java:260) 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:191) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:87) at java.util.logging.Logger.log(Logger.java:424) at java.util.logging.Logger.doLog(Logger.java:446) at java.util.logging.Logger.log(Logger.java:469) at com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream.flush(SystemOutandErrHandler.java:198) at java.io.PrintStream.write(PrintStream.java:260) 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:224) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88) at java.util.logging.Logger.log(Logger.java:424) at java.util.logging.Logger.doLog(Logger.java:446) at java.util.logging.Logger.log(Logger.java:510) at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:433) at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54) at com.sun.enterprise.server.PEMain.run(PEMain.java:274) at com.sun.enterprise.server.PEMain.main(PEMain.java:220) May 26, 2005 3:15:24 PM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/usr/local/sunapp/imq/bin]. May 26, 2005 3:15:24 PM com.sun.enterprise.server.logging.SystemOutandErrHandler$LoggingByteArrayOutputStream flush WARNING: May 26, 2005 3:15:24 PM com.sun.enterprise.jms.JmsProviderLifecycle checkProviderStartup INFO: JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/usr/local/sunapp/imq/bin].The server starts through MyEclipse but doesn’t load any of my Realm classes for my app, However the asadmin pages work fine and I can deploy the hello.war samples etc. Again all my code and Realm stuff works fine in command-line but not when started through MyEclipse. MyEclipse doesn’t seem to pick-up the values used in the domain.xml file. Does MyEclipse build it’s own on execution??
It seems to me that MyEclipse is unable to handle the execution of A.S 8.1. Maybe some classpath or lib is missing in MyEclipses execution of the server. Code compiles fine. I also tried using A.S 8.0 connetor to execute A.S 8.1 and received this.
[#|2005-05-26T15:13:49.170-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Could not start S1AS PE 8 Server : Null or zero length argument|#] [#|2005-05-26T15:13:49.184-0700|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=11;|CORE5071: An error occured during initialization java.lang.IllegalArgumentException: null source at java.util.EventObject.<init>(EventObject.java:34) at javax.management.Notification.<init>(Notification.java:202) at com.sun.enterprise.admin.event.AdminEvent.<init>(AdminEvent.java:102) at com.sun.enterprise.admin.event.ShutdownEvent.<init>(ShutdownEvent.java:32) at com.sun.enterprise.server.PEMain.shutdown(PEMain.java:354) at com.sun.enterprise.server.PEMain$ShutdownThread.run(PEMain.java:510) |#]Console printout differs from the A.S 8.1 connector. Maybe this may help.
Thanks in advance..
Please provide a link to the version of AS you are running (I want to duplicate exactly what you are seeing), I will download and test this problem today and confirm if there is an issue then file it ASAP for us to look into.
Sure.
http://java.sun.com/j2ee/1.4/download.html#sdk
I downloaded Netbeans 4.1 and everything worked great. However, I did pay for MyEclipse and would like to get some use out of it. 🙂 Also, if I run my app in command line I could use the debug attach feature to get some work done. Although I don’t get any of the server printout in the console window which doesn’t help much.
I upgraded my copy of Sun App server 8.1 to the release on the page you gave and got a lot of errors on startup, I think Sun changed something on us (again). I’ll have the devs take a look, sorry about this inconvenience.
Thats great news, thanks for your work looking at this decipher, I got to a dead end and just put up with the problem. I’ve kinda got used to seeing errors in quadruplets 😉
Colin.
