Javax.resource.ResourceException

Hi,
I'm trying to import the class javax.resource.ResourceException in my program but when I compile the code I get the error "class javax.resource.ResourceException not found in import". What is the name of the jar file that contains this class and where can I download it from ?
Many thanks
Angela

Oh that one!
Thats from royalblue. You have missed one of the .jar files supplied with the API.
Cheers

Similar Messages

Error in resource adapter cleanup.. javax.resource.ResourceException: java.

Hi,
I am getting the following error in my Oracle AS 10g R3 on Solaris .
Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
(Click on the log file link to download the log or view it as plain text)
Can any one explain why this error comes.
Regards,
Kumar

Hi,
I am getting the following error in my Oracle AS 10g R3 on Solaris .
Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
(Click on the log file link to download the log or view it as plain text)
Can any one explain why this error comes.
Regards,
Kumar

Java.lang.NoClassDefFoundError: javax/resource/ResourceException

Hi everybody,receive my sincere greeting,i have a slight problem right here.I am trying to test the Server API for Mobile Services i dowloaded from nokia forum.I have a J2SE program that sends an SMS to a mobile device.When i try to run the simple program in JBuilder 2005 Enterprise i encounter the error below.Please help me i am not sure if i should include the j2ee.jar for my project to detect the resource package in javax or not.Anyone related with this problem plz help me.
Nov 3, 2006 1:46:38 PM com.nokia.sams.util.sms.config.ServiceApiConfiguration init
INFO: Loading Service API configuration.
Nov 3, 2006 1:46:38 PM com.nokia.sams.util.sms.config.ServiceApiConfiguration init
INFO: Service API config file is: C:\Borland\JBuilder2005\jdk1.4\jre\lib\nokia_sams_service.properties
Nov 3, 2006 1:46:38 PM com.nokia.sams.util.sms.config.ServiceApiConfiguration init
INFO: Service API configuration loaded.
java.lang.NoClassDefFoundError: javax/resource/ResourceException
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:141)
     at com.nokia.sams.SmsMessageListenerHandler.<init>(SmsMessageListenerHandler.java:58)
     at com.nokia.sams.SmsSession.<init>(SmsSession.java:37)
     at com.nokia.sams.messaging.SmsMessagingSession.<init>(SmsMessagingSession.java:71)
     at com.nokia.sams.SmsService.openSession(SmsService.java:74)
     at com.klaas.sams.SMSServer.sendMessage(SMSServer.java:21)
     at com.klaas.sams.SMSServer.main(SMSServer.java:50)
Exception in thread "main"

Hi,
Just try to find connector.jar and put it into your lib location.
Regards,
Deddy

Javax.resource.ResourceException: Failed to start the connection

I have created the JMS bridge in Weblogic10.0 to connect with MQ server, I am getting error when startingup the weblogic server. Below the error
####<28-Mar-2009 10:56:25 o'clock GMT> <Info> <MessagingBridge> <clx25ao02> <aauat100-02> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1238237785804> <BEA-200042> <Bridge MQ_TO_JMS_1 failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (javax.resource.ResourceException: Failed to start the connection)>
I deployed the JMS adaptor also in weblogic10.0.
Could you please tell me the reason for the error?

A problem occurred with a Messaging Bridge between two JMS topics running in two Managed
Servers in the same domain, running on the same machine. As the Messaging Bridge was being
started during WebLogic Server startup, it threw the following warning message. Messages
could not be forwarded.
Analysis revealed that the bridge failed to create the message listener because it was
configured for durable topics and there was no JMS store available. The Bridge encountered an
internal error when trying to log the resource exception so the customer was not able to tell
why the bridge was failing.
The problem was resolved by a code change to allow the bridge to throw the correct resource
exception. Now, the correct exception is logged by the bridge.

Javax.resource.ResourceException: : Error in parsing XML

