Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:

I am recieving the following error , when I try to get home intervface by using JNDI name from sample java program
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
If any one let me know solution, I 'll be gr8ful to u.
Regards,
Siva

Siva ramakrishna <> writes:
It probably means what it says: the name cannot be found. So either
you are looking up the wrong name or the thing did not get deployed
correctly.
andy
I am recieving the following error , when I try to get home intervface by using JNDI name from sample java program
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
If any one let me know solution, I 'll be gr8ful to u.
Regards,
Siva

Similar Messages

How to Bind EJBs under COS Naming Service

Hi,
I want bind EJBs under COS Naming serices and
how to lookup those EJBs from java clients.
I am using Weblogic 5.1.
thanks,
-Ramesh

Can you give a complete example of this? I'm having the same issue. We
have CORBA clients that we want to redirect to EJB implementations
instead of ORB servers. How do I bind the CORBA objects in CosNaming?
The example provided with WLS seems to cover RMI/IIOP but doesn't cover
CORBA client to EJB.
Thanks,
Andy Piper wrote:
"Ramesh Raju" <[email protected]> writes:
You can only bind CORBA objects in CosNaming, so you would have to
bind RMI-IIOP stubs.
andy
Hi,
I want bind EJBs under COS Naming serices and
how to lookup those EJBs from java clients.
I am using Weblogic 5.1.
thanks,
-Ramesh--

Cos Naming & WLS Naming Service problem in distributed Tuxedo application

Hi,
we have been starting our investigation into using the distributed application feature of Tuxedo (multiple machines running under 1 Tuxedo domain which make up the entire Tuxedo Application).
when trying to access WLS EJB object references from Tuxedo, we hit a road block.
we have been using the standard method of searching through Cos Naming for a bind context which refers to WLS Naming Service. (this method is documented online and in dev2dev samples) Under non distributed application setup (1 Tux domain with 1 machine as in all examples), everything works fine and I can see into 1 WLS server's JNDI tree. But when in distributed application setup where we want to have two (for example) machines and we also want two WLS managed server with each running on their own machine, it seems that there are some unexpected problems:
1. - only one set of GWADM/GWTDOMAIN is running
- each WLS managed server has its own WTC server
- each WTC server has its own LOCAL ACCESS POINTs
- each WTC server uses the single REMOTE ACCESS POINT
(since only one GWTDOMAIN is running in this scenario)
--> problem: only one of the managed server's JNDI tree can be traversed into, and only one of the WTC link works for Cos Naming -> WLS Naming Service resolution
2. - each machine is running their set of GWADM/GWTDOMAIN
- in dmconfig, two local Tux domain-ids are defined, for the
two groups of GW
- WTC server setup is identical to above; except
each of the WTC is pointing to separate REMOTE ACCESS POINTs
- when DOMAINID in ubbconfig is not defined, the same Cos Naming to WLS Naming Service search fails.
- when DOMAINID in ubbconfig is defined, the same Cos naming to WLS Naming Service search fails with an CORBA:INTERNAL error.
Does anyone know how to get Cos Naming -> WLS Naming Service working properly under a distributed Tuxedo application setup and also with multiple sets of GWADM/GWTDOMAIN?
Thanks.
Edited by a_tam at 04/17/2008 11:34 AM

Hi,
we have been starting our investigation into using the distributed application feature of Tuxedo (multiple machines running under 1 Tuxedo domain which make up the entire Tuxedo Application).
when trying to access WLS EJB object references from Tuxedo, we hit a road block.
we have been using the standard method of searching through Cos Naming for a bind context which refers to WLS Naming Service. (this method is documented online and in dev2dev samples) Under non distributed application setup (1 Tux domain with 1 machine as in all examples), everything works fine and I can see into 1 WLS server's JNDI tree. But when in distributed application setup where we want to have two (for example) machines and we also want two WLS managed server with each running on their own machine, it seems that there are some unexpected problems:
1. - only one set of GWADM/GWTDOMAIN is running
- each WLS managed server has its own WTC server
- each WTC server has its own LOCAL ACCESS POINTs
- each WTC server uses the single REMOTE ACCESS POINT
(since only one GWTDOMAIN is running in this scenario)
--> problem: only one of the managed server's JNDI tree can be traversed into, and only one of the WTC link works for Cos Naming -> WLS Naming Service resolution
2. - each machine is running their set of GWADM/GWTDOMAIN
- in dmconfig, two local Tux domain-ids are defined, for the
two groups of GW
- WTC server setup is identical to above; except
each of the WTC is pointing to separate REMOTE ACCESS POINTs
- when DOMAINID in ubbconfig is not defined, the same Cos Naming to WLS Naming Service search fails.
- when DOMAINID in ubbconfig is defined, the same Cos naming to WLS Naming Service search fails with an CORBA:INTERNAL error.
Does anyone know how to get Cos Naming -> WLS Naming Service working properly under a distributed Tuxedo application setup and also with multiple sets of GWADM/GWTDOMAIN?
Thanks.
Edited by a_tam at 04/17/2008 11:34 AM

