Anil,
      Actually, for this problem to occur, tracing does not even have to be
enabled.
      Because, the problem occurs when the  "org.apache.wsif.logging.Trc"
class is referenced for the
      first time and when its static member variable "private static Log
log = LogFactory.getLog(wsifPackageName+".*");"
      gets initialized.

      Which version of WSIF are you using? WSAD 5.0 comes with an old
version of wsif.
      In order to use the latest version, I have set the Classloader Mode
to PARENT_LAST
      for my ejb application and the latest nightly build and its
associated lib's are included in my project as utility jars.

      Looking at the commons logging documentation, you can also create a
properties file "commons-logging.properties" and
      make it available to your application's class path. This properties
file will contain the logger implementation class name.

      Hope this helps,

Simon


                                                                           
             Anil Ambati                                                   
             <[EMAIL PROTECTED]                                             
             om>                                                        To 
                                       [EMAIL PROTECTED]             
             08/19/2003 09:21                                           cc 
             AM                        [EMAIL PROTECTED]             
                                                                   Subject 
                                       Re: Problem With WSAD 5.0 AND WSIF  
             Please respond to                                             
             [EMAIL PROTECTED]                                             
                  he.org                                                   
                                                                           
                                                                           
                                                                           








Hello:
I am using WSIF in same environment and I have not run into this error. I
have not set the system property that you mentioned. Although, I am not
sure if the tracing is enabled. I bet it is not enabled, that is why I have
not encountered this problem. Would you please tell me how to turn on
tracing in WSIF code in WSAD 5.0 test environment? Where does it create the
trace file?

You talked about using properties file, where will you place this file? Is
it in <WSAD test environment root>/properties directory?

Thanks in advance.

Regards,
Anil Ambati
SDWB Development
919-254-6152
[EMAIL PROTECTED]
"You have no responsibility to live up to what other people think you ought
to accomplish." -Richard Feynman (1918-1988)
"Money is as bad as it is necessary" - Anonymous



                      Simon Solomon

                      <[EMAIL PROTECTED]>         To:
[EMAIL PROTECTED]

                                               cc:

                      08/18/2003 01:36         Subject:  Re: Problem With
WSAD 5.0 AND WSIF
                      PM

                      Please respond to

                      wsif-user










Thanks,

      got it working after performing the following changes.

      I have set a System property "org.apache.commons.logging.LogFactory"
to
      "org.apache.commons.logging.impl.LogFactoryImpl" in my test server.

      In the future I will set this property within a "
commons-logging.properties" file.

Simon





             Aleksander
             Slominski
             <[EMAIL PROTECTED]                                          To
             .edu>                     [EMAIL PROTECTED]
                                                                        cc
             08/18/2003 01:07
             PM                                                    Subject
                                       Re: Problem With WSAD 5.0 AND WSIF

             Please respond to
             [EMAIL PROTECTED]
                  he.org






Simon Solomon wrote:

>
>
>Has anyone experienced the following exception while using WSIF within a
>WSAD 5.0 Test server?
>- EjbApplication
>- Classloader Mode: PARENT_LAST
>
>java.lang.ExceptionInInitializerError:
>org.apache.commons.logging.LogConfigurationException:
>java.lang.ClassCastException: com.ibm.ws.commons.logging.TrLogFactory
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609)
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>java.security.AccessController.doPrivileged(Native Method)
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:561)
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:352)
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>org.apache.commons.logging.LogFactory.getLog(LogFactory.java:414)
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>org.apache.wsif.logging.Trc.<clinit>(Trc.java:104)
>[8/18/03 12:09:23:578 EDT] 5f9be443 SystemErr     R   at
>org.apache.wsif.providers.soap.apacheaxis.WSIFDynamicProvider_ApacheAxis$1.run(WSIFDynamicProvider_ApacheAxis.java:216)



>
>
>
>
it look sliek it may be problem specific to WSAD setup and how your app
interacts with common logging andcom.ibm.ws.commons.logging:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg60516.html

HTH,

alek

--
If everything seems under control, you're just not going fast enough.
—Mario Andretti


Reply via email to