JMS & Tomcat & J2EE

hi all
I would like to run JMS with Tocmat 4.1.24. and SUN J2EE.
I encountered following problem.
three days .... I can't solve this problem.
there is a lot of this question in this forum. but no answer. so I try to again.
this is very important to me....sample code is basic sample in JMS tutorial.
personally, It's very important to me.
thanks in Advance.
following error ->
javax.naming.NameNotFoundException: Name QueueConnectionFactory is not bound in
this Context
at org.apache.naming.NamingContext.lookup(NamingContext.java:811)
at org.apache.naming.NamingContext.lookup(NamingContext.java:194)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.safeidentity.ps.auth.TestJMS.doGet(TestJMS.java:31)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)

it's all very well having Tomcat, but it's not JMS Server. You need to have a JMS Server running, which is what your application should be 'looking up'. Try the open source OpenJMS (http://openjms.sourceforge.net). Once the JMS server is running (which is what creates the JNDI context) you will then be able to find/bind to it.

Similar Messages

JMS tomcat problem

Hi,
I have Tomcat 4.0.3 and a J2EE 1.3.1 reference implementation server.
From the tomcat server, I am trying to publish into a topic that is on a remote machine. However I get the exception
javax.naming.NameNotFoundException : Name TopicConnectionFactory is not bound in this context.
Since this is running from the tomcat server, I cannot give the java -D option for starting the client.
Also, I have the orb.properties modified to the required machine name.

javax.naming.NameNotFoundException : NameTopicConnectionFactory is not bound in this context.As the exception says, this is not a JMS problem but rather a JNDI issue. Are you sure that you have bound the name "TopicConnectionFactory" to an object in the context that you are doing the lookup in.
Steve Trythall

What is the best way to SSO custom Tomcat J2EE, Sharepoint and Portal?

We are implementing EP7.0 and I believe we can use logon tickets and SAPSECULIB to integrate all our infrastructure which is Sharepoint (Runs on IIS), our custom J2EE applications (run on Apache webserver and Tomcat).
Is using of logon tickets and SAPSECULIB the recommended way to accomplish SSO or is there a better way?
Thanks in advance

Hi Victoria,
I would put the html file that you generated on the file system
let say the Apache/Apache/htdocs
Then I'd put an HTML portlet on the page and show the HTML file using an iframe
<iframe src="name of your file"
            height="600"
            width="800"
            frameborder="0"
            scrolling="no"
</iframe>Hope this helps.
Cheers
Diego

FAM 8.0, Tomcat J2EE agent installation problem

Hello:
I was able to install FAM 8.0 in Tomcat 6.0.14 on Ubuntu (7.04) Linux. Everything seems fine. In the end, the applications I want to use with OpenSSO also make use of Tomcat 6.0.14. I noticed on the opensso users email list that the Tomcat 3.0 agent won't be available until early next year; but that the 2.2 agents should work with FAM 8.0. So, I got the the J2EE agent for Tomcat - SJS_Tomcat_Server_55_agent_2.2-01.tar.gz. The documentation makes no references to Tomcat 6, and I'm hoping this is due to the fact that Tomcat 6 was not available when the documentation was written.
Does this agent work with Tomcat 6? I have this problem when installing the agent (agentadmin --install):
$CATALINA_HOME environment variable is the root of the tomcat
installation.
[ ? : Help, < : Back, ! : Exit ]
Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Invalid directory specified for the $CATALINA_HOME environment variable
Invalid CATALINA_HOME directory :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14I can see in debug/agentadmin.log the following:
[05/24/2008 13:06:37:684 PDT] FileSystemValidator : Is directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? true
[05/24/2008 13:06:37:686 PDT] HomeDirValidator : Is $CATALINA_HOME directory /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14 valid ? false
[05/24/2008 13:06:37:686 PDT] Invalid CATALINA_HOME directory : /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14This directory does indeed exist, and is accessible by the user I'm logged in as. It appears FileSystemValidator agrees with me, but HomeDirValidator has a problem. I tried this on both Ubuntu 6.04 and Mac OS X 10.5.2. Does this indicate that Tomcat 6 is not supported? Or is it indicative that neither OS on which I've tried to install the agent is officially supported?
Thanks!
Jeff

Hi Denis:
Before being redirected to another short term task, I did indeed get the Tomcat 6 agent to work. I probably won't be able to look at OpenSSO again seriously for another couple of months. :(
I have the OpenSSO server running on Tomcat 6.0.14 on Ubuntu 6.x Linux running in a virtual machine on my Mac. I was not able to get the server to run directly on the Mac, and I cannot remember the reason at this time.
But, as far as the agent goes, I run it again using Tomcat 6.0.14 on my Mac (Mac OS X 10.5.2), using the 1.5 JRE. I do have the agentapp war deployed as well as the agentsample web application to play with. In my catalina.out file:
Jun 18, 2008 10:07:20 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
Jun 18, 2008 10:07:20 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive agentapp.war
Jun 18, 2008 10:07:21 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive agentsample.war
Jun 18, 2008 10:07:22 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Jun 18, 2008 10:07:22 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8011
Jun 18, 2008 10:07:22 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=nullI have no error messages is any Tomcat log file.
I checked out the source code for the Tomcat v6 agent (2.2) on May 27, so I don't know how that compares to yours or what's been checked into CVS since my build. I also don't know what the OpenSSO NamingService is.
I assume you used fully qualified domain names to specify the web application to be protected by agent as well as the OpenSSO server itself. The following is the output of the conversation when I run the agent installer script on my system. It has been redacted a bit (domain name and encryption key) to protect my client, but otherwise this is what I supplied to the installer:
Enter the complete path to the directory which is used by Tomcat Server to
store its configuration Files. This directory uniquely identifies the
Tomcat Server instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the Tomcat Server Config Directory Path
[/opt/apache-tomcat-6.0.14/conf]: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
Enter the fully qualified host name of the server where Access Manager
Services are installed.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Host: login.opensso.example.com
Enter the port number of the Server that runs Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services port [80]: 8080
Enter http/https to specify the protocol used by the Server that runs Access
Manager services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Protocol [http]:
Enter the Deployment URI for Access Manager Services.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Deployment URI [/amserver]: /opensso
Enter the fully qualified host name on which the Application Server
protected by the agent is installed.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Host name: analysis.opensso.example.com
$CATALINA_HOME environment variable is the root of the tomcat
installation.
[ ? : Help, < : Back, ! : Exit ]
Enter the $CATALINA_HOME environment variable: /Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Choose yes to deploy the policy agent in the global web.xml file.
[ ? : Help, < : Back, ! : Exit ]
Install agent filter in global web.xml ? [true]:
Enter the preferred port number on which the application server provides its
services.
[ ? : Help, < : Back, ! : Exit ]
Enter the port number for Application Server instance [80]: 8090
Select http or https to specify the protocol used by the Application server
instance that will be protected by Access Manager Policy Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the Preferred Protocol for Application Server instance [http]:
Enter the deployment URI for the Agent Application. This Application is used
by the agent for internal housekeeping.
[ ? : Help, < : Back, ! : Exit ]
Enter the Deployment URI for the Agent Application [/agentapp]:
Enter a valid Encryption Key.
[ ? : Help, < : Back, ! : Exit ]
Enter the Encryption Key [XXmyencryptionkeyXX]:
Enter a valid Agent profile name. Before proceeding with the agent
installation, please ensure that a valid Agent profile exists in Access
Manager.
[ ? : Help, < : Back, ! : Exit ]
Enter the Agent Profile name: testagent1
Enter the path to a file that contains the password to be used for identifying
the Agent.
[ ? : Help, < : Back, ! : Exit ]
Enter the path to the password file: /Users/jas/Development/opensso/tryout/agent_password
SUMMARY OF YOUR RESPONSES
Tomcat Server Config Directory :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf
Access Manager Services Host : login.opensso.example.com
Access Manager Services Port : 8080
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /opensso
Agent Host name : analysis.opensso.example.com
$CATALINA_HOME environment variable :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14
Tomcat global web.xml filter install : true
Application Server Instance Port number : 8090
Protocol for Application Server instance : http
Deployment URI for the Agent Application : /agentapp
Encryption Key : XXmyencryptionkeyXX
Agent Profile name : testagent1
Agent Profile Password file name :
/Users/jas/Development/opensso/tryout/agent_password
Verify your settings above and decide from the choices below.
1. Continue with Installation
2. Back to the last interaction
3. Start Over
4. Exit
Please make your selection [1]: 1
Updating the
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/bin/setclasspath.sh
script with the Agent classpath ...DONE.
Creating directory layout and configuring Agent file for Agent_001
instance ...DONE.
Reading data from file
/Users/jas/Development/opensso/tryout/agent_password and encrypting
it ...DONE.
Generating audit log file name ...DONE.
Creating tag swapped AMAgent.properties file for instance Agent_001 ...DONE.
Creating a backup for file
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
...DONE.
Creating a backup for file
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
...DONE.
Adding SJS Tomcat Agent Realm to Server XML file :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/server.xml
...DONE.
Adding filter to Global deployment descriptor file :
/Users/jas/Development/opensso/tryout/apache-tomcat-6.0.14/conf/web.xml
...DONE.
Adding SJS Tomcat Agent Filter and Form login authentication to selected Web
applications ...DONE.
SUMMARY OF AGENT INSTALLATION
Agent instance name: Agent_001
Agent Configuration file location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/config/AMAgent.properties
Agent Audit directory location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/audit
Agent Debug directory location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/Agent_001/logs/debug
Install log file location:
/Users/jas/Development/opensso/tryout/tomcat_v6_agent/logs/audit/install.log
Thank you for using Access Manager Policy Agent
[jaslap:tryout/tomcat_v6_agent/bin] jas% Can you post the exception details you're getting. That might help someone diagnose the problem.
Take it easy,
Jeff

Connecting JMS to J2EE Reference Implementation 1.3 beta

Is it possible to write JMS client talking with J2EE server without having in path j2ee.jar? Something like remote small client communicating with the server due JMS? Do I have to use some third party
software (I have swiftMQ in mind) for this? If somebody have configuration for swift bridge to J2EE
Refernce Implementation can you share it?

The JMS service provider that comes with J2EE SDK 1.3 is only a reference implementation of the JMS API.
In a real application system, one will be using a JMS service provider from some vendor. Preferably one that is certified to be J2EE compatible.
In fact, this is true as such for anything in j2ee.jar Through j2ee.jar, Sun provides a reference implementation of J2EE APIs with its J2EE SDK and in a real application one will not have j2ee.jar in the client or server classpath. Instead one will use jar files specific to the vendor that one has chosen.
Specifically about swiftMQ, as per Sun, it is not a J2EE licensee. swiftMQ is JMS 1.0.2 compliant. But it is not certified to be J2EE compatible.
Refer http://java.sun.com/products/jms/nonlicensedvendors.html for more details.

JDBC, Tomcat, J2EE server

I would like to request help with JDBC, Tomcat and the J2EE server.
I have figured out how to connect a servlet running in Tomcat 4.0 to a Filemaker database using Filemaker's JDBC drivers:
Class.forName("com.fmi.jdbc.JdbcDriver");
fmpConnection = DriverManager.getConnection("jdbc:fmpro:http://127.0.0.1:80");
Now I'm trying to use the drivers in a web application (CMP, session facade - much along the lines of Sun's Duke's Bank app) in the free J2EE server downloadable from Sun. When I try to 'Generate Default SQL' in the 'deployment settings' for the CMP that uses the driver (via JNDI), an error dialogue box displays "java.sql.SQL.Exception: Feature Not Supported". No default sql is generated.
This web app works all right with MySQL.
I was wondering if someone out there could offer some advice on how to interpret the error message.
Thanks.

Hi,
throw away ur jdbc driver.some standard jdbc methods (required by the
container) may be missing in your jdbc driver. refer vendor
documnets/faq on error messages and its expalanation.stick on the
database and driver which is giving u a satisfacory performance
(seems MySQL is working fine for u !).
HTH,
asharaf

JMS in J2EE

I have tried to modify the JMS example in /jms/clientmdbentity folder and it works fine. But what I have tried to convert from Container-managed-persistence into Bean-managed-persistence bean and it does not work. And I really don't understand the error message, it says something like this: can not add another resources ....
I also tried a simple java class which access both database resource and jms resource and the error is similar, if anyone can help that would be great.
Thanks

I have to create new jdbc resource which used XA Datasource (PointbasePool) and it works OK now. I only doing this in order to have a better understanding the JMS. Thanks anyway.

Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish


Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

How to enable JMS to be J2EE Compliant from within JVM

I am wondering how I can use JMS in J2EE compliant mode from within the JVM via a Java stored procedure.
I know that I can set a property (i.e. oracle.jms.j2eeCompliant="true") at execution time, but was wondering how I can make the entire JVM J2EE compliant.

You cannot make the JVM J2EE compliant! However, you can use some J2EE APIs such as JMS, on top of J2SE.
See a basic use of JMS in Java stored procedure
http://otn.oracle.com/sample_code/tech/java/jsp/samples/jms/Readme.html
Note: the main purpose of JMS support within the database is to integrate with AQ.
Kuassi

Getting the below error while using the JMS server.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

The pooled JMS session is enlisted in another transaction error

I have an MDB with pool size 2 deployed in weblogic 9.2.3(linux). I see the following error in server logs.
<May 27, 2009 7:32:26 AM CDT> <Error> <EJB> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: javax.jms.JMSException: [J2EE:160054]The pooled JMS session is enlisted in another transaction and may not be used elsewhere
The exception is : javax.jms.JMSException: [J2EE:160054]The pooled JMS session is enlisted in another transaction and may not be used elsewhere
     at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
     at weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(WrappedTransactionalSession.java:196)
     at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:198)
     at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:297)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:394)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:517)
     at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:533)
     at java.lang.Thread.run(Thread.java:595)
