JNDI lookup issue in weblogic 10 server

Hi all,
I have a serious problem in getting the datasource lookup. My application uses EJB3 and JPA and it is deployed in weblogic10. I configured datasource in the domain (ex:mydomain) using weblogic 10 admin console. Now when i try to call from a client program, it is giving me javax.naming.NameNotFoundException. I use eclipse IDE to deploy the application. From the IDE, i can start the oracle 10.3 server and it automatically deploys the application into the server in mydomain. The admin console shows that the application deployed fine. And i can see the webcontent WAR file and EJB jar deployed. Coming back to the issue.... I verified user_projects\domains\mydomain\config\jdbc\datasource-jdbc.xml and user_projects\domains\mydomain\config\config.xml file enteries. My entries are present in those files.
When i start the server i am getting below error...
<< Stacktrace >>
javax.naming.NameNotFoundException: While trying to look up jdbc in /app.; remaining name 'jdbc'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
     at weblogic.deployment.PersistenceUnitInfoImpl.lookUpAppScopedDataSource(PersistenceUnitInfoImpl.java:529)
     at weblogic.deployment.PersistenceUnitInfoImpl.reconfig(PersistenceUnitInfoImpl.java:549)
     at weblogic.ejb.container.deployer.EJBModule.reconfigPersistenceUnits(EJBModule.java:529)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:515)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
<< Client program snippet >>
Hashtable ht = new Hashtable();
               ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
               ht.put(Context.PROVIDER_URL, "t3://10.237.76.132:7001");
               InitialContext ctx = null;
               ctx = new InitialContext(ht);
               Object obj = (Object)ctx.lookup(EmployeeBean.RemoteJNDIName);
               EmployeeRemote empRemote = (EmployeeRemote)PortableRemoteObject.narrow(obj,com.acs.test.emp.EmployeeRemote.class);
               List empList = empRemote.getEmployeeDetails(1);
               System.out.println("SUCCESS"+empList.size());
<< Persistence.xml >>
<?xml version="1.0" encoding="UTF-8"?>

<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0">
<persistence-unit name="cmsepool">
<jta-data-source>java:/mydatasource</jta-data-source>
          <class>com.acs.test.emp.EmployeeVO</class>
          <properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.HSQLDialect"/>
          <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.WeblogicTransactionManagerLookup"/>
</properties>
</persistence-unit>
</persistence>

Make sure that this Datasource you created is Targetted to Admin Server and full Cluster (incase of cluster domain). From Admin Console, select your datasource and check for the Targets tab. Since its JNDI lookup error, most probably it may not be deployed properly.
HTH
Ravi Jegga

Similar Messages

Unable to do JNDI lookup in JDeveloper-Weblogic server

Dear All,
I'm getting the below error when i try to call stateless EJB which is deployed in Weblogic 10.3 from the java stand alone class.
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at HelloWorldClient.main(HelloWorldClient.java:21)
Caused by: java.net.ConnectException: t3://localhost:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     ... 8 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteCluster(RJVMFinder.java:316)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:205)
     ... 14 more
The Client code is :
Hashtable<String, String> env = new Hashtable<String, String>();
env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL,"weblogic");
env.put(Context.SECURITY_CREDENTIALS,"weblogic123");
env.put(Context.PROVIDER_URL,"t3://localhost:7101");
Context ctx = new InitialContext(env); // Error throws here.
System.out.println("Initial Context created");
I'm able to login localhost as admin console and see the JNDI name binding. But dont know why it throws this error.
Kindly help me out to resolve this issue.

Sir,
First of all pls try giving jdeveloper version...
can you try other combinations
like instead of 127.0.0.1, use localhost, actual ip of PC. Because when you are using 11.1.2.x.x version then before creating default domain jdeveloper asks the IP address to bind and make server accessible from that IP...
At-Last if problem is not solved then
Try this:
1) start integrated weblogic server from jdeveloper by selecting Run -> Start Server Instance
2) when weblogic is up go to http://localhost:7101/console
3) login (username weblogic password weblogic1), go to services, go to jdbc and create your datasource
4) shut weblogic down
5) goto C:\Documents and Settings\<your username>\Application Data\JDeveloper\system11.1.1.2.36.55.36\DefaultDomain\bin the path may be different depending on your version of jdeveloper
6) edit setDomainEnv.cmd and change "set WLS_JDBC_REMOTE_ENABLED=-Dweblogic.jdbc.remoteEnabled=true"
7) go back to jdev and start weblogic as above

