WTC problem
Hi,
I'a new with tuxedo and I have to test the integration between weblogic integration(weblogic8.1) and the bea tuxedo product.
I've installed the bea tuxedo(9) and run the qsample example.
This one is ok. What I want to test now is the functionality with wtc to post message from jms to tuxedo queue and receive messages from tuxedo queue to jms.
I've configured the wtc connector with the Bridge and 2 redirections. I've also changed the ubbconfig file in order to add the dmadm, gwadm and gwtdomain. I've also created the dmconfig file. All seems to be ok.
But when I try to post a message on the jms queue, I received a message error and the message is enqueued to the jms error queue. The message is :
<cgServer> <Thread-11> <<WLS Kernel>> <> <BEA-180046> </tBexec/jmsQ2tuxQ/t#1 TPException explanation: TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not find service QSPACE>
After reading and rereading the documentation on the gateway and wtc, I still don't understand what's wrong with the config.
Has anyone an idea?
Thanks,
Rodrigue
here is the ubbconfig :
*RESOURCES
IPCKEY 52617
DOMAINID qsample
MASTER SITE1
MAXACCESSERS 100
MAXSERVERS 50
MODEL SHM
*MACHINES
BOROMIR
LMID = SITE1
TUXDIR ="c:\beatuxedo\tuxedo9.0"
TUXCONFIG = "C:\beatuxedo\test\qssampdir\tuxconfig"
TLOGDEVICE ="C:\beatuxedo\test\qssampdir\TLOG"
TLOGSIZE=10
APPDIR = "C:\beatuxedo\test\qssampdir"
ULOGPFX = "C:\beatuxedo\test\qssampdir\ULOG"
# On Windows NT replace '/' character with '\' in paths.
# So use instead:
# TUXCONFIG = "<full path of APPDIR>\tuxconfig"
# TLOGDEVICE ="<full path of APPDIR>\TLOG"
# ULOGPFX = "<full path of APPDIR>\ULOG"
*GROUPS
DMADMGRP
LMID = SITE1
GRPNO=3
GWGROUP
LMID = SITE1
GRPNO=4
GROUP1
LMID = SITE1 GRPNO = 1
TMSNAME=TMS TMSCOUNT=2
QUE1
LMID = SITE1 GRPNO = 2
TMSNAME = TMS_QM TMSCOUNT = 2
OPENINFO = "TUXEDO/QM:C:\beatuxedo\test\qssampdir\QUE;QSPACE"
# For Windows NT delete previous line, uncomment next line
# OPENINFO = "TUXEDO/QM:<full path of APPDIR>\QUE;QSPACE"
*SERVERS
DEFAULT: CLOPT="-A"
server SRVGRP=GROUP1 SRVID=2
DMADM
SRVGRP=DMADMGRP
SRVID=4
REPLYQ=N
RESTART=Y
GRACE=0
GWADM
SRVGRP=GWGROUP
SRVID=5
REPLYQ=N
GWTDOMAIN
SRVGRP=GWGROUP
SRVID=6
CLOPT = "-A -- -s"
TMQUEUE
SRVGRP = QUE1 SRVID = 2
GRACE = 0 RESTART = Y CONV = N MAXGEN=10
CLOPT = "-s QSPACE:TMQUEUE -- "
TMQFORWARD
SRVGRP=QUE1 SRVID= 7 GRACE=0 RESTART=Y CONV=N MAXGEN=10
CLOPT="-- -i 2 -q STRING"
*SERVICES
The dmconfig :
*DM_LOCAL
LOCAL1 GWGRP=GWGROUP
TYPE=TDOMAIN
ACCESSPOINTID="qsample"
*DM_REMOTE
REMOT1 TYPE=TDOMAIN
ACCESSPOINTID="PLDAAccessPoint"
*DM_EXPORT
QSPACE LACCESSPOINT=LOCAL1
CONV=N
RNAME=QSPACE
STRING LACCESSPOINT=LOCAL1
CONV=N
RNAME=STRING
*DM_TDOMAIN
LOCAL1 NWADDR="//192.168.1.105:3051"
REMOT1 NWADDR="//192.168.1.102:7003"
part of the config.xml :
<WTCServer DeploymentOrder="3000" Name="PldaWTC Service" Targets="cgServer">
<WTCLocalTuxDom AccessPoint="PLDAAccessPoint"
AccessPointId="PLDAAccessPoint" ConnectionPolicy="ON_DEMAND"
NWAddr="//192.168.1.102:7003" Name="WTCLocalTuxDom-1128428553157"/>
<WTCtBridgeGlobal DeliveryModeOverride="PERSIST"
JmsFactory="weblogic.jws.jms.QueueConnectionFactory"
JndiFactory="weblogic.jndi.WLInitialContextFactory"
Name="WTCtBridgeGlobal-1128428647252"
TuxFactory="tuxedo.services.TuxedoConnection" WlsErrorDestination="javax.jms.TuxedoErrorQueue"/>
<WTCtBridgeRedirect Direction="JmsQ2TuxQ"
Name="JmsQ2TuxQRedirection" SourceAccessPoint=""
SourceName="javax.jms.TuxedoSenderQueue"
TargetAccessPoint="qsample" TargetName="STRING" TargetQspace="QSPACE"/>
<WTCRemoteTuxDom AccessPoint="qsample" AccessPointId="qsample"
AllowAnonymous="true" ConnectionPolicy="ON_DEMAND"
LocalAccessPoint="PLDAAccessPoint"
NWAddr="//192.168.1.105:3051" Name="WTCRemoteTuxDom-1128462130197"/>
<WTCtBridgeRedirect Direction="TuxQ2JmsQ"
Name="TuxQ2JmsQRedirection" SourceAccessPoint="qsample"
SourceName="RPLYQ" SourceQspace="QSPACE"
TargetAccessPoint="" TargetName="javax.jms.TuxedoReceiverQueue"/>
</WTCServer>
Yes, I use TMQFORWARD. In the jmsQ2TuxQ(a part of the WTC configuration for bridge), I've put as:
reply queue : RPLYQ(a queue that I've created on QSPACE), target Qspace : QSPACE(the name of the qspace on the remote domain)
and as Queue name : STRING(which is also with TMQFORWARD the name of the service).
Then I don't understand why the wtc says it doesn't find the
QSPACE service. Why it doesn't search the STRING service?
In which config file is the error(in the ubbconfig?)?
Thanks
Similar Messages
-
Hi buddies:
I've connected a tuxedo service through WTC, now I need to connect from AquaLogic the same tuxedo service. The question is: Do I need to have a webservice for do that?, How can I configure AquaLogic? The documentation is not quite clear.
Thanks for yours answers.
JPHi JP,
For ALSB 2.0 and 2.1 the supported way to connect to Tuxedo is via the JMS transport and the WTC tBridge. For the next release of ALSB we hope to have a native Tuxedo transport.
In terms of requiring a Web Service, this is really a matter what you are trying to accomplish. If you are trying to access a Tuxedo service via a Web Service (SOAP over HTTP) then you need to configure a Tuxedo Business service using the JMS transport as described in the documentation and as well configure an HTTP Proxy service that takes a SOAP message. Create a route from the proxy to the business service and you'll have a Web Service that invokes your Tuxedo service. If this isn't what you meant, please provide some more details as to what you are trying to accomplish.
Regards,
Todd Little
BEA Tuxedo Engineering -
I have a problem when running my own EJB as a TUXEDO service using WTC.
Hello,
I have a problem when running my own EJB as a TUXEDO service using WTC. I am using TUXEDO 8.1 and WL 9.1.
When I am trying to run my own EJB as a TUXEDO service error appears.
TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not find service TOUPPER
at weblogic.wtc.gwt.WTCService.getImport(WTCService.java:4988)
at weblogic.wtc.gwt.TuxedoConnection.getImport(TuxedoConnection.java:303)
at weblogic.wtc.gwt.TuxedoConnection.tpcall(TuxedoConnection.java:1302)
at examples.MyTestSessionBean.Toupper(MyTestSessionBean.java:102)
at examples.TestSessionBean_knby6k_EOImpl.Toupper(TestSessionBean_knby6k_EOImpl.java:61)
at net.roseindia.web.servlets.SessionTestServlet.doGet(SessionTestServlet.java:69)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
e8
10
java.rmi.RemoteException: EJB Exception: ; nested exception is:
java.lang.NullPointerException
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:713)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:447)
at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
at examples.TestSessionBean_knby6k_EOImpl.Toupper(TestSessionBean_knby6k_EOImpl.java:75)
at net.roseindia.web.servlets.SessionTestServlet.doGet(SessionTestServlet.java:69)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: java.lang.NullPointerException
at examples.MyTestSessionBean.Toupper(MyTestSessionBean.java:130)
at examples.TestSessionBean_knby6k_EOImpl.Toupper(TestSessionBean_knby6k_EOImpl.java:61)
... 15 more
Any clue on this.
With Regards,
MVSIf you are trying to create a Tuxedo service in Java using WTC you need to develop an EJB that implements the TuxedoService interface and register its home in JNDI so WTC can look it up. Once that is done you can then export the service to a remote domain in the WTC configuration.
Regards,
Todd Little
Oracle Tuxedo Chief Architect -
Tuxedo -WTC stuck thread problem
Hi,
Tuxedo 8.1
OS: HP-UX
Weblogic:8.1
I am facing problem while using the WTC along with Tuxedo Service. My SVCTIMEOUT is 300 and causes the server kill. But its does not immediately start the server and give
1666 WARN: Could not terminate server(8709) processing after SVCTIMEOUT.
After sometime it do restarts the server. But the WTC threads which called the service are not released and gets stuck.
Can anyone please help?
Regards,
ArunaHi Todd,
Thanks for the answer. But actually I have already checked all these settings. The BLOCKTIME setting on Tuxedo ubb file is 100 and on WTC its is 100 as well for the Local Access Point. For domain there is no setting and as I understand it should take the ubb settings then.
Now, however I have one more problem at hand. I have following settings:
WTC BLOCKTIME 150
Tuxedo BLOCKTIME 150
SVCTIMEOUT 120
tpcall with TPNOTRAN|TPNOTIME flags set.
When I am making a call though WTC it gives me TPTIME and times out in 60 seconds. With these settings I am expecting it to timeout after 120 seconds when the server gets SIGKILL and restarts itself.
When I am using the Tuxedo client from Unix it works as exepcted.
Any help would be appreciated as I have tried all setting and serached all forums for an answer.
Regards,
Aruna Ahlawat -
Problem to connecte Tuxedo Service via WTC
Hello,
I'm new to WTC. I want to call a tuxedo service disposed in our serveur tuxedo by using WTC.
I created Local APs, Remote APs and Imported for this Tuxedo Service.
When I call I have always same erreur (perrno = 6) in tpcall
See below my calling webservice method
Have any one guide to avoid this problem?
Any help will be greatly appreaciated.
Thanks
@WebMethod
public void getClientInfo() {
Context ctx;
TuxedoConnection myTux;
TypedString dataIn = new TypedString("1, 10032600");
//TypedBuffer dataIn = null;
Reply rpy = null;
try{
System.out.println("getClientInfo called : " + dataIn);
TuxedoConnectionFactory tcf;
ctx = new InitialContext();
tcf = (TuxedoConnectionFactory) ctx.lookup("tuxedo.services.TuxedoConnection");
myTux = tcf.getTuxedoConnection();
System.out.println("About to call tpcall cnx = "+myTux);
rpy = myTux.tpcall("LireInfoClient_SE",null, 1);
System.out.println("tpcall successfull!");
dataIn = (TypedString) rpy.getReplyBuffer();
myTux.tpterm(); // Closing the association with Tuxedo
System.out.println("Return = "+dataIn.toString());
}catch (TPReplyException tpx) {
// Could not get the tuxedo object, throw TPENOENT
System.out.println("TPReplyException perrno = " + tpx.gettperrno()+" DETAILS "+tpx.gettperrordetail()+" getLocalizedMessage "+tpx.getLocalizedMessage()+" "+tpx.getCause());
tpx.printStackTrace();
}catch (TPException tpx1) {
// Could not get the tuxedo object, throw TPENOENT
System.out.println("TPReplyException perrno = " + tpx1.gettperrno()+" DETAILS "+tpx1.gettperrordetail()+" getLocalizedMessage "+tpx1.getLocalizedMessage()+" "+tpx1.getCause());
tpx1.printStackTrace();
}catch (NamingException ne) {
// Could not get the tuxedo object, throw TPENOENT
System.out.println("Could not get TuxedoConnectionFactory : " + ne.getMessage());
ne.printStackTrace();
}catch(Exception e){
System.out.println("Exception in getClientInfo ->"+e.getMessage());
e.printStackTrace();
return;
Output :
<getClientInfo called : 1, 10032600>
<About to call tpcall cnx = weblogic.wtc.gwt.TuxedoConnection@159d713>
<TPReplyException perrno = 6 DETAILS 0 getLocalizedMessage null null>
Edited by: user5653726 on 1 déc. 2008 04:06The tpcall function only supports an input parameter, an input buffer. In the input buffer you must send all the information the service needs. If you need send some data items you can use FML buffers, strings buffers, ... By example, with strings buffers in C:
#define NAME_LEN 16
#define LASTNAME_LEN 30
#define ADDRESS_LEN 30
#define AGE_LEN 3
typedef struct {
char name[NAME_LEN+1];
char lastname[LASTNAME_LEN+1];
char address[ADDRESS_LEN+1];
char age[AGE_LEN+1];
} persondat;
Client side:
main(int argc, char *argv[])
persondat *ptrperson;
char *sendbuff = NULL;
long sendlen = 0;
MAXBUFFIN_LEN = sizeof(persondat);
if((sendbuff = (char*)tpalloc("STRING", NULL, MAXBUFFIN_LEN+1)) == (char*)NULL) {
fprintf(stderr, "Error tpalloc(%s).\n", tpstrerror(tperrno));
tpterm();
exit(1);
ptrperson = (persondat*)sendbuff;
** Fill out the information.
sprintf(sendbuff->name, "%*s", NAME_LEN, "your name");
sprintf(sendbuff->lastname, "%*s", LASTNAME_LEN, "your lastname");
sprintf(sendbuff->address, "%*s", NAME_LEN, "your address");
sprintf(sendbuff->age, "%0*d", NAME_LEN, 37);
** Service call.
ret = tpcall("ADDPERSONSVC", (char*)sendbuff, 0, (char**)&recvbuff, &recvlen, (long)0);
if(ret == -1) {
fprintf(stderr, "Error tpcall(%s).\n", tpstrerror(tperrno));
tpterm();
exit(1);
Server side:
void ADDPERSONSVC(TPSVCINFO *rqst)
persondat *ptrperson;
ptrperson = (persondat*)rqst->data;
fprintf(fout, "Name: [%s].\n", ptrperson->name);
fprintf(fout, "Last Name: [%s].\n", ptrperson->lastname);
fprintf(fout, "Address: [%s].\n", ptrperson->address);
fprintf(fout, "Age: [%d].\n", atoi(ptrperson->age));
Regards. -
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
edI 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 -
Hi Experts
I am new to WTC and tudexo and trying to setup WTC and call a TOUPPER Tuxedo service from java. My Tuxedo is installed in Unix box and my Weblogic in windows . I am using weblogic 10. When i created a WTC server and try to fire up the weblogic I am gettign this exception
<Aug 29, 2008 9:16:35 AM GMT+05:30> <Error> <WTC> <BEA-180052> <Unable to cancel ON_STARTUP connection retry due to: Non-positive period..>
I tried looking up the message number to find somethign which may help I could not find much help on the site
BEA-180052
Error: Unable to cancel ON_STARTUP connection retry due to: exceptioninfo.
Description
Unable to cancel open connection retry object for ON_STARTUP connection policy.
Cause
Unable to delete timer service object for ON_STARTUP connection policy during connection termination.
Action
Contact BEA Customer Support.
Can you please guid me to the solution.
thanks and regards
GautamHey Gautam,
I was wondering if you found a resolution to this as I have the same issue in my wl/tux 10 environment (Both are installed on AIX). This was a working environment and then we went to bring it down and start it back up and this is the error we get. -
Problem with the NodeManager in Weblogic 10.0 MP1
Hi,
I have a problem starting the Nodemanager successfully. I have currently installed BEA Weblogic 10.0 MP1. The admin server is getting started successfully. When, I start the Nodemanager with the command:
startnodemanager -machine <hostname>, it neither gives the success message nor the error message. It comes to a stand still. Please see the below text, which appears on the Command prompt, when I run the nodemanager command.
Machine PUNITP128166D.ad.infosys.com
Listen Address: PUNITP128166D.ad.infosys.com
Listen Port: 8097
PID for D:\Ariba9r1\shared/bin/startNodeManager.cmd: 5980
D:\Ariba9r1\BuyerDev9r1\Server\bin>
D:\Ariba9r1\BuyerDev9r1\Server>set CLASSPATH=D:\BEA10\wlserver_10.0\server\lib\A
ribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib\tools.jar;D:\BEA10\wlserver_1
0.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;
D:\Ariba9r1\BuyerDev9r1\Server>chdir /d "D:\Ariba9r1\shared\nodemanager"
D:\Ariba9r1\shared\nodemanager>"D:\BEA10\jdk150_11\bin\java.exe" -client -Xms32m
-Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Xverify:none -classpath "D:\BE
A10\wlserver_10.0\server\lib\AribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib
\tools.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_1
0.0\server\lib\weblogic.jar;" -Dbea.home=D:\BEA10 -Djava.security.policy=D:\BEA1
0\wlserver_10.0\server\lib\weblogic.policy -DSavedLogsDirectory=D:\Ariba9r1\shar
ed\nodemanager\logs -DJavaHome=D:\BEA10\jdk150_11 -DTrustedHosts=D:\BEA10\wlserv
er_10.0\common\nodemanager\config\nodemanager.hosts -DListenAddress=PUNITP128166
D.ad.infosys.com -DListenPort=8097 -DReverseDnsEnabled=true -DLogToStderr=true -
DLogFile=D:\Ariba9r1\shared\nodemanager\nodemanager.log -DNodeManagerHome=D:\Ari
ba9r1\shared\nodemanager weblogic.NodeManager
After this, when I check the nodemanager status in Console, then the status appears as REACHABLE. Assuming, this to be the successfully message, I try to start the managed servers associated with the Machine/Server. But, it fails and there appears a message on the console with the status as 'Force Shutting Down' for this server.
When I check the logs, there seems to be some problem with the Nulll exception. Please see the below logs as it appears, its only a part of the logs
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040306> <JMS service is active now.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281003> <SAF Service has been initialized.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281002> <SAF Service has been started.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226120> <BEA-101128> <Initializing HTTP services.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101135> <buyerserver1 is the default Web server.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101052> <[HttpServer (defaultWebserver) name: buyerserver1] Initialized>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101129> <Initializing the Web application container.>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226198> <BEA-180046> <INFO: Logging service enabled.>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC license service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Task Manager instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC security service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Transaction service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <JMX> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226604> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://PUNITP128166D.ad.infosys.com:8050/jndi/weblogic.management.mbeanservers.runtime .>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226651> <BEA-000287> <Invoking startup class: ariba.j2ee.appserver.weblogic.Startup.startup(directory=D:\Ariba9r1\BuyerDev9r1\Server)>
####<Jun 28, 2010 4:20:27 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227229> <BEA-000288> <ariba.j2ee.appserver.weblogic.Startup reports: Changed directory to D:\Ariba9r1\BuyerDev9r1\Server>
####<Jun 28, 2010 4:20:27 PM IST> <Info> <Management> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227244> <BEA-141187> <Java system properties are defined as follows:
ariba.server.home = D:\Ariba9r1\BuyerDev9r1\Server
awt.toolkit = sun.awt.windows.WToolkit
bea.home = D:\BEA10
file.encoding = Cp1252
file.encoding.pkg = sun.io
file.separator = \
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBOracleJDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBDB2JDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBMssqlJDBC.zip;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes;D:\Ariba9r1\BuyerDev9r1\Server\classes\AribaJ2EE.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions;D:\BEA10\wlserver_10.0\server\lib\wls-api.jar
java.class.version = 49.0
java.endorsed.dirs = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed
java.ext.dirs = D:\BEA10\jdk150_11\jre\lib\ext
java.home = D:\BEA10\jdk150_11\jre
java.io.tmpdir = C:\DOCUME~1\suram_vishal\Local Settings\Temp\
java.library.path = D:\BEA10\jdk150_11\bin;.;C:\SYSROOT\system32;C:\SYSROOT;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\jdk150_11\bin;D:\BEA10\patch_wlw1001\profiles\default\native;D:\BEA10\patch_wls1001\profiles\default\native;D:\BEA10\wlserver_10.0\server\native\win\32;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\modules\org.apache.ant_1.6.5\bin;D:\BEA10\jdk150_11\jre\bin;D:\BEA10\jdk150_11\bin;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:/Ariba9r1/BuyerDev9r1/Server/bin/Win32;D:/Ariba9r1/BuyerDev9r1/Server/bin;C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\System32\Wbem;C:\Program Files\Java\jre1.5.0_06;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;D:\BEA10\wlserver_10.0\server\native\win\32\oci920_8;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\lib\Win32;D:\Ariba9r1\BuyerDev9r1\Server\internal\lib\Win32
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net
java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version = 1.5.0_11-b03
java.security.policy = D:\BEA10\wlserver_10.0\server\lib\weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.5
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
java.version = 1.5.0_11
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.5.0_11-b03
javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
org.xml.sax.driver = weblogic.apache.xerces.parsers.SAXParser
org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
os.arch = x86
os.name = Windows 2003
os.version = 5.2
path.separator = ;
sun.arch.data.model = 32
sun.boot.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\serializer.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xalan.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xercesImpl.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xml-apis.jar;D:\BEA10\jdk150_11\jre\lib\rt.jar;D:\BEA10\jdk150_11\jre\lib\i18n.jar;D:\BEA10\jdk150_11\jre\lib\sunrsasign.jar;D:\BEA10\jdk150_11\jre\lib\jsse.jar;D:\BEA10\jdk150_11\jre\lib\jce.jar;D:\BEA10\jdk150_11\jre\lib\charsets.jar;D:\BEA10\jdk150_11\jre\classes
sun.boot.library.path = D:\BEA10\jdk150_11\jre\bin
sun.cpu.endian = little
sun.desktop = windows
sun.io.unicode.encoding = UnicodeLittle
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = Cp1252
sun.management.compiler = HotSpot Client Compiler
sun.os.patch.level = Service Pack 2
user.country = US
user.dir = D:\Ariba9r1\BuyerDev9r1\Server
user.home = C:\Documents and Settings\suram_vishal
user.language = en
user.name = suram_vishal
user.timezone = Asia/Calcutta
vde.home = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\ldap
weblogic.Name = buyerserver1
weblogic.ReverseDNSAllowed = false
weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
weblogic.management.server = http://PUNITP128166D.ad.infosys.com:8099
weblogic.net.http.URLStreamHandlerFactory = ariba.util.net.URLStreamHandlerFactory
weblogic.nodemanager.ServiceEnabled = true
weblogic.security.SSL.ignoreHostnameVerification = true
weblogic.security.TrustKeyStore = DemoTrust
weblogic.system.BootIdentityFile = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\nodemanager\boot.properties
>
####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229510> <BEA-000365> <Server state changed to STANDBY>
####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229525> <BEA-000365> <Server state changed to STARTING>
####<Jun 28, 2010 4:20:29 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722229572> <BEA-149209> <Resuming.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230182> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_NEW to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_NEW to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
####<Jun 28, 2010 4:20:35 PM IST> <Warning> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-101162> <User defined listener ariba.server.ormsserver.ServletContextListener failed: java.lang.NullPointerException.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)
at ariba.j2ee.core.J2EEServer.initialize(J2EEServer.java:77)
at ariba.j2ee.core.AribaServletContextListener.contextInitialized(AribaServletContextListener.java:25)
at ariba.server.ormsserver.ServletContextListener.contextInitialized(ServletContextListener.java:26)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:168)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1744)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jun 28, 2010 4:20:35 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_ADMIN to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Jun 28, 2010 4:20:35 PM IST> <Alert> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Kindly help me in getting this resolved.
Thanks,
Vishal.The error appears to come from the ariba code. I suggest asking them.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53) -
JNDI conflict for WTC in cluster env
I found this error when starting more than one managed server in clustered environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.40 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
object you have bound from 161.215.254.41 is non clusterable and you have tried
to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable and you have
tried to bind more than once from two or more servers. Such objects can only deployed
from one server.>
Please help.Hi Salim,
Salim Djaffar wrote:
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
Salim Djaffar wrote:
I have a stateless ejb using this context to get the same JNDI namefrom tuxedo
connection factory. This ejb is deployed as clustered. I deployed thisejb into
many managed servers in the cluster. In other word every managed serverdeploys
this ejb.
I also have the web server configured with clustered plugin, but Iguess it has
nothing to do with it.
Isn't the wtc_config.xml stanza "WlsClusterName" a little misleadingsince it
does not support cluster at all ?Yes, it is kind of misleading. It is not used in WTC and will be removed
from dtd
(and document) in the future.
Besides in the admin console, I configured the WTC startup target to"cluster".
Is there any advise to overcome this problem ?I can't think of a good way to overcome this problem. One thing you
can do is to
target WTC to a WLS in the cluster. One drawback is that you have only
one WTC in
the cluster.
Honghsi
Does it mean I have to use RMI/IIOP to do the lookup to one particular server
for WTC ?No. The RMI/IIOP lookup is specific for CORBA NS lookup. It won't help you at
all.
>
Will WTC be available for clustered in the future ?There will be some changes to WTC that will make it possible for you to deploy WTC
instance on every WL server in the cluster. There are some administration (and
configuration) restrictions associate with it if you want to be able to do load
balancing and fail over.
Hong-Hsi :-)
>
>
Thanks.
Please help.
"A. Honghsi Lo" <[email protected]> wrote:
Hi Salim,
The current version of WTC will have this problem. Because the connection
factory is bound
to the same name in JNDI tre. However, the first WTC booted in the
WLS
cluster should
still be available to use.
BTW, I am interested in knowing how you use WTC currently, and howyou
plan to use in the
future.
Honghsi
Salim Djaffar wrote:
I found this error when starting more than one managed server in
clustered
environment.
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.40 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoConnection in the
JNDI
tree. The
object you have bound from 161.215.254.41 is non clusterable and
you
have tried
to bind more than once from two or more servers. Such objects can
only
deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.40 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
<Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
You
tried to bind
an object under the name tuxedo.services.TuxedoCorbaConnection in
the
JNDI tree.
The object you have bound from 161.215.254.41 is non clusterable
and
you have
tried to bind more than once from two or more servers. Such objectscan only deployed
from one server.>
Please help. -
Hi,
I am using Form Builder 6.0.8.11.3 .
I have a problem with the Trigger Level Execution Hierarchy Property.
I have when-new-item-instance trigger set at Item level and at the block level.The Item level triger has it's execution hierarchy set to after.
But still the Item level trigger fires first and then the block level trigger fires whereas it shud be the other way round.
Is it a Version Bug or anything else??
Pls help
AlfredWe do have a fix in this area and it was for WTC to TUX6.5.
I believe this is a padding problem. I was expect if you send
101 bytes and tuxedo will get 104 byte. Sending 100 bytes and tuxedo
receives 101, 102, or 103 bytes is strange to me. Anyway, please contact
with BEA customer support to create a CR and a test case for this. At
this moment, I do not know where is the problem. It could be in tuxedo
side.
Thanks
linsondean wrote:
Are you saying that you send 100 bytes, but when the server receives
the message,
the TPSVCINFO->len value is 101?Right! sometimes it may be 102 or 103. and befor tpcall, the length of bytes is
still 100.
my code:
data = new TypedCArray(baInput.length);
// for example: length = 100
data.carray = baInput;
// my data, byte[] type
System.out.println("data carray length:"+ data.carray.length);
// length =100
System.out.println("data length:"+ data.sendSize);
// length =100
try {
reply = tc.tpcall(svcName, data, 0);
} catch (TPReplyException tre) {
throw tre;
however, the tuxedo server get 101(102 or 103) bytes.
And if the tuxedo server reply 100 bytes, i get 100!! -
Here are some common WTC questions and answers:
Q1: What is the transaction story for WTC between WLS and Tuxedo and how
does it differ from Jolt?
A1: In version 1.0 of WTC transactions may be started in WLS and will
"infect" Tuxedo with the same transaction. That implies that there is one
and only one commit coordinator, and that is in WLS. In version 1.0 of WTC
transactions originating
in Tuxedo via WTC is not supported. In version 1.1 of WTC transactions from
Tuxedo into WLS via WTC can be used, but only in Beta mode, as we will not
have done the required QA of "inbound" transactions. In order to use
inbound transactions in WTC 1.1 you will need to turn on the use of beta
features with an attribute called "UseBetaInboundTransactions" on the WTC
Startup class
in WLS.
This differs from Jolt in that while Jolt can start transactions in Tuxedo,
these transactions are not coordinated with anything in WLS. Hence it is
impossible to do a 2 phase commit which involves WLS resources and Tuxedo
resources with Jolt. Since Jolt does not have any means of invoking WLS
services transactions in that direction do not make sense.
Q2. How does the security mapping work?
A2: WLS and Tuxedo can share the same set of users (though they may be
administered differently in the two systems) and the users can propagate
their credentials from one system to the other. For example, if John Wells
logs into WLS then the services which he invokes in Tuxedo will have all of
the ACL permissions of John Wells as defined on the Tuxedo side.
Furthermore, if Jolene User logs into Tuxedo then any resources she attempts
to access in WLS via WTC will be checked against Jolene User's rights in WLS
land.
In order to accomplish this, a few things need to be set up:
1. You must be using Tuxedo 7.1 or Tuxedo 8.0 for this to work. Tuxedo 6.5
did not have the security infrastructure necessary to make this happen.
2. In your BDMCONFIG on the Tuxedo side you will need to set ACL_POLICY and
CREDENTIAL_POLICY to "GLOBAL" for the WLS remote domain. ACL_POLICY
controls whether or not a domain accepts credentials coming from a remote
domain and CREDENTIAL_POLICY controls whether or not we send credentials to
a remote domain. (In Tuxedo 7.1 there was no CREDENTIAL_POLICY - we always
sent the credentials to the remote domain).
3. In your BDMCONFIG on the WLS side you must likewise specify <ACL_POLICY>
and <CREDENTIAL_POLICY> to be "GLOBAL."
4. On the WLS side you must also configure a <TpUsrFile> which will point
to a file of the exact same format as the tpusr file generated by the
various Tuxedo commands to add and delete users. (Which also happens to be
of the same format as the unix /etc/passwd file). WTC needs this file
because in WLS users do not have user identification numbers or group
identification numbers. Hence we need a way to map WLS users into the
standard Tuxedo UID/GID appkey.
Voila! You have now set up your system such that users logged into either
system can be given access privelidges in the other system. This is known
as single sign-on. We are currently working on a way to better integrate
the two user databases between WLS and Tuxedo, and one day we will have
single administration and single-sign on!
Q3: How is the performance of WTC?
A3: Obviously, results will vary based on your machine, CPU, application
(i.e., transactions/no transactions) etc...
However, in the performance lab here we have seen WTC perform at levels that
nearly equal Tuxedo in a similar configuration.
Q4: What fail-over/fail-back mechanisms are there in WTC?
A4: WTC has many of the same fail-over fail-back mechanisms which /T
domains had. Any service can be offered by multiple remote domains, and if
a domain link is down we will attempt all of the backup domains. In /T
domains there was a limit of three backup remote domains, but in WTC there
is no limit to the number of backup domains you can configure for a service.
Furthermore, we support the connection policies of ON_STARTUP, ON_DEMAND and
INCOMING_ONLY. If the policy is ON_STARTUP then you can also configure a
retry interval and max-retries. We will attempt to connect to ON_STARTUP
remote domains every retry interval for a maximum number of retries before
giving up. If a domain is configured as ON_STARTUP or INCOMING_ONLY and the
connection is not currently established then no services will be routed to
that remote domain.
Q5: What support features are available in WTC?
A5: WTC has a tracing feature which can be enabled dynamically. If a
customer reports a problem, support will likely ask the customer to turn
tracing on and send a log file. This tracing facility has several levels of
severity and can also help debug WTC applications. It is turned on by
setting TraceLevel in the WTC startup class. The following are the defined
levels:
10000 - TBRIDGE Input/Output
15000 - TBRIDGE extra information
20000 - Gateway Input/Output (this will trace the ATMI verbs)
25000 - Gateway extra information
50000 - JATMI Input/Output (this will trace the low-level jatmi calls)
55000 - JATMI extra information
60000 - CORBA Input/Output (this will trace CORBA calls)
65000 - CORBA extra information
Q6: Will Jolt be deprecated?
A6: No. There are some features of Jolt that are not covered by WTC. For
example, the Jolt registry API are not supported by WTC. Furthermore WTC
must run in conjunction with WLS, while Jolt can be run from Applets or from
free-standing Java applications.
Q7: What about JCA? Is WTC a JCA adapter?
A7: WTC is not a JCA adapter. JCA does not define semantics for inbound
invokations into the JCA container, but WTC allows for Tuxedo clients to
invoke WLS EJBs. However, the jATMI object interactions are based on the
JCA client model. BEA is currently evaluating several JCA strategies for
connections into Tuxedo.
Q8. What versions of Tuxedo are supported?
A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which adds
CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
release of both of these products we will certify WTC with Tuxedo 7.1.
However, the version of Tuxedo 7.1 you will need to have will be Tuxedo 7.1
after RP 89.
Q9. What WLS Releases will be supported?
A9. WTC 1.0 will be certified on WLS 6.0 SP2, WTC 1.1 will be bundled with
WLS 6.1
Q10. How will WTC be packaged?
A10. WTC 1.0 will be a separately downloaded binary (one for unix, one for
NT) that the user will have to install and configure in his/her WLS
environment. (Configuration will consist of putting the jatmi.jar file into
the classpath (as well as the normal BDMCONFIG configuration, of course)).
WTC 1.1 will be bundled right in there with the WLS 6.1.
John Wells (Aziz)
[email protected]
[email protected]References:
http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/28f02631-2291-4f8c-875a-4fa5397536ee/
Amalaraja Fernando,
SharePoint Architect
This post is provided "AS IS" with no warrenties and confers no rights. -
Here are some common WTC questions and answers:
Q1: What is the transaction story for WTC between WLS and Tuxedo and how
does it differ from Jolt?
A1: In version 1.0 of WTC transactions may be started in WLS and will
"infect" Tuxedo with the same transaction. That implies that there is one
and only one commit coordinator, and that is in WLS. In version 1.0 of WTC
transactions originating
in Tuxedo via WTC is not supported. In version 1.1 of WTC transactions from
Tuxedo into WLS via WTC can be used, but only in Beta mode, as we will not
have done the required QA of "inbound" transactions. In order to use
inbound transactions in WTC 1.1 you will need to turn on the use of beta
features with an attribute called "UseBetaFeatures" on the WTC Startup class
in WLS.
This differs from Jolt in that while Jolt can start transactions in Tuxedo,
these transactions are not coordinated with anything in WLS. Hence it is
impossible to do a 2 phase commit which involves WLS resources and Tuxedo
resources with Jolt. Since Jolt does not have any means of invoking WLS
services transactions in that direction do not make sense.
Q2. How does the security mapping work?
A2: WLS and Tuxedo can share the same set of users (though they may be
administered differently in the two systems) and the users can propagate
their credentials from one system to the other. For example, if John Wells
logs into WLS then the services which he invokes in Tuxedo will have all of
the ACL permissions of John Wells as defined on the Tuxedo side.
Furthermore, if Jolene User logs into Tuxedo then any resources she attempts
to access in WLS via WTC will be checked against Jolene User's rights in WLS
land.
In order to accomplish this, a few things need to be set up:
1. You must be using Tuxedo 7.1 or Tuxedo 8.0 for this to work. Tuxedo 6.5
did not have the security infrastructure necessary to make this happen.
2. In your BDMCONFIG on the Tuxedo side you will need to set ACL_POLICY and
CREDENTIAL_POLICY to "GLOBAL" for the WLS remote domain. ACL_POLICY
controls whether or not a domain accepts credentials coming from a remote
domain and CREDENTIAL_POLICY controls whether or not we send credentials to
a remote domain. (In Tuxedo 7.1 there was no CREDENTIAL_POLICY - we always
sent the credentials to the remote domain).
3. In your BDMCONFIG on the WLS side you must likewise specify <ACL_POLICY>
and <CREDENTIAL_POLICY> to be "GLOBAL."
4. On the WLS side you must also configure a <TpUsrFile> which will point
to a file of the exact same format as the tpusr file generated by the
various Tuxedo commands to add and delete users. (Which also happens to be
of the same format as the unix /etc/passwd file). WTC needs this file
because in WLS users do not have user identification numbers or group
identification numbers. Hence we need a way to map WLS users into the
standard Tuxedo UID/GID appkey.
Voila! You have now set up your system such that users logged into either
system can be given access privelidges in the other system. This is known
as single sign-on. We are currently working on a way to better integrate
the two user databases between WLS and Tuxedo, and one day we will have
single administration and single-sign on!
Q3: How is the performance of WTC?
A3: Obviously, results will vary based on your machine, CPU, application
(i.e., transactions/no transactions) etc...
However, in the performance lab here we have seen WTC perform at levels that
nearly equal Tuxedo in a similar configuration. The performance is equal to
or better than Jolt, and will scale much better than Jolt because of the
concentration of network bandwidth.
Q4: What fail-over/fail-back mechanisms are there in WTC?
A4: WTC has many of the same fail-over fail-back mechanisms which /T
domains had. Any service can be offered by multiple remote domains, and if
a domain link is down we will attempt all of the backup domains. In /T
domains there was a limit of three backup remote domains, but in WTC there
is no limit to the number of backup domains you can configure for a service.
Furthermore, we support the connection policies of ON_STARTUP, ON_DEMAND and
INCOMING_ONLY. If the policy is ON_STARTUP then you can also configure a
retry interval and max-retries. We will attempt to connect to ON_STARTUP
remote domains every retry interval for a maximum number of retries before
giving up. If a domain is configured as ON_STARTUP or INCOMING_ONLY and the
connection is not currently established then no services will be routed to
that remote domain.
Q5: What support features are available in WTC?
A5: WTC has a tracing feature which can be enabled dynamically. If a
customer reports a problem, support will likely ask the customer to turn
tracing on and send a log file. This tracing facility has several levels of
severity and can also help debug WTC applications. It is turned on by
setting TraceLevel in the WTC startup class. The following are the defined
levels:
10000 - TBRIDGE Input/Output
15000 - TBRIDGE extra information
20000 - Gateway Input/Output (this will trace the ATMI verbs)
25000 - Gateway extra information
50000 - JATMI Input/Output (this will trace the low-level jatmi calls)
55000 - JATMI extra information
60000 - CORBA Input/Output (this will trace CORBA calls)
65000 - CORBA extra information
Q6: Will Jolt be deprecated?
A6: No. There are some features of Jolt that are not covered by WTC. For
example, the Jolt registry API are not supported by WTC. Furthermore WTC
must run in conjunction with WLS, while Jolt can be run from Applets or from
free-standing Java applications.
Q7: What about JCA? Is WTC a JCA adapter?
A7: WTC is not a JCA adapter. JCA does not define semantics for inbound
invokations into the JCA container, but WTC allows for Tuxedo clients to
invoke WLS EJBs. However, the jATMI object interactions are based on the
JCA client model. BEA is currently evaluating several JCA strategies for
connections into Tuxedo.
John Wells (Aziz)
[email protected]
[email protected]Q8. What versions of Tuxedo are supported?
A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which adds
CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
release of both of these products we will certify WTC with Tuxedo 7.1.
However, the version of Tuxedo 7.1 you will need to have will be Tuxedo 7.1
after a certain patch level, which I don't know the number of yet. I will
attempt to keep the public informed about which patch level will be required
in Tuxedo 7.1
Q9. What WLS Releases will be supported?
A9. WTC 1.0 will be certified on WLS 6.0 SP2, WTC 1.1 will be bundled with
WLS SilverSword release (6.1?)
Q10. How will WTC be packaged?
A10. WTC 1.0 will be a separately downloaded binary (one for unix, one for
NT) that the user will have to install and configure in his/her WLS
environment. (Configuration will consist of putting the jatmi.jar file into
the classpath (as well as the normal BDMCONFIG configuration, of course)).
WTC 1.1 will be bundled right in there with the WLS SilverSword release.
Q11. When will WTC go live (no more beta)?
A11. This is a question for Jeff Cutler, but my impression is that WTC 1.0
will be shipped in the same time-frame as the Tuxedo 8.0 release and
obviously (see A10) WTC 1.1 will be shipped with WLS SilverSword.
John Wells (Aziz)
[email protected] -
Hi, I am evaluating the weblogic 6.1 server. I have posted my question to
support.bea.com and weblogic.developer.interest.wtc but no reply. Thank you.
Problem description
I used Server - Sparc 20(32bit kernel) with 512 MB RAM and 1GB swap space to
install Weblogic server 6.1 sp1.
What I need to do is to connect Weblogic with our existing Tuxedo 6.5 or
vice versa. In order to test the connection between the two products, I will
call TOUPPER at TUXEDO 6.5.
I followed the document from
/wls/samples/examples/wtc/atmi/simpapp/package-summary.html to configure
WTC. When I run "run.sh aaa", below error message displayed:
setSessionContext called
ejbCreate called
toupper called, converting aaa
About to call tpcall
tpcall threw TPException TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could
not get a Tuxedo session
below are the configuration files for your reference:
ubbconfig
#Skeleton UBBCONFIG file for the TUXEDO Simple Application.
#Replace the <bracketed> items with the appropriate values.
*RESOURCES
IPCKEY 41828
#Example:
#IPCKEY 123456
#DOMAINID simpapp
MASTER REL4_DC
MAXACCESSERS 50
MAXSERVERS 25
MAXSERVICES 50
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
APPDIR="/software/tuxedo6.5/sunos53.sc30/apps/simpapp"
TUXCONFIG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/tuxconf
ig"
TUXDIR="/software/tuxedo6.5/sunos53.sc30"
#Example:
# APPDIR="/home/me/simpapp"
# TUXCONFIG="/home/me/simpapp/tuxconfig"
# TUXDIR="/usr/tuxedo"
"itdrnd01" LMID="REL4_DC"
#Example:
#beatux LMID=simple
*GROUPS
GROUP1
LMID="REL4_DC" GRPNO=1 OPENINFO=NONE
GROUP2
LMID="REL4_DC" GRPNO=2 OPENINFO=NONE
*SERVERS
DEFAULT:
CLOPT="-A"
simpserv SRVGRP=GROUP1 SRVID=1
DMADM SRVGRP=GROUP2 SRVID=1
GWADM SRVGRP=GROUP2 SRVID=2
GWTDOMAIN SRVGRP=GROUP2 SRVID=3
*SERVICES
TOUPPER
dmconfig
*DM_RESOURCES
VERSION=U22
*DM_LOCAL_DOMAINS
txndom01 GWGRP=GROUP2
TYPE=TDOMAIN
DOMAINID="REL4_DC"
BLOCKTIME=20
MAXDATALEN=56
MAXRDOM=89
DMTLOGDEV="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/DMTLOG"
AUDITLOG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/AUDITLOG"
DMTLOGNAME="DMTLOG"
*DM_REMOTE_DOMAINS
TDOM2 TYPE=TDOMAIN
DOMAINID="TDOM2"
*DM_TDOMAIN
#txndom01 NWADDR="0x0002a3660a610232"
txndom01 NWADDR="//10.97.2.50:41830"
NWDEVICE="/dev/tcp"
#TDOM2 NWADDR="0x00021b590a610236"
TDOM2 NWADDR="//10.97.2.54:7007"
NWDEVICE="/dev/tcp"
*DM_REMOTE_SERVICES
TOLOWER RDOM="TDOM2"
bdmconfig.xml
<?xml version="1.0"?>
<!DOCTYPE WTC_CONFIG SYSTEM
"file:/software/bea/wlserver6.1/config/wlsdomain/wtc
_config.dtd">
<!--Java and XML-->
<WTC_CONFIG>
<BDMCONFIG>
<T_DM_LOCAL_TDOMAIN AccessPoint="TDOM2">
<WlsClusterName>Coolio</WlsClusterName>
<AccessPointId>TDOM2</AccessPointId>
<Type>TDOMAIN</Type>
<Security>NONE</Security>
<ConnectionPolicy>ON_DEMAND</ConnectionPolicy>
<BlockTime>30</BlockTime>
<NWAddr>//10.97.2.54:7007</NWAddr>
<!-- Example address: //wlsdomain.com:20304 -->
</T_DM_LOCAL_TDOMAIN>
<T_DM_REMOTE_TDOMAIN AccessPoint="txndom01">
<LocalAccessPoint>TDOM2</LocalAccessPoint>
<AccessPointId>REL4_DC</AccessPointId>
<Type>TDOMAIN</Type>
<NWAddr>//10.97.2.50:41830</NWAddr>
<Interoperate>Yes</Interoperate>
<!-- Example address: //wlsdomain.com:20305 -->
</T_DM_REMOTE_TDOMAIN>
<T_DM_EXPORT ResourceName="TOLOWER"
LocalAccessPoint="TDOM2">
<EJBName>tuxedo.services.TOLOWERHome</EJBName>
</T_DM_EXPORT>
<T_DM_IMPORT
ResourceName="TOUPPER"
LocalAccessPoint="TDOM2"
RemoteAccessPointList="txndom01">
<TranTime>600</TranTime>
</T_DM_IMPORT>
</BDMCONFIG>
</WTC_CONFIG>Hi.
First, I'll say that I know very little about WTC. However, from the following
link I don't know that WTC is supported with WLS 6.1:
http://e-docs.bea.com/wtc/wtc10/notes/WTC_ReleaseNotes_New.html#1109022
This link says it's only supported with WLS 6.0 sp2. I suggest you download
this version and try again. If you are still having problems then you should
open a case with support.
Regards,
Michael
Neo Gigs wrote:
Hi, I am evaluating the weblogic 6.1 server. I have posted my question to
support.bea.com and weblogic.developer.interest.wtc but no reply. Thank you.
Problem description
I used Server - Sparc 20(32bit kernel) with 512 MB RAM and 1GB swap space to
install Weblogic server 6.1 sp1.
What I need to do is to connect Weblogic with our existing Tuxedo 6.5 or
vice versa. In order to test the connection between the two products, I will
call TOUPPER at TUXEDO 6.5.
I followed the document from
/wls/samples/examples/wtc/atmi/simpapp/package-summary.html to configure
WTC. When I run "run.sh aaa", below error message displayed:
setSessionContext called
ejbCreate called
toupper called, converting aaa
About to call tpcall
tpcall threw TPException TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could
not get a Tuxedo session
below are the configuration files for your reference:
ubbconfig
#Skeleton UBBCONFIG file for the TUXEDO Simple Application.
#Replace the <bracketed> items with the appropriate values.
*RESOURCES
IPCKEY 41828
#Example:
#IPCKEY 123456
#DOMAINID simpapp
MASTER REL4_DC
MAXACCESSERS 50
MAXSERVERS 25
MAXSERVICES 50
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
APPDIR="/software/tuxedo6.5/sunos53.sc30/apps/simpapp"
TUXCONFIG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/tuxconf
ig"
TUXDIR="/software/tuxedo6.5/sunos53.sc30"
#Example:
# APPDIR="/home/me/simpapp"
# TUXCONFIG="/home/me/simpapp/tuxconfig"
# TUXDIR="/usr/tuxedo"
"itdrnd01" LMID="REL4_DC"
#Example:
#beatux LMID=simple
*GROUPS
GROUP1
LMID="REL4_DC" GRPNO=1 OPENINFO=NONE
GROUP2
LMID="REL4_DC" GRPNO=2 OPENINFO=NONE
*SERVERS
DEFAULT:
CLOPT="-A"
simpserv SRVGRP=GROUP1 SRVID=1
DMADM SRVGRP=GROUP2 SRVID=1
GWADM SRVGRP=GROUP2 SRVID=2
GWTDOMAIN SRVGRP=GROUP2 SRVID=3
*SERVICES
TOUPPER
dmconfig
*DM_RESOURCES
VERSION=U22
*DM_LOCAL_DOMAINS
txndom01 GWGRP=GROUP2
TYPE=TDOMAIN
DOMAINID="REL4_DC"
BLOCKTIME=20
MAXDATALEN=56
MAXRDOM=89
DMTLOGDEV="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/DMTLOG"
AUDITLOG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/AUDITLOG"
DMTLOGNAME="DMTLOG"
*DM_REMOTE_DOMAINS
TDOM2 TYPE=TDOMAIN
DOMAINID="TDOM2"
*DM_TDOMAIN
#txndom01 NWADDR="0x0002a3660a610232"
txndom01 NWADDR="//10.97.2.50:41830"
NWDEVICE="/dev/tcp"
#TDOM2 NWADDR="0x00021b590a610236"
TDOM2 NWADDR="//10.97.2.54:7007"
NWDEVICE="/dev/tcp"
*DM_REMOTE_SERVICES
TOLOWER RDOM="TDOM2"
bdmconfig.xml
<?xml version="1.0"?>
<!DOCTYPE WTC_CONFIG SYSTEM
"file:/software/bea/wlserver6.1/config/wlsdomain/wtc
_config.dtd">
<!--Java and XML-->
<WTC_CONFIG>
<BDMCONFIG>
<T_DM_LOCAL_TDOMAIN AccessPoint="TDOM2">
<WlsClusterName>Coolio</WlsClusterName>
<AccessPointId>TDOM2</AccessPointId>
<Type>TDOMAIN</Type>
<Security>NONE</Security>
<ConnectionPolicy>ON_DEMAND</ConnectionPolicy>
<BlockTime>30</BlockTime>
<NWAddr>//10.97.2.54:7007</NWAddr>
<!-- Example address: //wlsdomain.com:20304 -->
</T_DM_LOCAL_TDOMAIN>
<T_DM_REMOTE_TDOMAIN AccessPoint="txndom01">
<LocalAccessPoint>TDOM2</LocalAccessPoint>
<AccessPointId>REL4_DC</AccessPointId>
<Type>TDOMAIN</Type>
<NWAddr>//10.97.2.50:41830</NWAddr>
<Interoperate>Yes</Interoperate>
<!-- Example address: //wlsdomain.com:20305 -->
</T_DM_REMOTE_TDOMAIN>
<T_DM_EXPORT ResourceName="TOLOWER"
LocalAccessPoint="TDOM2">
<EJBName>tuxedo.services.TOLOWERHome</EJBName>
</T_DM_EXPORT>
<T_DM_IMPORT
ResourceName="TOUPPER"
LocalAccessPoint="TDOM2"
RemoteAccessPointList="txndom01">
<TranTime>600</TranTime>
</T_DM_IMPORT>
</BDMCONFIG>
</WTC_CONFIG>--
Michael Young
Developer Relations Engineer
BEA Support -
What the best way to call twenty tuxedo domains from one weblogic server use WTC
I need to call twenty tuxedo domains from one weblogic server use
WTC. the Service be called in the twenty tuxdo domains are same, do I need to
write twenty EJB in the weblogic server to call the same service? who have good
adea to deal with this problem?Hi,
I have a question on the second case. When the client doesn't care of which
Tuxedo domain it is hitting. What happens if one of the Tux domain is down ? What
happens to the client request to that domain ?
Another question is lets say i have a Tuxedo configuration as MP mode( Multi
machine mode) how does WTC load balance between the Tuxedo domains.
Thanks,
Srinivas
"A. Honghsi Lo" <[email protected]> wrote:
Hi xcjing,
One way to handle your needs is to use local service name to remote
reservice name translation. For instance,
(in 6.1,6.0 WLS)
<T_DM_IMPORT ResourceName="TOUPPER1" LocalAccessPoint="WTC"
RemoteAccessPointList="TUX-DOM1">
<RemoteName>TOUPPER</RemoteName>
</T_DM_IMPORT>
<T_DM_IMPORT ResourceName="TOUPPER2" LocalAccessPoint="WTC"
RemoteAccessPointList="TUX-DOM2">
<RemoteName>TOUPPER</RemoteName>
</T_DM_IMPORT>
<T_DM_IMPORT ResourceName="TOUPPER3" LocalAccessPoint="WTC"
RemoteAccessPointList="TUX-DOM3">
<RemoteName>TOUPPER</RemoteName>
</T_DM_IMPORT>
etc
With this configuration if your client have to call "TOUPPER" service
in
TUX-DOM1 then you code your client to call "TOUPPER1" and the request
will be routed to TUX-DOM1. The same way for request has to go to
TUX-DOM3, your client calls "TOUPPER3" service and WTC will route it
to
TUX-DOM3. In this remote name translation you may have to write 20 EJB
although they are almost the same. However, if your EJB can analyze
your client input to decide which Remote Tuxedo Domain to send the
service request to then you probably only need one EJB.
In the case that your client does not care which remote Tuxedo Domain
provides the service then adding
<T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
RemoteAccessPointList="TUX-DOM1">
<RemoteName>TOLOWER</RemoteName>
</T_DM_IMPORT>
<T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
RemoteAccessPointList="TUX-DOM2">
<RemoteName>TOLOWER</RemoteName>
</T_DM_IMPORT>
<T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
RemoteAccessPointList="TUX-DOM3">
<RemoteName>TOLOWEr</RemoteName>
</T_DM_IMPORT>
etc
Will load balance your client "TOLOWER" service request among your 20
remote Tuxedo Domain.
However, there is a bug in WTC that causes the Remote Service Name
translation functionality not working properly. It is fixed in the
upcoming release of WLS.
Honghsi :-)
xcjing wrote:
Thank you very much! But I still have question, give an example,
twenty Tuxedo domain is named domain1,domain2,....domain20. The
same Tuxedo Service: TOUPPER is deploy on those twenty Tuxedo domains,some time
I need call the TOUPPER Service on domain1,saome time I need call theTOUPPER
Service on domain3 or
other domain depend on the input from client. you mean I need to importThe TOUPPER
Service from twenty Tuxedo domains in the console,then write one EJBto call the
TOUPPER Service,but how can the EJB know which Tuxedo domain's TOUPPERto call
from?
Thank you!
"A. Honghsi Lo" <[email protected]> wrote:
hi xcjing,
You don't have to write 20 beans or deploy 20 beans because there
are
20
remote Tuxedo TDomain you need get the service from. Of course, WLSand
WTC does not prohibit you from doing it though. Whether you need20
beans or not depend more on you architecture.
To access 20 remote Tuxedo Domain from one single WLS with singleWTC
you can configure 20 remote Tuxedo Domain in the BDMCONFIG (6.1,6.0)
or
from the console (7.0). You import 20 services one from each remote
Tuxedo domain. You write one bean, and deploy one bean. Your WLS
clients will be able to access THE ejb, the EJB will access the WTC
service, and WTC will load balanced the service requests among the20
remote Tuxedo Domain.
Regards,
honghsi :-)
xcjing wrote:
I need to call twenty tuxedo domains from one weblogic server use
WTC. the Service be called in the twenty tuxdo domains are same,
do
I need to
write twenty EJB in the weblogic server to call the same service?
who
have good
adea to deal with this problem? -
Enqueued messages with Tuxedo /Q and WTC
Hi everyone,
I have a Tuxedo /Q that through a WTC puts messages in a JMS queue in
a Weblogic. During a period with heavy load ( +- 200 messages per
second), the total messages in the destination queue starts to
increase, deprecating the application response time.
Some configurations
• The queues are in non persistent mode
• The connection policy in WTC and Tuxedo Domain is ON_STARTUP
• WTC with Retry Interval and Block Time 60, keep alive and
keep alive wait 0
• Tuxedo 8, Weblogic 10g in RedHat 5
Some analysis information
• There is available threads in the Weblogic to process the
messages, so it isn’t the problem.
• There isn’t any enqueued packets in the network between
tuxedo and Weblogic server
• There is low use of CPU and memory in all machines
I think that WTC connector hasn’t sufficient throughput to process
the messages in the destination queue.
Any suggestions????
Thanks!Hi,
If you are saying you are using a tBridge (JMS bridge component of WTC) redirection to take messages from Tuxedo /Q and place them on a JMS queue, then the problem is that only a single thread will process the redirection. In other words, a single thread is started to perform tpdequeue() operations on the Tuxedo /Q queue, and then put the message on a JMS queue. If you need more throughput than a single thread offers, you will need to add another redirection in the WTC configuration.
Regards,
Todd Little
Oracle Tuxedo Chief Architect
Maybe you are looking for
-
CoA issues between ISE and 3750x
We are having an issue using the cisco ise 1.1.2 and a 3750x (Version 12.2(58)SE2) When the radius sends a reauthentication CoA message to the switch, the switch responds with a 'session contect not found' reply. I have upgraded the code to the lates
-
No wireless when starting in Safe mode - iMac 21.5 i5 OS X 10.6.7
On my new iMac i5 21.5" (2011) system when I startup in Safe mode the Airport driver isn't available. On my old iMac 24" system I did have wireless networking when booting to Safe mode. Is this expected behavior with the new iMac i5 under 10.6.7?
-
I have been working on a movie project and I saved my work many times. Before I closed the application I saved it again to my desktop just be on the safe side. When I opend Imovie to continue work on my project, the file could not open some of my cli
-
SAP Note 1614681 - ESI monthly report for filing details of ESIable employe
Any one implemented this SAP Note While doing the manual steps mentioned in SAP Note 1614681 - ESI monthly report for filing details of ESIable employees . we found some difficulties. Please let me know the steps that you followed while implementing
-
Sdo_pc pointcloud blob in SDO_PC_BLK type
docs say: POINTS BLOB BLOB containing the points. Consists of an array of points, with the following information for each point: ■ d 8-byte IEEE doubles, where d is the PC_TOT_ DIMENSIONS value ■ 4-byte big-endian integer for the BLK_ID value ■ 4-byt