Thread are gettin stuck causing the WebLogic server to hang

We are developing an application for an US client which inclueds the following technology.
- WebLogic 9.2 JMS (Foreign Server, Queue, Connection Factor, persistent Store)
- Oracle 10g & Oracle 9i
- J2EE (MDB)
Different application uses different databases.
After the server run for a few day it is getting a stuck thread and reported the same as a Hogging Thread in server -> monitoring -> thread. At this point the server hangs and stopped working with the status in 'warning' state (in the same page itself).
The problem remains until the managed server is restarted.
We have taken thread dump of different times and one of the error that we have got is attached below:
"[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.rjvm.ResponseImpl@1279315 WAITING
     java.lang.Object.wait(Native Method)
     weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:82)
     weblogic.rjvm.ResponseImpl.getTxContext(ResponseImpl.java:109)
     weblogic.messaging.dispatcher.DispatcherProxy.unmarshalResponse(DispatcherProxy.java:238)
     weblogic.messaging.dispatcher.DispatcherProxy.dispatchSyncTranFuture(DispatcherProxy.java:131)
     weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:241)
     weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:266)
     weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
     weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1061)
     weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:670)
     weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:455)
     weblogic.jms.client.JMSProducer.send(JMSProducer.java:337)
     weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:966)
     com.ctb.dex.messagehost.InputMessageListener.onMessage(Unknown Source)
     weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
     weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
     weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
     weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
     weblogic.jms.client.JMSSession.execute(JMSSession.java:3962)
     weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
     weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Any body has any idea why this is happening? Please let me know in case you need to know more about the problem. Mail me at [email protected].

Tom, we are experiencing the similar stuck thread max time out errors on our weblogic server(weblogic 8.1 sp5). Below is the thread dump:
Blocked lock chains
===================
Chain 4:
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" id=101 idx=0xca tid=19298 waiting for java/lang/String@0x9c1fb10 held by:
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=102 idx=0xcc tid=19299 in chain 3
Open lock chains
================
Chain 1:
"ExecuteThread: '33' for queue: 'weblogic.kernel.Default'" id=62 idx=0x80 tid=19223 waiting for java/lang/String@0xbd00b10 held by:
"ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" id=32 idx=0x44 tid=19192 (waiting on notification)
Chain 2:
"ExecuteThread: '45' for queue: 'weblogic.kernel.Default'" id=74 idx=0x98 tid=19235 waiting for java/lang/String@0x1d1083a8 held by:
"ExecuteThread: '11' for queue: 'weblogic.kernel.Default'" id=40 idx=0x54 tid=19200 (waiting on notification)
Chain 3:
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" id=100 idx=0xc8 tid=19297 waiting for java/lang/String@0x9c1fb10 held by:
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" id=102 idx=0xcc tid=19299 (active)
Can you help us in resolving the issue? This causes the weblogic server to hung and eventually non responsive.
Below are our java version details:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
Can you let me know how to proceed and what can be done to avoid this issue?
Thanks a bunch Tom.
Regards
RV

Please tell me How to access the COS NAMING?

In COS Naming, I create a new context as follows:
Initial context
|
QuerryApp (a new Context)
|
OrderQuery (a object)
But I don't know how to access the "OrderQuery"(using jdk 1.3.1).
Please help me!!
email: [email protected]

Please do not crosspost your questions.