Issue in Weblogic Server - Server Stops abruptly

Hi All,
I am facing an issue with Weblogic server(8.1). One of the managed servers stops abruptly. Server run for some days. After 5 or 6 days it stops without giving any log message. Admin(mgt server) and this managed server are running in the same box(AIX Environment). Below is the only log I got. Any idea why it is happening?
According to the BEA Message it may be due to network problem. Since both the servers are running in same box, i don't think it is network issue.
Can anyone please help me on this? - thanks in advance
Log Trace Message:
==================
<AF[196]: Allocation Failure. need 528 bytes, 67173345 ms since last AF>
<AF[196]: managing allocation failure, action=1 (0/1040390840) (32611304/33283912)>
<GC(197): freeing class jsp_servlet._ofr._invoice._shipper._jsp.__exceptioninvoicelist(302453c8)>
<GC(197): freeing class jsp_servlet._lcom._common._jsp.__page_navigation(3024ecc8)>
<Dec 21, 2005 10:47:18 PM KST> <Warning> <Management> <BEA-141138> <Managed Server ofrserver is disconnected from the ad
min server. This may be either due to a managed server getting temporarily partitioned or the managed server process exi
ting.>
<GC(197): freeing class jsp_servlet._ofr._filter._jsp.__filterdetails(30252718)>
<GC(197): freeing class jsp_servlet._lcom._admin._jsp.__devtools(3040f898)>
<GC(197): freeing class jsp_servlet._lcom._admin._util._jsp.__devtoolslogin(3040f260)>
<GC(197): freeing class jsp_servlet._lcom._admin._util._jsp.__processdevtoolslogin(30411870)>
<GC(197): freeing class jsp_servlet._ofr._admin._util._jsp.__xmlcommmanagerimport(30413e58)>
<GC(197): freeing class jsp_servlet._ofr._admin._util._jsp.__processxmlcommmanagerimport(30414a88)>
<GC(197): unloaded and freed 8 classes>
<GC(197): GC cycle started Wed Dec 21 22:47:23 2005
<GC(197): freed 721499624 bytes, 70% free (754110928/1073674752), in 263157 ms>
<GC(197): mark: 248258 ms, sweep: 1857 ms, compact: 13042 ms>
<GC(197): refs: soft 0 (age >= 32), weak 0, final 27363, phantom 0>
<GC(197): moved 0 objects, 0 bytes, IC reason=14>
<GC(197): stop threads time: 1356, start threads time: 19>
<AF[196]: completed in 282883 ms>
Thanks,
Shanmuga perumal
[email protected]

I think you should be able to follow the same steps but whenever you come across Domain B in the instructions, just substitute the values for Domain A. Because it is the same domain you may not even have to go through some of the certificate steps. If you have questions I suggest you post them in the WLS Security forum.
WebLogic Server - Security

Security issue between weblogic server

Hello,
Here is security issue that we are facing.
Here is setup
Environment 1
Admin server say "env1admin"
Managed Weblogic Server say "env1managed"
We deployed an EJB called HelloEJB in env1managed server and this has an api
sayHello(). HelloClient is a client to HelloEJB.
S/w Weblogic 6.1 sp3
Environment 2
Admin server say "env2admin"
Managed Weblogic Server say "env2managed"
We deployed an EJB called ServiceEJB in env2managed server and this has an api
serviceRequest(). We use weblogic role based security and restrict access to this
api by user HelloEJB.
s/w Weblogic 6.1 sp3
Here is how the system works:
We start the env2admin, env2managed (ServiceEJB is which is a Stateless session
EJB deployed in env2Managed)
We start the env1admin and env1managed (HelloEJB(which is a Stateless session
EJB is deployed in env1Managed)
Test case:
1)HelloClient invokes HelloEJB api sayHello().
2)Now at this point in ejbCreate() at HelloEJB() end we get a reference to ServiceEJB
using Jndi and the context is never closed ). HelloEJB then calls serviceRequest()
api in ServiceEJB. Then gets back a response and then returns response to HelloClient.
Now if we repeat the above testcase.
After step1 in step2 HelloEJB though has all the permissions to invoke api on
ServiceEJB gets an SecurityException.
Question is why doe this happen. Only way HelloEJB can make api calls to serviceEJB
is by making a lookup() every single time. Which is very expensive. I looked at
documents what they say is leave the context open and never close it. Though I
am doing that I am getting this exception.
Any thoughts ?
Thanks in advance,
Vijay

