AquaLogic WTC problem

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.
JP

Hi 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

Similar Messages

Aqualogic WSDL problem!

Hi,
We have registered few proxy services in Aqualogic Service Bus. We can access then and get their WSDL by URL.
http://<myserver>:7001/services/service1?wsdl
The biggest problem is this: some of services do not return HTTP Content-Type header, but some do. And when we enter URL address to WSDL file in client software, it throws exception - not content type set.
For instance:
WebService1 returns:
Date: Mon, 14 Jul 2008 16:18:05 GMT
Transfer-Encoding: chunked
Content-Type: text/xml
X-Powered-By: Servlet/2.5 JSP/2.1
200 OK
WebService2 returns:
Date: Mon, 14 Jul 2008 16:18:56 GMT
Transfer-Encoding: chunked
X-Powered-By: Servlet/2.5 JSP/2.1
200 OK
I have exceptions with WebSercice2. Is this a bug og Aqualogic service bus or must I configure something to return Content-type? If I enter direct URL to service WSDL file, not to a proxy service WSDL file, content type is returned correctly...
Please help me to fix this problem.

Hello,
What kind of exception did you get?
Is it null pointer exception for syncProvider or you have just missed line of code for syncProvider initialization?
Dmitry

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

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,
MVS

If 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

BEA Aqualogic Service Registry Installation Problem

I am getting the following error while installing the Aqualogic Service Registry.
[echo] Building scripts ...
[echo] Platform is Windows
[echo] Preparing 'admin' account ...
[echo] Preparing account_list ...
[echo] Preparing permission_list ...
[echo] Preparing approval management ...
[java] java.lang.ExceptionInInitializerError: java.lang.SecurityException: Cannot set up certs for trusted CAs
[java]      at javax.crypto.b.<clinit>([DashoPro-V1.2-120198])
[java]      at javax.crypto.KeyGenerator.getInstance([DashoPro-V1.2-120198])
[java]      at com.systinet.uddi.config.CipherHelper.<init>(CipherHelper.java:82)
[java]      at com.systinet.uddi.config.CipherHelper.getApiInstance(CipherHelper.java:51)
[java]      at com.systinet.uddi.config.XMLConfigurable.<clinit>(XMLConfigurable.java:22)
[java]      at com.systinet.uddi.config.XMLConfigurator.createConfigurable(XMLConfigurator.java:23)
[java]      at com.idoox.config.xml.XMLConfigurator.getConfigurable(XMLConfigurator.java:113)
[java]      at com.idoox.config.xml.XMLConfigurator.init(XMLConfigurator.java:423)
[java]      at com.idoox.config.xml.XMLConfigurator.init(XMLConfigurator.java:333)
[java]      at com.systinet.uddi.config.ConfigHelper.addConfig(ConfigHelper.java:341)
[java]      at com.systinet.uddi.config.ConfigHelper.init(ConfigHelper.java:84)
[java]      at com.systinet.uddi.util.Register.main(Register.java:58)
[java] Exception in thread "main"
Java returned: 1
Installation failed. If accessible, see "D:\bearegistry20\log\install.log".
To correct installation parameters and resume installation click Recover.
You may also want to consult Service Registry dev2dev page at http://dev2dev.bea.com/.
I know the problem is due to old JCE installation.I have downloaded the JCE 1.2.2 and tried to solve the problem.But I could not solve the problem.I will be highly grateful if somebody can show me how to solve the problem.I am having SUN JDK 1.4.2.

I'm facing the exact same problem.
<Nov 2, 2007 3:05:14 PM MET> <Error> <HTTP> <BEA-101216> <Servlet: "Registry Servlet" failed to preload on startup in Web application: "registry.war".
I'm curious to get an idea what is causing it.
Looks like a config file with some touch in the security space is read but the read ends prematurely.
Thanks
Falk

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,
Aruna

Hi 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:06

The 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.

Aqualogic ServiceBus tutorial, add namespace problem?

Hi,
I am playing around with Aqualogic ServiceBus and thought I would go
through tutorials just to see if there is something that I don't realize
from document (http://e-docs.bea.com/alsb/docs20/pdf/tutorial.pdf).
On page 5-13 there is step where you are supposed to insert new
namespace into message. On paper it seems very easy, just click + and
type in prefix and namespace and press ok. But in reality pressing ok
does absolutely nothing and because of this I can't insert namespace
definition like in tutorial and everything is downhill from there...
I am optimistic and assume that there is actually way to do what is
described in tutorial but server just doesn't give out any error
messages even when there is some strange step I have missed. :) Any ideas?
jari k

