Weblogic.wtc.applicationQueue problem on WLS 813

Hi all I am trying to get WLS 813 to use weblogic.wtc.applicationQueue as opposed to the default execution queue when it is called by Tuxedo. When I test this on 815 it works perfectly however when I try it on 813 it seems to ignor the dispatch policy input in the deployment descriptor and simply uses the default execution queue.
One solution is to upgrade to 815 however my client does not want to do this as they feel the risk is too great at the moment.
Have any of you out there experienced a similar situation and is there a fix without resorting to an upgrade?
tia
ed

I think that property was introduced post WLS 8.1SP3, but I'm not certain of that. If so, you could request a backport of the change from BEA Support. They should be able to accomodate you.
Regards,
Todd Little
BEA Tuxedo Chief Architect

Similar Messages

WTC, wls-api.jar, weblogic.wtc.gwt.*, missing classes ?!

Hi WLS fans,
I've installed WLS 10.3 and I've tried to migrate WLS 8.1 App to WLS 10.3 via Workshop.
I was supprised NOT to find the classes: TuxedoConnection, TuxedoConnectionFactory and all the rest needed classes to compile the code, in the wls-api.jar, weblogic.wtc.gwt
package .
WLS-ARI.JAR, weblogic.wtc.gwt package_ (in WL_HOME\server\lib)
I've realized that till v. 9, the package contained these classes.
Since v. 10, the pachage contains ONLY one class: genpasswd. And there are a lot of missing classes/interfaces from the weblogic.wtc.jatmipackage as well.
Could somebody tell me where are the other needed classes ? Have they been moved to some other package ?
Have the WTC EJB logic been modified ?
I use this code:
{color:#0000ff}import weblogic.wtc.gwt.*;
import weblogic.wtc.jatmi.*;
TuxedoConnection myTux;
TypedString myData;
Reply myRtn = myTux.tpcall("MyTuxService", myData, 0); {color}
//etc.

Hi, George.
From weblogic 10 onwards, weblogic transitively includes jars in the BEA_HOME/modules directory. The jar you are looking for is:
modules/com.bea.core.jatmi_1.0.1.0.jar
Cheers,
-Adrian

Enterprise application conversion problem from WLS 10.3.0 to WLS 10.3.2

Hi all,
I'm posting this just to document a problem I had when converting an Enterprise Application from WLS 10.3.0 across to WLS 10.3.2 environment.
Upon deployment of the application I was getting this error:
Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.ApplicationParamBeanImpl@b720894d(/ApplicationParams[webapp.encoding.default])"
     at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:227)
     at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setApplicationParams(WeblogicApplicationBeanImpl.java:560)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:536)
     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
     at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:329)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
It turns out this was an issue with the META-INF/weblogic-application.xml having duplicate entries for the "webapp.encoding.default" parameter.
This obviously got duplicated when my app was re-imported into the Eclipse OPEP environment for WLS 10.3.2
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd">


<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
</wls:weblogic-application>
Removing the duplicate entry resolved this problem.
I hope this helps anyone else that experiences this issue.
Regards,
Paul

Below link might be helpful.
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
Regards,
Anandraj
http://weblogic-wonders.com/

General install and deployment problem with WLS clustering on two boxes

Hi,
I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
Any help appriecated.
Surfbum.

Hi I think I've found the answer. You can build a managed server template using the pack command.
http://e-docs.bea.com/common/docs90/pack/tasks.html

Tuxedo queues to configure to weblogic WTC

