RDBMS event generator & JNDI datasources

Hi everyone,
My WLI 8.1 SP5 is going nuts ! I'm under a cluster architecture, WL 8.1 SP6 with Red Hat Linux, JRockit 1.4.2_10. Deploying an application i need to create some RDBMS event generator, but when i do this, i get an NameNotFoundException looking for my jndi datasource ( see below ). The datasource is created and i can work with it, since it's a must for my application. How is it possible that a datasource exists for a web application and does not for an integration event ? Does anyone have any experience about this ? Any help will be very appreciated !!
<18-may-2007 23H47' CEST> <Error> <WLW> <000000> <Error occurred while retrieving the Database Type
javax.naming.NameNotFoundException: Unable to resolve 'DSDataSource' Resolved ; remaining name 'DSDataSource'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:924)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:230)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:154)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:258)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:363)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.bea.wli.event.util.EventUtils.getDataSourceConnection(EventUtils.java:640)
at com.bea.wli.oam.rdbmseg.RDBMSChannelValidator.setChannelValues(RDBMSChannelValidator.java:471)
at com.bea.wli.oam.rdbmseg.RDBMSChannelValidator.validate(RDBMSChannelValidator.java:218)
at com.bea.wli.oam.rdbmseg.RDBMSMainServlet.submitChannel(RDBMSMainServlet.java:327)
at com.bea.wli.oam.eg.framework.XEGMainServlet.processRequest(XEGMainServlet.java:88)
at com.bea.wli.oam.eg.framework.XEGMainServlet.doPost(XEGMainServlet.java:151)
at com.bea.wli.oam.core.BaseServlet.userService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
at com.bea.wli.oam.core.BaseServlet.run()Ljava.lang.Object;(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.security.authentication.AuthenticationService.runAs(AuthenticationService.java:109)
at com.bea.wli.oam.core.BaseServlet.secureService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
at com.bea.wli.oam.core.BaseServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

If you are using a cluster you need to make sure the connection pool and data source are deployed on the admin server. I have had this problem many times before.

Similar Messages

RDBMS Event Generator Issue - JDBC Result Set Already Closed

All -
I am having a problem with an RDBMS event generator that has been exposed by our Load Testing. It seems that after the database is under load I get the following exception trace:
<Aug 7, 2007 4:33:06 PM EDT> <Info> <EJB> <BEA-010213> <Message-Driven EJB: PollerMDB_SessionRqt_1186515408009's transaction was rolledback. The transact ion details are: Xid=BEA1-7F8C65474500D80A5B94(218826722),Status=Rolled back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],numRepli esOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_Affinity_cgJMSStore_auto_1]=(ServerResourceInfo[JMS_Affi nity_cgJMSStore_auto_1]=(state=rolledback,assigned=wli_int_1),xar=JMS_Affinity_cgJMSStore_auto_1,re-Registered = false),XAServerResourceInfo[ACS.Telcordi a.XA.Pool]=(ServerResourceInfo[ACS.Telcordia.XA.Pool]=(state=rolledback,assigned=wli_int_1),xar=ACS.Telcordia.XA.Pool,re-Registered = false),XAServerReso urceInfo[JMS_Affinity_cgJMSStore_auto_2]=(ServerResourceInfo[JMS_Affinity_cgJMSStore_auto_2]=(state=rolledback,assigned=wli_int_2),xar=null,re-Registered = false),SCInfo[wli_int_domain+wli_int_2]=(state=rolledback),SCInfo[wli_int_domain+wli_int_1]=(state=rolledback),properties=({START_AND_END_THREAD_EQUAL =false}),local properties=({weblogic.jdbc.jta.ACS.Telcordia.XA.Pool=weblogic.jdbc.wrapper.TxInfo@d0b2687}),OwnerTransactionManager=ServerTM[ServerCoordin atorDescriptor=(CoordinatorURL=wli_int_1+128.241.233.85:8101+wli_int_domain+t3+, XAResources={weblogic.jdbc.wrapper.JTSXAResourceImpl, Affinity_cgPool, J MS_Affinity_cgJMSStore_auto_1, ACSDispatcherCP_XA, ACS.Dispatcher.RDBMS.Pool, ACS.Telcordia.XA.Pool},NonXAResources={})],CoordinatorURL=wli_int_1+128.241 .233.85:8101+wli_int_domain+t3+).>
<Aug 7, 2007 4:33:06 PM EDT> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
javax.ejb.EJBException: Error occurred while processing message received by this MDB. This MDB instance will be discarded after cleanup; nested exceptio n is: java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages.
javax.ejb.EJBException: Error occurred while processing message received by this MDB. This MDB instance will be discarded after cleanup; nested exception is: java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages
java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages
at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.fetchUsingResultSet(RDBMSIntrusiveQryMDB.java:561)
at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.onMessage(RDBMSIntrusiveQryMDB.java:310)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2523)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: java.sql.SQLException: Result set already closed
at weblogic.jdbc.wrapper.ResultSet.checkResultSet(ResultSet.java:105)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:67)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next()Z(Unknown Source)
at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.handleResultSet(RDBMSIntrusiveQryMDB.java:611)
at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.fetchUsingResultSet(RDBMSIntrusiveQryMDB.java:514)
... 8 more
javax.ejb.EJBException: Error occurred while processing message received by this MDB. This MDB instance will be discarded after cleanup; nested exception is: java.lang.Exception: Error occurred while preparing messages for Publication or while Publishing messages
at com.bea.wli.mbconnector.rdbms.intrusive.RDBMSIntrusiveQryMDB.onMessage(RDBMSIntrusiveQryMDB.java:346)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2523)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
I have tried several things and had my team do research but we have not been able to find an answer to the problem.
If anyone can offer any insight as to why we might be getting this error it would be greatly appreciated. Thanks!

