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.

Similar Messages

  • JAVA client JNDI lookup for EJB session in cluster in WLS 5.1

    The documentation says :
              to obtain a Context for JNDI lookup do the following :
              Hashtable ht = new Hashtable();
              ht.put(Context.INITIAL_CONTEXT_FACTORY,
              "weblogic.jndi.WLInitialContextFactory");
              ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
              try {
              Context ctx = new InitialContext(ht);
              // Do the client's work
              catch (NamingException ne) {
              // A failure occurred
              finally {
              try {ctx.close();}
              catch (Exception e) {
              // a failure occurred
              where "mycluster" is the DNS name of my cluster. My DNS server (Windows 200
              DNS server) use round robin
              to call alernatively all the wls server node in "mycluster" and it's OK. The
              two servers of my cluster
              are called alternatively for my EJB session stateless.
              Now I unplug one of the two nodes of my cluster and the remaining server is
              called only 2 times
              and not after.
              Questions :
              -is the load balancing between the nodes of mycluster only rely on DNS or
              is there an internal
              mecanism in EJB sub to try one server then an other ?
              - do I need to obtain a new reference on JNDI Context for each call ?
              Thank's a lot.
              Farid Bellameche.
              

              I too have the same problem. My scenario is :
              I have the web tier architecture away from cluster. All ejbs are in cluster
              running in two seperate machines. We have a factory class running in
              webtier(we use servlet in this tier) which obtains home interface only once
              and stores it for future reference. When ever we need the remoteobject stub,
              we ask the factory class and which in turn uses the stored home interface to
              get the same.
              In the webtier, I list all the servers in the cluster as a part of url as
              mentioned by you.
              I started the web tier as well as Object tier cluster. I could see the
              request coming in both the machines in the cluster for the ejb. But When I
              bring one the server in the cluster,
              1. Web tier throws an exception saying that it could not connect
              to server using t3.
              2. The other machine which is running the server, also says
              'failed to create socket to : -32323234324 sever name
              using protocol t3.
              It looks like I am able to get load balance. But I am not able to get the
              fail over to be working.
              In the weblogic-ejb-jar.xml, I added the following.
              <clustering-descriptor>
              <home-is-clusterable>true</home-is-clusterable>
              <home-load-algorithm>round-robin</home-load-algorithm>
              </clustering-descriptor>
              I compiled and added the .jar file. So the jar file now has replica aware
              stubs.
              Could any one of you help me for why the fail over is not working?
              Suersh
              "Giri Alwar" <[email protected]> wrote in message
              news:[email protected]...
              > Farid,
              > (1) Yes, the stub has the logic to perform load-balancing and
              fail-over.
              > (2) In almost all cases, no. You can get the context once, store it
              and
              > use it thereafter. Please refer to
              > http://www.weblogic.com/docs51/cluster/concepts.html#1025061 for more
              info.
              >
              > A couple of notes on your situation. From what you are describing, your
              > Windows DNS server is setup to serve only one IP from the cluster (using
              > round-robin) as opposed to a list of all IP's in the cluster. Hence, the
              > initial context you obtain is tied to a single server in the cluster (the
              > one returned by the DNS). The weblogic implementation on the client side
              has
              > no idea of the existence of the other servers in the cluster. This is not
              a
              > cluster aware context. To obtain a cluster aware context, either list all
              > the IP's in the URL like t3://server1,server2,server3:7001 or have
              > "mycluster" return a list of all servers in the cluster.
              >
              > Giri
              >
              >
              > "Farid Bellameche" <[email protected]> wrote in message
              > news:[email protected]...
              > > The documentation says :
              > >
              > > to obtain a Context for JNDI lookup do the following :
              > > Hashtable ht = new Hashtable();
              > > ht.put(Context.INITIAL_CONTEXT_FACTORY,
              > > "weblogic.jndi.WLInitialContextFactory");
              > > ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
              > > try {
              > > Context ctx = new InitialContext(ht);
              > > // Do the client's work
              > > }
              > > catch (NamingException ne) {
              > > // A failure occurred
              > > }
              > > finally {
              > > try {ctx.close();}
              > > catch (Exception e) {
              > > // a failure occurred
              > > }
              > > }
              > >
              > > where "mycluster" is the DNS name of my cluster. My DNS server (Windows
              > 200
              > > DNS server) use round robin
              > > to call alernatively all the wls server node in "mycluster" and it's OK.
              > The
              > > two servers of my cluster
              > > are called alternatively for my EJB session stateless.
              > > Now I unplug one of the two nodes of my cluster and the remaining server
              > is
              > > called only 2 times
              > > and not after.
              > >
              > > Questions :
              > > -is the load balancing between the nodes of mycluster only rely on DNS
              > or
              > > is there an internal
              > > mecanism in EJB sub to try one server then an other ?
              > >
              > > - do I need to obtain a new reference on JNDI Context for each call ?
              > >
              > >
              > > Thank's a lot.
              > >
              > > Farid Bellameche.
              > >
              > >
              > >
              > >
              >
              >
              

  • JNDI name for a JMB is not replicatet to other servers in the cluster

    Hi,
              wl6.1sp7, two server cluster
              When I look at the JNDI Tree for a server I can't find JNDI names of JMB's from the other server in the cluster.
              I get an exception when trying to send to a destinaton on the other server. (Unable to resolve 'xlink.jms.service.report.biztalk-lab.Report' Resolved: 'xlink.jms.service.report' Unresolved:'biztalk-lab')
              Setting are same as explained in this thread...
              http://forums.bea.com/bea/thread.jspa?threadID=600003492&tstart=0
              And JNDINameReplicated is set to true....
              Why is the JNDI names not replicated?
              <JMSQueue JNDIName="xlink.jms.service.report.biztalk-lab.Report"
              JNDINameReplicated="true" Name="Report" StoreEnabled="default"/>
              This is the DD of a JMB:
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>xlink.jms.service.report.biztalk-lab.Report</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>3</max-beans-in-free-pool>
              <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>xlink.jms.service.report.biztalk-lab.Report</destination-jndi-name>
              <connection-factory-jndi-name>xlink.jms.factory.commerceFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <jndi-name>xlink.jms.service.report.biztalk-lab.Report</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              ~b

    1. yes
              <JMSConnectionFactory AllowCloseInOnMessage="false"
              DefaultDeliveryMode="Persistent" DefaultPriority="4"
              DefaultTimeToLive="0"
              JNDIName="xlink.jms.factory.commerceFactory"
              MessagesMaximum="10" Name="xlink.jms.factory.commerceFactory"
              OverrunPolicy="KeepOld" Targets="bluej,biztalk-lab,devtestCluster"/>
              2. No I am just using the jndi name of the queue.
              This is an example of how I send a message:
                   Context ctx = new InitialContext();
              QueueConnectionFactory qconFactory;
              QueueConnection qcon;
              QueueSession qsession;
              QueueSender qsender;
              Queue queue;
              ObjectMessage msg;
              qconFactory = (QueueConnectionFactory) ctx.lookup("xlink.jms.factory.commerceFactory");
              qcon = qconFactory.createQueueConnection();
              qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
              queue = (Queue) ctx.lookup("xlink.jms.queue.biztalk-lab.OrdrspImport");
              qsender = qsession.createSender(queue);
              msg = qsession.createObjectMessage(reportExecutorContainer);
              qcon.start();
              qsender.send(msg);
              qsender.close();
              qsession.close();
              qcon.close();
              3. I don't know those setting (wl 6.1sp7)

  • How do i setup WTC in cluster environment using WLS6.1 sp3?

    Hello:
    the situation is:
    (1)Two solaris machines.
    (2)one WLS domain.
    (3)one admin server and four managed servers in this domain.
    (4)we cluster these 4 managed servers.
    (5)each machine contains 2 managed server.
    Here is the problem,
    when we start managed servers in the same machine, the wtc is ok, but when we start managed servers in diffent machine, the wtc fail.
    here is the error message:
    [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 10.64.32.188 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.]
    [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 10.64.32.187 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.]
    So, how can i setup wtc in cluster environment using WLS 61. sp3?
    Regards,
    cjyang

    cjyang <[email protected]> writes:
    [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 10.64.32.188 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.] I believe that this is a known problem and that WTC clustering is not
    supported in WLS 6.1.
    andy

  • Issue with LCM while migrating planning application in the cluster Env.

    Hi,
    Having issues with LCM while migrating the planning application in the cluster Env. In LCM we get below error and the application is up and running. Please let me know if anyone else has faced the same issue before in cluster environment. We have done migration using LCM on the single server and it works fine. It just that the cluster environment is an issue.
    Error on Shared Service screen:
    Post execution failed for - WebPlugin.importArtifacts.doImport. Unable to connect to "ApplicationName", ensure that the application is up and running.
    Error on network:
    “java.net.SocketTimeoutException: Read timed out”
    ERROR - Zip error. The exception is -
    java.net.SocketException: Connection reset by peer: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)

    Hi,
    First of all, if your environment for source and target are same then you will have all the users and groups in shared services, in that case you just have to provision the users for this new application so that your security will get migrated when you migrate the from the source application. If the environs are different, then you have to migrate the users and groups first and provision them before importing the security using LCM.
    Coming back to the process of importing the artifacts in the target application using LCM, you have to place the migrated file in the @admin native directory in Oracle/Middleware/epmsystem1.
    Open shared services console->File system and you will see the your file name under that.
    Select the file and you will see all your exported artifacts. Select all if you want to do complete migration to target.
    Follow the steps, select the target application to which you want to migrate and execute migration.
    Open the application and you will see all your artifacts migrated to the target.
    If you face any error during migration it will be seen in the migration report..
    Thanks,
    Sourabh

  • HAFileAdapter based OSB processing 1st file twice in 2 node cluster env

    Hi,
    I am trying my hands in OSB with HA File Adapter and came across a strange issue where in OSB service designed to pick up a message of "*.CSV" format and process it's record one at a time recursively as per below details:
    The reason I am saying it's been processed by 2 nodes of the cluster independently is because I can see 2 separate threads picking up same file at the same time on both the nodes in log files. I enabled the debugging property on managed servers.
    ----------------------------------------------------- Start Log Snippet -----------------------------------------------------
    Node 1 : ExecuteThread: '51'
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Translated inbound batch index "1" of fil
    e {CCISU_500.csv} sucessfully.>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Publisher::publishMessage called with prim
    aryKey=[Qz6n0UOYTQ1oJ2QeawJThlv-jKbiLeH1Bkko5wHl1Lg.]>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447695272> <BEA-000000> <Sending batch to Adapter Framework for pos
    ting to BPEL engine: {
    batchId=_-H9OvOxmH30ZcxGkXWAK8mVTcajl3SHsnnVKxfsEBU., batchIndex=1, publishSize=1
    }>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699920> <BEA-000000> <Copying file :/FileAdapters/Input/CCISU_500.csv to user-defined archive directory for processed files :/FileAdapters/Archive>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699928> <BEA-000000> <Deleting/Soft deleting file : /FileAdapters/Input/CCISU_500.csv>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699928> <BEA-000000> <Deleting file : CCISU_500.csv>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699929> <BEA-000000> <Deleted file : true>
    ####<Oct 17, 2012 3:21:39 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447699929> <BEA-000000> <Poller has reached max raise size, will not raise anymore>
    Node 2 : ExecuteThread: '53'
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Translated inbound batch index "1" of file
    {CCISU_500.csv} sucessfully.>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Publisher::publishMessage called with prima
    ryKey=[ODfzwSUr85GeHkzscyhXrh2URW1FEAposlikUkdTZL8.]>
    ####<Oct 17, 2012 3:21:35 PM EST> <Debug> <AlsbJcaFrameworkAdapter> <pcalin01> <WLS_OSB1> <[ACTIVE] ExecuteThread: '53' for queue: 'weblogic.kernel.Defa
    ult (self-tuning)'> <oracle> <> <7dca6b7cd27159da:58554710:13a6c24a0f9:-8000-000000000001b722> <1350447695186> <BEA-000000> <Sending batch to Adapter Framework for post
    ing to BPEL engine: {
    batchId=ZkZ5HZA43QtsPZFqU2prPmxVS83NBMHcZa5n76yKC-Q., batchIndex=1, publishSize=1
    }>
    ####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Def
    ault (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700939> <BEA-000000> <Since file could not be copied to specifi
    ed archive directory, file : CCISU_500.csv_CbOXCcnMsRq44Slx2jiJrbM5vvgER0M_cYJsXlmvzWU= is being copied to a default archive directory :/oracle/ofmw3u/admin/ofmw3u_doma
    in/mserver/ofmw3u_domain/fileftp/defaultArchive/>
    ####<Oct 17, 2012 3:21:40 PM EST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.De
    fault (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700940> <BEA-000000> <Endpoint will shutdown process to preven
    t data loss as file :CCISU_500.csv could not be being copied to default archive : /oracle/ofmw3u/admin/ofmw3u_domain/mserver/ofmw3u_domain/fileftp/defaultArchive/. Plea
    se ensure that there is enough free space available to copy this file.
    java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or direct
    ory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:120)
    at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:1024)
    at oracle.tip.adapter.file.inbound.PostProcessor.defaultArchive(PostProcessor.java:300)
    at oracle.tip.adapter.file.inbound.PostProcessor.performArchival(PostProcessor.java:229)
    at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:178)
    at oracle.tip.adapter.file.inbound.PollWork.publishFile(PollWork.java:1574)
    at oracle.tip.adapter.file.inbound.PollWork.processFilesInSameThread(PollWork.java:1001)
    at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:335)
    at weblogic.work.ContextWrap.run(ContextWrap.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Oct 17, 2012 3:21:40 PM EST> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700940> <BEA-000000> <ProcessWork::run Fatal exception caught
    java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or directory)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:120)
    at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:1024)
    at oracle.tip.adapter.file.inbound.PostProcessor.defaultArchive(PostProcessor.java:300)
    at oracle.tip.adapter.file.inbound.PostProcessor.performArchival(PostProcessor.java:229)
    at oracle.tip.adapter.file.inbound.ProcessorDelegate.process(ProcessorDelegate.java:178)
    at oracle.tip.adapter.file.inbound.PollWork.publishFile(PollWork.java:1574)
    at oracle.tip.adapter.file.inbound.PollWork.processFilesInSameThread(PollWork.java:1001)
    at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:335)
    at weblogic.work.ContextWrap.run(ContextWrap.java:41)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Processer thread calling onFatalError with exception [java.io.FileNotFoundException: /FileAdapters/Input/CCISU_500.csv (No such file or directory)]>
    ####<Oct 17, 2012 3:21:40 PM EST> <Info> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Unable to call onFatalError since the adapter could not find an endpoint>
    ####<Oct 17, 2012 3:21:40 PM EST> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <pcalin03> <WLS_OSB2> <[ACTIVE] ExecuteThread: '51' for queue: 'weblogic.kernel.Default (self-tuning)'> <oracle> <> <70d9e8b790dff210:-480a1b4a:13a6c31d21b:-8000-000000000023fd0a> <1350447700941> <BEA-000000> <Poller::processFilesInSameThread will abort as the endpoint has been released>
    ----------------------------------------------------- End Log Snippet -----------------------------------------------------
    ----------------------------------------------------- Start Questions to the Gurus Out There -----------------------------------------------------
    1. Is there any property to make sure that only one activation agent is active at anytime in a cluster env ?
    2. Does JCA property "<property name="SingleThreadModel" value="true"/> holds good when used in OSB ? or it's just supported in composite ??
    3. Does both the nodes of cluster polls independently ? As I have seen in logs that node1 polling and complaining about time to live factor while the other node picking it before node1 completes another cycle of polling.
    4. In above log you can see that node1 processed all the records 1sec earlier than node2 in a race condition and as a result node2 completed about file not found exception?
    Gurus any help will be appriciated.
    ----------------------------------------------------- End Questions to the Gurus Out There -----------------------------------------------------
    ----------------------------------------------------- Start Details -----------------------------------------------------
    Protocol : jca
    Endpoint URI : jca://eis/FileAdapter
    Get All Headers : No Headers
    JCA: <adapter-config name="RequestHandler" adapter="File Adapter" wsdlLocation="RequestHandler.wsdl"; xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory location="eis/HAFileAdapter" UIincludeWildcard="*.csv"/>
    <endpoint-activation portType="Read_ptt" operation="Read">
    <activation-spec className="oracle.tip.adapter.file.inbound.ScalableFileActivationSpec";>
    <property name="DeleteFile" value="true"/>
    <property name="MinimumAge" value="120"/>
    <property name="PhysicalDirectory" value="/FileAdapters/Input"/>
    <property name="PhysicalArchiveDirectory" value="/FileAdapters/Archive"/>
    <property name="PhysicalErrorArchiveDirectory" value="/FileAdapters/Error"/>
    <property name="Recursive" value="true"/>
    <property name="PublishSize" value="1"/>
    <property name="PollingFrequency" value="300"/>
    <property name="MaxRaiseSize" value="1"/>
    <property name="SingleThreadModel" value="true"/>
    <property name="IncludeFiles" value=".*\.csv"/>
    <property name="UseHeaders" value="false"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>
    ----------------------------------------------------- End Detail -----------------------------------------------------
    Edited by: 964320 on Oct 17, 2012 10:58 PM

    You need to define the below property in composite.xml file of your bpel. This will allow only one adapter active and another passive to pick up the file.
    <activationAgents>
    <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PickupFile/FTPConsumer">
    *<property name="clusterGroupId">BPELProcessNameCluster</property>*
    <property name="portType">FTP/FileConsumer_Message_ptt</property>
    </activationAgent>
    </activationAgents>
    Thanks,
    Vijay

  • Custom Objects in JNDI Not Being Replicated in Cluster

    I know this is going to end up being something really simple, but I can't find
    any docs or other posts on it.
    I have a simple two node weblogic 7.0 cluster. In a startup class that is deployed
    to the cluster I check for and create a subcontext. This subcontext will just
    hold custom objects when a node comes up. When a node does come up, one of the
    web applications binds a non-RMI custom object to the subcontext created via the
    startup class.
    Once both nodes in the cluster are up I can see via the weblogic console's "View
    JNDI tree" feature that the custom object bound on node 1 is only visible in the
    JNDI tree of node 1. Similarly the object bound on node 2 is only visible in
    the JNDI tree of node 2.
    Is the JNDI tree that is visible via the console the JNDI specific to the node
    and not the clusterwide JNDI tree? Do I have to do something special to get access
    to the cluster wide JNDI tree (for instance when creating an InitialContext)?
    Is there a way to view the cluster wide JNDI tree?
    Thanks for any information.

    Hi Matt,
    how did you compile t3 stubs,there are -clusterable or something like this
    option shat should make replicatable-aware stubs.
    "Matt" <[email protected]> wrote:
    >
    I know this is going to end up being something really simple, but I can't
    find
    any docs or other posts on it.
    I have a simple two node weblogic 7.0 cluster. In a startup class that
    is deployed
    to the cluster I check for and create a subcontext. This subcontext
    will just
    hold custom objects when a node comes up. When a node does come up,
    one of the
    web applications binds a non-RMI custom object to the subcontext created
    via the
    startup class.
    Once both nodes in the cluster are up I can see via the weblogic console's
    "View
    JNDI tree" feature that the custom object bound on node 1 is only visible
    in the
    JNDI tree of node 1. Similarly the object bound on node 2 is only visible
    in
    the JNDI tree of node 2.
    Is the JNDI tree that is visible via the console the JNDI specific to
    the node
    and not the clusterwide JNDI tree? Do I have to do something special
    to get access
    to the cluster wide JNDI tree (for instance when creating an InitialContext)?
    Is there a way to view the cluster wide JNDI tree?
    Thanks for any information.

  • OMB02904: Namespace conflict for map name

    Hello all,
    I was running an OMB script which was to create the several Mappings, and after the creation of all the mappings it was supposed to commit. This script was being run in UNIX env, but unfortunately the UNIX session got killed and script terminated, persumably before commit, because I do not see any of the mappings in OWB.
    So I started the script again but got this message,
    OMB02904: Namespace conflict for map name MAP_1: PRS-00303: Name <MAP_1> Already reserved under your user name. with
    oracle session ID: 31
    I cleaned up the oracle sessions in Design Rep, but still getting the same error message both at command line and in GUI.
    Has anyone else in the forum experienced similar problem. Any suggestions or pointer on How to fix thi will be appreciated.
    TIA

    It seems that the mapping got created. Have you tried to refresh the OWB client to see the mapping by clicking on the "Synchronize this view with the repository" button (second icon from the left just under the "Project" menu entry)? If this is true, you will either have to delete the existing mapping and commit, or rename your mapping.
    Regards:
    Igor

  • Weblogic Integration failed to build Cluster ENV

    Dear buddies,
    I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
    Here is the process how I created WLI cluster:
    ENV:RedHat9+ WL8.1_SP4
    Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
    BEA_HOME=/opt/bea/
    1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
    and I didn't create extra JDBC POOL except the standard one.
    2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
    Now I am having following problem.
    1.admin Server(cgServer) can startup without any problem
    2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
    3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
    but seems the pointbase only listen 9092!!
    4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
    below are detailed output when I startManagedServers:
    command:
    [root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
    ####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
    Listen Address          172.16.4.236:7001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
    Channel Weight          50
    Accept Backlog          50
    Login Timeout          5000ms
    Max Message Size     10000000
    Message Timeout     60s
    Idle Timeout          65s
    Tunneling Timeout     40s
    Tunneling Ping          45s>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)

    Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.

  • JNDI lookup for UserTransaction

              Hi all,
              in Weblogic, in a typical scenario, do a client provide exactly
              one JNDI lookup for the UserTransaction object (interface) or do
              the client have to provide a JNDI lookup for each transaction?
              In some EJB implementations, a JNDI lookup for UserTransaction
              returns always the same reference. For example, in JOnAS, you can
              have one static reference which is set when the client starts.
              Then, more threads can simultaneously use the same static
              UserTransaction reference without any conflict, since the
              implementation of UserTransaction recognizes, which thread invoked
              a particular method.
              In other words, can I make an assumption that two different JNDI
              lookups for UserTransaction returns different references or not?
              Thanks a lot,
              Marek Prochazka
              Distributed Systems Research Group
              Department of Software Engineering
              Charles University, Faculty of Mathematics and Physics
              Malostranske namesti 25, 118 00 Prague 1, Czech Republic
              phone: +420-2-2191 4236
              http://nenya.ms.mff.cuni.cz/thegroup/
              

    Actually, UserTransaction is a singleton and it's not a transaction. It's just
              very mis-named.
              It should be called UserTransactionManager or UserInterfaceToJTA.
              The actual transaction is javax.transaction.Transaction.
              -- Rob
              Cameron Purdy wrote:
              > Within a transaction, it is different instances? For example, if you call
              > it two times one right after another?
              >
              > A transaction is a unit of work. I understand why the transaction object
              > changes from transaction to transaction, since a single transaction object
              > (UserTransaction) represents exactly one transaction. Why would it be a
              > singleton? It is not a transaction manager.
              >
              > Peace,
              >
              > --
              > Cameron Purdy
              > Tangosol, Inc.
              > http://www.tangosol.com
              > +1.617.623.5782
              > WebLogic Consulting Available
              >
              > "Sarita" <[email protected]> wrote in message
              > news:[email protected]...
              > >
              > > Hi Priscilla--
              > >
              > > This is not the behavior that I'm seeing, and I'm perplexed.
              > > Every time I request a UserTransaction from JNDI, I receive a
              > > a different instance. Should the value immediately returned by JNDI be
              > the singleton
              > > instance? If not, then how do I retrieve the singleton instance?
              > >
              > > I would like a session bean to start a transaction, and then call a method
              > on another
              > > session bean (which should operate under the same transaction). How does
              > the second
              > > session bean grab the correct transaction object? Is that possible?
              > >
              > > Thanks In Advance,
              > > Sarita
              > >
              > > "Priscilla Fung" <[email protected]> wrote:
              > > >
              > > >Hi Marek,
              > > >
              > > >In Weblogic 6.0, JNDI lookup of UserTransaction returns a reference to
              > the
              > > >singleton
              > > >Transaction Manager instance, which is thread-safe and can be used from
              > > >multiple
              > > >threads for transaction demarcations etc.
              > > >
              > > >-- Priscilla Fung, BEA Systems, Inc.
              > > >
              > > >"Marek Prochazka" <[email protected]> wrote:
              > > >>
              > > >>Hi all,
              > > >>
              > > >>in Weblogic, in a typical scenario, do a client provide exactly
              > > >>one JNDI lookup for the UserTransaction object (interface) or do
              > > >>the client have to provide a JNDI lookup for each transaction?
              > > >>
              > > >>In some EJB implementations, a JNDI lookup for UserTransaction
              > > >>returns always the same reference. For example, in JOnAS, you can
              > > >>have one static reference which is set when the client starts.
              > > >>Then, more threads can simultaneously use the same static
              > > >>UserTransaction reference without any conflict, since the
              > > >>implementation of UserTransaction recognizes, which thread invoked
              > > >>a particular method.
              > > >>
              > > >>In other words, can I make an assumption that two different JNDI
              > > >>lookups for UserTransaction returns different references or not?
              > > >>
              > > >>Thanks a lot,
              > > >>Marek Prochazka
              > > >>--------------------------------------------------------------
              > > >> Distributed Systems Research Group
              > > >> Department of Software Engineering
              > > >> Charles University, Faculty of Mathematics and Physics
              > > >> Malostranske namesti 25, 118 00 Prague 1, Czech Republic
              > > >> phone: +420-2-2191 4236
              > > >> http://nenya.ms.mff.cuni.cz/thegroup/
              > > >>--------------------------------------------------------------
              > > >>
              > > >
              > >
              

  • Format of the JNDI name for lookup in DataSource

    Hi
    a) I have made a datasource in Weblogic 10.3 called SQL and its JNDI name as jdbc/SQLDS.
    The driver was BEA'S Type 4 Driver for MS SQL Server
    Now I am trying to lookup the datasource through an application. I have used the following
    lines of code:
    InitialContext context = new InitialContext();
    DataSource ds = context.lookup("jdbc/SQLDS");
    Connection conn = ds.getConnection();
    The Application was a success.
    I saw in some articles that you can refer to the datasource by even java:comp/env/jdbc/SQLDS,
    instead of just jdbc/SQLDS. I tried both ways and I was able to run the application.
    b) Then I made another datasource in Weblogic 10.3 called SQL1 and its JNDI name as jdbc/SQL1.
    The driver was MS SQL Server Type 4 Driver for versions 2000, 2005
    Now I am trying to lookup the datasource through an application. I have used the following
    lines of code:
    InitialContext context = new InitialContext();
    DataSource ds = context.lookup("jdbc/SQL1");
    Connection conn = ds.getConnection();
    The Application was a success.
    I saw in some articles that you can refer to the datasource by even java:comp/env/jdbc/SQL1,
    instead of just jdbc/SQL1. I tried the first way and it didnt work. It gave me a NullPointerException
    at the line Connection conn = ds.getConnection();
    c)Then I made a 3rd datasource in Weblogic 10.3 called SQL2 and its JNDI name as jdbc/SQL2DS.
    The driver was MS SQL Server Type 4 Driver for versions 2000, 2005
    Now I am trying to lookup the datasource through an application. I have used the following
    lines of code:
    InitialContext context = new InitialContext();
    DataSource ds = context.lookup("jdbc/SQL2DS");
    Connection conn = ds.getConnection();
    The Application was a success.
    I saw in some articles that you can refer to the datasource by even java:comp/env/jdbc/SQL2DS,
    instead of just jdbc/SQL2DS. I tried the first way and it didnt work. Again, it gave me a NullPointerException
    at the line Connection conn = ds.getConnection();
    I was confused why the 2nd and 3rd way didnt work . Is it becaue I used Microsoft's MS SQL Server Type 4 Driver?
    I have added the jar file in the WEBLOGIC_CLASSPATH. Why is it not recognising java:comp/env/jdbc/SQL2DS ?
    I would be grateful if somebody could give me ideas on this...
    Thanks
    Neeti

    To use application scoped or indirect JNDI lookups (i.e. java:comp/env/...) you usually need to define a &lt;resource-ref&gt; entry in your deployment descriptor(s). Not sure what type of application you are using to test (web-app, EJB,) but for java:comp/env/ lookups to work, you need to define resource references. The fact that your first test succeeded is somewhat strange. Without the resource reference definitions, I would have expected your JNDI lookups to fail with a NamingException instead of the lookup returning NULL for the datasource.
    Assuming you are doing your test from a web-app, you need to add &lt;resource-ref&gt; definitions to your web.xml file similar to the following:
    &lt;resource-ref&gt;
    &lt;res-ref-name&gt;*jdbc/SQL2DS*&lt;/res-ref-name&gt;
    &lt;res-type&gt;java.sql.DataSource&lt;/res-type&gt;
    &lt;res-auth&gt;Container&lt;/res-auth&gt;
    &lt;/resource-ref&gt;
    and then add &lt;reference-descriptor&gt; definitions to your weblogic.xml file similar to the following:
    &lt;reference-descriptor&gt;
    &lt;resource-description&gt;
    &lt;res-ref-name&gt;*jdbc/SQL2DS*&lt;/res-ref-name&gt;
    &lt;jndi-name&gt;*jdbc/SQL2DS*&lt;/jndi-name&gt;
    &lt;/resource-description&gt;
    &lt;/reference-descriptor&gt;
    Once you do these steps your lookup("java:comp/env/jdbc/SQL2DS") should function properly from within your web-app.

  • Jndi context is replicated by cluster?

    Greetings,
    If I create a Initial Factory Context that returns a custom Context
    which may have object information (~cache), a second server instance
    will replicate that information?
    thanks,
    Pedro Salazar.

    Hi Matt,
    how did you compile t3 stubs,there are -clusterable or something like this
    option shat should make replicatable-aware stubs.
    "Matt" <[email protected]> wrote:
    >
    I know this is going to end up being something really simple, but I can't
    find
    any docs or other posts on it.
    I have a simple two node weblogic 7.0 cluster. In a startup class that
    is deployed
    to the cluster I check for and create a subcontext. This subcontext
    will just
    hold custom objects when a node comes up. When a node does come up,
    one of the
    web applications binds a non-RMI custom object to the subcontext created
    via the
    startup class.
    Once both nodes in the cluster are up I can see via the weblogic console's
    "View
    JNDI tree" feature that the custom object bound on node 1 is only visible
    in the
    JNDI tree of node 1. Similarly the object bound on node 2 is only visible
    in
    the JNDI tree of node 2.
    Is the JNDI tree that is visible via the console the JNDI specific to
    the node
    and not the clusterwide JNDI tree? Do I have to do something special
    to get access
    to the cluster wide JNDI tree (for instance when creating an InitialContext)?
    Is there a way to view the cluster wide JNDI tree?
    Thanks for any information.

  • How to create EVENTS for a View Cluster.

    Hi Tech Gurus,
    I have created a view cluster on 5 tables. I need to do a validation and this can be done by using events. But i am unable to create a EVENT for the View Cluster. Could anyone please tell me how to create events for a View Cluster.
    Thanks in advance for your esteemed replies.
    Regards,
    Raghavendra Goutham P.

    Hello Pasapula
    When you are in the View Cluster maintenance dialog (SE54) click on dialog "Events".
    Below the field for the view cluster you have an additional field <b>FORM routines main program</b>. There you have to add the main program containing the FORM routines called by the VC events.
    For example: I had defined a normal report containing an include with all the FORM routines. The report contains only the following lines of coding:
    report zus_0120_u1.
    * Common Data und access routines for user exits in VC maintenance
    include LSVCMCOD.
    include  zus_0120_f1. "FORM routines for VC events
    Now in the "Events" dialog of the view cluster maintenance you assign your FORM routines to the events.
    Regards
      Uwe

  • Error while passing ODI variable in JNDI Url for JMS Queue XML

    Hi,
    Facing a weird problem while passing ODI variable in JNDI Url for JMS Queue XML.
    Below is the JNDI Url configured under ODI Topology:
    JNDI Url: t3://<host_location>?d=#TEST.SCHEMA_FILE&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
    where,
    #TEST.SCHEMA_FILE --> ODI variable storing xsd name and location
    Issue Description:
    If we restart ODI server then for the first run of any ODI interface using JMS Queue XML, it is unable to get the value for ODI variable present in JNDI Url (d=#TEST.SCHEMA_FILE).
    It throws error message saying: No XSD found
    Temporary Resolution:
    As a temporary fix if we hard-code and pass the value in that ODI variable as shown below, it will successfully go through.
    eg: JNDI Url: t3://<host_location>?d=C:\XSD\test.xsd&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
    Reverting it back to variable later will have no issues and subsequent run will succeed.
    But again anytime later if server is restarted then first run will have this issue.
    Want to have permanent fix for it.
    Any one having idea on it please share. Appreciate your help!

    What ODI version are you using? It could be related to the bug in the older version as described in support note Doc ID 1290326.1

  • Problem in Jndi lookup for  ITaskService

    HI,
    I am trying to initiate oracle bpm Human task programatically by using Java remotely.
    for this I am using following JNDI lookup for ITaskService.
    Hashtable ht = new
                  Hashtable<IWorkflowServiceClientConstants.CONNECTION_PROPERTY,java.lang.String>();
              ht.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_INITIAL_CONTEXT_FACTORY, 
                     "weblogic.jndi.WLInitialContextFactory");
              ht.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_PROVIDER_URL, "t3://localhost:7001");
              ht.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_SECURITY_PRINCIPAL, "username"); 
              ht.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_SECURITY_CREDENTIALS, "password");
              Context ctx  = new InitialContext(ht);
    ITaskService taskService = (ITaskQueryService)ctx.lookup("ejb/bpel/services/workflow/TaskServiceBean");
    taskService.initiateTask(task);
    It the right approach or not.
    Please help.

    To access human workflow api remotely try using the following code :
    Map properties = new HashMap();
      properties.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_PROVIDER_URL, "t3://localhost:8001");
      properties.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_SECURITY_CREDENTIALS, "welcome1");
      properties.put(IWorkflowServiceClientConstants.CONNECTION_PROPERTY.EJB_SECURITY_PRINCIPAL, "weblogic");
    IWorkflowServiceClient wfSvcClient =
      WorkflowServiceClientFactory.getWorkflowServiceClient(WorkflowServiceClientFactory.REMOTE_CLIENT, properties, null);
      //Get the task query service
      ITaskQueryService querySvc = wfSvcClient.getTaskQueryService();
      //Login as weblogic
      IWorkflowContext ctx = querySvc.authenticate("weblogic","welcome1".toCharArray(),null);
    after getting the workflow context, you can call any method like query task list. perform actions etc. just see the api doc.
    Regards,
    Anshul