Hi I am trying to create queues in the tuxedo config .I have the following configurations in my ubb file.
UBB
+++
*GROUPS
OS_WT_GP1 LMID="TX_MAS" GRPNO=110
*SERVERS
GWADM SRVGRP=OS_WT_GP1 SRVID=2
GWTDOMAIN SRVGRP=OS_WT_GP1 SRVID=3
redirect SRVGRP=OS_WT_GP1 SRVID=500 REPLYQ=Y RQADDR=SERVER1_Q1 MIN=1 MAX=2
CLOPT="-A -- -s CHECKSERVICE"
redirect SRVGRP=OSB_WTC_GP1 SRVID=510 REPLYQ=Y RQADDR=SERVER1_Q2 MIN=1 MAX=2
CLOPT="-A -- -s CHECKSERVICE"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I have the following entries in the DMC file to make the calls to contact the WTC.
DMC
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
*DM_LOCAL_DOMAINS
TUXOS_DOM_1
GWGRP=OS_WT_GP1
TYPE=TDOMAIN
ACCESSPOINTID="TUXOS_DOM_1"
DMTLOGNAME="DMTLOG"
SECURITY=NONE
CONNECTION_POLICY=ON_STARTUP
*DM_REMOTE_DOMAINS
OS_DOM_1
TYPE=TDOMAIN
ACCESSPOINTID="OSDOM_1"
*DM_TDOMAIN
TUXOS_DOM_1
NWADDR="<IP:PORT NO>"
OS_DOM_1
NWADDR="<IP:PORT NO>"
LACCESSPOINT="TUXOS_DOM_1"
*DM_IMPORT
CHECKSERVICE
AUTOTRAN=N
RNAME="checkserviceresult"
RACCESSPOINT=OS_DOM_1
LACCESSPOINT=TUXOS_DOM_1
I am trying to contact from machine A to Machine B using tuxedo. The machine B is weblogic server
1)I would like to know if we can create queues in the tuxedo service and same can be configured in the WTC of weblogic
2)If yes, I would like to know the configurations required on the weblogic side to address the different queues mentioned in the UBB file
Thanks in advance

Hi,
Your post is a little confusing as I'm not sure what you mean by the term "queue". If you want to call a WTC based EJB in WLS, then what you have on the Tuxedo side looks OK. On the WLS side you will need to create a WTC server instance, add the appropriate local domain and remote domain, and then add an export. Both the Tuxedo and WLS documentation describes how to do this.
If by queue you mean a Tuxedo /Q and/or JMS queue, then you need to configure the WTC tBridge. The tBridge provides a JMS bridge that can:
1) Take entries off of a JMS queue and call a Tuxedo service and place the reply on another JMS queue
2) Take entries off of a JMS and place them on a Tuxedo /Q queue
3) Take entries off of a Tuxedo /Q queue and place them on a JMS queue
If you can provide a little more information or details, I can give you a more definitive answer.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Weblogic 10.0 Problems with stripes/struts

When trying to deploy the sample application for the stripes framework on weblogic 10.0 I get the following error when deploying.
<Dec 3, 2009 12:16:51 PM CET> <Error> <HTTP> <BEA-101165>
<Could not load user defined filter in web.xml:
net.sourceforge.stripes.controller.StripesFilter.net.sourceforge.stripes.exception.StripesRuntimeException:
Problem instantiating default configuration objects.I actually had to switch to using the Sun JDK to get this error. JRockit does not report it, and just fails when I try to use the application. The problem appear to be weblogic 10.0 specific. No problems with jetty or tomcat, and I've heard reports that it is resolved in weblogic 10.3. Have ayone come accross similar problems when using stripes/struts on weblogic 10.0, and found a solution to this? Is there a patch available for 10.0 than fix this?
Regards
Morten
PS: I have ommited the complete stack trace, since it is monstrously huge.

Guess I was wrong in thinking that this was an isolated weblogic 10.0 problem. I just downloaded weblogic 10.3 and tried to deploy the same application there, and the same error happened.
<03.des.2009 kl 15.12 CET> <Error> <HTTP> <BEA-101165>
<Could not load user defined filter in web.xml:
net.sourceforge.stripes.controller.StripesFilter.net.sourceforge.stripes.exception.StripesRuntimeException:
Problem instantiating default configuration objects.
        at net.sourceforge.stripes.config.DefaultConfiguration.init(DefaultConfiguration.java:220)
        at net.sourceforge.stripes.config.RuntimeConfiguration.init(RuntimeConfiguration.java:272)
        at net.sourceforge.stripes.controller.StripesFilter.init(StripesFilter.java:125)
        at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:329)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        Truncated. see log file for complete stacktrace
