T3ShutdownDef deprecated in WLS 6.1 SP5 ?

After switching over from SP4 to SP5 of WebLogic Server 6.1 I get deprecation warnings
when compiling my Shutdown Class implementing weblogic.common.T3ShutdownDef.
Also other classes from weblogic.common are marked as deprecated (e.g. T3ServicesDef)
in Eclipse.
Strangely enough I can't find any hint that these interfaces are really deprecated
now in the JavaDocs. Nor can I find any replacements for these services.
Should I ignore the deprecation warnings?
Or should I use different services for shutdown classes in the future?
Thanks for your answers
Andreas

Hello,
I am also looking forward with the replacement of these interfaces t3shutdowndef and t3filesystem.
I am using weblogic 8.1 sp4.

Similar Messages

Can't get adf-faces-demo.war working on WLS 8.1 SP5

Did a search & found some others facing the same difficulties as I am, also followed some recommendations of using an exploded war instead of archive war, and also adding some JARs from Tomcat 5.5.* onto my classpath, but the demo still refuses to work on WLS 8.1 SP5.
Using the hyperlink http://127.0.0.1:7001/adf-faces-demo, I kept getting a blank page. And on my WLS console, I'm seeing these:
Mar 15, 2006 6:37:23 PM oracle.adfinternal.view.faces.webapp.ConfigParser parseConfigFile
INFO: ADF Faces is running in debug mode. Do not use in a production environment. See:/WEB-INF/adf-f
aces-config.xml
Could somebody help me with this?
Or WLS 8.1 totally doesn't work with JSF?

Dear Prasanth,
You're right; so what I did next was to rename my .jspx to .jsp, and this time round I hit this exception while accessing the index.jsp page, any idea what other stuffs I did to do?
Thanks for your help!
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405)
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105)

Using native IIS 6.0 Gzip Compression in front of WLS 8.1 SP5