i also have same error during load testing, mainly this error
"Unexpected exception while enlisting XAConnection java.sql.SQLException"
i tried rerunning after increasing connection pool sizes, transaction timeout, but no luck, marginal improvement in performance though
also tried changing the default tracking levl to none, but no luck.
i am with 8.1SP5, how about you ?
do share if you are able to bypass these errors
cheers

How to create an RDBMS event generator using wlst on weblogic 10.3

how to create an RDBMS event generator using wlst on weblogic 10.3, i got a code fragment needing class "com.bea.wli.management.configuration.RDBMSEventGenChannelConfiguration"
but i can' t find this class in classpath on weblogic 10.3, pls help me, thanks. code sample is better.

Hi,
RDBMS Event Generator Channel Rule Definition
When you are creating channel rule definitions in the WebLogic Integration Administration Console, it is recommended that you do not use the Back button if you want to resubmit the details on a page.
You should always use the navigation links provided and create a new channel rule definition.
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/deploy/cluster.html
http://download.oracle.com/docs/cd/E13214_01/wli/docs81/relnotes/relnotesLimit.html
http://otndnld.oracle.co.jp/document/products/owli/docs10gr3/pdf/deploy.pdf
This problem has been seen in the past when defining the channel rule for an RDBMS Event Generator if schema name was specified with the incorrect case (i.e. lowercase when it should have been uppercase or vice versa). To that end, it is suggested to change the case of the schema when creating the channel rule
Regards,
Kal

New article: Exploring the WebLogic Integration 8.1 RDBMS Event Generator

Dev2Dev has just published an article that you may be interested in:
Exploring the WebLogic Integration 8.1 RDBMS Event Generator
http://dev2dev.bea.com/pub/a/2007/02/rdbms-event-generator.html
If you'd like to write for Dev2Dev on a WebLogic Integration (or any other) topic, please contact me!
Regards,
Jon
Jon Mountjoy - Editor, Dev2Dev - http://dev2dev.bea.com/pub/au/13

If you are using a cluster you need to make sure the connection pool and data source are deployed on the admin server. I have had this problem many times before.

WLST Script for RDBMS Event Generator

Hello WLI Gurus,
I need the WLST Script for RDBMS Event Generator. There was a script in dev2dev but is no longer accessible. I need it for WLI 9.2.
Thanks in advance.
Varun

If you are using a cluster you need to make sure the connection pool and data source are deployed on the admin server. I have had this problem many times before.

Defining Channel Rules for a RDBMS Event Generator

