Exception in server

          I'm getting following exception on the server (WL6.0 SP1), when I'm
          calling a servlet from a Java application. Java app gets a XML message
          form a JMS queue and calls a Servlet URL, and sends that XML as
          one of the parameters.
          Any leads will be helpful!
          <Apr 3, 2001 6:33:40 PM EDT> <Error> <NT Performance Pack> <failure in
          processSockets() - GetData: 'weblogic.socket.GetData@690247 - fd:
          '1168', numBytes: '29''
          java.net.SocketException: fd=1168: socket was closed on this end
          at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
          at
          weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:632)
          at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          thanks,
          Sanjay Ungarala

You should check with IBM Support.
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ73363
-Akshay

Similar Messages

Java.lang.Exception: Oracle server error604....

can you please let me know what might be the cause for this
"java.lang.Exception: Oracle server error604...."

Hi,
its JDeveloper and ADF on this forum. For EM related questions, you should try the EM forum
Frank

Exception:weblogic.server.ServiceFailureException:

JAVA Memory arguments: -Xms96m -Xmx256m
WLS Start Mode=Development
CLASSPATH=C:/cspDomain/lib/patches/CSP_patch_434.jar;;;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\bea\JROCKI~1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\bea\JROCKI~1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;C:\bea\WEBLOG~1\portal\lib\wps_system.jar;C:/cspDomain/lib/post/ClaimsServiceClient.jar;C:/cspDomain/lib/post/commons-beanutils.jar;C:/cspDomain/lib/post/commons-collections.jar;C:/cspDomain/lib/post/commons-digester.jar;C:/cspDomain/lib/post/commons-fileupload.jar;C:/cspDomain/lib/post/commons-logging.jar;C:/cspDomain/lib/post/commons-validator.jar;C:/cspDomain/lib/post/hibernate2.jar;C:/cspDomain/lib/post/junit.jar;C:/cspDomain/lib/post/log4j-1.2.8.jar;C:/cspDomain/lib/post/MemberServiceClient.jar;C:/cspDomain/lib/post/PhsAudit.jar;C:/cspDomain/lib/post/PhsBOD.jar;C:/cspDomain/lib/post/PhsExceptions.jar;C:/cspDomain/lib/post/PhsLogging.jar;C:/cspDomain/lib/post/PhsSchema.jar;C:/cspDomain/lib/post/PhsUtility.jar;C:/cspDomain/lib/post/ProductServiceClient.jar;C:/cspDomain/lib/post/ProviderServiceClient.jar;C:/cspDomain/lib/post/PurchaserServiceClient.jar;C:/cspDomain/lib/post/ServiceLocator.jar;C:/cspDomain/lib/post/struts-adapter.jar;C:/cspDomain/lib/post/struts.jar;C:/cspDomain/lib/post/strutstestcase.jar;C:/cspDomain/lib/post/west_fax_client.jar;C:/cspDomain/settings
PATH=C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\OraHome1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\bea\WEBLOG~1\server\bin\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
=== Debugging ===
This window is necessary for debugging code using WebLogic Workshop
Starting WLS with line:
C:\bea\JROCKI~1\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms96m -Xmx256m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dejbruntime.database=oracle81xthin -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=cspServer -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
ERROR: Proxy already running...
<May 6, 2005 2:58:55 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_04 JVM Version ari-31788-20040616-1132-win-ia32 from BEA Systems, Inc.>
<May 6, 2005 2:58:55 PM GMT+05:30> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<May 6, 2005 2:58:55 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464
WebLogic Portal 8.1 SP3 Wed Jun 30 14:02:15 PDT 2004 405464>
<May 6, 2005 2:58:56 PM GMT+05:30> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at C:\CSPDOM~3\domains\CSPDOM~1\.\config.xml.>
Could not bind to Weblogic server (Error attaching to Weblogic Server.).
<May 6, 2005 2:59:00 PM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file C:\CSPDomain\domains\cspDomain\cspServer\cspServer.log is opened. All server side log events will be written to this file.>
<May 6, 2005 2:59:01 PM GMT+05:30> <Error> <EmbeddedLDAP> <000000> <Error Instantiating 'dc=cspDomain': null>
<May 6, 2005 2:59:01 PM GMT+05:30> <Critical> <EmbeddedLDAP> <BEA-171522> <An error occurred while initializing the Embedded LDAP Server. The exception thown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot. This may indicate a problem with the data files for the Embedded LDAP Server. If the problem is with the data files and it can not be corrected, backups of previous versions of the data files exist in .\cspServer\ldap\backup.>
<May 6, 2005 2:59:01 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServiceFailureException: Error initializing Embedded LDAP Server - with nested exception:
[java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot]
java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot
     at weblogic.ldap.EmbeddedLDAP.initialize()V(EmbeddedLDAP.java:192)
     at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:816)
     at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
     at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
     at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