>
any idea why this error is coming??

Looks it is like a bug, you can ask patch for from support.

Language support in JMS adapter with Oracle JDev 10.1.3.1

Hi,
I' using JDeveloper 10.1.3.1 with Oracle SOA Suite - ESB 10.1.3.1 in the following scenario:
1) Use Database adapter with "on insert" condition to read Student record with Chinese name (Unicode format) - ESB process
2) Use JMS adapter to push this data into "DemoTopic" as string - ESB process
3) Use Message Driven Bean's (EJB 3.0) "onMessage" method to fetch the data from JMS topic - J2EE app
4) Use JDBC executeUpdate to update this Chinese name into another database table - J2EE app
5) Finally, verify the updated Chinese name in ADF application - J2EE app
Prerequisites
1) The database charset on both sides of the flow is UTF8
2) The ADF application JSF page encoding is UTF8
3) The SOA Suite is installed on DB repository (UTF8 charset)
Result
1) The flow from Step 1-5 works.
2) But, the println of the JMS message (holding the Chinese name) gives "????" when checked with Wordpad (Unicode readable word processor)
3) Junk characters are inserted into the database
Please let me know where I'm going wrong. Also, let me know if I need to configure/set the character encoding in OC4J, or the JMS adapter and how.

Hi all,
This is been resolved by using the AL32UTF8 character set in the database. JMS adapter by default supports UTF-8. No setting/configuration needs to be done.