Hi
I am trying to build my first RDBMS event (http://e-docs.bea.com/wli/docs81/manage/evntgen.html#1123751)
But I can only find the other types of events in the console
(File, Email, JMS, Times, MQ Series and HTTP).
What am I doing wrong? I have been reading through the help for the wliconsole too, and it doesn't say anything at all about RDBMS
Jon

In sp3, there is "Application Integration Design Console" avaliable at:
http://localhost:7001/wlai
and you can use this utility to define event generator for DB, but the utility at sp4 is better...

WLI 8.1 RDBMS Event Generator Problem

Hi,
I am using WLI 8.1 SP4. I have created a Trigger type RDBMSEventGenerator which publishes events in xml format.
It is supposed to poll every 8 seconds.
This event generator works fine if it is created after the server is started.
However, if the server is restarted, the same event generator stops polling completely. No events are published irrespective of the number of inserts made in the specified table.
Could anyone shed some light on why this is happening. I have tried to suspend and resume the event generator several times as well, to no effect.

I would ask in the WebLogic Server - JMS forum.

RDBMS Event Generator

The RDBMS EG (from sp4 - it replaces the RDBMS adapter)produces an error when creating the channel rule definition:
'java.lang.illegalArgumentException: illegal group reference at java.util.regex.Matcher.appendReplacement...'
...when generating event triggers on (oracle) tables with colum-names containing '$' (which is end-of-line in java!!)
Is there any workaround (other than change the colum-names, which is not an option here since all DB names are auto-created by another apps.)?
Thanks
TH

Is it my question not clear? can someone let me know what am missing. I'm struggling get this working..

Problems creating RDBMS Event Generators in a WebLogic cluster

Hi Everybody,
I just set up an integration cluster with one admin server and two managed servers into only one computer.
My deployed Application needs an RDBMS Event generator with 5 channel rules to be created and when I create the first channel rule I get this exception:
java.lang.NullPointerException
at com.bea.wli.management.configuration.RDBMSEventGenChannelConfiguration.equals(RDBMSEventGenChannelConfiguration.java:285)
at java.util.LinkedList.indexOf(LinkedList.java:398)
at java.util.LinkedList.contains(LinkedList.java:176)
at java.util.AbstractCollection.removeAll(AbstractCollection.java:354)
at com.bea.wli.management.mbconnector.rdbms.RDBMSEventGenConfigManager.setChannels(RDBMSEventGenConfigManager.java:886)
at com.bea.wli.management.mbconnector.GenericEventGenConfigurationMBeanImpl.setChannels(GenericEventGenConfigurationMBeanImpl.java:59)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1662)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1109)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:372)
at com.bea.wli.management.internal.WLIConfigurationMBeanImpl.setAttribute(WLIConfigurationMBeanImpl.java:152)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.RemoteMBeanServerImpl.private_setAttribute(RemoteMBeanServerImpl.java:431)
at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:387)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:735)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:469)
at com.bea.wli.management.configuration.GenericEventGenConfigurationMBean_Stub.setChannels([Lcom.bea.wli.management.configuration.GenericEventGenChannelConfiguration;)V(Unknown Source)
at com.bea.wli.oam.eg.framework.XEGHelper.updateEventGenerator(XEGHelper.java:243)
at com.bea.wli.oam.eg.framework.XEGMainServlet.saveGenerator(XEGMainServlet.java:709)
at com.bea.wli.oam.rdbmseg.RDBMSMainServlet.submitChannel(RDBMSMainServlet.java:349)
at com.bea.wli.oam.eg.framework.XEGMainServlet.processRequest(XEGMainServlet.java:88)
at com.bea.wli.oam.eg.framework.XEGMainServlet.doPost(XEGMainServlet.java:151)
at com.bea.wli.oam.core.BaseServlet.userService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
at com.bea.wli.oam.core.BaseServlet.run()Ljava.lang.Object;(Unknown Source)
at
The funny thing is that in my one server development / test production environment I don't have any problems at the time of the RDBMS Event generators...
Please anyone can help me? Any special JMS queue need to be created or something?? I'm becoming desperate!!
Thank you all!
Oscar

Well
At last I've found the answer...
In order to successfully create an RDBMS Event Generator, the creation app (in this case, wliconsole) must have access to the destination datasource. Thus, both connection pool and datasource targeted by the RDBMS EG must be deployed in the same server running the wliconsole.
In this particular case, I just had to redeploy my datasources targetting all servers in the cluster plus the admin server and that's it...
See you...
O.

Weblogic 10R3 event generator crash

I deloy my application on weblogic 10R3 flatform, some timer&RDBMS event generator created, most time, it works well,but sometime i find it crashes the RDBMS event generator can't work ,no row be readed,but it do exists in table, and should be readed, what happened to event generator
in the weblogic console, i find the corresponding event generator application is abnormal, in the releated thread pool , available ejb instance size is 0, is it a problem?
in this situation, what can i do is just to delete the specified RDBMS event generator and rereated it , who can help me? i expect your suggestion and troubleshooting, thanks.
Edited by: 918965 on 2012-3-5 下午10:31
Edited by: 918965 on 2012-3-7 下午6:19

I deloy my application on weblogic 10R3 flatform, some timer&RDBMS event generator created, most time, it works well,but sometime i find it crashes the RDBMS event generator can't work ,no row be readed,but it do exists in table, and should be readed, what happened to event generator
in the weblogic console, i find the corresponding event generator application is abnormal, in the releated thread pool , available ejb instance size is 0, is it a problem?
in this situation, what can i do is just to delete the specified RDBMS event generator and rereated it , who can help me? i expect your suggestion and troubleshooting, thanks.
Edited by: 918965 on 2012-3-5 下午10:31
Edited by: 918965 on 2012-3-7 下午6:19

Using WLST: Unable to create WLI Timer Event Generator

Hello,
I'm trying to create a WLST script, whcih will create Timer Event Generator on WLI 9.2 MP2.
Though to some extent script runs perfect, but it gives error when calling MBean egCfgMBean = getTarget("TimerEventGeneratorss/TimerEventGenerators")
Here is my script:-
import weblogic.Deployer
import com.bea.wli.mbconnector.timer as timereggen
import com.bea.wli.mbconnector.file as fileeggen
import com.bea.wli.management.configuration as wlicfg #Must have wli.jar in classpath
import java.lang.Boolean as bool
import jarray
import sys
print 'Starting the Timer Event Generation Configuration script .... '
if connected != 'true':
print 'Connecting to weblogic server .... '
connect(userName,passWord,URL)
else:
print 'Connected'
try:
print "Creating Timer EG ", timerEgName
timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir + "/" + "WLITimerEG_" + timerEgName + ".jar"])
#timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir,"-destJNDIName",jndiName])
#timereggen.TimerConnGenerator.main(["-inName", timerEgName,"-outfile", domaindir])
#wlst.config()
custom()
#egCfgMBean = wlst.getTarget("TimerEventGenerators/TimerEventGenerators")
egCfgMBean = getTarget("TimerEventGeneratorss/TimerEventGenerators")
egMBean = egCfgMBean.newTimerEventGenConfigurationMBean(timerEgName)
#egMBean = cmo.getTimerEventGenConfigurationMBeans()
cData = jarray.zeros(1, wlicfg.TimerEventGenChannelConfiguration)
print 'pass one'
cData[0] = wlicfg.TimerEventGenChannelConfiguration()
cData[0].setChannel(channel)
cData[0].setEffective(effectiveTime)
#cData[0].setExpiry(expiryTime)
cData[0].setFrequency(frequency)
cData[0].setMessageContent(message)
cData[0].setCalendarName(calendar)
cData[0].setPublishAsUser(publishAsUser)
egMBean.setChannels(cData);
appName = "WLITimerEG_" + timerEgName
deploy( appName, domaindir + "/" + appName + ".jar", adminServerName, "nostage" )
cd("Applications/" + appName)
set("LoadOrder", 1500)
cd("../..")
print "script returns SUCCESS"
except:
print "ERROR: configuration"
#dumpStack()
# Finished
print 'Disconnecting from server...'
disconnect('y')
print 'Finished.'
exit()
I really need some help to fix this issue.
Thanks
dig