--------------- nested within: ------------------
weblogic.server.ServiceFailureException: Error initializing Embedded LDAP Server - with nested exception:
[java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot]
     at weblogic.ldap.EmbeddedLDAP.initialize()V(EmbeddedLDAP.java:276)
     at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:816)
     at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
     at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
     at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
<May 6, 2005 2:59:01 PM GMT+05:30> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.server.ServiceFailureException: Error initializing Embedded LDAP Server - with nested exception:
[java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot]>
Stopping the Weblogic Workshop debugger...
Debugger Stopped.
i am getting the above exception what is the problem
thanks,
siva
Thanks & Regards,
Siva VP,
[email protected]

Deletion of this folder works. But the error popups again while i am restarting server. Should i delete this everytime before i start. Is there any other way to fix this?

Unexpectedly error - ex_handle_except encountered exception C0000005 - Server terminating - (SQL 2008 R2 10.50.4000.0 (SP2))

Hi Guys,
I've faced an unexpected error in my test and production environment. The SQL Server was shutdown and it was created a dump file with the follow information:
* BEGIN STACK DUMP:
*   01/16/14 17:18:16 spid 5272
* ex_handle_except encountered exception C0000005 - Server terminating
* MODULE                          BASE      END       SIZE
* sqlservr                       0000000000360000 0000000003F71FFF 03c12000
* ntdll                          0000000077130000 00000000772D8FFF 001a9000
* kernel32                       0000000077010000 000000007712EFFF 0011f000
* KERNELBASE                     000007FEFD270000 000007FEFD2DAFFF 0006b000
* ADVAPI32                       000007FEFEAA0000 000007FEFEB7AFFF 000db000
* msvcrt                         000007FEFE8D0000 000007FEFE96EFFF 0009f000
* sechost                        000007FEFE2A0000 000007FEFE2BEFFF 0001f000
* RPCRT4                         000007FEFE970000 000007FEFEA9CFFF 0012d000
* MSVCR80                        0000000074680000 0000000074748FFF 000c9000
* MSVCP80                        00000000744A0000 00000000745A8FFF 00109000
* sqlos                          0000000073780000 0000000073786FFF 00007000
* Secur32                        000007FEFCAB0000 000007FEFCABAFFF 0000b000
* SSPICLI                        000007FEFCD40000 000007FEFCD64FFF 00025000
* pdh                            000007FEF5B20000 000007FEF5B6DFFF 0004e000
* SHLWAPI                        000007FEFE2C0000 000007FEFE330FFF 00071000
* GDI32                          000007FEFEC60000 000007FEFECC6FFF 00067000
* USER32                         0000000076F10000 0000000077009FFF 000fa000
* LPK                            000007FEFE3F0000 000007FEFE3FDFFF 0000e000
* USP10                          000007FEFE750000 000007FEFE818FFF 000c9000
* USERENV                        000007FEFC210000 000007FEFC22DFFF 0001e000
* profapi                        000007FEFCEA0000 000007FEFCEAEFFF 0000f000
* WINMM                          000007FEF5AE0000 000007FEF5B1AFFF 0003b000
* IPHLPAPI                       000007FEFA780000 000007FEFA7A6FFF 00027000
* NSI                            000007FEFE340000 000007FEFE347FFF 00008000
* WINNSI                         000007FEFA760000 000007FEFA76AFFF 0000b000
* opends60                       0000000073740000 0000000073747FFF 00008000
* NETAPI32                       000007FEFA3E0000 000007FEFA3F5FFF 00016000
* netutils                       000007FEFC3A0000 000007FEFC3ABFFF 0000c000
Does someone have any idea what's going on?
Is there any KB for it?
Thanks