Here are the details of exception stack trace:
java.rmi.AccessException: Security violation: insufficient permission to access
method; nested exception is:
java.lang.SecurityException: Security violation: insufficient permission
to access method
java.lang.SecurityException: Security violation: insufficient permission to access
method
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:92)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:63)
at service.ServiceBean_nr0s19_EOImpl.sendServiceRequest(ServiceBean_nr0s19_EOImpl.java:25)
at service.ServiceBean_nr0s19_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
Vijay
"Vijay" <[email protected]> wrote:
>
Hello,
Here is security issue that we are facing.
Here is setup
Environment 1
Admin server say "env1admin"
Managed Weblogic Server say "env1managed"
We deployed an EJB called HelloEJB in env1managed server and this has
an api
sayHello(). HelloClient is a client to HelloEJB.
S/w Weblogic 6.1 sp3
Environment 2
Admin server say "env2admin"
Managed Weblogic Server say "env2managed"
We deployed an EJB called ServiceEJB in env2managed server and this has
an api
serviceRequest(). We use weblogic role based security and restrict access
to this
api by user HelloEJB.
s/w Weblogic 6.1 sp3
Here is how the system works:
We start the env2admin, env2managed (ServiceEJB is which is a Stateless
session
EJB deployed in env2Managed)
We start the env1admin and env1managed (HelloEJB(which is a Stateless
session
EJB is deployed in env1Managed)
Test case:
1)HelloClient invokes HelloEJB api sayHello().
2)Now at this point in ejbCreate() at HelloEJB() end we get a reference
to ServiceEJB
using Jndi and the context is never closed ). HelloEJB then calls serviceRequest()
api in ServiceEJB. Then gets back a response and then returns response
to HelloClient.
Now if we repeat the above testcase.
After step1 in step2 HelloEJB though has all the permissions to invoke
api on
ServiceEJB gets an SecurityException.
Question is why doe this happen. Only way HelloEJB can make api calls
to serviceEJB
is by making a lookup() every single time. Which is very expensive. I
looked at
documents what they say is leave the context open and never close it.
Though I
am doing that I am getting this exception.
Any thoughts ?
Thanks in advance,
Vijay

JNDI lookup using a proxy server

Hi,
I'm trying to use a weblogic server as a proxy server for a cluster of
weblogic servers. The static and dynamic content delivery works fine but
when I try to do a JNDI lookup from an applet client, I get a name not
resolved exception. I guess, it happens because the proxy server tries to
resolve the name from it's JNDI tree, whereas I expect it to forward this
request to one of the servers in the cluster. Is this possible? If it is, do
I need to set up some parameters in the proxy server? If not, can I do this
myself by writing a name resolution class which in turn will forward the
request to one of the servers in the cluster?
Any help would be greatly appreciated.
thanks
- sanjay

when u say "cluster of weblogic servers"..u mean the weblogic`s inbuilt
cluster..
the reason i ask is weblogic`s cluster do provide JNDI clustering too by using
cluster-wide naming tree..
Sanjay Aggarwal wrote:
Hi,
I'm trying to use a weblogic server as a proxy server for a cluster of
weblogic servers. The static and dynamic content delivery works fine but
when I try to do a JNDI lookup from an applet client, I get a name not
resolved exception. I guess, it happens because the proxy server tries to
resolve the name from it's JNDI tree, whereas I expect it to forward this
request to one of the servers in the cluster. Is this possible? If it is, do
I need to set up some parameters in the proxy server? If not, can I do this
myself by writing a name resolution class which in turn will forward the
request to one of the servers in the cluster?
Any help would be greatly appreciated.
thanks
- sanjay

BPM engine deployment issue on Weblogic server

Hello,
I read all threads related to this issue, but I am getting mad.
Yesterday:
I have successfully deployed BPM 10.3.1 + certified WLS 10.3.0 on Linux Redhat + Oracle
I have successfully created a BPM configuration with the BPM Admin configuration wizard.
I could successfully access to BPM workspace admin and BPM workskape.
Today:
I have restarted weblogic server and BPM, the engine is not starting, with an error raised in another thread. Below is the most detailed message:
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com', port: '80'..
weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-soapocengine.jar)
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '1' addresses, but could not connect over HTTP to server: 'www.bea.com', port: '80'.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
My server is not connected to the Internet, and will probably not. But it could not access the internet yesterday (before restart) neither...
a reply to another thread says that a patch coprrects this issue. which one is it? please note I cannot download it from the server... I have downloaded all public patches for WLS 10.3 for Linux (ZIP files), but the BSU tool refused to detect them... how should I proceed?
Thank you for your help
Hervé