Hi,
RDBMS Event Generator Channel Rule Definition
When you are creating channel rule definitions in the WebLogic Integration Administration Console, it is recommended that you do not use the Back button if you want to resubmit the details on a page.
You should always use the navigation links provided and create a new channel rule definition.
http://download.oracle.com/docs/cd/E13214_01/wli/docs85/deploy/cluster.html
http://download.oracle.com/docs/cd/E13214_01/wli/docs81/relnotes/relnotesLimit.html
http://otndnld.oracle.co.jp/document/products/owli/docs10gr3/pdf/deploy.pdf
This problem has been seen in the past when defining the channel rule for an RDBMS Event Generator if schema name was specified with the incorrect case (i.e. lowercase when it should have been uppercase or vice versa). To that end, it is suggested to change the case of the schema when creating the channel rule
Regards,
Kal

How do I use a JNDI datasource in my application?

Not sure how to access the JNDI datasource i setup in my config.xml. I tried to browse it at rmi://localhost:1099/ but it only shows jmxrmi in the tree.
My config.xml looks like
<n1:config xsi:schemaLocation="http://www.bea.com/ns/wlevs/config/server wlevs_server_config.xsd" xmlns:n1="http://www.bea.com/ns/wlevs/config/server" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<netio>
    <name>NetIO</name>
    <port>9002</port>