JNDI lookup from OC4J to weblogic throws javax.naming.NameNotFoundException

Hi All,
We have the below setup in our production environment.
EJB application is deployed in the Weblogic 10.3.4.0 Server on Sun Solaris. The EJB version is 3.0
OC4J 10.2.0 is running on another Sun Solaris machine.
There are 2 webservice applications WEBSERV1 & TestSoapEJB running on this OC4J container.
We need to do lookup the EJBs deployed on the Weblogic server. For this we used the below logic in the web service's Stateless session bean:
String weblogicURL = "";
Properties props = new Properties();
try
props.load(Thread.currentThread().getContextClassLoader().getResourceAsStream("wl.properties"));
weblogicURL     = props.getProperty("weblogicURL");
catch (FileNotFoundException e)
e.printStackTrace();
catch (IOException e)
e.printStackTrace();
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(Context.SECURITY_PRINCIPAL,"weblogic");
ht.put(Context.SECURITY_CREDENTIALS,"weblogic654");
ht.put(Context.PROVIDER_URL, weblogicURL);
ctx = NamingManager.getInitialContext(ht) ;
// tried using //ctx = new InitialContext(ht); same behavior.
TestEJB.AdministratorEJB ejb = (TestEJB.AdministratorEJB) ctx.lookup("TestEJB#TestEJB.AdministratorEJB");
ctx.close();
When we first test first WEBSER1, the lookup is fine.
But when we test the second webservice WEBSER2, the webservice name itself not able to lookup: It gives the below error:
javax.naming.NameNotFoundException: remaining name: env/TestSoapEJB
Below is the stack throws thrown on browser:
500 Internal Server Error
javax.naming.NameNotFoundException: remaining name: env/TestSoapEJB
at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)
at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:59)
at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:64)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at oracle.j2ee.ws.SessionBeanRpcWebService.init(SessionBeanRpcWebService.java:65)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.loadServlet(HttpApplication.java:2354)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.findServlet(HttpApplication.java:4795)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2821)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:680)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:662)
It seems that, the OC4J is looking in Weblogic context. But it should be looking in its own context. How to resolve this issue.
The same case happens if i restart the OC4J and first test the TestSoapEJB the lookup is fine . But if i test the WEBSERV1 , it throws the same error as above. In short, if one of the webservices lookup is working fine, the other webservice is not working. At the same time only one webservice's lookup is working.
Kindly help me to resolve this issue.
regards,
Zia
Edited by: PT Expert on Sep 9, 2012 3:16 AM

I work now more that two days on this error!!!
-> I remade my complete jdev project, it did not work!
-> I deleted the jdev/system/j2ee/oc4j/workspace dir
-> I search for some .lock files
-> and many more tries!!! But without success...
Is there a way to reset the Embedded OC4J?

Weblogic 8.1 SP2 ORA-01000 caused by Weblogic's pending XA recovery process.