Hi,
I have downloaded weblogic from oracle downloads 2 weeks back. i thought all the patches would be installed?? But am facing the same issue when deploying engine ear..
Do you think I need to install the above patch ???
A month back I downloaded ( might be by March) Weblogic. I was not facing any issue. But with the new download am facing the issue.
Kindly suggest.
Thanks,
Charan

JNDI lookup Issue

All,
I have this question in my head about JNDI lookups, but haven't received proper
information when i do research. The question is simple.
The setup is simple as well. Suppose that we have a typical WLS cluster setup,
with
WLS running in a JVM on a server host somewhere, with objects bound to its
JNDI tree, and we also have a WLS client Java application. The client connects
to WLS
and performs JNDI lookups on the server.
The question is, if the client uses JNDI to lookup an object that exists in a
separate JVM, it does load balancing and failover properly. Alternatively, if
client uses same JVM to lookup an object in failover case, we are encountering
application specific error. I just need to know what makes difference when you
lookup an object(RMI) from same JVM and separate JVM.
Any and all help appreciated,
-Senthil

No one?

Issues starting weblogic server

I get the following error in my Jdeveloper console whenever I try starting the webLogic server.
<AnnotatedLogger> <logWithThrowable> JAXB marshaller creation fails due to underlying error "javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespacePrefixMapper" must be an instance of type com.sun.xml.bind.marshaller.NamespacePrefixMapper, not oracle.wsm.resmgmt.ResourceMarshaller$ResourceNamespacePrefixMapper".
javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespacePrefixMapper" must be an instance of type com.sun.xml.bind.marshaller.NamespacePrefixMapper, not oracle.wsm.resmgmt.ResourceMarshaller$ResourceNamespacePrefixMapper
     at com.sun.xml.bind.v2.runtime.MarshallerImpl.setProperty(MarshallerImpl.java:502)
     at oracle.wsm.resmgmt.ResourceMarshaller$1.run(ResourceMarshaller.java:297)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.wsm.resmgmt.ResourceMarshaller.<init>(ResourceMarshaller.java:285)
     at oracle.wsm.resmgmt.ResourceMarshaller.<init>(ResourceMarshaller.java:263)
     at oracle.wsm.policymanager.accessor.BeanAccessor.buildIndexes(BeanAccessor.java:477)
     at oracle.wsm.policymanager.accessor.BeanAccessor.updateCache(BeanAccessor.java:1647)
     at oracle.wsm.policymanager.accessor.BeanAccessor.fetchDocuments(BeanAccessor.java:989)
     at oracle.wsm.policymanager.accessor.BeanAccessor.access$400(BeanAccessor.java:133)
     at oracle.wsm.policymanager.accessor.BeanAccessor$MissingDocsFetcherTask.run(BeanAccessor.java:208)
     at oracle.wsm.common.scheduler.TimerManagerWrapper$TimerListenerImpl.timerExpired(TimerManagerWrapper.java:57)
     at weblogic.timers.internal.commonj.ListenerWrap.timerExpired(ListenerWrap.java:37)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     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)
<WsmMessageLogger> <logSevere> Failed to retrieve requested documents due to underlying error "javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespac

go to the below loacation and remove the system folder and try to start weblogic server it will ask to set the login credentials and port number,
C:\Users\###\AppData\Roaming\JDeveloper
let us know how it goes...

BIBeans internationalization issue with weblogic server 8.1 sp2

We use oralce bibeans 9.0.4 to develop OLAP web application in Chinsese Simplified environment. When deploy the web application on the embedded OC4J server, everything goes well. All the labels (Line items and image button labels etc. ) of the crosstab is displayed in chinese. but it always display English labels when delploy it on weblogic server V8.1 sp2.
currently on my web page java.util.Locale.getDefault() return zh_CN
I have done two things:
first, add exportCharacterEncoding init param for UIXServlet
<init-param>
<param-name>exportCharacterEncoding</param-name>
<param-value>GBK</param-value>
</init-param>
second,Set locale for the BIThinSession instance in jsp file.
oracle.dss.addins.jspTags.BIThinSession bisession = (oracle.dss.addins.jspTags.BIThinSession) pageContext.findAttribute("SalesBIThinSession");
bisession.setLocale(Locale.getDefault());
Is this a bug that bibeans can not locate resource bundles correctly base on the user's specified environment? Is there an invisible environment variable base on which the bibean tags judge to select a resource file and result in this phenomenon?