</netio>
<work-manager>
    <name>JettyWorkManager</name>
    <min-threads-constraint>5</min-threads-constraint>
    <max-threads-constraint>10</max-threads-constraint>
</work-manager>
<jetty>
    <name>JettyServer</name>
    <network-io-name>NetIO</network-io-name>
    <work-manager-name>JettyWorkManager</work-manager-name>
</jetty>
<rmi>
    <name>RMI</name>
    <http-service-name>JettyServer</http-service-name>
</rmi>
<jndi-context>
    <name>JNDI</name>
</jndi-context>
<exported-jndi-context>
    <name>exportedJndi</name>
    <rmi-service-name>RMI</rmi-service-name>
</exported-jndi-context>
<jmx>
    <jndi-service-name>JNDI</jndi-service-name>
    <rmi-service-name>RMI</rmi-service-name>
    <rmi-registry-port>1099</rmi-registry-port>
    <rmi-jrmp-port>9999</rmi-jrmp-port>
</jmx>
<transaction-manager>
      <name>transactionmanager</name>
      
</transaction-manager>
<data-source>
      <name>hqsqlconn</name>
      <driver-params>
        <url>jdbc:hsqldb:hsql://localhost/wlevdb</url>
        <driver-name>org.hsqldb.jdbcDriver</driver-name>
        <properties>
          <element>
            <name>user</name>
            <value>sa</value>
          </element>
          <element>
            <name>password</name>
            <value></value>
          </element>
        </properties>
        <use-xa-data-source-interface>true</use-xa-data-source-interface>
      </driver-params>
      <connection-pool-params>
        <initial-capacity>1</initial-capacity>
        <max-capacity>5</max-capacity>
        <test-table-name>test_table</test-table-name>
      </connection-pool-params>
      <data-source-params>
        <jndi-names>
          <element>hqsqlconn</element>
        </jndi-names>
        <global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
      </data-source-params>
</data-source>
</n1:config>

I see what you are saying.
The JNDI approach should work-we will try to reproduce this internally.
I would recommend leveraging the OSGi service registry, instead of using JNDI, however. The Event Server is a modular server based on OSGi, so one should use the OSGi service registry whenever possible instead of using the jndi registry. Jndi is primarily there to support legacy code that requires Jndi.
Any data sources that you configure are automatically registered in the OSGi service registry. When there is more than one data source they can be distinguished using their name.
There are a couple of options.
If you want to inject a reference to your datasource into a Spring bean, you can use an annotation, @Service, to annotate a setter method on your bean (see my previous post). The container will then inject a reference to the data source into the bean.
You can also put the following in your spring application context file
<osgi:reference id="myDataSource"
interface="javax.sql.DataSource"/>
This creates a bean proxy that references the datasource by looking up the datasource in the OSGi service registry. It works similarly to JndiObjectFactoryBean, but it uses the OSGi service registry instead of the JNDI registry. You can read more about it here
http://www.springframework.org/osgi/specification
(Look in section 3.3)
Hope that helps.
Seth
Edited by swhite at 08/01/2007 6:19 PM

[EJB:010112] - error with WLI8.1 Event Generator for foreign JMS/MQ provider

I'm getting following error in weblogic server log when starting a JMS Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect
every 10 seconds. This log message will repeat every 600 seconds until the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted, but the pro
vider defined in the EJB is not transacted. Provider should be transacted if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly. QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott

Hi Scott,
I need a transaction from the MDB since I am not using an EJb to pursue the action.
Hence I need to retain the <trans-attribute>Required</trans-attribute> at the
MDB.
Have any answers?
Pradip
"Scott Yen" <[email protected]> wrote:
>
It's resolved.
The MDB automatically created by JMS Event Generator defaults to be deployed
with
“transacted”. That requires the foreign JMS provider to be “XA”.
The deployment descriptor is created as <domain-directory>/WLIJmsEG_<event_gen_name>.jar
e.g. C:\bea812\user_projects\domains\jmsInterop\WLIJmsEG_mqQueueEventGen.jar
Since MQ in the localhost and remote SLUDV18 are not XA-enabled, we had
to manually
change the <container-transaction> section in ejb-jar.xml:
From :
<trans-attribute>Required</trans-attribute>
To:
<trans-attribute>NotSupported</trans-attribute>
"Scott Yen" <[email protected]> wrote:
I'm getting following error in weblogic server log when starting a JMS
Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to
reconnect
every 10 seconds. This log message will repeat every 600 seconds until
the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted,
but the pro
vider defined in the EJB is not transacted. Provider should be transacted
if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator
for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly.
QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign
JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott

Using a Foreign JMS Destination as a JMS Event Generator Subscription

NOTE THIS IS BUMPED UP FROM ROBERT NORTON'S POST. I am having the same
problem here. From the wliconsole, the only queues listed to have events
generated from are local ones.
Hello,
I'm trying to create a workflow that is started by a JMS message queue
event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a
queue
on a remote WebLogic 8.1 installation, publish the incoming messages to
a channel,
then initiate a workflow by subscribing to that channel. Here's a copy
of my configuration
file for the tool:
<message-broker-jms-event-generator-def
source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection
Factory,
and Destination using the Weblogic Admin Console. Below are the
parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi
connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name:
weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name:
InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the
following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The
Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to
the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS
destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure
that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS
destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in
my configuration.
I found the existing BEA documentation to be a bit too generic,
containing no
specific examples of the proper syntax to use for this task. Can anyone
offer
any advice or better, a working example? Any BEA reps out there?

NOTE THIS IS BUMPED UP FROM ROBERT NORTON'S POST. I am having the same
problem here. From the wliconsole, the only queues listed to have events
generated from are local ones.
Hello,
I'm trying to create a workflow that is started by a JMS message queue
event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a
queue
on a remote WebLogic 8.1 installation, publish the incoming messages to
a channel,
then initiate a workflow by subscribing to that channel. Here's a copy
of my configuration
file for the tool:
<message-broker-jms-event-generator-def
source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection
Factory,
and Destination using the Weblogic Admin Console. Below are the
parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi
connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name:
weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name:
InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the
following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The
Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to
the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS
destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure
that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS
destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in
my configuration.
I found the existing BEA documentation to be a bit too generic,
containing no
specific examples of the proper syntax to use for this task. Can anyone
offer
any advice or better, a working example? Any BEA reps out there?

Using JMS Event Generator w/ remote WebLogic 8.1 queue

Hello,
I'm trying to create a workflow that is started by a JMS message queue event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
file for the tool:
<message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
and Destination using the Weblogic Admin Console. Below are the parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
I found the existing BEA documentation to be a bit too generic, containing no
specific examples of the proper syntax to use for this task. Can anyone offer
any advice or better, a working example? Any BEA reps out there?

Hello,
I'm trying to create a workflow that is started by a JMS message queue event.
I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
file for the tool:
<message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
and Destination using the Weblogic Admin Console. Below are the parameters I used
to define the remote connection
Foreign JMS Server:
jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
url: //OPER1090:7001
Foreign connection factory:
local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
(Are username and password required?)
Foreign JMS Destination:
local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
After I try to deploy my generated JMS Event jar, I receive the following error:
<Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
been deployed.>
I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
I found the existing BEA documentation to be a bit too generic, containing no
specific examples of the proper syntax to use for this task. Can anyone offer
any advice or better, a working example? Any BEA reps out there?

RDBMS event generator & JNDI datasources

Similar Messages

Maybe you are looking for