Hi, we are migrating our application from Weblogic 6.1 SP5 to Weblogic 8.1
SP2 and we are facing the nasty ORA-01000 problem.
After tracking it for some days we happened to find "what" was causing it.
After issuing the following select on an Oracle instance used by a weblogic
running for a day
SELECT sql_text,count(*) FROM V$OPEN_CURSOR
GROUP BY sql_text
ORDER BY sql_text
and this is what we get::
SQL_TEXT COUNT(*)
ALTER SESSION SET NLS_LANGUAGE = 'AMERICAN' 2
ALTER SESSION SET NLS_TERRITORY = 'AMERICA' 2
SELECT 1 FROM DUAL 2
SELECT VALUE FROM NLS_INSTANCE_PARAMETERS WHERE PARAMETER =' 2
SELECT count (*) FROM SYS.DBA_PENDING_TRANSACTIONS 2
SELECT formatid, globalid, branchid FROM SYS.DBA_PENDING_TRA 2669
SELECT max(version) FROM "SYS"."JAVA$POLICY$SHARED$TABLE" 2
begin :1 := JAVA_XA.xa_commit_new (:2,:3,:4,:5); end; 2
begin :1 := JAVA_XA.xa_end_new(:2,:3,:4,:5); end; 2
begin :1 := JAVA_XA.xa_start_new(:2,:3,:4,:5,:6); end; 2
insert into javasnm$(short, longname, longdbcs) values(:1,:2 2
select longname from javasnm$ where short = :1 2
(In fact there are two Weblogic instances running against the same Oracle
instance and as we didn't filtered by connection I supouse that's why
numbers "seem" to be "duplicated")
We do currently have 1500 cursors max declared for session in our Oracle's
ora.init file.
After activating Weblogic's jdbc.log we have seen that with an interval of 5
seconds the
SELECT formatid, globalid, branchid FROM SYS.DBA_PENDING_TRANSACTIONS
is issued against the DBMS.
After executing both selects on an SQLPLUS console we have seen that the
SELECT count(*)... sentence returns 1 and after looking at
SYS.DBA_2PC_PENDING table there is one transaction on it (although it was
already manually rollback forced three months ago). I know we should delete
already forced transactions in order to clean up that table but the fact is
we didn't and maybe that is what is causing Weblogic issuing the second
select (the SELECT formatid, globalid... one) periodically.
A number of questions come to our mind:
1. Is this Weblogic's correct behaviour? I mean, is it normal for weblogic
to issue this select every five seconds?
If yes.
2. Why is this select leaving opened cursors? I presume that this select is
being executed within a transaction and it's neither commited nor rolledback
If actually it is being executed within a transaction then:
3. Why is Weblogic opening a transaction to issue a select?
As additional info we have two datasources configured into our weblogic
server, I must say we do use TopLink as our persistence manager and it
requires both transactional (XA) and not transactional datasources to work.
We are using Oracle thin drivers (classes12.zip) to connect to an Oracle
8.1.7 database instance. I know that Weblogic 8.1 now ships with the
ojdbc14.jar Oracle thin driver classes but we are not sure if we can use it
with Oracle 8.1.7 (as it seems to be prepared to be used with Oracle 9.0.2.
Is it?).
Looking at jdbc.log we can also see this at the beginging of the file:
java.sql.SQLException: SQL operations are not allowed with no global
transaction by default for XA drivers. If the XA driver supports performing
SQL operations with no global transaction, explicitly allow it by setting
"SupportsLocalTransaction" JDBC connection pool property to true. In this
case, also remember to complete the local transaction before using the
connection again for global transaction, else a XAER_OUTSIDE XAException may
result. To complete a local transaction, you can either set auto commit to
true or call Connection.commit() or Connection.rollback().
I have readed somewhere at edocs.bea.com that Weblogic 8.1 -by default-
begins a transaction whenever using an XA connection (as some XA drivers
require a transaction to be started when using them, although IIRC this can
be disabled on Weblogic's console). If in fact it happens that we can
disable the default transaction oppening when using an XA connection, is it
safe? Is there a prefered way to solve this than disabling the transaction
"auto begining" feature?
I think there is also possible to disable Weblogic's pending transactions
auto-recover mechanism but we think this is a great Weblogic feature and we
would prefer not having to do it. As in two years we have managed to get
about three of them due to unexpected server crashes (even if it those cases
Weblogic 6.1 didn't managed to recover them at least it showed the problem
on the log).
Thanks if advance.
Regards.
Ignacio.

Seems that removing classes12.zip from the classpath solves the problem. I
don't get that periodic error any more so now I don't get the ORA-01000. I
still seeing -from time to time- the "SQL operations are not allowed with no
global
transaction by default for XA drivers" error in the jdbc.log though, so I
presume the ORA-01000 would raise sooner or later but now with a much larger
period after starting the server.
Well there seems that ojdbc14.jar has not so subtle changes. Let's hope
there are not "newer" issues with it that would not happen with
classes12.zip.
Ignacio.

Does Weblogic Jndi support naming.event

Hi gurus,
our app needs to be notified in case an object (already bound) has changed. or rebound into the jndi tree..
i tried using javax.naming.event.*
and the call to
EventContext = (EventContext)(new InitialContext(env)).lookup("");
gives me a ClassCastException...
java.lang.ClassCastException: weblogic.jndi.toolkit.WLContextStub
Any pointers..
I plan to use NamespaceChangeListener and ObjectChangeListener to get notified. didnt find any material in weblogic docs...
thanks in Advance
Nagesh

As I know, WL does not implement directory events machinery. You should use
another mechanism to notify your app about JNDI changes. For example, you
can use any LDAP directory service to bind your objects to. In this case,
directory events should work.
kesha
"Nagesh" <[email protected]> wrote in message
news:39edfc4d$[email protected]..
>
Hi gurus,
our app needs to be notified in case an object (already bound) haschanged. or rebound into the jndi tree..
i tried using javax.naming.event.*
and the call to
EventContext = (EventContext)(new InitialContext(env)).lookup("");
gives me a ClassCastException...
java.lang.ClassCastException: weblogic.jndi.toolkit.WLContextStub
Any pointers..
I plan to use NamespaceChangeListener and ObjectChangeListener to getnotified. didnt find any material in weblogic docs...
thanks in Advance
Nagesh

[Solved] Recent updates cause Gramps error: No module named _bsddb

Did a 'pacman -Syu' today and Gramps fails to start:
$ gramps
2599: ERROR: gramps.py: line 142: Unhandled exception
Traceback (most recent call last):
File "/usr/share/gramps/gui/grampsgui.py", line 271, in __startgramps
from GrampsLogger import RotateHandler, GtkHandler
File "/usr/share/gramps/GrampsLogger/__init__.py", line 45, in <module>
from _GtkHandler import GtkHandler
File "/usr/share/gramps/GrampsLogger/_GtkHandler.py", line 4, in <module>
from _ErrorView import ErrorView
File "/usr/share/gramps/GrampsLogger/_ErrorView.py", line 15, in <module>
from _ErrorReportAssistant import ErrorReportAssistant
File "/usr/share/gramps/GrampsLogger/_ErrorReportAssistant.py", line 14, in <module>
import bsddb
File "/usr/lib/python2.7/bsddb/__init__.py", line 67, in <module>
import _bsddb
ImportError: No module named _bsddb
Was working fine a few days ago ...
Last edited by ninian (2011-07-07 20:20:32)

Please put it in the bug report, as installing python2-bsddb didn't seem to fix the issue...
Report for python2: https://bugs.archlinux.org/task/25045 [CLOSED]
EDIT:
In fact, the problem comes from gramps, which should import bsddb3, see GRAMPS wiki.
Report for gramps (the config should be changed to use bsddb3 by default): https://bugs.archlinux.org/task/25050
Last edited by Fififox (2011-07-07 08:54:32)

Weblogic Ejb JNDI Naming

Dear all,
when I use Stateless Session bean with mappedName properties, it JNDI name become like mappName+#+packagename+classname.
I don't want "#" notation between them.
if it is not possible, how can i know default JNDI name without using mappedName property?
With Regards,
Wai Phyo

Make use of the weblogic-ejb-jar.xml file to control the EJB JNDI name. The following example works in WebLogic 11g and replaces the default #<package><class> with the specified values.
Regards
Neil
<weblogic-enterprise-bean>
<ejb-name>DepartmentEJB</ejb-name>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>com.sopragroup.uk.whitepaper.hr.jee.ejb.department.DepartmentRemote</business-remote>
<jndi-name>ejb/HR/DepartmentEJB</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>ejb/HR/DepartmentEJB</jndi-name>
<local-jndi-name>ejb/HR/DepartmentEJBLocal</local-jndi-name>
</weblogic-enterprise-bean>

Idlj java compile problem from badly named interfaces in idl

I am trying to build a java client to communicate with an application using corba interfaces.
The large/complex idl I am using to build all the client stubs has interface names that seem to cause problems for the generated java. For example there is an interface in the idl called 'Device' as well as an interface called 'DeviceOperations'. This causes problems because idlj creates java interfaces with the word 'Operations' appended to it.
So I get a bunch of weird results in my generated java which has many compiler errors.
Unfortunately I cannot change the idl because it is not an application I work on directly.
Any suggestions?
Thanks!

My guess is that you are between a rock and a hard place unless you can 1) change the IDL or 2) change how the IDL is compiled. You have said you can't do the former, so maybe you can influence the latter (unfortunately for you, I suspect not). On the change you can, keep reading.
IDL only creates interfaces such as DeviceOperations if you compile the IDL using the Tie model. But you would definitely have a problems since 1) the IDL has an interface called Device and DeviceOperations and as a result will create java files Device.java and DeviceOperations.java and 2) the Tie model will want to create two interfaces, DeviceOperations.java and DeviceOperationsOperations.java. I suspect that the second interface compiled by the IDL compiler will be the winner the first one will be overwritten).
If you can, change the IDL compilation to that you do not use the Tie model. However, you said you have no ability to change the IDL, so you also may not have the ability to change how it is compiled, so I am not sure if this is practical advice. I can't imagine that this application ever successfully used both interfaces.