Hello,
As suggested by Olaf best is to raise a case with Microsoft and get your Dump analyzed.Generally can be due to bad hardware and rouge queries executing on your system .Exact cause MS will point out
see below links for same discussion( might be helpful)
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea05a4e1-dfea-4293-ac45-85a9ea949832/sql-server-2008-is-terminating-because-of-fatal-exception-c0000005?forum=sqldatabaseengine
http://connect.microsoft.com/SQLServer/feedback/details/646293/ex-handle-except-encountered-exception-c0000005-server-terminating
http://connect.microsoft.com/SQLServer/feedback/details/713402/ex-handle-except
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SJWS 7u1 exception initializing server side logger

OS: Solaris 10
JDK: 1.5_09
WS: 7u1
I get a very random, once in a blue moon error where i get the error message:
service-j2ee reports: exception initializing server side logger java.lang.NullPointerException
java.lang.NullPointerException
at com.sun.webserver.logging.ServerLogManager.getConfiguredLogLevel(ServerLogManager.java:98)
at com.sun.webserver.logging.ServerLogManager$3.run(ServerLogManager.java:250)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.webserver.logging.ServerLogManager.initializeLogger(ServerLogManager.java:246)
at com.sun.webserver.logging.BaseLogManager.doInitializeLogger(BaseLogManager.java:97)
at com.sun.webserver.logging.BaseLogManager.addLogger(BaseLogManager.java:146)
at java.util.logging.Logger.getLogger(Logger.java:258)
at com.sun.org.apache.commons.logging.impl.Jdk14Logger.getLogger(Jdk14Logger.java:152)
at com.sun.org.apache.commons.logging.impl.Jdk14Logger.<init>(Jdk14Logger.java:53)
at sun.reflect.GeneratedConstructorAccessor3.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
at com.sun.org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at org.apache.tomcat.util.IntrospectionUtils.<clinit>(IntrospectionUtils.java:42)
at org.apache.catalina.core.StandardWrapper.getRootCause(StandardWrapper.java:695)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:820)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:630)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:548)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:984)
at org.apache.jsp.index_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:917)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:464)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:358)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:917)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:398)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:792)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:630)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:548)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:984)
at org.apache.jsp.index_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:917)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:464)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:358)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:917)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:398)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:792)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:630)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:548)
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:984)
at org.apache.jsp.index_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.
After this error mesage appears, I start getting StackOverflow errors for every JSP requested. All other requests work just fine (DWR, imgs, etc).
I have no idea what is causing this error and I can' reproduce it. I'm going to try updating to SJWS 7u3 to see if that fixes the problem and hopefully someone else will have an idea. I can't even find reference to that error on the web.
Thanks for any input!

I think, you are probably running into CR: 6604075. This issue was addressed in U2. Do try out U3 . I guess, this should address your problem

TS3274 Cannot send email. It says nobody will except my server

Cannot email out. Every time I get a message that the recipient will not except my server.

What is the complete and exact error message?

Exception in Server Logs : JMSCC0033 While using Weblogic 10.3.X and MQ 7

Following exception is contuniously occuring in Weblogic Managed Server Logs after migrating to IBM MQ 7.
com.ibm.msg.client.jms.DetailedIllegalStateException: JMSCC0033: A synchronous method call is not permitted when a session is being used asynchronously: 'acknowledge' The JMS specification does not permit the use of a session for synchronous methods when asynchronous message delivery is running. Create a separate session if you wish to use both synchronous methods and asynchronous delivery simultaneously.
     at sun.reflect.GeneratedConstructorAccessor43.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:516)
     at com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NLSServices.java:313)
     at com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLSServices.java:388)
     at com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErrorUtils.java:104)
     at com.ibm.msg.client.jms.internal.JmsSessionImpl.checkSynchronousUsage(JmsSessionImpl.java:2375)
     at com.ibm.msg.client.jms.internal.JmsMessageImpl.acknowledge(JmsMessageImpl.java:1559)
     at com.ibm.jms.JMSMessage.acknowledge(JMSMessage.java:351)
     at weblogic.ejb.container.internal.MDListener$MDMessage.acknowledge(MDListener.java:802)
     at weblogic.ejb.container.internal.MDListener$1.run(MDListener.java:237)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2473)
     at weblogic.ejb.container.internal.MDListener.putListener(MDListener.java:234)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:687)
     at weblogic.ejb.container.internal.MDListener.run(MDListener.java:744)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