JMS queue question

Hi all,
I am using Weblogic Application Server and say I have 1000 messages in a JMS Queue say "Q1".
Q1. How are these messages picked up from the queues? i.e. by a thread etc.
Q2. If they are picked up by threads then who configures these threads? Are they default threads created by the Weblogic Application Server or are user-created threads?
Q3. Also, if 20 threads are involved in picking the messages from the queue and of them one thread snaps while picking the message then what will happen? and what will be the solution??
Thanks.

Q1/Q2*:
The answer to your question is "its provider specific".
You will need someone who explicitly works on weblogic to provide specifics so you may want to utilize a weblogic specific forum instead of a generic JMS forum
I'll try to answer this in very generic terms that should apply to all providers:
If you are receiving messages with an MDB: there is a thread pool associated with the resource adapter which plugs the JMS provider into the server. This is generally configured as part of the application server configuration. That pool dictates the maximum number of threads which can call the same MDB's at the same time.
If you are receiving messages with a Servlet: In this case, you are probably calling receive within the servlet. That will use the thread provide by the webstack which is executing the servlet
If you are receiving messages in an AppClient or Standalone provider: You are using your own thread if you call receive(), or a thread provided by the provider if you are calling onMessage()
In all cases, the provider may be allocating additional threads "beneath the covers" to process those messages.
Q3*:
I'm not quite sure what snaps means. Threads run until they exit. I'm going to guess that the question is "what if the MDB or code throws a RuntimeException". If you mean something different, please supply a more specific description of the error.
This one depends on what whether or not you are using transactions and how you are receiving those messages.
If you are using transactions in an MDB: the transaction will rollback and the message will be redelivered to another consumer.
In all other cases, it depends on the specifics (I was going to list them but it seems like to much work for a Friday afternoon).
If you are using a non-transacted or non-MDB method to retrieve the messages, let me know and I can tell you how, per the JMS and J2EE specs, it should work. I'll need to know acknowledge mode/transaction, type of client and if you are calling receive() or onMessage().
-- Linda

Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'