Hi
Iam developing a connector application.
Iam using OC4J 9.0.4 version(standalone) for deployment of RAR file. We are parsing the below xml in our application using SAX parser.
<?xml version="1.0" encoding="utf-8"?>
<DocAnnoList xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" LibName="IMGSERV" DocID="1698353" SystemType="1">
<AnnoDefPermission>
<security>
<securityobject libraryid="IMGSERV" systemtype="idmis" objectid="" objecttype="annotation" clientpermission="change">
<permission id="1" name="Test1G" type="group" level="read" />
<permission id="2" name="Test1G" type="group" level="write" />
<permission id="3" name="Test1G" type="group" level="append" />
</securityobject>
</security>
</AnnoDefPermission>
</DocAnnoList>
But iam getting the below error while parsing this xml with OC4J running on Win2k/HPUX/Solaris.
Error in parsing XML Stream. The element "DocAnnoList" is not as per the XSD.
04/03/26 14:11:06 org.xml.sax.SAXException: : Error in parsing XML Stream. The element "DocAnnoList" is not as per the
XSD.
04/03/26 14:11:06 at com.abc.is.ra.util.AB_IS_XMLObjectHandler.startElement(Unknown Source)
04/03/26 14:11:06 at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1181)
04/03/26 14:11:06 at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:300)
04/03/26 14:11:06 at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:267)
04/03/26 14:11:06 at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
04/03/26 14:11:06 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:286)
04/03/26 14:11:06 at oracle.xml.jaxp.JXSAXParser.parse(JXSAXParser.java:224)
I put the xSchema.jar,xml.jar & xmlparserv2.jar in java CLASSPATH as described at below URL.
http://otn.oracle.com/pub/articles/vohra_xmlschema.html
But problem is still there.
Can anyone tell me what is the problem. Iam sure, there is nothing wrong with our code as it is running well on Websphere 5, Weblogic 8.1, JBoss 3.2.3, SUN ONE 7.

will come if there are any tab spaces in the file..
delete the tab spaces from the file..

Error in javax.resource.cci.Connection during Compilation

Hi,
I am using NW 04 to write a par for my EP.
But I encountered the following error at the line
package com.sap.nwrig.demo;
The error is as shown :
This compilation unit indirectly references the missing type javax.resource.cci.connection (typically some required class file is referencing a type outside the classpath)
Do hope anyone could help.
Thanks.
Regards,
Mike Lee

Hi Mike,
I guess you need to add the JCA library that contains the javax.resource.cci.Connection class to the classpath of your project. Here's how to do it (assuming you're using the NetWeaver Developer Studio):
1. Right click on your project and choose Properties.
2. Choose Java Build Path from the lefthand side tree, and then choose the Libraries tab on the right.
3. Click on the Add External JARs button and browse to the following directory: <NW_Dev_Studio_inst_dir>\eclipse\plugins\com.tssap.ext.libs.j2ee_1.3\lib
4. Select connector.jar and choose Open.
This adds the library and now the referenced type should be resolved.
Regards,
Ivo

Eclipse Error : javax.resource.cci.connection not found

Hi,
I am new to Eclipse development. I downloaded a Sap connector PAR project from sdn and imported it in Eclipse then i showed lots of error with portal.HTMLB, portal.connector and javax.resource.cci.connection.
I want to know where can i find the JAR file for this import? or how to resolve this problem?
Thank you
arun

Thanks Carlton and Jain,
I searched for the JAR files in the EP60 Installation directory usr\EP60,
.../additional-lib/connector.jar
.../additional-lib/com/sapportals/connectorframework/framework/GenericConnector.jar
.../additional-lib/com/sapportals/connectorframework/framework/ConnectorHelper.jar
.../additional-lib/jta.jar
.../portalapps/com.sap.portal.ivs.connectorservice/lib/com.sap.portal.ivs.connectorserviceapi.jar
I could find the names in the path specified by you but they are all ZIP files. When i Unzip them i could only find .class files inside them not the JAR files.
I resolved all the problems except Javax.cci import error.
If you have any idea where to find them it would help me a lot?
Thank you
arun

Need java file: javax.resource.cci.ConnectionSpec

Hi,
My application is showing classpath error:
The project was not built since its classpath is incomplete. Cannot find the class file for javax.resource.cci.ConnectionSpec. Fix the classpath then try rebuilding this project.
This compilation unit indirectly references the missing type javax.resource.cci.ConnectionSpec (typically some required class file is referencing a type outside the classpath) MDMFetcherView.java MDMFetcher/gen_wdp/packages/com/burberry/appl/mdmfetcher line 0
Could you please let me know what is the problem here?