What Causes High CPU Usage Even When PC is Idle

How can I fixed the high cpu usage on my pc?

mcmillan wrote:
rohankolay wrote:Right now i have kernel26-2.6.35.4 which i updated on 27 aug. That is around the same time the problem began.Should i downgrade it to kernel26-2.6.35.3 or kernel26-2.6.34.3?
I think most people have been seeing the problems in any of the 2.6.35 kernels, so 2.6.34.3 would be my recommendation
+1
And put kernel26 in IgnorePkg.

Naming Exception in looking up JMS queue

I use my code to send message to queue (DeliveryService/inbound) configured in an weblogic app server in a Dev. Environment. But when I use the same code but ofcourse different URL, username, password etc. to send to another queue with same JNDI (DeliveryService/inbound) @ SQA environment setup I get the following error:
javax.naming.NameNotFoundException: Exception in lookup.: `DeliveryService/inbound' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:63)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:235)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at gov.va.med.deliveryservice.dsd.delegates.jms.JMSDeliveryServiceDelegate.getOutboundQueue(JMSDeliveryServiceDelegate.java:229)
at gov.va.med.deliveryservice.dsd.delegates.jms.JMSDeliveryServiceDelegate.deliverMessage(JMSDeliveryServiceDelegate.java:147)
at gov.va.med.deliveryservice.dsd.delegates.BaseDeliveryServiceDelegate.sendMessagePTP(BaseDeliveryServiceDelegate.java:99)
at gov.va.med.deliveryservice.samples.PTPSend.dsTest1(PTPSend.java:202)
at gov.va.med.deliveryservice.samples.PTPSend.main(PTPSend.java:219)
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java:72)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 7 more
Any help/suggestion would be appreciated.
-Ankur

Hi ,
i am also facing the same problem on Unix OS, even the Queue and Connectionfactories are deployed properly.
Any help/suggestion would be appreciated.
But in Windows env its working fine.
java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Exception in lookup.: `
com/bt/jms/bridge/connectionFactory/CLA' could not be found. [Root exception is weblogic.corba.cos.n
aming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.security.subject.SubjectProxy.doAs(SubjectProxy.java:97)
at weblogic.security.subject.SubjectManager.runAs(SubjectManager.java:258)
at weblogic.security.Security.runAs(Security.java:67)
at com.concert.msc.common.util.WLUtil.runAs(WLUtil.java:43)
at com.bt.btgs.eai.testclient.JMSClient.processStart(JMSClient.java:49)
at com.bt.btgs.eai.testclient.JMSClient.main(JMSClient.java:40)
at com.bt.btgs.eai.testclient.PushFileOnebyOne.getInputFromUser(PushFileOnebyOne.java:85)
at com.bt.btgs.eai.testclient.StartTestClient.start(StartTestClient.java:49)
at com.bt.btgs.eai.testclient.StartTestClient.main(StartTestClient.java:23)
Caused by: javax.naming.NameNotFoundException: Exception in lookup.: `com/bt/jms/bridge/connectionFa
ctory/CLA' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.
NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:63)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:235)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.bt.btgs.eai.testclient.JMSClient.publishToQueue(JMSClient.java:90)
at com.bt.btgs.eai.testclient.JMSClient$Inner_PublishAction.run(JMSClient.java:74)
at weblogic.security.subject.SubjectProxy.doAs(SubjectProxy.java:89)
... 8 more
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming
/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java
:72)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
plz Would you reply me back quick.

Application client troubles

Hey guys,
I'm having some trouble getting my application client to pass a message to my jms queue. My code may be right and my queue maybe setup correctly but the input parameter I use to set the InitialContex keep throwing the exception:
parameter: t3:\\localhost:7001
The code works on a different laptop (that i don't have access to) so i'm thinking the parameter is being entered wrong :(
Exception in thread "Main Thread" javax.naming.InvalidNameException: url does not contain //
     at weblogic.corba.j2ee.naming.NameParser.parseURL(NameParser.java:395)
     at weblogic.corba.j2ee.naming.ORBHelper.parseURL(ORBHelper.java:611)
     at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:503)
     at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
     at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at cms.crown.jms.QueueSend.getInitialContext(QueueSend.java:119)
     at cms.crown.jms.QueueSend.main(QueueSend.java:87)
Anyone know what my mistake is ;P
thanks

Sorry, I stopped using the commandline parameter and hardcoded the url. New error...
Exception in thread "Main Thread" javax.naming.NameNotFoundException: Exception in lookup.: `weblogic/examples/jms/exampleQueue' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
     at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:65)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:230)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:168)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at cms.crown.jms.QueueSend.init(QueueSend.java:47)
     at cms.crown.jms.QueueSend.main(QueueSend.java:93)
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
     at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java:72)
     at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:208)
     ... 4 more