Maybe you are looking for

  • Late 2007 MacBook Pro - Fresh install

    I have a late 2007 MacBook Pro. I want to do a fresh install. Is it best to use the original discs, which would take me back to tiger, or can I just use a new retail copy of Snow Leopard? Will that retail copy of Snow Leopard hold all the proper driv

  • Delivery get created with one line item from sale ord having two line item

    I have an issue when delivery is created with reference to a sales order. The sale order consist of a header with customer group VBKD-KDGRP = '01'. There are two line item for this header with item 10 having customer group '01' and line item '20' hav

  • Automatic update from Word source into Indesign

    Hi I have followed all threats and cannot seem to find a solution to my query. I have to complete a 280page annual report within a very short period of time. Based on the client it seems that there will be multiple changes on content after layout is

  • Getting ClassNotFoundException in Applet by using JDK1.6_20

    In my web application, we are using an applet which gets invoked from the jsp. Its working fine with jdk1.5 and 1.4 but when I am executing it on machine having JDK1.6_20 its throwing ClassNotFoundException. (Please see the log below) I cleared the c

  • WebUtil ORA-06508

    Hi all, I'm trying to setup webutil on Forms And Reports Services 10g with database 10g on RHEL 2. When I'm trying to run the demo form: WU_DEMO.fmx(compiled on the server machine) I am getting this error: FRM:40735: WHEN-CUSTOM-ITEM-EVENT trigger ra