The intersting point here is that the application works using an Oracle stack but does not work using an IBM stack. I will contact our development engineers for more information and will post another response when I have a reply.
Business Intelligence Beans Product Management Team
Oracle Corporation

JNDI lookup on a specific server node

Hi experts
I am facing the following issue, we are loading data from ECC tables on PI JAVA memory to improve performance at runtime, this is done by a JCO,
it works fine within one Java node. But when we tested it in Productive system (with 2 java nodes) it failed because data is stored in just one Java node, so if the message does not go through
that node it does not find that data.
This is part ofe the code from the UDF where we are loading data to java memory:
props.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
*                         props.put(javax.naming.Context.PROVIDER_URL, "sapms://localhost:8110     ");*
*                         props.put("domain", "true");*
And this is part of the code from the UDF where we are getting data from memory
javax.naming.Context ctx = null;
*          java.util.Hashtable props = new java.util.Hashtable(1);*
*          props.put("domain", "true");*
*          props.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");*
                                                                                props.put(javax.naming.Context.PROVIDER_URL, "sapms://localhost:8110");
Can someone give me some light about how to send data to both nodes or how to do the data lookup into a specific node??
Thanks in advanced.
Emmanuel

Hi,
I guess what you are trying to achieve is to build a cache of ECC data in PI memory. In this case you have to maintain local cache of the data on each server node. Hopefully the amount of memory required will not impact the system stability.
Regarding the lookup of different server node, although it is technically possible, you need to bind a remote object in the JNDI and use costly remote communication to transfer the data between the server nodes.
I guess you also have to think of some kind of update / eviction strategy for your cache.
Hope this helps!
Best Regards,
Dimitar

Data source JNDI lookup fails in Weblogic 12.1.2

What is changed in the Weblogic 12.1.2 JNDI handling?
My EJB 2.1 application has been working fine with Weblogic versions up to 12.1.1, but with version 12.1.2 it is giving the following error at startup:
weblogic.application.ModuleException: javax.naming.NameNotFoundException: remaining name: comp/env/jdbc/DataSourceAlias
where jdbc/DatasourceAlias is the res-ref-name of the actual datasource named jdbc/APP_DATASOURCE which is set through the admin console.
The discovery of the datasource is performed by this piece of code :
ds = initialContext.lookup ("java:comp/env/" + refName)
This is what is failing with Weblogic 12. After some research I found out that in order for the datasource lookup to succeed, I have to :
1) ignore the subcontext "comp/env" and
2) use the actual JNDI name "jdbc/APP_DATASOURCE" instead of the reference "jdbc/DataSourceAlias"
However for the EJBs, nothing is changed, they are found in the comp/env subcontext.
Hope this helps someone, or let someone tell me how the migration to Weblogic 12.1.2 is supposed to be done.

Hi,
If it is war then try to apply following Patch 13893259.
Regards,
Kal

Jndi lookup problem between weblogic 6.1 and 8.1

Hello,
I have a portal application running in weblogic 6.1(sp2). It needs to lookup a
Stateless Session Bean which is deployed in Weblogic 8.1.
I have the 8.1 version ejb client jar in my WEB-INF/lib
Here is my code:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.TengahInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://server1.abc.com:port);
ctx = new InitialContext(env);
Object objref = ctx.lookup(EJBJNDI_NAME);
mEJBHome = (EJBServiceHome)PortableRemoteObject.narrow(objref, EJBServiceHome.class);
mEJBService=mEJBHome.create();
An exception occurred during the ctx.lookup call:
javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException:
Problem finding error class; nested exception is:
java.lang.ClassNotFoundException: java.lang.StackTraceElement
java.lang.ClassNotFoundException: java.lang.StackTraceElement
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass
Loader.java:180)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAw
areClassLoader.java:68)
What troubles me is that the exact same code worked for a regular web application
(web1.war), but not the portal application (portal1.war). Both web1.war and portal1.war
are inside app.ear
Please help!! Any guess/suggestions are welcome.
Thank you!
Ellen