Devashish,
<i>I have added all the required references</i>
Exactly what references did you add?
By references I mean either of the following:
1. Class-path reference (Required Library) if you are using non-DC project
2. Public part reference (Used Public Part) if you are in DC project.
Also it might be required to add run-time references to interface / library (see properties of WD project).
VS

Javax.resource.cci interface

          Hi.
          I´m getting a bit frustrated by now. My contact at BEA wont answer my questiona...
          I am (still) trying to get my adapter to work on WL 6.1 SP1-2.
          The adapter I´m using (trying anyway) implements the javax.resource.cci interface.
          BUT, when I´m trying to reference it (the adapter) from an EJB in the ejb-jar.xml
          descriptor, I get an error message from ejbc.
          When I try to edit the descriptor from within the Admin Console, the interface
          is not available in the dropdown menu.
          So, the question I have to ask: Does WL 6.1 support the cci-interface?
          This is it, if I can´t work it out by Friday I will have to tell our customer
          that WebLogic is not the way to go. I´d hate to do that...
          regards,
          Oskar


          Hi Timothy.
          Thanks for answering.
          When referencing an adapter from an EJB, you are supposed to make that reference
          in ejb-jar.xml (attached). But the resource type <res-type> that is supposed to
          be used is javax.resource.cci.ConnectionFactory.
          However if you try to set that resource type in the Admin Console, that option
          is not available. It is not present in the drop-down box.
          The same thing goes for ejbc. When I try to compile with ejbc I get the following
          error:
          ejbc:
          [java] ERROR: Error processing 'ejb-jar.xml': .ejb-jar.enterprise-beans.session.resource-ref.res-type.
          must be one of the values: javax.sql.DataSource,javax.jms.QueueConnectionFactory,javax.jms.TopicConnectionFactory,java.net.URL,javax.mail.Session
          [java] ERROR: ejbc found errors
          Which seems like the same thing.
          I would much appreciate any help, my time is running out.
          Thanks
          Oskar
          "Timothy Potter" <[email protected]> wrote:
          >Dear Oskar,
          >
          >I'm sorry to hear that you are not getting the support you need. An
          >application server doesn't actually care about your client interface,
          >so yes
          >WebLogic does support CCI so to speak. The application server only cares
          >about your adapter's SPI. What is the specific error message from ejbc?
          >Also, can you attach your ejb-jar.xml file so that I can see what interface
          >you are referencing?
          >
          >Best regards,
          >
          >Timothy Potter
          >Senior Software Engineer
          >eCommerce Server Division
          >BEA Systems, Inc.
          >

Missing type javax.resource.cci.connection

Hi,
I'm would like to use JCA framwork, but I guess I should have appropriate connection class.
the missing class type is javax.resource.cci.connection
Where can I find/download this class jar file?
Any help would be appriciated
Thanks
Ami

The error I get that prevent me from compiling the projects is:
This compilation unit indirectly references the missing type javax.resource.cci.Connection (typically some required class file is referencing a type outside the classpath)
any idea of what should I do?
Thanks
Ami

Javax.resource.spi.ResourceAdapterInternalException: max connections reache

Hello,
I am writing an application to read messages from queues.
Everything seems to be working fine, but after a number of un-deployments and deployments I start getting the following exception and have no choice but to restart the application server.
Any hint on what the root cause might be?
Exception stack trace:
2008-02-15 14:47:19,095 WARN [org.jboss.system.ServiceController:424] Problem starting service jboss.j2ee:ear=Application-1.0.ear,jar=Application-1.0.jar,name=MDB,service=EJB3
org.jboss.deployment.DeploymentException: Endpoint activation failed ra=jboss.jca:service=RARDeployment,name='wmq.jmsra.rar' activationSpec=javax.jms.Queue:wsmq/Q@@localhost; - nested throwable: (javax.resource.spi.ResourceAdapterInternalException: max connections reached)
     at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
     at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.activate(JBossMessageEndpointFactory.java:310)
     at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:194)
     at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:190)
     at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:156)
     at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
     at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:103)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
     at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:417)
     at org.jboss.system.ServiceController.start(ServiceController.java:435)
     at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy361.start(Unknown Source)
     at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:120)
     at org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:301)
     at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:362)
     at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
     at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
     at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
     at $Proxy0.start(Unknown Source)
     at org.jboss.system.ServiceController.start(ServiceController.java:417)
     at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy34.start(Unknown Source)
     at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512)
     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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
     at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
     at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
     at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87)
     at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
     at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy35.start(Unknown Source)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
     at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
     at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
     at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
     at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
     at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
     at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
     at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
     at $Proxy10.deploy(Unknown Source)
     at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
     at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
     at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: javax.resource.spi.ResourceAdapterInternalException: max connections reached
     at com.ibm.mq.connector.ResourceAdapterConnectionPool.allocateConnection(ResourceAdapterConnectionPool.java:231)
     at com.ibm.mq.connector.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:333)
     at org.jboss.resource.deployment.RARDeployment.endpointActivation(RARDeployment.java:271)
     at org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:226)
     at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
     at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
     at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
     at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
     at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.activate(JBossMessageEndpointFactory.java:305)
     ... 101 more