java.lang.NullPointerException
        at java.io.FilterInputStream.read(FilterInputStream.java:116)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
        at java.io.InputStreamReader.read(InputStreamReader.java:167)
        Truncated. see log file for complete stacktraceSo is there anyone out there with experience with struts/stripes, that can tell why this does not work? If you need to try this yourself, you can download the stripes sample application here:
http://sourceforge.net/projects/stripes/files/stripes/Stripes%201.5.2/stripes-1.5.2.zip/download
There is an example WAR called "stripes-examples.war" in the zip that is ready to be deployed.
Regards
Morten
PS: you still need to start weblogic with Sun JDK rather than JRockit to get the error. With JRockit the application simply fails when used.

Where to Download weblogic.wtc.jatmi Library/Package

Dear Tuxedo Experts,
I am trying to somehow make a Java client for a Tuxedo Server that listens to C clients. I have found the online javadocs for weblogic.wtc.jatmi which seems to be the answer to my question. Would you guide if that package help me to build a complete Java client?
Would you also tell me where I can download this library/API.
Thanks a lot.
Ahsan

Hi Ahsan,
If you go to the Oracle Sample Code site (www.samplecode.oracle.com), you should be able to find the WTC samples that you can use as a starting point. I believe this link should get you there:
https://www.samplecode.oracle.com/tracker/tracking/linkid/prpl1004/remcurreport/true/template/ViewIssue.vm/id/S729/nbrresults/18
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Disabling logging to weblogic.log during startup of WLS

Hello,
Does anybody know how to disable logging to the weblogic.log file during startup
of WLS (v5.1.0).
Specifically I would like to hide parameters such as username and password that
show up as clear text for example when a database pool is created.
Thanks,
Murtaza.

Hi under WLS5.1.0, you can not do it.
thanks
Yu
Murtaza Sonaseth <[email protected]> wrote in message
news:3b5c729e$[email protected]..
>
Hello,
Does anybody know how to disable logging to the weblogic.log file duringstartup
of WLS (v5.1.0).
Specifically I would like to hide parameters such as username and passwordthat
show up as clear text for example when a database pool is created.
Thanks,
Murtaza.

Apache-soap Problem with WLS 5.1sp9

I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]

I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]

URG! problem with wls 9.2. DynamicMBeanImpl Class no exists in weblogic.jar

Hi all,
I have a problem instalating in startupclass and shutdownclass to uses jolt connections.
Theses classes are PoolManagerStartUp and PoolManagerShutdown.
it looks like the problem is in the joltwls.jar library (it contains the classes previously mentioned, bea.jolt.pool.servlet.weblogic.PoolManagerStartUp and bea.jolt.pool.servlet.weblogic.PoolManagerShutdown)
These classes uses a method that is in weblogic.jar version 7.0 but not in weblogic.jar version 9.2.
the class that hasn´t been found is weblogic/management/internal/DynamicMBeanImpl
this is the log :
<Dec 20, 2008 6:29:27 PM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: weblogic/management/internal/DynamicMBeanImpl
java.lang.NoClassDefFoundError: weblogic/management/internal/DynamicMBeanImpl
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:246)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:253)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
Truncated. see log file for complete stacktrace
thanks in advance!!
Edited by: user5481292 on 20-dic-2008 10:21
Edited by: user5481292 on 20-dic-2008 10:37

Hi,
This missing classes can be found inside the JAR : *"E:\bea10_3_3\wlserver_10.3\server\lib\wseeclient.jar"* As well as inside *"E:\bea10_3_3\wlserver_10.3\server\lib\wls-api.jar"*
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic/webservices/ (WebLogic Wonders Are Here)