Error running UploadJars.sh

Hi All,
I'm getting the following error when trying to run the UploadJars utility. Any suggestions would be appreciated...
[oracle@toim02 bin]$ ./UploadJars.sh
./UploadJars.sh: line 30: /bin/java: No such file or directory
[oracle@toim02 bin]$ export JAVA_HOME=/orahome/software/jdk1.6.0_29/
[oracle@toim02 bin]$ ./UploadJars.sh
[Enter Xellerate admin username :]xelsysadm
[Enter the admin password :]
[Enter serverURL :[ t3://localhost:7001 ]]t3://localhost:7001
[Enter context Factory :[ weblogic.jndi.WLInitialContextFactory ]]weblogic.jndi.WLInitialContextFactory
UsernamePasswordLoginModule.initialize(), debug enabled
UsernamePasswordLoginModule.login(), username xelsysadm
UsernamePasswordLoginModule.login(), URL t3://localhost:7001
oracle.iam.platform.utils.NoSuchServiceException: java.lang.reflect.InvocationTargetException
at oracle.iam.platform.OIMClient.getServiceDelegate(OIMClient.java:197)
at oracle.iam.platform.OIMClient.getService(OIMClient.java:174)
at oracle.iam.platform.OIMClient.loginSessionCreated(OIMClient.java:209)
at oracle.iam.platform.OIMClient.login(OIMClient.java:136)
at oracle.iam.platform.OIMClient.login(OIMClient.java:129)
at oracle.iam.platformservice.utils.JarUploadUtility.main(JarUploadUtility.java:217)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at oracle.iam.platform.OIMClient.getServiceDelegate(OIMClient.java:193)
... 5 more
Caused by: oracle.iam.platform.utils.NoSuchServiceException: javax.naming.NameNotFoundException: Exception in lookup.: `ejb/stateless/ClientLoginSessionService#oracle/iam/platformservice/api/ClientLoginSessionServiceRemote' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at oracle.iam.platformservice.api.ClientLoginSessionServiceDelegate.<init>(Unknown Source)
... 10 more
Caused by: javax.naming.NameNotFoundException: Exception in lookup.: `ejb/stateless/ClientLoginSessionService#oracle/iam/platformservice/api/ClientLoginSessionServiceRemote' could not be found. [Root exception is weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:65)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:289)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:227)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:132)
at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:88)
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:130)
at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:155)
... 11 more
Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:weblogic/corba/cos/naming/NamingContextAny/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextAnyPackage.NotFoundHelper.read(NotFoundHelper.java:72)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:87)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:267)
... 17 more
Error occurred in performing the operation:
null
Please check the server logs for details

Hi
You have to run this command the from OIM machine.
I think you are running this command from other machine.
Also make sure OIM managed servers are up.
Thanks,
Kuldeep
Edited by: Kuldeep on May 7, 2012 2:15 AM

Caused by: weblogic.corba.cos.naming.NamingContextAnyPackage.NotFound: IDL:

Similar Messages

Maybe you are looking for