ObjectName: jboss.j2ee:ear=Application-1.0.ear,jar=Application-1.0.jar,name=MDB,service=EJB3
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Endpoint activation failed ra=jboss.jca:service=RARDeployment,name='wmq.jmsra.rar' activationSpec=javax.jms.Queue:wsmq/Q@@localhost; - nested throwable: (javax.resource.spi.ResourceAdapterInternalException: max connections reached)My current configuration is:
- JBoss 4.2.2-GA (linux)
- WS MQ 6.0.2.2 (linux)
I have configured JBoss the following way:
- added wmq.jmsra.rar to the $JBOSS_SERVER/deploy directory
- added com.ibm.mqetclient.jar to the $JBOSS_SERVER/lib directory
- created $JBOSS_SERVER/deploy/wmq.jmsra-ds.xml as follows
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>

<mbean code="org.jboss.resource.deployment.AdminObject" name="jca.wmq:name=wsmqQ">
    <attribute name="JNDIName">wsmq/Q</attribute>
    <depends optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'</depends>
    <attribute name="Type">javax.jms.Queue</attribute>
    <attribute name="Properties">
      baseQueueManagerName=QM1
      baseQueueName=Q
    </attribute>
</mbean>

<tx-connection-factory>
    <jndi-name>MQCF</jndi-name>
    <xa-transaction />
    <rar-name>wmq.jmsra.rar</rar-name>
   <connection-definition>javax.jms.ConnectionFactory</connection-definition>
    <config-property name="channel" type="java.lang.String">SYSTEM.DEF.SVRCONN</config-property>
    <config-property name="hostName" type="java.lang.String">127.0.0.1</config-property>
    <config-property name="port" type="java.lang.String">1414</config-property>
    <config-property name="queueManager" type="java.lang.String">QM1</config-property>
    <config-property name="transportType" type="java.lang.String">CLIENT</config-property>
</tx-connection-factory>My java MDB (EJB3) is:
@MessageDriven(name = "MDB", activationConfig = {
        @ActivationConfigProperty(propertyName = "destination", propertyValue = "wsmq/Q"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
        @ActivationConfigProperty(propertyName = "transportType", propertyValue = "CLIENT"),
        @ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "true"),
        @ActivationConfigProperty(propertyName = "maxPoolDepth", propertyValue = "1") }, messageListenerInterface = MessageListener.class)
@ResourceAdapter("wmq.jmsra.rar")
public class MDB implements MessageListener {
    public void onMessage(Message message) {
        return;
}Thanks in advance for any information!
cheers!

hi
this is known to IBM as APAR IC54346 - fixed in pack 6.0.2.3

Javax.resource

I'm trying to compile a couple of classes that import this pakage and I'm not sure how to obtain it since it did not come with the standard JDK.
Can someone please guide me through the steps, so I can download this pkg.
Thanks,

Are you using J2EE 1.3? That's when the J2EE Connector Architecture was introduced (that is what you're asking about, right?). I looked in the j2ee.jar file for 1.3 and javax.resource is definitely there.

Javax.resource package

Hi!
I can't import javax.resource package. I have J2EE 1.4 SDK. Where can I download this package?
Jani

I think the install is ok.
j2ee.jar is in the C:\Sun\AppServer\lib directory. This directory is in the PATH environment variable.
U have this package???
Jani

EIS / javax.resource.cci.Interaction