Jari Kujansuu wrote:
Hi,
I am playing around with Aqualogic ServiceBus and thought I would go
through tutorials just to see if there is something that I don't realize
from document (http://e-docs.bea.com/alsb/docs20/pdf/tutorial.pdf).
On page 5-13 there is step where you are supposed to insert new
namespace into message. On paper it seems very easy, just click + and
type in prefix and namespace and press ok. But in reality pressing ok
does absolutely nothing and because of this I can't insert namespace
definition like in tutorial and everything is downhill from there...To answer my own message, in case others face same problem ...and to
hear if others have same problem.
So I looked at other things and now when returned to Aqualogic. Tried
again and after it failed for some reason decided to test same in
Internet Exlopder, even everything else seems to work beatifully using
Mozilla Firefox. Well in IE when pressed OK new namespace was added as
it should.
Tried looking if I had some security feature turned on in Firefox but
couldn't really see what could cause such thing. Does this work with
Firefox for others or is this Aqualogic stuff only for Internet Exploder
users?
Jari Kujansuu
Tel: +358-403400607
[email protected]
Endero Oyj www.endero.com
Kiviaidankatu 2F, FI-00210 Helsinki
The intelligent art of integration

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

Problem with WTC

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
Gautam

Hey 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.

Problems running the very first tutorial, AquaLogic 2.6

Hi,
I've gone through the first tutorial for AquaLogic 2.6, here:
[url http://e-docs.bea.com/alsb/docs26/tutorial/tutRoute.html]
Everything seems to work, except that the routing always goes to the normalLoan business service, regardless of the rate amount:
>ant run
Buildfile: build.xml
Trying to override old definition of task clientgen
run:
     [java] Loan Application Response: APPROVED BY THE <i><b>NORMAL</b></i> LOAN
APPLICATION PROCESSING SERVICE
     [java] Rate: 4.9
BUILD SUCCESSFUL
Total time: 4 secondsAs far as I can see, I've set up the XQuery expression correctly. The expression is: $body/exam:processLoanApp/loanRequest/java:RateThe condition (viewed in read-only mode) is:
[less than] [5] Route to [ ManagerLoanReview ] invoking [ processLoanApp ].
Any ideas what is going on?
- Mark

Hi,
Well, the issue was that I didn't notice that I was calling the original URL rather than the proxy service.
I would strongly suggest that you don't ask people to edit the default run task, but instead change the build.xml to add a couple of ant tasks like the following, so n00bs like me can more easily test the services they've just configured:
<project name="normal-loan-app-webservices-jws_basic-ejb" default="all" basedir=".">
<target name="gateway1" >
    <input
      message="Please type the interest rate: (5.5)"
      defaultvalue="5.5"
      addproperty="rate" />
    <java fork="yes" classname="normal.client.Main"
      failonerror="true" >
      <classpath refid="client.class.path"/>
      <arg line="http://${wls.hostname}:${wls.port}/loan/gateway1 steve 555 2500 20 ${rate} notes" />
    </java>
</target>
<target name="gateway2" >
    <input
      message="Please type the amount: (2500)"
      defaultvalue="2500"
      addproperty="amount" />
    <java fork="yes" classname="normal.client.Main"
      failonerror="true" >
      <classpath refid="client.class.path"/>
      <arg line="http://${wls.hostname}:${wls.port}/loan/gateway2 steve 555 ${amount} 20 5.1 notes" />
    </java>
</target>
</project>Please feel free to distribute this.
- Mark

Problem with aqualogic

Hi all:
I have installed weblogic server 9.2 and aqualogic on a solaris zone.
Whe i call a web services in fuego but I get this error:
FaultString [The method 'startSession' from class 'xobject.WfManageNISNotificationsWebServiceImpl.WfManageNISNotificationsServiceInternalAlbpmListenerImpl' could not be successfully executed.] FaultActor [null] Detail [<detail>
<OperationException>
<message>Exception [Protocol [null] not supported.
Technical detail:Verify that the needed plug-in supporting files are present in your system and that the provider name is not misspelled.
].</message>
<technicalInfo>fuego.directory.DirectoryRuntimeException: Exception [Protocol [null] not supported.
Technical detail:Verify that the needed plug-in supporting files are present in your system and that the provider name is not misspelled.
at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:84)
at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.fillPassport(RemoteJdbcDirectoryFactory.java:153)
at fuego.directory.Directory.fillPassport(Directory.java:182)
at fuego.components.WebServiceSessionManager$SessionImpl.<init>(WebServiceSessionManager.java:218)
at fuego.components.WebServiceSessionManager.createSession(WebServiceSessionManager.java:84)
at xobject.WfManageNISNotificationsWebServiceImpl.WfManageNISNotificationsServiceInternalAlbpmListenerImpl.startSession(WfManageNISNotificationsServiceInternalAlbpmListenerImpl.java:372)
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:585)
at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1478)
at fuego.lang.JavaObject.invoke(JavaObject.java:185)
at fuego.lang.Invokeable.invokeImpl(Invokeable.java:220)
at fuego.lang.Invokeable.invoke(Invokeable.java:161)
at fuego.soaptype.SoapListener.invoke(SoapListener.java:90)
at fuego.ejbengine.EJBWebServiceExecution$1.execute(EJBWebServiceExecution.java:65)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:290)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:462)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:540)
at fuego.transaction.TransactionAction.start(TransactionAction.java:213)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:117)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.ejbengine.EJBWebServiceExecution.execute(EJBWebServiceExecution.java:41)
at fuego.ejbengine.EJBProcessBean.executeWebService(EJBProcessBean.java:168)
at fuego.ejbengine.BaseProcessControlAdapter.executeWebService(BaseProcessControlAdapter.java:78)
at fuego.ejbengine.EJBProcessControlAdapter_g81xhg_EOImpl.executeWebService(EJBProcessControlAdapter_g81xhg_EOImpl.java:1643)
at fuego.ejbengine.EJBProcessControlAdapter_g81xhg_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:335)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at fuego.ejbengine.EJBProcessControlAdapter_g81xhg_EOImpl_922_WLStub.executeWebService(Unknown Source)
at fuego.ejbengine.EJBWebServiceExecutor.execute(EJBWebServiceExecutor.java:62)
at fuego.soaptype.WebServiceSkeleton.invokeMethod(WebServiceSkeleton.java:210)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:283)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at fuego.soaptype.SoapService.invoke(SoapService.java:318)
at fuego.soaptype.SoapHttpListener.process(SoapHttpListener.java:161)
at fuego.ejbengine.servlet.SoapServlet.doPost(SoapServlet.java:106)
at fuego.ejbengine.servlet.SoapServlet.doPost(SoapServlet.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3231)
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:2002)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1908)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1362)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: fuego.directory.exception.ProtocolNotSupportedException: Protocol [null] not supported.
Technical detail:Verify that the needed plug-in supporting files are present in your system and that the provider name is not misspelled.
at fuego.directory.exception.ProtocolNotSupportedException.create(ProtocolNotSupportedException.java:34)
at fuego.directory.provider.Factory.getFactoryFor(Factory.java:182)
at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.getRealFactory(RemoteJdbcDirectoryFactory.java:333)
at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.getRealFactory(RemoteJdbcDirectoryFactory.java:324)
at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.fillPassport(RemoteJdbcDirectoryFactory.java:146)
... 56 more
someone can help me?