JDBC Type 3 driver problem with WLS 6.1 SP4

We have Oracle 8.1.7.4 client running on WebLogic 6.1 SP4 on Solaris 2.6 connecting to Oracle OPS 8.1.7 running on Solaris 2.6. We are getting core dumps while running stress testing using Load Runner for 100 concurrent users. The performance is very good for a while in the beginning of the test and all of a sudden we see requests for connections queueing up on the WLS and the server crashes. Please send us details of any previous instances any one faced similar problem and the fix applied will be very helpful.
Regards,
Raj

The Member Feedback forum is for suggestions and feedback for OTN Developer Services. This forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. We recommend that you post this thread to the SQLJ/JDBC forum.
The URL is: http://forums.oracle.com/forums/forum.jsp?forum=99
Thanks, OTN Team

Spring 2.5.5 and EJB 3.0 Deployment problem in WLS 10.3

Hi,
I am attempting to deploy a EAR file that previously ran on SJSAS 9.1 update 1 to WLS 10.3. As part of the deployment I get the following error related to the EJB3 classes.
There are 1 nested errors: weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015002]Unable to load class au.edu.cqu.cis.web.ajaxservice.AjaxServicesBean in Jar D:\dev\env\oracle\middleware\jdeveloper\system\system11.1.1.0.31.51.56\DefaultDomain\servers\DefaultServer\tmp\_WL_user\ProgEnrol-ear-3\v540rk\ProgEnrol-ejb-3.0.4-SNAPSHOT.jar : java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
I suspect that this is related to the @Autowired spring annotation in use in the session bean. Either, the server is not finding the Spring JAR correctly or it has a problem with the annotation.
Can anyone point me in the right direction? Do I need to deploy the spring jar as a library?
Thank you.
Regards,
Graeme.

Hi, Graeme.
Seems there is an existing CR on something related from v10.0: CR353213
* WLS 10.0 - EJB 3.0 deployment fails when parsing class for Stateless annotation
According to http://edocs.bea.com/wls/docs103/issues/known_resolved.html, this is not addressed in 10.3
Closely review your classpath, and then (assuming you have access to the source) review the body of your ejb. If it is related to this CR, you may be able to workaround the issue by shortening the body and split large methods into more sub-methods.
I hope this helps,
-Adrian

Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

We are using simplified chinese, after swith to bea jdriver, it messed up
all the encoding. So we cannot display Chinese character correctly.
We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
environment, BEA supplied JDK 1.3.1_03.
We have many diffrent problems with oracle drivers:
1. We want to use XA driver to support distributed transaction, However:
* bea jdriver xa messes up with encoding
* when using oracle 901 driver, everything works fince except webservices.
Workshop application access the ejb, then the workshp application sets
isolation level, but oracle driver does not support it and gives error. Is
there a way to turn off isolation level in workshop? I tried manually edit
weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
2. When not using XA, oracle thin driver works fine. But we lost XA
capability.
Any work around?

I did try to change the value in this config file as well, but did not help.
In fact, the installation default setting is with
'<transaction-isolation-level>' commented out.
And when I use bea oracle jdriver, it somehow messed up with database
character set encoding, so our Chinese characters could not be retrieved
correctly. And I try to set the encoding of jdriver to 'GBK', it did not
work.
"Anurag Pareek" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
:[email protected]..
Hello Ma,
The transaction isolation level value for EJBs backing the JWS files is
specified in the <transaction-isolation-level> tag in the
WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
manipulate this value to serve your purpose.
Please do let me know how it goes.
Regards,
Anurag
Workshop Support
"Ma Jie" <[email protected]> wrote in message
news:[email protected]..
We are using simplified chinese, after swith to bea jdriver, it messed
up
all the encoding. So we cannot display Chinese character correctly.
We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
environment, BEA supplied JDK 1.3.1_03.
We have many diffrent problems with oracle drivers:
1. We want to use XA driver to support distributed transaction, However:
* bea jdriver xa messes up with encoding
* when using oracle 901 driver, everything works fince exceptwebservices.
Workshop application access the ejb, then the workshp application sets
isolation level, but oracle driver does not support it and gives error.Is
there a way to turn off isolation level in workshop? I tried manuallyedit
weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
2. When not using XA, oracle thin driver works fine. But we lost XA
capability.
Any work around?