You should check with IBM Support.
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ73363
-Akshay

RMI Exception in Server but ru

Hi Guys,
this error message i get when i run my application in my local machine
RemoteException :java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.net.MalformedURLException: no protocol: 5.5/webapps/ROOT/WEB-INF/classes/
But the question is the application runs well in my server
I already copied all the .class file from my server to my local but still encounter this error//
Anyone has any idea? maybe the java version of different application web server running application??

Thanks, I know already
Its because my tomcat directory path has space in between
C:\Tomcat 5.5\......
i already changed to C:\Tomcat5.5
and everything works fine

Java Exceptions in Server Trace file

Is it possible to tell the Server (817)
not to write the Java exceptions into the trace file ?
thx in advance
null

Ludovik Segaert wrote:
I have a java server that also acts as a client to another java server. When this second server throws an exception, it never reaches the first server acting as a client.Any ideas?What version of WLE ? Does the server acting as a client execute normally
or does it get a different exception?
Peter

Handle exception on server side and display a customized jsp error page

Hi,
I am developing a java/j2EE web application using servlet, jsp, ejb3 with JBOSS and ECLIPSE.
Two cases can occur on the server side :
1) either I have not an expected result in a method and in this case I want to display an error page (a JSP page I suppose) with a personnalized error message
2) or I have an exception thrown and I want to display the exception message in the former JSP page
I don't know how to cope with this problem of personnalized error message (or the message of a thrown exception) with a JSP page.
Does anybody can help me ? Thank you
Edited by: xflamant on Jun 20, 2009 10:51 AM

For the case of an unknown Error, simply use a default error page.
The redirection to this page can be accomplished by inserting folowing code into your web.xml:
     <error-page>
        <exception-type>java.lang.Throwable</exception-type>
        <location>/WEB-INF/jsp/error.jsp</location>
    </error-page>Known exception can be caught via a try-catch block.
Then simply dispatch to the page you want displayed an add an attribute containing the error message to the response object.
This attribute can then be used in the target page to diplay the error.

Exception starting server when using wlserver Ant task

Hello All:
When attempting to start my server using the wlserver Ant task, i receive the following error:
[wlserver] java.lang.NoClassDefFoundError: weblogic/Server
[wlserver] Exception in thread "main"
[wlserver] Error in server execution
my snippet is as follows:
<target name="start-server">
<wlserver beahome="C:\bea" weblogichome="c:\bea\weblogic81" host="localhost"
                    port="7001" username="weblogic" domainname="mydomain" password="weblogic"
                    servername="myserver" action="start"/>
</target>
It seems as if it should work fine. Anybody have any solutions? Thanks in advance.
Ricky

Ricky,
You have to add the weblogic JARs to the classpath of the wlserver task.
add something similar to the following (bold text are additions):
<path id="classpath.weblogic">
<fileset dir="c:/bea/weblogic81/server/lib">
<include name="weblogic_sp.jar" />
<include name="weblogic.jar" />
<include name="webserviceclient.jar" />
</fileset>
</path>
<target name="start-server">
<wlserver beahome="C:\bea" weblogichome="c:\bea\weblogic81" host="localhost"
port="7001" username="weblogic" domainname="mydomain" password="weblogic"
servername="myserver" action="start" classpathref="classpath.weblogic"/>
</target>
--Peter

JMS Exception when server goes down (Urgent) ?