I am trying to resolve a problem with a program written several years ago. I have narrow down the code below that is suppose to retrieve data from a database and store the values in the MappedRecord. The problem I am running into is that several of the fields are date fields and the values are being decremented by one day. This started happening several months ago. This program is running on WAS 6.1.0.25 using Java SDK 1.5 SR9 Cumulative Fix for WebSphere Application Server.
MappedRecord mrGetPropsInput = recordFactory.createMappedRecord("DocumentPropertiesRequest");
mrGetPropsInput.put("doc_id", new Long(strDocID));
mrGetPropsInput.put("is_lock_desired", new Boolean(true));
MappedRecord mrGetPropsResult = (MappedRecord)interaction.execute(iSpec, mrGetPropsInput);All help and suggestions would be greatly appreciated.

I am trying to resolve a problem with a program written several years ago. I have narrow down the code below that is suppose to retrieve data from a database and store the values in the MappedRecord. The problem I am running into is that several of the fields are date fields and the values are being decremented by one day. This started happening several months ago. This program is running on WAS 6.1.0.25 using Java SDK 1.5 SR9 Cumulative Fix for WebSphere Application Server.
MappedRecord mrGetPropsInput = recordFactory.createMappedRecord("DocumentPropertiesRequest");
mrGetPropsInput.put("doc_id", new Long(strDocID));
mrGetPropsInput.put("is_lock_desired", new Boolean(true));
MappedRecord mrGetPropsResult = (MappedRecord)interaction.execute(iSpec, mrGetPropsInput);All help and suggestions would be greatly appreciated.

Resource Allocation Issue in Weblogic messaging bridges

Hi,
We are using
Weblogic version à WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic Temporary Patch for CR250915 04/18/2006 22:21:33
Java JDK version à 1.4.2_11
Oracle version à 9.2.08
Solaris version à Solaris 5.8
The weblogic application is deployed on Unix Solaris.
We have configured 8 message bridges within weblogic between the 8 Topics in weblogic (source JMS destination) and 8 topics in the External EMS server (Target JMS destination) .
The properties set for the message bridges are
1] AsyncEnabled ="true"
2] DurabilityEnabled ="true"
3] QualityOfService="Exactly-once"TransactionTimeout="10"
4] TransactionTimeout="10"
The source and target JMS destinations are bridge using the resource adapter of jms-xa-adp (connector module)
The properties for the Source JMS Destination are
1] ConnectionFactory = weblogic.jms.client.JMSXAConnectionFactory
The properties for the Target JMS Destination are
1] InitialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
2] ConnectionFactory = XATopicConnectionFactory
The EMS client version library is EMS version client library à 4.2.0
The message Bridge Thread Pool Size is à 12
When the weblogic is started, all the bridges comes up properly and are forwarding message to the target, however after some time (1 to 2 days) we observe some that some of the bridges are going down and we get see following error in the weblogic logs
####<May 26, 2010 12:00:56 AM GMT> <Warning> <Connector> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
####<May 26, 2010 12:00:56 AM GMT> <Info> <MessagingBridge> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200042> <Bridge RefDataCompanyBridge failed to connect to the source destination and will try again in 60 seconds. (javax.resource.ResourceException: Failed to start the connection)>
Can you please help us resolve the above issue?
Thanks,
Mohanraj

There seems to be couple of known issues with WLS 8.1 and Tibco EMS.. Check with support whether your issue is related to any of the below:
Message bridge will stop responding and WLS has to be restarted to overcome this.
There is a known bug on WLS 8.1. Bug 8062571 is for the issue.
Should the connection be interrupted by a problem on the Tibco side, the messaging bridge never tries to reconnect. the problem can be that Tibco EMS is restarted for some reason or that the maximum number of messages that Tibco EMS can handle is reached.
Unpublished bug8066979 is available for WebLogic Server 8.1 SP6 and later
Unpublished bug8172940 is available for WebLogic Server 9.2 MP2 and later
Note you can get more info about bridge problems by following the below steps:
To debug the bridge you can enable debugging for the messaging bridge using either of the followings methods:
* Add the following lines to your WebLogic start script (before the weblogic.Server line):
-Dweblogic.debug.DebugMessagingBridgeStartup=true
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
* Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add “DumpToConsole” to the statements show above. For example:
-Dweblogic.debug.DebugMessagingBridgeStartupDumpToConsole=true
Edited by: atheek1 on May 30, 2010 5:19 AM

Javax.resource.ResourceException

Similar Messages

Maybe you are looking for