1) Take the action recommended in the error message which is :
Verify that the needed plug-in supporting files are present in your system and that the provider name is not misspelled.
2) Try posting on an ALUI forum (this forum is ALDSP)
3) Open a case with BEA customer support

Transaction problems using AquaLogic Data Services

Using WebLogic 10.2 and ALDSP 3.2.
I am using WebServices and DataServices.
I wrote a webservice to do the following:
1) Use a DSP Control to get data from a dataservice
2) Use a DSP Control to update some of that data
3) Use a DSP Control to create a new record (on a different table)
4) Throw a SOAPexception if something doesn't look right.
None of my data is getting rolled back on the Exception.
What attributes need to be set for the rollback to work correctly? Or do I have to write some transaction code in the web service?

I don't find any errors logged in AdminServer.log. All I find is a successful execution of the GRAVAR stored procedure. So, of course you will find the inserts that it does in the database.
####<12/06/2008 15h45min39s GMT-03:00> <Info> <ALDSP> <e082250> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1213296339348> <000000> <MedialDSP> <DSPAuditEvent timestamp: Thu Jun 12 15:45:38 GMT-03:00 2008 severity: WARNING id: MedialDSP:7:Thu Jun 12 15:45:38 GMT-03:00 2008 {
common/application {
user: weblogic
name: MedialDSP
eventkind: update
server: AdminServer
query/cache/queryplan {
type: XQUERY_PLAN_CACHE
found: false
query/performance {
compiletime: 15
query/wrappers/procedure {
datasource: jdbc/mdlpnpd
name: SOA.SOA_PROPOSTA_PG.GRAVAR
rows: 0
time: 1093
common/session/query/invocation {
time: Thu Jun 12 15:45:39 GMT-03:00 2008
duration: 0
update/service {
procedure: GRAVAR
arity: 43
dataservice: ld:fisico/mdlpnpd/proposta/GRAVAR.ds
script: declare namespace ns0="ld:fisico/mdlpnpd/proposta/GRAVAR";
declare namespace ns1="http://www.w3.org/2001/XMLSchema";
declare variable $__fparam0 as ns1:string external;
declare variable $__fparam1 as ns1:decimal external;
declare variable $__fparam2 as ns1:decimal external;
declare variable $__fparam3 as ns1:string external;
declare variable $__fparam4 as ns1:string external;
declare variable $__fparam5 as ns1:string external;
declare variable $__fparam6 as ns1:string external;
declare variable $__fparam7 as ns1:string external;
declare variable $__fparam8 as ns1:dateTime external;
declare variable $__fparam9 as ns1:decimal external;
declare variable $__fparam10 as ns1:decimal external;
declare variable $__fparam11 as ns1:decimal external;
declare variable $__fparam12 as ns1:decimal external;
declare variable $__fparam13 as ns1:decimal external;
declare variable $__fparam14 as ns1:decimal external;
declare variable $__fparam15 as ns1:string external;
declare variable $__fparam16 as ns1:string external;
declare variable $__fparam17 as ns1:string external;
declare variable $__fparam18 as ns1:string external;
declare variable $__fparam19 as ns1:decimal external;
declare variable $__fparam20 as ns1:decimal external;
declare variable $__fparam21 as ns1:decimal external;
declare variable $__fparam22 as ns1:decimal external;
declare variable $__fparam23 as ns1:string external;
declare variable $__fparam24 as ns1:string external;
declare variable $__fparam25 as ns1:string external;
declare variable $__fparam26 as ns1:string external;
declare variable $__fparam27 as ns1:string external;
declare variable $__fparam28 as ns1:decimal external;
declare variable $__fparam29 as ns1:decimal external;
declare variable $__fparam30 as ns1:decimal external;
declare variable $__fparam31 as ns1:decimal external;
declare variable $__fparam32 as ns1:decimal external;
declare variable $__fparam33 as ns1:string external;
declare variable $__fparam34 as ns1:string external;
declare variable $__fparam35 as ns1:string external;
declare variable $__fparam36 as ns1:string external;
declare variable $__fparam37 as ns1:string external;
declare variable $__fparam38 as ns1:string external;
declare variable $__fparam39 as ns1:string external;
declare variable $__fparam40 as ns1:string external;
declare variable $__fparam41 as ns1:decimal external;
declare variable $__fparam42 as ns1:string external;
{ return value ns0:GRAVAR($__fparam0,$__fparam1,$__fparam2,$__fparam3,$__fparam4,$__fparam5,$__fparam6,$__fparam7,$__fparam8,$__fparam9,$__fparam10,$__fparam11,$__fparam12,$__fparam13,$__fparam14,$__fparam15,$__fparam16,$__fparam17,$__fparam18,$__fparam19,$__fparam20,$__fparam21,$__fparam22,$__fparam23,$__fparam24,$__fparam25,$__fparam26,$__fparam27,$__fparam28,$__fparam29,$__fparam30,$__fparam31,$__fparam32,$__fparam33,$__fparam34,$__fparam35,$__fparam36,$__fparam37,$__fparam38,$__fparam39,$__fparam40,$__fparam41,$__fparam42); }
common/time {
timestamp: Thu Jun 12 15:45:38 GMT-03:00 2008
duration: 1156
}>
Edited by mreiche at 06/12/2008 2:07 PM

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)

Differences between Oracle BPM and Aqualogic BPM 6.0

Hello,
Does anyone know where I can find information that spells out the differences between Aqualogic 6.0 and Oracle BPM (if there are any)? I've searched the Oracle sites, documentation sections, etc. and I cannot find a datasheet that spells out anything related to the differences between the two aside from the name change.
Thank you.

I thought that there no major differences between the versions, only changes in the skin, logo and an improvement in the engine, but I was wrong.
My production enviroment runs BPM Enterprise in version 6, in other words runs Aqualogic BPM Enterprise, not Oracle BPM Enterprise, but in the development enviroment I made the decision to use the version 10 (Oracle BPM Studio 10g), because I thought there were no considerable changes between versions.
So I could not make the deployment of the project in the enterprise version, the log reported that many processes and screenflows of the project were not found, then I tried to open the project that was done in version 10 in version 6 of the BPM Studio and then try to export the ".exp" to try to do the deployment again. When I opened the project in BPM Studio 6 some errors occurred, but no significant errors. I fixed the errors, export the project again and try to do the deployment in the enterprise version and the same problems as before still occurring.
The only solution I found was to make the project in BPM Studio 6.04 (Aqualogic). Now I can make the deployment of the project in the production environment.
Conclusion: always use the same version in BPM studio/enterprise. If you use Oracle BPM Studio in development enviroment, use Oracle BPM Enterprise for production enviroment. The same way if you use Aqualogic BPM Studio in development enviroment, use Aqualogic BPM Enterprise in the production enviroment.

AquaLogic WTC problem

Similar Messages

Maybe you are looking for