Hi All,
I have three topics in the JMS Server which is on the top of Web logic server 8.1.
On the client side I have Swing thick cleint.For each topic I have a listener.
When the web logic server goes down ( I shut down manually ) Only one listener is recieving the Exception and the Swing client reacts accordingly.
After this ,
Client continousoly checks whether the server is up or not. Once the server is up again the Exception is thrown that server is down ( I guess now the second listener is recieving the message).
After some time again the third listener recives the message.....
and the client reacts on that exception 3 times.
How can I get rid of this ?
thanks in advance.
san

Hi,
this is probably a very good question to ask support. 'Logical' deployment sequence
was added to the WebLogic only recently (6.1sp?) ('logical' means that first datasources
are deployed, then EJB's and then web-apps, deployment-order parameter was added etc).
So, for applications where shutdown sequence is important there must be a document which
describes how server shutdown works.
On the other hand, this may not be as important as deployment sequence, because running
instance can crash at any time and it should not affect anything.
Jen <[email protected]> wrote:
Repost
Hi,
Most of my ejbs use connection from the connection pool. At the weblogic server shut
down time (heavy load), I can see the jsps call the ejb, sometime jsp can't find
the bean because it's removed from jndi. sometime jsp found the bean but when the
bean try to talk to database, ejb can't use the connection because the datasource
is removed from jndi. Also my shutdown class waits for the threads finish up, and
the threads calls the ejb and do the db operation, and the conn is cut when the db
operation is half way. So, the order of events when server shut down is important
to me. I am wondering how other people deal with it. Thanks --
Dimitri

Exception at server proxy

Hi,
In the scenario of server proxy where CRM is updating an application,
If at any such state where some error happens n CRM fails to update, how can i trigger this process again .
If i throw evception using exception class , then how can i generate the proxy again(think hav to generate proxy again to trigger whole process again)
so as to try updating again in CRM,
Pls suggest me on this ,
Thanks,

hi,
if you implemented the server proxy exception correctly
you just need to click on restart on your message
(or have it sheduled) and the proxy will be executed once more
Regards,
michal

Distinguish different exceptions from server?

hi,
In my application, there is a remote call:
public Object getXXXX
throws RemoteException, MyExceptionA, MyExceptionB;
(where MyExceptionA and MyExceptionB are both child class of RemoteException)
I have two related questions.
1. On the client side, it will always get the java.rmi.ServerException
NO MATTER what the server code actually throws, i.e, EVEN IF server
throws MyExceptionA (or B), the client will still get ServerException.
Is that always the case?
2. If it is always the case, then in client code, what is the best
practise to distinguish different exceptions?
Do I have to catch ServerException first and then use
ServerException.getCause() and then use instanceof to know exactly
which exception was actually thrown by the server? That seems to
be a little bit clumsy. Are there any other elegant ways to know
the EXACT exception thrown by server?
Thanks in advance for the help.
JK

The above argument makes perfect sense to me. But, it
seems
to me, no matter how many kinds of exceptions you
declare in
the signature of your remote call, assuming the remote
call gets
to the server and gets executed on the server, if any
exception
occurs on the server, the client will ONLY get ONE
exception:
java.rmi.ServerException (see my original question 1)
Is that REALLY the case or NOT?No, it is not the case. You only get a ServerException if a RemoteException happens on the server: 'A ServerException is thrown as a result of a remote method invocation when a RemoteException is thrown while processing the invocation on the server, either while unmarshalling the arguments, executing the remote method itself, or marshalling the return value'. In other words you only get a ServerException because of either a failure inside the RMI runtime in the server while setting up or tearing down the call, or if the remote method in the server calls another remote method itself (i.e. calls another server) and gets a RemoteException from that.
If your server deliberately throws an exception because you coded it that way, the client gets the exception thrown. If the server trips an Error you get a ServerError at the client. If the server trips a RuntimeException you get a RuntimeException at the client.
EJP

How to handle Exception on Server Side as well as Client side

Hello All,
what is the method of EXCEPTION HANDLING in Web Dynpro Java ? I have no idea how these exception throw.
Thks in advance.

Hi,
Exception handling in WDJav ais similar to that of Java.
exception handling in webdynpro
Regards,
SrinivaS

Exception in server

Similar Messages

Maybe you are looking for