Hi,
All I can say is Weblogic6.1 doesnot use JDK1.4 compared to Weblogic8.1, hence the class java.lang.StackTraceElement is not found when the object is executed in 6.1.
This is clue which you may like to take forward for debugging your application.
Thanks.

EJB2.0 issue on weblogic server 8.1 sp4

We are doing some ejb2.0 development on weblogic 8.1 sp4, and We have noticed some unusual and undesirable behavior with CMR.
The following session bean code is used to define a Many-Many relationship between different entity beans in the same EJB using CMR.
The method does the following:
1. Gets the existing Collection of parents EJBs for the child EJB.
2. Checks that the new parent EJB is not in the existing parents Collection
3. Adds the new parent to the Collection and finally sets the parents Collections for the child EJB.
public static void addChild(EntityHandle a_parent, EntityHandle a_child)
throws TrackingException
TrackedEntityLocal parent = null;
TrackedEntityLocal child = null;
parent = getEntity(a_parent);
child = getEntity(a_child);
Collection parents = child.getParents();
if (!containsEJB(parents, parent)) // return true if parent already exists in collection parents.
parents.add(parent);
child.setParents(parents);
In the problem scenario we are creating the child and its parent entities in the same transaction.
We then define the raltionships by adding parents to the same child EJB on the client side within the same transaction (that created the EJBs) like this:
addChild( parentOne, child);
addChild( parentTwo, child);
addChild( parentThree, child);
I expect 3 records in the CMR EJB table entity_relationship but I end up with 6 records in table entity_relationship like this.
parentOne,child
parentOne,child
parentTwo,child
parentOne,child
parentTwo,child
parentThree,child
What seems to be happening is that these EJB relationships are being duplicated in the EJB cache which means that when the container persists the relationships it breaks a unique constraint that is defined in Oracle.
It seems that each time I call child.getParents() I get a copy of the bean's current parent relationships in the cache (which I then add one new parent to).
Even though I set the parent Collection back into the bean (which i would expect to replace the existing Collection) at persist time the container seems to attempt to persist 3 distinct Collections.
We only seem to get this problem if the parent entity itself has not yet been persisted.
If the parent EJBs have already been created in table entity beforehand, we only get 3 relationships in table entity_relationship.
parentOne,child
parentTwo,child
parentThree,child
Anybody has any idea what's going on here? thanks a million.
EJB schema below:
both parent and child are from one table:entity.
CREATE TABLE entity
( id INTEGER NOT NULL PRIMARY KEY,
type_id INTEGER NOT NULL
CONSTRAINT entity_FK
REFERENCES entity_type(id),
orig_comp_id INTEGER NOT NULL
CONSTRAINT entity_FK2
REFERENCES component(id)
entity_relationship defines the relation between parent and child
CREATE TABLE entity_relationship
( end1_id INTEGER NOT NULL
CONSTRAINT entity_relationship_FK
REFERENCES entity(id),
end2_id INTEGER NOT NULL
CONSTRAINT entity_relationship_FK2
REFERENCES entity(id),
type_id INTEGER DEFAULT(1)
NOT NULL
CONSTRAINT entity_relationship_FK3
REFERENCES entity_rel_type(id),
CONSTRAINT entity_relationship_PK PRIMARY KEY(end1_id,end2_id,type_id)
EJB descriptors given below:
============================================ejb-jar.xml===============================================
<entity>
<ejb-name>TrackedEntityEJB</ejb-name>
<local-home>uk.police.pnn.psni.eai.bcomp.tracking.entity.TrackedEntityHomeLocal</local-home>
<local>uk.police.pnn.psni.eai.bcomp.tracking.entity.TrackedEntityLocal</local>
<ejb-class>uk.police.pnn.psni.eai.bcomp.tracking.entity.TrackedEntityBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>entity</abstract-schema-name>
<cmp-field>
<field-name>id</field-name>
</cmp-field>
<primkey-field>id</primkey-field>
<security-identity>
<use-caller-identity/>
</security-identity>
</entity>
<ejb-relation>
<ejb-relation-name>entity-entity</ejb-relation-name>
<ejb-relationship-role>
<ejb-relationship-role-name>Entity-has-Parents</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>TrackedEntityEJB</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>parents</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
<ejb-relationship-role>
<ejb-relationship-role-name>Entity-has-Children</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<relationship-role-source>
<ejb-name>TrackedEntityEJB</ejb-name>
</relationship-role-source>
<cmr-field>
<cmr-field-name>children</cmr-field-name>
<cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
<container-transaction>
<method>
<ejb-name>TrackedEntityEJB</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
==========================weblogic-ejb-jar.xml===================================================
<weblogic-enterprise-bean>
<ejb-name>TrackedEntityEJB</ejb-name>
<entity-descriptor>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
</persistence>
</entity-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<local-jndi-name>bcomp.tracking.entity.TrackedEntityHomeLocal</local-jndi-name>
</weblogic-enterprise-bean>
=============================weblogic-cmp-rdbms-jar.xml==========================================
<weblogic-rdbms-relation>
<relation-name>entity-entity</relation-name>
<table-name>entity_relationship</table-name>
<weblogic-relationship-role>
<relationship-role-name>Entity-has-Parents</relationship-role-name>
<relationship-role-map>
<column-map>
<foreign-key-column>end2_id</foreign-key-column>
<key-column>id</key-column>
</column-map>
</relationship-role-map>
</weblogic-relationship-role>
<weblogic-relationship-role>
<relationship-role-name>Entity-has-Children</relationship-role-name>
<relationship-role-map>
<column-map>
<foreign-key-column>end1_id</foreign-key-column>
<key-column>id</key-column>
</column-map>
</relationship-role-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
Edited by: user10185877 on 26-Aug-2008 02:06

I am also wondering what the status of this problem is? It is preventing us from going to SP4.
_Mike

TopLink issues using Weblogic Server 8.1 SP3 and MAC OS X with Oracle 9i

Hi, I have successfully deployed my EJB (entity bean) on WLS 8.1 (the generic version) on Mac OS X. I also have installed Apple jdk 1.4.2 and everything seems to be ok. The server came up without any problem and can connect to my Oracle DB. I verify this from Weblogic console. However, when I try to access the bean (create/find), I got this AbstractMethodError exception. Can anyone help ?
Thanks for any help/pointer you can provide.
Regards,
Message = Could not create network. javax.ejb.TransactionRolledbackLocalExceptio
n: EJB Exception: : java.lang.AbstractMethodError: oracle.toplink.internal.ejb.c
mp.wls.Wls81BeanManager.localCreate(Lweblogic/ejb20/internal/InvocationWrapper;L
java/lang/reflect/Method;Ljava/lang/reflect/Method;[Ljava/lang/Object;)Ljavax/ej
b/EJBLocalObject;
at weblogic.ejb20.internal.EntityEJBLocalHome.create(EntityEJBLocalHome.
java:170)
at com.maranti.msm.server.objectRepository.Network_kmp5vn_LocalHomeImpl.
create(Network_kmp5vn_LocalHomeImpl.java:151)
at com.maranti.msm.server.topologyManagement.TopologyManagerEJB.createNe
tworkBean(TopologyManagerEJB.java:157)
at com.maranti.msm.server.topologyManagement.TopologyManagerEJB.getRootN
etwork(TopologyManagerEJB.java:347)
at com.maranti.msm.server.topologyManagement.TopologyManager_363sal_EOIm
pl.getRootNetwork(TopologyManager_363sal_EOImpl.java:1558)
at com.maranti.msm.server.topologyManagement.TopologyManager_363sal_EOIm
pl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Any idea, anyone ?

PI 7.11 JMS adapter using JNDI weblogic server issue

Hi SAP experts,
I have a scenario to integrate to a application using JMS adapters. we use SAP PI 7.11 version.
We have deployed JMS drivers successfully and We face issue here to connect to weblogic server
We are using JMS adapter using JNDI to connect to weblogic server version 10.3.
Can anyone help with the exact format to be used in JMS properties table and additional parameters table in JMS communication channel. Your quick help will be appreciated.
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up destination: AccrualDetailsQueue for profile: ConnectionProfile of channel: CC_SND_JMS on node: 3010950 having object id: 673696a9fe8c39fdab32213f0930afb3: javax.naming.NameNotFoundException: Unable to resolve 'AccrualDetailsQueue'. Resolved ''<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination(JndiConnectorImpl.java:168)<br

Hi Padmini,
Refer to the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
It was very helpful to me, for configuring the additional parameters in the communication Channel JMS.
I leave you some screenshots of the settings that I did.
I seize the opportunity to ask you, where do I can get the drivers (.Jar) for Weblogic?
Regards.
Rodrigo.

JNDI lookup issue in weblogic 10 server

Similar Messages

Maybe you are looking for