Hi
When executing import/export service through FSM we are getting below error on server console. Can someone please help us to resolve this.
<Nov 22, 2012 10:25:14 PM IST> <Error> <oracle.j2ee.ws.common.jaxws.JAXWSMessages> <BEA-000000> <[MessageID: uuid:3eac9f32-ad81-4d96-b5b2-18cf0fd887c0[migRequestId=300100015300332][migObjectId=300100015300326][]] Could not send async request message to the JMS queue.
java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:365)
at oracle.j2ee.ws.server.jaxws.JMSChannel.getConnection(JMSChannel.java:468)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendMessage(JMSChannel.java:235)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendRequest(JMSChannel.java:199)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate$JMSMessageQueue.send(AsyncServiceRuntimeDelegate.java:170)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate.pro
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
FYI:
The "oracle.jrf.ws.async_template_11.1.1.jar" jar file required for JMS (oracle.j2ee.ws.server.async.) which is present in below directory path of weblogic standalone.
Edited by: user12820425 on Dec 2, 2012 11:56 PM

Are you using Standalone (or) Integrated WLS. It works only on Standalone WLS.
Also for these issues, please put this in Cross Pillar Integration Forum. Contact Ning.Dong

JMS with Eclipse

HI
I downloaded the example for JMS for J2EE 5. But I see these examples are developed in Netbeans... and the problem is particularly during compilation using ant... which depends on NetBeans. How do I proceed with running these examples in Eclipse?

could you describe the necessary changes in details? I met the same problem as yours. but connectionFactory or queue cannot be retrieved with " @Resource(mappedName = "jms/ConnectionFactory")". could you help me ?

JMS & Tomcat & J2EE

Similar Messages

Maybe you are looking for