|
I have configured VAJ for WCS5.1 as described in the chapter. Everything looks ok but when i try to hit the Display Catalog Page I am getting this error. Can someone help me solve this problem. *** Begin processing file : C:\Websphere\WCS/instances/frnpb/xml/frnpb.xml javax.naming.CommunicationException. Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.lang.RuntimeException(java.lang.String) org.omg.CORBA.SystemException(java.lang.String, int, org.omg.CORBA.CompletionStatus) org.omg.CORBA.COMM_FAILURE(java.lang.String, int, org.omg.CORBA.CompletionStatus) org.omg.CORBA.COMM_FAILURE(int, org.omg.CORBA.CompletionStatus) com.ibm.rmi.iiop.IIOPInputStream com.ibm.CORBA.iiop.HTTPConnection.send(com.ibm.rmi.iiop.IIOPOutputStream, boolean) com.ibm.rmi.iiop.IIOPInputStream com.ibm.CORBA.iiop.ClientRequestImpl.invoke(boolean) com.ibm.rmi.iiop.IIOPInputStream com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(com.ibm.rmi.IOR, int [], com.ibm.rmi.corba.ClientDelegate) com.ibm.rmi.ClientResponse com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(com.ibm.rmi.IOR [], com.ibm.rmi.corba.ClientDelegate) com.ibm.rmi.ClientResponse com.ibm.CORBA.iiop.ClientDelegate.invoke(com.ibm.rmi.ClientRequest) org.omg.CORBA.Object com.ibm.CORBA.iiop.InitialNamingClient.resolve(java.lang.String, java.lang.String, int) org.omg.CORBA.Object com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(java.lang.Str ing) org.omg.CORBA.Object com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_references(java.lang. String) org.omg.CORBA.Object com.ibm.CORBA.iiop.ORB.resolve_initial_references(java.lang.String) org.omg.ExtendedNaming.NamingContext com.ibm.ejs.ns.jndi.CNInitialContextFactory.initRootContext(com.ibm.CORBA.ii op.ORB, java.lang.String, int) javax.naming.Context com.ibm.ejs.ns.jndi.CNInitialContextFactory.getInitialContext(java.util.Hash table) javax.naming.Context javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable) javax.naming.Context javax.naming.InitialContext.getDefaultInitCtx() void javax.naming.InitialContext.init(java.util.Hashtable) javax.naming.InitialContext(java.util.Hashtable) javax.naming.InitialContext com.ibm.ivj.ejb.runtime.AbstractAccessBean.getInitContext(java.lang.String, java.lang.String) java.lang.Object com.ibm.ivj.ejb.runtime.AbstractAccessBean.getGlobalHome(java.lang.String, java.lang.String, java.lang.String) java.lang.Object com.ibm.ivj.ejb.runtime.AbstractAccessBean.getHome() com.ibm.commerce.base.objects.ConfiguratorHome com.ibm.commerce.base.objects.ConfiguratorAccessBean.ejbHome() void com.ibm.commerce.base.objects.ConfiguratorAccessBean.instantiateEJB() void com.ibm.commerce.base.objects.ConfiguratorAccessBean.initialize(com.ibm.comm erce.server.ConfigProperties) void com.ibm.commerce.server.RequestServlet.configInit(java.lang.String) void com.ibm.commerce.server.RequestServlet.servletInit() void com.ibm.commerce.server.RequestServlet.init() void javax.servlet.GenericServlet.init(javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.StrictServletInstance.doInit() void com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(javax.servlet.Ser vletConfig) void com.ibm.servlet.engine.webapp.PreInitializedServletState.init(com.ibm.servle t.engine.webapp.StrictLifecycleServlet, javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(javax.servlet.Serv letConfig) void com.ibm.servlet.engine.webapp.ServletInstance.init() void javax.servlet.GenericServlet.init(javax.servlet.ServletConfig) void com.ibm.servlet.engine.webapp.ServletManager.addServlet(java.lang.String, javax.servlet.Servlet, java.util.Properties) void com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(java.lang.Str ing) com.ibm.servlet.engine.webapp.ServletReference com.ibm.servlet.engine.webapp.WebAppServletManager.getServletReference(java. lang.String, com.ibm.servlet.engine.webapp.ServletReferenceListener) com.ibm.servlet.engine.webapp.ServletReference com.ibm.servlet.engine.webapp.WebApp.getServletReference(java.lang.String, com.ibm.servlet.engine.webapp.ServletReferenceListener) void com.ibm.servlet.engine.webapp.WebAppRequestDispatcherInfo.calculateInfo() com.ibm.servlet.engine.webapp.WebAppRequestDispatcherInfo(com.ibm.servlet.en gine.webapp.WebApp, java.lang.String) javax.servlet.RequestDispatcher com.ibm.servlet.engine.webapp.WebApp.getRequestDispatcher(java.lang.String) void com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(java.lang.Obje ct) void com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(java.lan g.Object) void com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(java.lang.S tring, com.ibm.servlet.engine.srp.ISRPConnection) void com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(com.ibm.ser vlet.engine.oselistener.api.IOSEConnection) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.handleConnection( java.net.Socket) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.run() void java.lang.Thread.run() *** Error: Initialization passing property parameters to EJB failure. java.net.SocketException: socket closed (code=0) java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.io.IOException(java.lang.String) java.net.SocketException(java.lang.String) int java.net.SocketInputStream.socketRead(byte [], int, int, java.net.SocketImpl, java.io.FileDescriptor) int java.net.SocketInputStream.read(byte [], int, int) int java.net.SocketInputStream.read() java.lang.String java.io.DataInputStream.readLine() void com.ibm.servlet.engine.http_transport.HttpTransportHandler.handleConnection( java.net.Socket) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.run() void java.lang.Thread.run() java.net.SocketException: socket closed (code=0) java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.io.IOException(java.lang.String) java.net.SocketException(java.lang.String) int java.net.SocketInputStream.socketRead(byte [], int, int, java.net.SocketImpl, java.io.FileDescriptor) int java.net.SocketInputStream.read(byte [], int, int) int java.net.SocketInputStream.read() java.lang.String java.io.DataInputStream.readLine() void com.ibm.servlet.engine.http_transport.HttpTransportHandler.parseHeaders(java .io.DataInputStream) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.handleConnection( java.net.Socket) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.run() void java.lang.Thread.run() java.net.SocketException: socket closed (code=0) java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.io.IOException(java.lang.String) java.net.SocketException(java.lang.String) int java.net.SocketInputStream.socketRead(byte [], int, int, java.net.SocketImpl, java.io.FileDescriptor) int java.net.SocketInputStream.read(byte [], int, int) int java.net.SocketInputStream.read() java.lang.String java.io.DataInputStream.readLine() void com.ibm.servlet.engine.http_transport.HttpTransportHandler.handleConnection( java.net.Socket) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.run() void java.lang.Thread.run() java.net.SocketException: socket closed (code=0) java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.io.IOException(java.lang.String) java.net.SocketException(java.lang.String) int java.net.SocketInputStream.socketRead(byte [], int, int, java.net.SocketImpl, java.io.FileDescriptor) int java.net.SocketInputStream.read(byte [], int, int) int java.net.SocketInputStream.read() java.lang.String java.io.DataInputStream.readLine() void com.ibm.servlet.engine.http_transport.HttpTransportHandler.parseHeaders(java .io.DataInputStream) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.handleConnection( java.net.Socket) void com.ibm.servlet.engine.http_transport.HttpTransportHandler.run() void java.lang.Thread.run() Thanks -----Original Message----- From: Tanveer, Mohammad Sent: Friday, August 24, 2001 11:40 AM To: 'JAVA400-L@midrange.com' Subject: RE: Problem when running Visual Age we are using VAJAVA3.5 is it possible to upgrade to 3.5.2 for free? -----Original Message----- From: Jim Mason [mailto:JEMason@compuserve.com] Sent: Wednesday, August 15, 2001 2:06 PM To: INTERNET:JAVA400-L@midrange.com Subject: Re: Problem when running Visual Age Hi Azeem. As Gary correctly points out, knowing the OS version is important. I run Windows NT 4.0 with service pack 6a, a very stable environment. I never get a blue screen of death even IF VisualAge terminates abnormally. I am running VisualAge for Java Enterprise, 3.5.2. It generally is VERY good. The REALLY good news is nothing is LOST if the environment crashes except the current method you were editing that hasn't been saved. All your work exists in the repository file (ivj.dat) that you can recover to your workspace after fixing the workspace image.... When you have repeated crashes in VisualAge like you mention: 1 Your image file ( ide.icx) probably has a corruption in it somewhere. 2 You can try to clear any corrupted cached classes that may cause the problem first: workbench | windows | options | general | cache clear memory cache clear disk cache then apply then ok to exit then exit VisualAge normally AFTER restarting VisualAge the cached objects are cleared. IF this doesn't work, try unloading and reloading your custom applications 3 Unload and reload your applications to the workspace Put all your custom applications in a single Solution object in the repository. Delete the applications from the workspace. Again, clear the cache in step 2. Exit VisualAge. Start VisualAge. Reload the Solution set bringing in all your applications. If you still have a problem, it is with a Java or VisualAge class, not your work. IF this doesn't work, the you must rebuild your image file from a backup copy.... 4 Get a new IDE.ICX file and update your workspace First save all your current work in a Solution object in your repository (ivj.dat FILE) per instructions above. Get a GOOD backup copy of IDE.ICX and copy over the one you have. (preferrably you saved one at install time from the fix pack or the original install that we KNOW is clean). Restart VisualAge with the clean workspace image file. Reload the Java and IBM features you had loaded before to your workspace. Reload your applications from the Solution in the repository. Save your workspace. You should be fine. I've never had a failure like you describe that couldn't be corrected this way. The "blue screen" of death is an OS failure in your fix packs and OS. An application failure shouldn't crash the OS... Jim Mason Message text written by INTERNET:JAVA400-L@midrange.com > Sorry that you're having problems. What version of VAJ are you on and what platform. I'm on Enterprise 3.5.3 and it has been very stable under Win2K. Gary ashaikhhafiz@chubb.com wrote: > > Hi! > I have this problem when running Visual Age. > > when i'm working on VAJava, when i'm making some changes and click to save, > it closes abruptly and all the changes that i have > made are lost, then i have to redo them all over again. The second problem > is also related to this. in this case when i make some changes and click to > save, the crash debug blue screen comes out. nowadays it's happening like > atleast 10 to 15 times a day. It is really frustrating because i have to > keep doing the same changes again and again all over. so i sort of tried to > get over this by importing the classes everytime i make changes, so that i > don't forget the changes i've done and i can start from the point the last > import was done. but then every time either VAJava closes abruptly or the > crash debug comes and the machine reboots, i have to import back the > changed classes. but it so happens that when i'm importing, it closes > abruptly. it's become very difficult for me to fix bugs and make changes. > sometimes the whole screen hangs and the mouse and key board are locked > out. then i have to power down and power on my machine again. It never use > to happen in the earlier days when i was working on java on the jdk swing. > but now > after the integration of the application codes it has started happening. > the no of application classes and the codes are extensive. i also open up > the ie browser to do the testing on the websphere test environment and > connect to the AS400 to check if the datas coming to the browser are > synchronous or not. > > mine is a IBM Personal Computer 300GL where the config is PIII450 processor > and a ram of 128MB. > I would be very happy if someone and especially from IBM help me on this so > that i don't have to keep worrying always that anytime either VAJava will > close > or the System would be locked or the crash debug will appear and the > machine would get rebooted. > > now even though the RAM has been upgraded to 256 i have the same problems. > Thanks in Advance for the solutions. > > Thanks & Regards > Azeem. > > Office Tele : +65 - 3359 570 > Res Tele : +65 - 5659 761 > Mobile : +65 - 9621 6556< +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.