(IIS 6.0 => ISAPI proxy(/*) => WLS 8.1 SP5 )
Instead of usign a servlet filter and Gzip compression inside the, I would like to test the IIS 6.0 Gzip compression. I want to do this because the IIS server farm is severley underutilized in CPU and seems like the best use of that resource.
It is easy to config this in IIS 6.0. However, I can get IIS served static pages back compressed, but requests proxied to WLS return uncompressed, even though I have configured DLL calls to be zipped inide IIS.
The question is: has anyone done this and if so, what is the config.

I am trying to solve the same issue. This is what I've discovered so far. I have been able to get page compression to work with IIS 4.0 and 5.0 using the iisproxy plugin. The trick was to add both "jsp" and "wlforward" extensions to the script file list to compress dynamic files.
IIS 6.0 changed the compression module from an ISAPI plugin to internal code. The configurations look the same, but I am not able to get JSPs to be compressed. I can compress static files, I can compress ASP files so I know I have compression working and I know that I have dynamic file compression working.
This is a great article on configuring compression in IIS, it should get you started in the right direction. I know it's from a .Net site, but the fundamentals are the same and it's very well written.
http://dotnetjunkies.com/Article/16267D49-4C6E-4063-AB12-853761D31E66.dcik
I am now trying to figure out how to get IIS 6.0 dynamic page compression to work with the iisproxy plugin. Any ideas?

Re: Can WLS 8.1 sp5 work with WLP 8.1 sp2?

We were thinking of upgrading WL server that our WLP 8.1 uses from 8.1 sp2 to 8.1 sp4. Can WLS 8.1 sp5 work with WLP 8.1 sp2?
Manish

You will need to follow the upgrade steps to upgrade your SP2 app to SP5.
http://e-docs.bea.com/wlp/docs81/upgrade/servicepack4to5.html
Kunal Mittal

Migrating from WLS 8.1 SP5 to Sp6

We have successfully runned WLS 8.1 SP5
When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
l edxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?

Anton Gavazuk wrote:
We have successfully runned WLS 8.1 SP5
When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
l edxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?Hi. This is a known issue with 81sp6. Ask support for the patch
for CR308071. We document that it is forbidden to have multiple
XA datasources pointing to the same pool, and we now enforce that,
but the bug is that we were also preventing mulitple datasources
to non-XA pools as well.
Joe

Struts action classes not reloaded in WLS 8.1 SP5

Hi,
          We are in the process of upgrading from WLS6.1 to WLS8.1(SP5). I installed WLS8.1 in development mode with no change to any of the default settings and got our app up and running. However, one issue that I noticed was that WLS8.1 is not reloading new classes copied int WEB-INF/classes directory within the webapp.
          I read the document at http://edocs.bea.com/wls/docs81/webapp/deployment.html#157139 and it clearly says that any changes to classes are automatically picked up.
          I have verified that "servlet-reload-check-secs" is set to 1. Is there any configuration item that I am missing here ?
          Thanks in advance,
          Prasad

Hi,
          I am deploying my application on bea weblogic 8.1SP5........and it showing errors below::::while iit's working fine on sp4........
          JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
          JVMDG315: JVM Requesting Heap dump file
          .........JVMDG318: Heap dump file written to /soft_dump/BEA815/user_projects/dom
          ains/mydomain/heapdump274442.1150373114.phd
          JVMDG303: JVM Requesting Java core file
          JVMDG304: Java core file written to /soft_dump/BEA815/user_projects/domains/mydo
          main/javacore274442.1150373147.txt
          JVMDG274: Dump Handler has Processed OutOfMemory.
          Is dere any solution for it?
          Thanks
          Samit Katiyar
          [email protected]

WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out

Hi,
I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
<BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.

I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
- try upgrading to a newer SP, or better yet, a new version of WebLogic
- try changing to synchronous forwarding
- examine thread dumps from when the bridge appears to be stalled
- post the exception that bridge is throwing when it tries to connect
- try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
- write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
Tom

Wls 8.1 sp5 - cannot deploy exploded archive anymore

Hi all,
I used to deploy exploded archive in development mode with wls 8.1 sp4. When browsing the file system, the console used to show a radio button to the left of folders which contained an exploded war.
Since I replace 8.1 sp4 with 8.1 sp5, this radio button does not appear anymore along folders that contain exploded war.
Is this a known issue ? Anyone reproduced the same behaviour ?
Thanks for letting me know of any workaround as this feature is really handy ...
Kind regards,
Regis

Dear Prasanth,
You're right; so what I did next was to rename my .jspx to .jsp, and this time round I hit this exception while accessing the index.jsp page, any idea what other stuffs I did to do?
Thanks for your help!
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405)
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105)

Re: WLS 6.1 SP5 changed behaviour with OracleThinClob?

Thorsten Roskowetz wrote:
Hi,
while trying to update a Weblogic 6.1 server installation to SP5, I noticed
the following change in behaviour: Apparently, SP5 will return an instance
of class oracle.sql.CLOB for Clob column value from Resultset, whereas
previous versions returned an instance of a wrapper class.
As a consequence, the programming examples from
http://e-docs.bea.com/wls/docs61/jdbc/thirdparty.html#1043705
for accessing the Oracle blob extensions using OracleThinBlob/Clob
fail with a ClassCastException - oracle.sql.CLOB can not be casted
to OracleThinClob!
This makes it impossible to write code that runs without changes on SP4
and SP5 and updates oracle clobs - or am I missing something?
Could not find any mention of this in the SP5 release notes...You are not mistaken. In sp4 and previous we wrapped all serverside
JDBC objects obtained through a DataSouce in multiple redundant
wrapper objects, including the unnecessary rmi driver. For 61sp5, for
performance and also functionality reasons, we removed the rmi layer.
One unfortunately undocumented affect is that you now get direct access
to the Oracle Blobs/Clobs. I do understand and appologise for the
problem this caused to your code. We had been wrapping the Blob/Clobs
with an rmi-capable wrapper in keeping with the intended use of the
rmi driver in external clients. We are now considering whether for backward
compatibility we should provide a change to continue to wrap oracle
blob/clob objects in the rmi wrapper.
Joe
>
>
Best regards,
T. Roskowetz

We have the same problem with the generated code of a CMP entity bean.
After installing Weblogic Sp5 we can no longer store a Clob field in the database using a CMP entity bean.
the line of weblogic generated code it fails on is:
Writer writer = ((weblogic.jdbc.common.OracleClob) lob).getCharacterOutputStream();
the error is:
<Nov 11, 2003 1:27:18 PM CET> <Info> <EJB> <Exception from ejbStore: java.lang.ClassCastException: oracle.sql.CLOB
java.lang.ClassCastException: oracle.sql.CLOB
at ep.pericles.eb.useraccount.UserAccount_34c4w2__WebLogic_CMP_RDBMS.__WL_set_profileForOutput(UserAccount_34c4w2__WebLogic_CMP_RDBMS.java:2507)
at ep.pericles.eb.useraccount.UserAccount_34c4w2__WebLogic_CMP_RDBMS.__WL_store(UserAccount_34c4w2__WebLogic_CMP_RDBMS.java:2350)
at ep.pericles.eb.useraccount.UserAccount_34c4w2__WebLogic_CMP_RDBMS.ejbStore(UserAccount_34c4w2__WebLogic_CMP_RDBMS.java:2107)
at weblogic.ejb20.manager.DBManager.storeBean
Are there any work arounds?
TIA
Duncan

WLS 6.1 SP5 changed behaviour with OracleThinClob?

Hi,
while trying to update a Weblogic 6.1 server installation to SP5, I noticed
the following change in behaviour: Apparently, SP5 will return an instance
of class oracle.sql.CLOB for Clob column value from Resultset, whereas
previous versions returned an instance of a wrapper class.
As a consequence, the programming examples from
http://e-docs.bea.com/wls/docs61/jdbc/thirdparty.html#1043705
for accessing the Oracle blob extensions using OracleThinBlob/Clob
fail with a ClassCastException - oracle.sql.CLOB can not be casted
to OracleThinClob!
This makes it impossible to write code that runs without changes on SP4
and SP5 and updates oracle clobs - or am I missing something?
Could not find any mention of this in the SP5 release notes...
Best regards,
T. Roskowetz

We have the same problem with the generated code of a CMP entity bean.
After installing Weblogic Sp5 we can no longer store a Clob field in the database using a CMP entity bean.
the line of weblogic generated code it fails on is:
Writer writer = ((weblogic.jdbc.common.OracleClob) lob).getCharacterOutputStream();
the error is:
<Nov 11, 2003 1:27:18 PM CET> <Info> <EJB> <Exception from ejbStore: java.lang.ClassCastException: oracle.sql.CLOB
java.lang.ClassCastException: oracle.sql.CLOB
at ep.pericles.eb.useraccount.UserAccount_34c4w2__WebLogic_CMP_RDBMS.__WL_set_profileForOutput(UserAccount_34c4w2__WebLogic_CMP_RDBMS.java:2507)
at ep.pericles.eb.useraccount.UserAccount_34c4w2__WebLogic_CMP_RDBMS.__WL_store(UserAccount_34c4w2__WebLogic_CMP_RDBMS.java:2350)
at ep.pericles.eb.useraccount.UserAccount_34c4w2__WebLogic_CMP_RDBMS.ejbStore(UserAccount_34c4w2__WebLogic_CMP_RDBMS.java:2107)
at weblogic.ejb20.manager.DBManager.storeBean
Are there any work arounds?
TIA
Duncan

WLS 8.0 SP5 JDBC deploy error

Heya,
I'm upgrading our servers from SP4 to SP5 and found that the application scoped JDBC Pool/Data Source to SQL Server 2000 in my EAR will no longer deploy. I'm using the ant task wldeploy and I tried using the Admin Console. I keep getting a NullPointerException. All worked fine under SP4, so has anyone else had this problem? I can post the error trace/weblogic-application.xml file if it'll help...
Thanks,
Anna

Anna Veirauchs wrote:
Thank you for your time.
The Admin Server log has the following:
####<Oct 26, 2005 3:37:24 PM PDT> <Warning> <RMI> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljavax.management.ObjectName;)
java.lang.NullPointerException.
java.lang.NullPointerException
     at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:245)Hi. At this point, I think official support should get involved.
Can you open a case with them? The exceptions aren't being generated
or at least reported from JDBC-related code, but if they can dig
more, it might end up in my court.
Joe
     at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149033> <failed application **** on ****>
####<Oct 26, 2005 3:37:25 PM PDT> <Info> <Management> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
####<Oct 26, 2005 3:37:25 PM PDT> <Warning> <Deployer> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application ****.>
####<Oct 26, 2005 3:37:25 PM PDT> <Debug> <Deployer> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
     Module: JDBCDataSource     Error: java.lang.NullPointerException
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
================
The Managed Server log has:
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module JDBCDataSource of application **** is transitioning from unprepared to prepared on server ****.>
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <JDBC> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-001155> <The following exception has occurred:
java.lang.NullPointerException
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
     at weblogic.management.internal.AdminMBeanHomeImpl_815_WLStub.getMBean(Unknown Source)
     at weblogic.jdbc.common.internal.JDBCDataSourceFactory.createDataSource(JDBCDataSourceFactory.java:74)
     at weblogic.jdbc.common.internal.JDBCModule.prepare(JDBCModule.java:140)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3149)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1590)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1234)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1077)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2530)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2480)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: java.lang.NullPointerException
     at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:245)
     at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
     ... 2 more
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149061> <Module JDBCDataSource of application **** failed to transition from unprepared to prepared on server ****.>
####<Oct 26, 2005 3:37:25 PM PDT> <Error> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 3 for the application ****.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
     Module: JDBCDataSource     Error: java.lang.NullPointerException
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
     Module: JDBCDataSource     Error: java.lang.NullPointerException
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2413)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
====
My weblogic-application.xml is:
<!DOCTYPE weblogic-application PUBLIC '-//BEA Systems, Inc.//DTD WebLogic Application 8.1.0//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd'>
<weblogic-application>
     <jdbc-connection-pool>
          <data-source-name>JDBCDataSource</data-source-name>
          <connection-factory>
               <connection-properties>
                    <user-name>******</user-name>
                    <password>******</password>
                    <url>jdbc:bea:sqlserver://10.10.10.99\\MYINSTANCE</url>
                    <driver-class-name>weblogic.jdbc.sqlserver.SQLServerDriver</driver-class-name>
                    <connection-params>
                         <parameter>
                              <param-name>databaseName</param-name>
                              <param-value>****</param-value>
                         </parameter>
                    </connection-params>
               </connection-properties>
          </connection-factory>
<pool-params>
<size-params>
<initial-capacity>10</initial-capacity>
<max-capacity>10</max-capacity>
<capacity-increment>2</capacity-increment>
<shrinking-enabled>true</shrinking-enabled>
<shrink-frequency-seconds>300</shrink-frequency-seconds>
<highest-num-waiters>100</highest-num-waiters>
<highest-num-unavailable>4</highest-num-unavailable>
</size-params>
<login-delay-seconds>1</login-delay-seconds>
<leak-profiling-enabled>false</leak-profiling-enabled>
<connection-check-params>
<table-name>SQL SELECT COUNT(*) FROM sysobjects</table-name>
<check-on-reserve-enabled>true</check-on-reserve-enabled>
<check-on-release-enabled>false</check-on-release-enabled>
<check-on-create-enabled>false</check-on-create-enabled>
<connection-reserve-timeout-seconds>30</connection-reserve-timeout-seconds>
<connection-creation-retry-frequency-seconds>360
</connection-creation-retry-frequency-seconds>
<inactive-connection-timeout-seconds>360
</inactive-connection-timeout-seconds>
<test-frequency-seconds>600</test-frequency-seconds>
</connection-check-params>
</pool-params>
<driver-params>
<prepared-statement>
<cache-size>10</cache-size>
<cache-type>LRU</cache-type>
</prepared-statement>
<row-prefetch-enabled>true</row-prefetch-enabled>
<row-prefetch-size>500</row-prefetch-size>
<stream-chunk-size>1024</stream-chunk-size>
</driver-params>
     </jdbc-connection-pool>
</weblogic-application>

JTA with WLS 8.1 sp5 and Oracle 10.1.0.4

Hi,
          I am testing a global transaction involving two EJBs (stateless session beans) running on two separate WebLogic servers. Each ejb calls an Oracle stored procedure against a different datbase. One ejb is deployed on one server the other one on the second server.
          I want to know if it is mandatory to set up a trust relationship between the two servers. The reason I ask is that it seems the transaction is working without it (with the SecurityIdentity automatically downgraded to 'anonymous').
          However it only seems to consistently work between certain servers and randomly failing when using a different pair of servers.
          Thanks
          Cristian

Cristian Mihaila wrote:
          > Hi Joe,
          >
          > Here is the stack trace :
          Ok, you should make sure you're using consistent SecurityInteropMode settings
          on the different servers. Trust is only needed if the servers are on different
          domains otherwise trust is not needed. We made many changes to correct a downgrade
          issue on different subsystems JTA, JMS, EJB in 81sp6. There is a patch
          available for 81sp5 for this.
          Please read: http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1120356
          Joe
          >
          > <Feb 20, 2007 11:53:54 AM EST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.loyalty.arrow.services.epin.ejb.EPinFacadeSession.authenticate(java.lang.String,java.lang.String,java.lang.String,java.lang.String)],Xid=BEA1-02DD480140BE7F28EDB9(12622847),Status
          > =Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=89,seconds left=10,XAServerResourceInfo[OmdbXMultiPool]=(ServerResourceInfo[OmdbXMultiPool]=(state=new,assigned=pinpp2),xar=null,re-Registered = false),SCInfo[pinpp+pinpp2]=(state=rolling-back),SCInfo[mydomain+m
          > yserver]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.loyalty.arrow.services.epin.ejb.EPinFacadeSession.authenticate(java.lang.String,java.lang.String,java.lang.String,java.lang.String)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+159
          > .175.18.251:7001+mydomain+t3+, XAResources={JMS_FileStore, shadbConnectionPool, arrow1lclprdPool},NonXAResources={})],CoordinatorURL=myserver+159.175.18.251:7001+mydomain+t3+): weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9
          > at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1600)
          > at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1147)
          > at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1882)
          > at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1064)
          > at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
          > at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
          > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
          > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
          > at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
          > --------------- nested within: ------------------
          > weblogic.transaction.RollbackException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9 - with nested exception:
          > [weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds
          > BEA1-02DD480140BE7F28EDB9]
          > at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1684)
          > at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
          > at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
          > at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:320)
          > at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
          > at com.loyalty.arrow.services.epin.ejb.EPinFacade_y6z7xe_EOImpl.authenticate(EPinFacade_y6z7xe_EOImpl.java:110)
          > at com.loyalty.arrow.services.epin.ejb.EPinFacade_y6z7xe_EOImpl_WLSkel.invoke(Unknown Source)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
          > at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
          > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
          > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
          > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
          >
          > Thanks
          > Cristian

Wlst / wls 8.1 sp5 / add-remove defaultAuditor

I was wondering if there is some example code for removing an auditor?
I've seen an exmaple of adding one, but wasn't sure if there was anything special to remove one.
Thanks.

Did you try the delete command? Use it exactly as create, that should work.
HTH,
-satya
BEA Blog:
http://dev2dev.bea.com/blog/sghattu/
Get Involved in CodeShare:
https://wls-console-extensions.projects.dev2dev.bea.com/
https://wlnav.projects.dev2dev.bea.com/
https://eclipse-wlst.projects.dev2dev.bea.com/
https://wlst.projects.dev2dev.bea.com/

Java SDK compatibility under RHEL 4 and WLS 8.1 SP5

I am in the process of installing BEA WebLogic 8.1 SP5 under Red Hat Linux ES 4 on x86 processors, and am verifying the supported Java SDKs. Accoriding to:
http://edocs.bea.com/platform/suppconfigs/configs81/rhelinux40as_es_x86/81sp5.html
only the JRockit JDK is listed. Is this implying that Sun's JDK 1.4.2_08 is not supported under this configuration?
The installation binary installs both Sun's and Jrockit's JDK.
Thanks for your assitance.

I am in the process of installing BEA WebLogic 8.1 SP5 under Red Hat Linux ES 4 on x86 processors, and am verifying the supported Java SDKs. Accoriding to:
http://edocs.bea.com/platform/suppconfigs/configs81/rhelinux40as_es_x86/81sp5.html
only the JRockit JDK is listed. Is this implying that Sun's JDK 1.4.2_08 is not supported under this configuration?
The installation binary installs both Sun's and Jrockit's JDK.
Thanks for your assitance.

Exploded EAR in WLS 6.1 SP5

Hello
Is it possible to deploy exploded ear in WLS 6.1 during the development ?
If yex, What is the structure of an exploded ear ?
Thank you for your help
Barry

barry wrote:
Hello
Is it possible to deploy exploded ear in WLS 6.1 during the development ?
Yes
If yex, What is the structure of an exploded ear ?
Same as an archived EAR that you unzipped.
-- Rob
Thank you for your help
Barry

T3ShutdownDef deprecated in WLS 6.1 SP5 ?

Similar Messages

Maybe you are looking for