Sponsored Content
Special Forums UNIX and Linux Applications Exception in Weblogic Application server Post 302506126 by Siddheshk on Friday 18th of March 2011 02:35:39 PM
Old 03-18-2011
Exception in Weblogic Application server

Hi,

I have a application running on weblogic server. i am getting these errors in logs very frequently. Could you please suggest any solution for this.

Code:
-02-09 10:02:32,346 ERROR [Main Thread] psn.properties.RemotePropertiesCache - Error occurred while attempting to retrieve property: 

default.jms.topic.ConnectionFactory. Returning default value.
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://voasams1,voasams2:7502: Destination unreachable; nested exception is: 
    java.net.ConnectException: Connection refused; No available router to destination]

2011-02-14 10:14:40,649 ERROR [Transport Shepherd] psn.properties.RemotePropertiesCache - Error occurred while attempting to retrieve property: 

loggingevent.ExternalTransportError. Returning default value.
java.rmi.ConnectException: Could not establish a connection with 

8802516135776057077S:voasams2:[7502,7502,-1,-1,-1,-1,-1]:voasams1:7502,voasams2:7502:vfop6dom:ams-stream1-svr2, java.rmi.ConnectException: Destination 

unreachable; nested exception is:

Any help would be appreciated.
Thanks in advance

Regards,
SiddheshK

Last edited by radoulov; 03-18-2011 at 05:00 PM.. Reason: Code tags, please!
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

difference weblogic server/webserver/app server

Hi All, I am getting confused with the terms below. All I know is an application can be installed on a server. But I see the following terms used in a company. All of them are installed on same Unix box. Could you please help me out in layman terms as to what these exactly means. (PS: I don't... (1 Reply)
Discussion started by: tostay2003
1 Replies

2. Solaris

Veritas WebLogic Server log files

Hi All, I am trying to change the log file to an incremental log file so that I do not needd to restart weblogic everytime the server /tmp directory reach 100% usage. I want to make it an incremental log, just like adm messages. At the moment, operation process is written to a log file (eg:... (1 Reply)
Discussion started by: ronny_nch
1 Replies

3. Solaris

Problem in deployment in weblogic server in solaris

I am getting following error during deployment in solaris. when i deploy same war in other machine (non-solaris) it works fine. the stacktrace is < ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277738498407> <BEA-149205> <Failed to initialize the... (0 Replies)
Discussion started by: paradesi143
0 Replies

4. UNIX and Linux Applications

Version of Weblogic server

Hi All, How to find the version of the weblogic server configured? Our server is a Linux based server. Regards Dhivya (1 Reply)
Discussion started by: dhivya.enjoy
1 Replies

5. Shell Programming and Scripting

How can i get the state of weblogic server

Hi, all Now i want write a shell to get the state of weblogic server,and when the Managed Server's state is not ok, after 3 times checking, i will send msg to the system administrator by sms. BTW, my environment is : Linux ,Redhat 5.4 64bit weblogic version: 10.3.3 the count number... (1 Reply)
Discussion started by: wangsk
1 Replies
XML::SAX::Exception(3)					User Contributed Perl Documentation				    XML::SAX::Exception(3)

NAME
XML::SAX::Exception - Exception classes for XML::SAX SYNOPSIS
throw XML::SAX::Exception::NotSupported( Message => "The foo feature is not supported", ); DESCRIPTION
This module is the base class for all SAX Exceptions, those defined in the spec as well as those that one may create for one's own SAX errors. There are three subclasses included, corresponding to those of the SAX spec: XML::SAX::Exception::NotSupported XML::SAX::Exception::NotRecognized XML::SAX::Exception::Parse Use them wherever you want, and as much as possible when you encounter such errors. SAX is meant to use exceptions as much as possible to flag problems. CREATING NEW EXCEPTION CLASSES
All you need to do to create a new exception class is: @XML::SAX::Exception::MyException::ISA = ('XML::SAX::Exception') The given package doesn't need to exist, it'll behave correctly this way. If your exception refines an existing exception class, then you may also inherit from that instead of from the base class. THROWING EXCEPTIONS
This is as simple as exemplified in the SYNOPSIS. In fact, there's nothing more to know. All you have to do is: throw XML::SAX::Exception::MyException( Message => 'Something went wrong' ); and voila, you've thrown an exception which can be caught in an eval block. perl v5.16.2 2011-09-14 XML::SAX::Exception(3)
All times are GMT -4. The time now is 04:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy