PasswordSync with a Sun JMS Server: javax.jms.QueueConnectionFactory

Hi,
I have installed Sun IDM 8.1 and Sun DSEE7 and uses Active Directory as source for identities.
I then added a resource for the JMS Listener, but when I tried to do Test Connection I got this message:
Test connection failed for resource:
java.lang.ClassCastException: com.sun.messaging.ConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory
Can anybody help me with this.
rgds
Crimson
Edited by: Crimson on May 3, 2010 4:46 AM

Hi Sean,
it's better to ask this question at Sun Java System Messaging Server forum:
http://swforum.sun.com/jive/forum.jspa?forumID=15

Similar Messages

Configuring message redelivery with jmcjca (sun-jms-adapter) in Glassfish

I use Glassfish v2 server and its OpenMQ as JMS Provider.
My MDB is configured to use sun-jms-adapter for accessing JMS Provider.
ra.xml of adapter wasn't change so all configuration is done through the sun-ejb-jar.xml of my MDB.
Type of destination my MDB listens to is javax.jms.Topic.
At the same time, I have defined the following redelivery strategy in the sun-ejb-jar.xml
<activation-config-property>
<activation-config-property-name>RedeliveryHandling</activation-config-property-name>
<activation-config-property-value>2:1000; 3:move(queue:*psdmqqueue*)</activation-config-property-value>
</activation-config-property>
psdmqqueue is an administred server Destination of type javax.jms.Queue. So a target destination of MDB is topic and redelivery should be performed to queue
The problem is that application deplyment failes with this configuration with the following exception:
#|2008-11-22T18:38:48.152+0300|WARNING|sun-appserver9.1|com.stc.jmsjca.core.Activation|_ThreadID=169;_ThreadName=JMSJCA connect;_RequestID=ed86af75-1577-4548-ac57-60ca127a28a2;|JMSJCA-E016: [sync-Durable TopicSubscriber(provisioning_subscription)(lookup://targetTopic) @ [mq://localhost:7676/jms]]: message delivery initiation failed (attempt #85); will retry in 10 seconds. The error was: java.lang.ClassCastException: com.sun.messaging.jmq.jmsclient.XATopicSessionImpl
java.lang.ClassCastException: com.sun.messaging.jmq.jmsclient.XATopicSessionImpl
at com.stc.jmsjca.core.RAJMSObjectFactory.createDestination(RAJMSObjectFactory.java:423)
at com.stc.jmsjca.core.Delivery.createDLQDest(Delivery.java:626)
at com.stc.jmsjca.core.SyncDelivery.start(SyncDelivery.java:204)
at com.stc.jmsjca.core.Activation.asyncStart(Activation.java:535)
at com.stc.jmsjca.core.Activation.access$000(Activation.java:80)
at com.stc.jmsjca.core.Activation$1.run(Activation.java:343)
at java.lang.Thread.run(Thread.java:595)
Could you please help me to figure out what is wrong with my configuration?
Part of sun-ejb-jar.xml related to ra activation spec:
<mdb-resource-adapter>
<resource-adapter-mid>sun-jms-adapter</resource-adapter-mid>
<activation-config>
<activation-config-property>
<activation-config-property-name>ConnectionURL</activation-config-property-name>
<activation-config-property-value>lookup://targetConnFactory</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>Destination</activation-config-property-name>
<activation-config-property-value>lookup://targetTopic</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>DestinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Topic</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>RedeliveryHandling</activation-config-property-name>
<activation-config-property-value>2:1000; 3:move(queue:psdmqqueue)</activation-config-property-value>
</activation-config-property>

</activation-config>
</mdb-resource-adapter>
</ejb>
</enterprise-beans>
</sun-ejb-jar>

Hi Alexej,
I looked at the problem and found out what the issue is. We recently added some functionality that will test if the dead letter destination is in fact a valid destination -- we thought it's better to find that out upfront, rather than if an error occurs. This is especially important with dead letter destinations being looked up in JNDI: mistakes are easily be made there.
In any case, this new functionality introduced a problem where messages are sent from a queue, and the dead letter destination is a topic, or vice versa, where messages are received from a topic, and the dead letter destination is a queue.
In case you're wondering why: we still need to support JMS 1.0.2 servers. For these servers, the queues and topics are strictly segregated. We do have automated tests that test functionality across domains, but as it turns out, these tests also test some other functionality at the same time that fool the dead-letter-destination-validation into thinking it is the same messaging domain.
In any case, I've have created a fix for this, and I'm testing it right now.
I'll send you an updated RAR by email in case you don't want to wait until the updated bits are available for download. What you also could do, as a workaround, is doing the same trick that fooled the automated test: you can specify the redelivery handling in the MDB code, e.g.
public void onMessage(Message message) {
message.setStringProperty("JMS_Sun_JMSJCA_RedeliveryHandling", "2:1000; 3:move(queue:*psdmqqueue*)");
// do stuff
HTH, Frank Kieviet

How to create the deployment descriptor with the sun application server

I have packaged my .war and ejb-jar files. I go to autodeploy and it says i need a deployment descriptor?

this is actually an example .ear file that i am trying to run. When i create the client with the deploytool that comes with suns application server i get
C:\appclient>appclient -client swe645-appClient.jar
Caught an unexpected exception!
javax.naming.NameNotFoundException: EditEmpBean not found
        at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.
java:185)
        at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.ja
va:157)
        at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialCont
extProviderImpl.java:101)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(Reflecti
veTie.java:123)
        at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
tchToServant(CorbaServerRequestDispatcherImpl.java:648)
        at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
tch(CorbaServerRequestDispatcherImpl.java:192)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
Request(CorbaMessageMediatorImpl.java:1709)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
(CorbaMessageMediatorImpl.java:1569)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(C
orbaMessageMediatorImpl.java:951)
        at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.call
back(RequestMessage_1_2.java:181)
        at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
(CorbaMessageMediatorImpl.java:721)
        at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatc
h(SocketOrChannelConnectionImpl.java:473)
        at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(
SocketOrChannelConnectionImpl.java:1262)
        at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.
run(ThreadPoolImpl.java:409)

Problem with starting Sun ONE Server after changing Java version

Hi
I installed Sun ONE Java Server 6.1 SP6 on Redhat Enterprise 4.0 64bit. This version uses java version "1.4.2_04" which is intalled in /opt/SUNWwbsvr/bin/https/jdk. With this configuration everything works ok. When I changed Java (/usr/java/jdk1.5.0_09) on version "1.5.0_09 (in server.xml) Sun One doesn't start. I have such error:
CORE3170: Configuration initialization failed: Error running init function load-modules: dlopen of /opt/SUNWwbsvr/bin/https/lib/libj2eeplugin.so failed (libjvm.so: cannot open shared object file: No such file or directory)
I checked file libjvm.so and it is in locations: /opt/SUNWwbsvr/bin/https/lib/ and /usr/java/jdk1.5.0_09/jre/lib/amd64/server.
Does anybody know what is wrong ???
Thanks for help

Hi Ges7
You were right. I installed Java 1.5_10 and 1.6 32 bit version and SUN ONE works but i have some errors
[https-fast1]: Sun ONE Web Server 6.1SP6 B05/07/2006 14:57
[https-fast1]: warning: CORE3283: stderr: Java HotSpot(TM) Server VM warning: Can't detect initial thread stack location - find_vma failed
[https-fast1]: info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.6.0] from [Sun Microsystems Inc.]
[https-fast1]: info: WEB0100: Loading web module in virtual server [https-fast1] at [XagentBr]
[https-fast1]: info: WEB0100: Loading web module in virtual server [https-fast1] at [search]
[https-fast1]: info: WEB2798: [XagentBr] ServletContext.log(): AuthAgent v1.55 starting ...
[https-fast1]: info: WEB2798: [XagentBr] ServletContext.log(): Filter configuration file was not found
[https-fast1]: failure: WebModule[XagentBr]: WEB2680: Exception starting filter Authorization Agent Filter
[https-fast1]: javax.servlet.ServletException: Filter configuration file was not found
[https-fast1]: at com.pl.comprze.authagent.AuthAgentFilter.init(AuthAgentFilter.java:262)
[https-fast1]: at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
[https-fast1]: at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:322)
[https-fast1]: at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:120)
[https-fast1]: at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3321)
[https-fast1]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3797)
[https-fast1]: at com.iplanet.ias.web.WebModule.start(WebModule.java:257)
[https-fast1]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-fast1]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-fast1]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-fast1]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-fast1]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-fast1]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-fast1]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-fast1]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-fast1]:
[https-fast1]: failure: WebModule[XagentBr]: WEB2705: Context startup failed due to previous errors
[https-fast1]: info: HTTP3072: [LS ls1] http://fast1:8088 ready to accept requests
[https-fast1]: startup: server started successfully
Success!
The server https-fast1 has started up.
Do You know what it can be ???

JMS Connection Factory jms/QueueConnectionFactory could not be found

Hi,
Previously, i tried to extend weblogic domain "oim_domain" that only configured for OIM, and integrate the OIM with OAM 11g.
The integration was failed, because all users cannot login to OAM login page (using Active Directory authentication), so i rolled back all configuration by copying MW_HOME i've backed-up before extend the weblogic domain.
When i start the OIM after rolled back, i've found an error message as follow :
<May 16, 2013 11:38:15 AM WIT> <Error> <oracle.iam.platform.async> <IAM-0050009> <Async Service initialization failed because JMS Connection Factory jms/Queu
eConnectionFactory could not be found. Please check that a JMS Connection Factory with JNDI Name jms/QueueConnectionFactory is present in the Application Ser
ver.>
<May 16, 2013 11:38:15 AM WIT> <Error> <oracle.iam.platform.async> <IAM-0050010> <Error Trace Follows
javax.naming.NamingException: String index out of range: -1
at weblogic.jndi.Environment.getContext(Environment.java:308)
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)
and this error message :
<May 16, 2013 11:38:15 AM WIT> <Warning> <oracle.iam.platform.utils> <IAM-0070016> <An error occurred while initializing service : oracle.iam.platform.async.
AsyncService>
<May 16, 2013 11:38:15 AM WIT> <Warning> <oracle.iam.platform.utils> <IAM-0070016> <An error occurred while initializing service : {0}
javax.naming.NamingException: String index out of range: -1
at weblogic.jndi.Environment.getContext(Environment.java:308)
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)
Please help.
Best Regards,
Heri

I have the same error!!! Do you manage to solve it?

Using Sun Web Server 6.1 from the IDE

Using JSE 8 with Sun Web Server 6.1 set as the target container, I have a SUNWS61deployment.xml file created.
That didn't exist in JSE 7. Is it WS 6.1 SP4 or SP5 -related ?
I also have ws61-sun-web.xml with a simple <sun-web-app/> tag (empty deployment descriptor).
What should this file contain? Is it a replacement for sun-web.xml?
Do I still need sun-web.xml? Its DTD declaration sounds like Sun
App Server 7 (http://www.sun.com/software/sunone/appserver/dtds/sun-web-app_2_3-1.dtd)
So you have plans to make "Sun Resources" (pools, JNDI resources, ...) created in the IDE be registerable directly in the Web Server just like it's possible with the sun app server?
How safe is it to use JSE 8 with an older Web Server Service Pack (say 6.1SP1)?

SUNWS61deployment.xml is created bythe IDE to be used internally and not to be used by the developer. This file wouldn't be sent to webserver after deployment.
The ws61-sun-web.xml is sun-web.xml only and yes it is same as it is in Appserver7 as the webcontainer for both Webserver6.1 and Appserver7 are same. After deployment to webserver, ws61-sun-web.xml is renamed to Webserver as sun-web.xml by the IDE. When opened the developer can edit in the XML editor.
The reason for having it as ws61-sun-web.xml in IDE is to avoid the clash between sun-web.xml of Appserver8.1 which is J2EE1.4 based whereas Webserver6.1 Web container is J2EE1.3 based.
It should be okay to use any service pack of Webserver6.1 with JSE8
Hope this helps

Running Sun App Server 7 and 8 on the same box

Hello,
Are there any known issues with running Sun App Server 7 and 8 in the same host box ? Currently I am encountering some class not found exceptions with Sun App Server 8 . Sun App Server 7 runs just fine.
Thanks,
Aswin.

It's not advisable to run separate installations of
ColdFusion 7 and ColdFusion 8 single server on the same machine the
re are several services that will try to use the same ports.
However, you can install ColdFusion Enterprise using the
multi-server configuration and then deploy the J2EE versions of
ColdFusion to JRun. You can change the JVM that each instance uses
(we recommend the latest 1.4 for CF7 and the latest 1.6 for CF8),
and everything should run fine.
ColdFusion itself is essentially just a J2EE application, the
J2EE server itself is JRun 4. So the specific answer to your
question is "don't install 2 copies of JRun 4 to the same machine".
But yes, it's 100% possible, I'm running this configuration in my
own development environment.

Sun Calendar Server as a master calendar

Greetings!
We currently use the Sun Java System Calendar Server for student, faculty & staff personal calendars (via the web client) and use a separate in-house system for our web-based master events calendar. The latter is starting to show its age, so we are looking at ways of either updating it to make it more flexibile or to move to a different solution.
As we already own the Sun Calendar Server, we were wondering what the feasibility of using it as a master calendar would be. Have any of you used it this way, and if so, would you mind sharing your experiences with me?
Also, are there any tools already developed to do so? I have done some experimentation with the APIs and the XML generated from the calendar with some success, but would rather not reinvent the proverbial wheel.
Thanks,
Eric

The university I work at is also looking into this as well. We are seeking to have a public calendar that different people/accounts can post public events and meetings.
I am currently investigating if this can be done with the Sun Calendar Server. The notion of a 'layered' calendar comes to mind, but am not sure if this is possible with the Sun Calendar.
I'll share what I find If I have the chance.
thanks..

SUN 280R Server

Hi Guys,
I know that thius is not the forum for Sun but I've got a problem with the sun 280R Server that has our Oracle 10g database. When I switch the server on, It does switch on because there's a green light but there's also an orange light with a spanner. What can I do? Please assist this is the production server and no one can assist.
Thanx.

NPD wrote:
so there's no troubleshooting I can try maybe because we've go no maintanance agreements
Thanx.I do not have one of these servers, but by performing a couple of Google searches I was eventually able to find the owner's guide for the server and the service manual. The documentation states that the light color is amber, rather than orange - so that might explain part of the problem in searching for an answer.
The owner's guide:
http://dlc.sun.com/pdf/806-4806-10/806-4806-10.pdf
PDF page 38 (page 10 in the page footer) states that a fan failure could cause the amber light to turn on, a power supply has failed, or another problem has happened (RAM or CPU failure?).
PDF page 223 (page 195 in the page footer) states how to quickly see if the amber light means a power supply failure. There are apparently amber lights on the back of the server next to each of the power supplies - if one of those amber lights is lit, the hot swap power supply needs to be replaced.
The service manual:
http://dlc.sun.com/pdf/806-4807-10/806-4807-10.pdf
PDF page 189 (page 163 in the page footer) indicates how to isolate the failed component.
You might try unplugging the server from the electric power for 1 minute, then plugging it back in, to test if it was just a temporary "power good" problem report from the power supplies. If that does not fix the problem, see if one of the power supplies is showing an amber light. If not, verify that the three internal fans are functioning.
Good luck.
Charles Hooper
Co-author of "Expert Oracle Practices: Oracle Database Administration from the Oak Table"
http://hoopercharles.wordpress.com/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

JMS problem with Sun Application Server 8.2

Hi!
I've just started trying JMS and found a problem.
I set a connection factory called "QueueConnectionFactory" in the Sun Application Server Admin Consol.
After this I test this code:
import javax.jms.*;
import javax.naming.*;
public class Sun_JNDI
public static void main(String args[]) throws Exception
Context jndiContext = null;
System.setProperty("java.naming.factory.initial","com.sun.enterprise.naming.SerialInitContextFactory" );
System.setProperty("java.naming.factory.url.pkgs","=com.sun.enterprise.naming");
System.setProperty("java.naming.provider.url","localhost:1024");
jndiContext = new InitialContext();
Object O = jndiContext.lookup("QueueConnectionFactory");
System.out.println(jndiContext);
in result I got this long Exception message:
2006.02.12. 10:52:59 com.sun.corba.ee.spi.logging.LogWrapperBase doLog
INFO: "IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/1356"
2006.02.12. 10:53:00 com.sun.enterprise.connectors.ActiveRAFactory createActiveResourceAdapter
SEVERE: RAR6001 : Class Not found : com.sun.messaging.jms.ra.ResourceAdapter
2006.02.12. 10:53:00 com.sun.enterprise.connectors.ActiveRAFactory createActiveResourceAdapter
SEVERE:
com.sun.enterprise.connectors.ConnectorRuntimeException: Error in creating active RAR
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:76)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:267)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:189)
at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:71)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:293)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at Sun_JNDI.main(Sun_JNDI.java:40)
Caused by: java.lang.ClassNotFoundException: com.sun.messaging.jms.ra.ResourceAdapter
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:50)
... 7 more
2006.02.12. 10:53:00 com.sun.enterprise.naming.SerialContext lookup
SEVERE: NAM0004: Exception during name lookup : {0}
com.sun.enterprise.connectors.ConnectorRuntimeException: Error in creating active RAR
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:76)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:267)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:189)
at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:71)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:293)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at Sun_JNDI.main(Sun_JNDI.java:40)
Caused by: java.lang.ClassNotFoundException: com.sun.messaging.jms.ra.ResourceAdapter
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:50)
... 7 more
Exception in thread "main" javax.naming.CommunicationException: serial context communication ex [Root exception is com.sun.enterprise.connectors.ConnectorRuntimeException: Error in creating active RAR]
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:317)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at Sun_JNDI.main(Sun_JNDI.java:40)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Error in creating active RAR
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:76)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:267)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:189)
at com.sun.enterprise.naming.factory.ConnectorObjectFactory.getObjectInstance(ConnectorObjectFactory.java:71)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:293)
... 2 more
Caused by: java.lang.ClassNotFoundException: com.sun.messaging.jms.ra.ResourceAdapter
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:50)
... 7 more
So I tested this code under Netbeans5 and I don't where to find jar file contains the class: com.sun.messaging.jms.ra.ResourceAdapter
Other time I tryied to lookup this URL: "java:comp/env/jms/QueueConnectionFactory"
The result was: javax.naming.NameNotFoundException
I know it is a small code example but if I'm not able to solve this problem I can't go on with JMS.
I would be glad by any help.
Regards:
Sandor

Hello
In my code it looks like that:
1: System.setProperty("com.sun.jndi.ldap.LdapCtxFactory", "iiop://localhost:3700");
2: Context ctx = new InitialContext();
3: TopicConnectionFactory factory = (TopicConnectionFactory)ctx.lookup("jms/DailyDestinationFactory");
4: TopicConnection connection = factory.createTopicConnection();
5: TopicSession session = connection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
6: Topic topic = (Topic)ctx.lookup("jms/DailyBean");
7: TopicPublisher pub = session.createPublisher(topic);
8: TextMessage msg = session.createTextMessage();
9: msg.setText("NewMessage");
10: pub.send(msg);
and it work with Sun App Server 8.2.

Failure to Start JMS Service in Sun Java Server

Hi,
I'm using Sun Java Server on Unix platform with Java 5.
When I start the Sun server I find the JMS service in in unable to start.
Please find below the Error Log Trace I observe:
[#|2005-11-18T04:19:13.320-0600|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms
|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory
/home/jai/cts141/SUNWappserver/imq/var/instances|#]
[#|2005-11-18T04:19:13.321-0600|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms
|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service
broker instance imqbroker. Please refer to the JMS provider documentation for the exact
location of this log file.|#]
[#|2005-11-18T04:19:13.322-0600|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.cor
e|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection
creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused
(errno:4127)
        at
com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:
415)
        at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
        at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection
creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused
(errno:4127)
        at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.ja
va:233)    at
com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.ja
va:180)
        at
com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
        at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandl
er.java:53)
        at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
        at
com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
        at
com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
        at
com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
        at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
        at
com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
        at
com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
        at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
        at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
        at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
        at om.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
        at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
        at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:32
      at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
        ... 7 more
Caused by: java.net.ConnectException: Connection refused (errno:4127)
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
        at java.net.Socket.connect(Socket.java:507)
        at java.net.Socket.connect(Socket.java:457)
        at java.net.Socket.<init>(Socket.java:365)
        at java.net.Socket.<init>(Socket.java:178)
        at
com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
        ... 25 more
|#]
[#|2005-11-18T04:19:13.327-0600|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.cor
e|_ThreadID=10;|Server Startup failed. Exiting...|#][
* The JMS service is unable to start on the port 7676 which I find free .
* The directory /home/jai/cts141/SUNWappserver/imq/var/instances also holds all permissions to all users
* The log for MQ startup gets created if I explicitly run the script imqbrokerd located at /home/jai/cts141/SUNWappserver/imq/bin.
But this script does not get executede when the server is started .
But all these JMS startup happens fine when I start the sever setup with
previous version of Java (Java 1.4.2).
Please clarify the same.
Thanks in Advance,
Jay

I guess if you don't start the managed servers with NodeManager they do come up?
Not sure if this is related, but did you take a look at MOS note 1336100.1? It basically says there was a failure during configuration of NodeManager; it is not entirely related to forms but to FMW 11.1.1.5 which is somehow the version number of forms 11.1.2. A cause of it is that NodeManager isn't using the correct script when starting a managed server; this also sounds a little bit like your problem...
Regarding the OutOfMemory exception you might look at note 1312573.1; it is related to running WLS as windows services (without NodeManager); but it might as well apply to running the Servers with NodeManager.
It might be a shot in the dark, but it might be worth a try.
In any case when running into (forms related) troubles with weblogic I found very little specific forms related informations on weblogic; this is probably due to the fact that forms doesn't make much use of weblogic at all (all in all most of the work is done by the good old fashioned C- forms runitmes); but the generic notes on weblogic often did the trick.
cheers

Integrating Sun App Server with WebSphere MQ

Hi,
I am using Sun App server V8.1 . I also have a websphere MQ v5.3 installed in my system. I want to integrate this MQ with the App server.
I created a queueManager and a Queue in MQ and using the JMSAdmin console of the Mq, i created jndi lookup resources using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
In the application server side, i created a Resource adapter using the command:
create-resource-adapter-config --property SupportsXA=true:ProviderIntegrationMode=jndi:RMPolicy=OnePerPhysicalConnection:JndiProperties=java.naming.factory.url.pkgs\\=com.ibm.mq.jms.naming,java.naming.factory.initial\\=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\=file\\:D\\:\\MQ:LogLevel=finest mqra
Then i deployed this resource adaptor using the command :
deploy name mqra target server "D:\Sun\AppServer\lib\addons\resourceadapters\genericjmsra\genericra.rar"
Using this resource adapter i created a connection pool, connector resource and an admin object using the commands
create-connector-connection-pool raname mqra connectiondefinition javax.jms.QueueConnectionFactory transactionsupport XATransaction property ConnectionFactoryJndiName=MQQCF mymqpool
create-connector-resource --poolname mymqpool jms/MyMqQCF
create-admin-object raname mqra restype javax.jms.Queue --property DestinationJndiName=RTQueue jms/MyMqQueue
After that, i wrote a java code to lookup these resources and put a message into the queue.
This is the snippet of my java code
InitialContext ic = new InitialContext();
QueueConnectionFactory cnxFact = (QueueConnectionFactory)ic.lookup("jms/MyMqQCF");
Queue qu = (Queue)ic.lookup("jms/MyMqQueue");
try {
QueueConnection qConn = cnxFact.createQueueConnection();
QueueSession qSess = qConn.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
QueueSender qSend = qSess.createSender(qu);
TextMessage msg = qSess.createTextMessage();
msg.setText("1");
qSend.send(msg);
qConn.close();
I am getting an exception in the line, QueueConnection qConn = cnxFact.createQueueConnection();
here is the stack trace
java.lang.ClassCastException: com.ibm.mq.jms.MQQueueConnectionFactory
at com.sun.genericra.outbound.ManagedQueueConnectionFactory.createXAConnection(ManagedQueueConnectionFactory.java:45)
at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createPhysicalConnection(AbstractManagedConnectionFactory.java:127)
at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createManagedConnection(AbstractManagedConnectionFactory.java:111)
at com.sun.enterprise.resource.ConnectorAllocator.createResource(ConnectorAllocator.java:90)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getUnenlistedResource(IASNonSharedResourcePool.java:437)
at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:355)
at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:250)
at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:213)
at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:174)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:286)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:145)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121)
at com.sun.genericra.outbound.ConnectionFactory.createConnection(ConnectionFactory.java:69)
at com.sun.genericra.outbound.ConnectionFactory.createQueueConnection(ConnectionFactory.java:101)
Can anybody help???

bump
update:
So to avoid this problem I added spring.jar to the server classpath. that got rid of this message but then it started complaining that its missing struts2 core jar..i added that in server classpath as well...I did same for 4 other files and in the end it said 'bean for xwork has already been initialized' (because all these jars are in the application as well).
So I am stuck. if I add all jars to server classpath..it says beans have already been initialized. If I take out the jars from server classpath then it says that stuff is missing (eg. contextLoader.properties missing - orig post)
again, all this goes away when I restart the server..so i am just trying to avoid having to restart server every code change.

Deprecation of javax.jms.QueueConnectionFactory

i found out in weblogic 6.1 docs that javax.jms.QueueConnectionFactory and javax.jms.TopicConnectionFactory is deprecated.
But i found no mention of this in the latest javadocs that i downloaded from java.sun.com.(jms 1.0.2 b)
clarifications in this regard is appreciated

Hi -
I'm the JMS Specifecation Lead. Let me reassure you: the javax.jms.QueueConnectionFactory and and javax.jmsTopicConnectionFactory interfaces have not been deprecated.
I spoke with a senior BEA techincal person for JMS, and he explained that this is a documentation issue. He's filed a request to have it fixed. Here's what he said.
" In WebLogic, there are default connection
factories. Those default factories have some well known names. The
original names chosen were "javax.jms.QueueConnectionFactory" and
"javax.jms.TopicConnectionFactory". WebLogic changed the JNDI name in 6.0
(multiple reasons mostly to do with customer backward compatibility).
As far as I know the specification makes no statements about how a product
is administered, that there would even be default connection factories, or
what their names might be if there were. The documentation is misleading
in that it doesn't mention that those are the *JNDI names* of the factories,
not the interfaces for the factories. I will file an appropriate bug
report against the documentation.
Feel free to post my comments in your forum, or send me to the URL where I
can officially respond. Thanks for bringing this up."
I want to thank BEA for a prompt response on this.
i found out in weblogic 6.1 docs that
javax.jms.QueueConnectionFactory and
javax.jms.TopicConnectionFactory is deprecated.
But i found no mention of this in the latest javadocs
that i downloaded from java.sun.com.(jms 1.0.2 b)
clarifications in this regard is appreciated

Help with creating AQ JMS

Hiello,
I'm trying to create JMS resource on WLS 10.3 to connect to AQ on a different server
Here is what I'm trying to do:
1. I have an Oracle application (OTM) that can en-queue payload in an AQ. I have configured the AQ on the OTM server
2. I want to read from the OTM AQ in my composite, so I'm trying to create the necessary JMS reources in WLS. Since AQ JMS uses a database connection for the stored JMS messages, I created a JDBC connection factory for the target OTM server.
3. I created a JMS queue as well
Now I'd like to know the remaining steps so that the JMS queue can be linked with the AQ. Any pointer will be appreciated
thanks

Assuming AQ is properly configured
- Set up a datasource to connect to your database, use Oracle Thin XA driver or Oracle Thin driver. If you choose Oracle Thin driver accept the defaults of Supports Global Transactions and One-Phase Commit on the Transaction Options screen.
- Create a JMS module and target that module to your server or cluster.
- In the module, create a Foreign Server resource and accept the default targeting it inherits from the module (that is, do not use the Advanced Targeting
button).
- Using the foreign server’s General Configuration tab, set the JNDI Initial Context Factory to oracle.jms.AQjmsInitialContextFactory and add the datasource property to the JNDI Properties field and set its value to the JNDI name of the data source you created for accessing AQ.
- Set up the foreign server’s connection factories using its Connection Factories Configuration tab. Note that AQ JMS does not require predefining the connection factories in the database. Map each AQ JMS connection factory your application requires to an appropriate Local JNDI Name using the Remote JNDI Name
Remote JNDI Name JMS Object Type
QueueConnectionFactory javax.jms.QueueConnectionFactory
TopicConnectionFactory javax.jms.TopicConnectionFactory
ConnectionFactory javax.jms.ConnectionFactory
XAQueueConnectionFactory javax.jms.XAQueueConnectionFactory
XATopicConnectionFactory javax.jms.XATopicConnectionFactory
XAConnectionFactory javax.jms.XAConnectionFactory
- Set up the foreign server’s destinations using its Destinations Configuration tab. For queues, the Remote JNDI Name will be of the form Queues/<AQ queue name>, where the AQ queue name is the one specified in the database. For topics, it will be of the form Topics/<AQ queue name>.

Problem with Java System Application Server *(Sun one 8 or J2EE 1.4 app server)

Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.Veerendra

M.S. Veerendra-
This is a known incompatibility, described at:
http://support.solarmetric.com/Ticket/Display.html?id=14082
Can you try the workarounds listed at:
http://forum.java.sun.com/thread.jsp?forum=136&thread=499803&tstart=0&trange=15
and let us know if it works?
In article <[email protected]>, veerendra wrote:
Hi,
Iam able to deploy KODO JDO through JCA in Sun One App server 7,
But iam unable to deploy in J2EE1.4 app server. I followed the J2EE1.4
guide developer guide it is compitable with JCA1.5 and also given backward
compatibility for JCA1.0
I had removed the sun-ra.xml from kodo.rar which is not needed in
J2EE1.4 and deployed but iam un able to get the
PersistanceManagerConnectionFactory.
Can any one heip in sloving this issues the exceptions Iam getting
Starting J2EE(TM) Application Server 1.4 Developer Release (build b44-dr)
[#|2004-03-06T18:07:16.801+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076:
Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun
Microsystems Inc.]|#]
[#|2004-03-06T18:07:20.356+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following
is the information about the JMX MBeanServer used:|#]
[#|2004-03-06T18:07:20.757+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer
initialized successfully|#]
[#|2004-03-06T18:07:23.761+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
Engine server|#]
[#|2004-03-06T18:07:25.223+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating
virtual server server|#]
[#|2004-03-06T18:07:25.283+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS
AVK Instrumentation disabled|#]
[#|2004-03-06T18:07:25.353+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143:
Loading policy provider
com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-03-06T18:07:32.904+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014:
Recoverable JTS instance, serverId = [100]|#]
[#|2004-03-06T18:07:37.701+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying
Optional Packages dependencies...|#]
[#|2004-03-06T18:07:38.392+0530|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008
: Initialized monitoring registry and listeners|#]
[#|2004-03-06T18:07:41.016+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading
system apps|#]
[#|2004-03-06T18:07:43.239+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB
Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-03-06T18:07:45.122+0530|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010:
All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6005
: Could not create mcf : kodo.jdbc.ee.JDBCManagedConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR6021
:Failed to create MCF : JDOKODO#javax.resource.cci.ConnectionFactory|#]
[#|2004-03-06T18:07:47.275+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5059:
Error in loading resource|#]
[#|2004-03-06T18:07:47.285+0530|SEVERE|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to create
MCF
     at
com.sun.enterprise.connectors.ConnectorConnectionPoolAdminServiceImpl.createConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:202)
     at
com.sun.enterprise.connectors.ConnectorRuntime.createConnectorConnectionPool(ConnectorRuntime.java:282)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createDefaultConnectorConnectionPools(ActiveOutboundResourceAdapter.java:297)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.createAllConnectorResources(ActiveOutboundResourceAdapter.java:124)
     at
com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.setup(ActiveOutboundResourceAdapter.java:96)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:226)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:294)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.reCreateActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:318)
     at
com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.addResourceAdapterConfig(ResourceAdapterAdminServiceImpl.java:349)
     at
com.sun.enterprise.connectors.ConnectorRuntime.addResourceAdapterConfig(ConnectorRuntime.java:598)
     at
com.sun.enterprise.resource.ResourceAdapterConfigDeployer.deployResource(ResourceAdapterConfigDeployer.java:36)
     at com.sun.enterprise.server.ResourcesLoader.load(ResourcesLoader.java:70)
     at
com.sun.enterprise.server.ConnectorResourcesLoader.loadRAConfigs(ConnectorResourcesLoader.java:74)
     at
com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:172)
     at
com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:282)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:217)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:171)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
With Regards,
M.S.Veerendra--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

PasswordSync with a Sun JMS Server: javax.jms.QueueConnectionFactory

Similar Messages

Maybe you are looking for