Clustering Problems with WLS 4.5.1

Hi!
          I'm trying to configure a WebLogic 4.5.1 cluster (named "cluster1", on two
          WinNT4 SP5 servers (instances WLS "server A" and "server B")
          When I start each WLS instance in each server, both create a cluster where I
          can only find one WLS server, not two! So I have on each NT server, one
          cluster which contain one WLS server!!!
          To see that, I use the WLS console on the 2 servers, and I see that in each
          server, there is a cluster "cluster1" and only one server ("server A" in the
          first NT Server, and "server B" in the second one).
          The two server are identical, same OS, same SP, same WLS version, same WLS
          Service Pack, same IP Multicast address, same TCP port (7001), and there is
          no multihoming.
          I can't see how to put the two WLS servers in the same cluster!
          Do someone have a clue?
          Best regards,
          Jean-Michel Gautreau
          [email protected]


Here is a console screendump, taken after the two WLS servers' boot.
          I forgot to tell we have installed WLBS on both NT servers, before
          installing WebLogic 4.5.1. Is there a problem in the communication between
          the two servers? I'm not sure but I feel it is a network problem, the two NT
          servers don't seem to communicate correctly through WLBS with the WLS
          cluster?
          Any hint?
          [dump.bmp]

Problems with WLS 4.5.1 and F5 Big IP HA+ Switch

Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
          4.5.1 servers (two in the pool currently). At seemly random intervals the
          Big IP believes the one or both of the servers are not responding, so they
          are removed from the pool. We have a growing body of anecdotal evidence to
          suggest that the servers are actually on-line and available during the
          event. Either the switch is confused or the WLS servers aren't always
          responding correctly to the HTTP requests sent by the switch for polling.
          We're having problems catching the problem with the right diagnostics.
          Has anyone out there observed similar behavior with these components?
          Thanks.
          - Sean McRae


Sort of,
          I use iplanet between the 2, so I havent had this problem, but I have had
          several problems with clustering, here is what I recomend doing:
          write a simple java program (or whatever your prefered language) to do a HTTP
          ping on your distinct weblogic servers every X seconds/minutes where X is less
          than Big IPs death tolerance. Time how long/or if ever each of your pings take.
          turn on verbose gc.
          My guess is its one of 3 things:
          1.) your have a big gc going on and your server isnt responding quick enough
          and big ip is marking it dead
          2.) you have thread contention that is causing your server not to respond quick
          enough
          3.) your network has some issues and the packets arent making it there, or not
          quick enough.
          the ping program will prove/disprove #2 and lead you to or away from 3. Verbose
          gc will prove/disprove #1.
          hope this helps
          -Joel
          Sean wrote:
          > Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
          > 4.5.1 servers (two in the pool currently). At seemly random intervals the
          > Big IP believes the one or both of the servers are not responding, so they
          > are removed from the pool. We have a growing body of anecdotal evidence to
          > suggest that the servers are actually on-line and available during the
          > event. Either the switch is confused or the WLS servers aren't always
          > responding correctly to the HTTP requests sent by the switch for polling.
          > We're having problems catching the problem with the right diagnostics.
          >
          > Has anyone out there observed similar behavior with these components?
          >
          > Thanks.
          >
          > - Sean McRae

Weblogic.wtc.applicationQueue problem on WLS 813

Similar Messages

Maybe you are looking for