users@genericjmsra.java.net

RE: Re: InvalidPropertyException when deploying MDB on Weblogic

From: Evans, Martin <martin.evans_at_credit-suisse.com>
Date: Wed, 12 Aug 2009 09:46:54 -0400

Hi Ramesh,

The logging still refuses to play :-(

Weblogic has an option for the logging implementation, Log4J or JDK I
tried both of those. I can put a call into Oracle but I probably need
more info on the logging mechanism before I can do that.

Regards,

Martin

-----Original Message-----
From: Ramesh.Parthasarathy_at_Sun.COM [mailto:Ramesh.Parthasarathy_at_Sun.COM]

Sent: 11 August 2009 21:37
To: users_at_genericjmsra.dev.java.net
Subject: Re: InvalidPropertyException when deploying MDB on Weblogic

Hi Martin,
    Thanks for the update, glad to know its working.
The case sensitivity could be because of the connector runtime
implementation in WebLogic. As far as i know atleast the connector
implementation in GlassFish tries to set the property by trying both
cases for the first character.
Also, sorry for the delay in responding, but the following should work
without having to modify the generic ra code

<config-property-name>LogLevel</config-property-name>

<config-property-type>java.lang.String</config-property-type>

<config-property-value>FINEST</config-property-value>


Thanks
-Ramesh

Evans, Martin wrote:
> Update - issue somewhat resolved
>
> OK, I couldn't get debug working with weblogic, so I rebuilt the
> genericjmsra code and replaced the debug statement for a
> System.out.println.
>
> Here's what I'm getting;
>
> /Properties passed to InitialContext ::
> {java.naming.provider.url=file:/H:/JNDI,
>
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory}/
>
> /Looking the JNDI name :null/
>
> So my properties for the JNDI ic are fine, it's just not getting the
> connection factory JNDI name.
>
> I took another look at my EJB activation spec; it seems that the
> problem is due to me using an uppercase C for
connectionFactoryJndiName?
>
> before;
>
>
<activation-config-property-name>*C*onnectionFactoryJndiName</activation
-config-property-name>
>
> after;
>
>
<activation-config-property-name>connectionFactoryJndiName</activation-c
onfig-property-name>
>
>
> I'm using the 1.7 adapter. All the examples I found had an uppercase
C?
>
> Martin
>
>
------------------------------------------------------------------------
> *From:* Evans, Martin
> *Sent:* 07 August 2009 16:25
> *To:* users_at_genericjmsra.dev.java.net
> *Subject:* RE: RE: InvalidPropertyException when deploying MDB on
Weblogic
>
> mmm, taken a look at the code, seems debug would really be my friend
here;
>
>
> public Object createObject() throws _ResourceException_ {
>
> try {
>
> _Hashtable_ props = _parseToProperties_(this.jndiProps);
>
> debug("Properties passed to InitialContext :: " + props);
>
> InitialContext ic = new InitialContext(props);
>
> debug("Looking the JNDI name :" + this.jndiName);
>
> return ic.lookup(this.jndiName); <<<<<< This is line 98 --
> ObjectBuilderFactory.java:98 >>>>>
>
> } catch (Exception e) {
>
> throw _ExceptionUtils_.newInvalidPropertyException(e);
>
> }
>
>
>
------------------------------------------------------------------------
> *From:* Evans, Martin
> *Sent:* 07 August 2009 16:01
> *To:* users_at_genericjmsra.dev.java.net
> *Subject:* RE: InvalidPropertyException when deploying MDB on Weblogic
>
> Hi All,
>
> I've set the adapter to debug but I still don't see anything in my
> weblogic log, even if I set all debug flags in weblogic?
>
> I set the log level in ra.xml and I can see it in the weblogic
console;
>
>
> <config-property>
>
> <config-property-name>LogLevel</config-property-name>
>
> <config-property-type>java.lang.String</config-property-type>
>
> <config-property-value>DEBUG</config-property-value>
>
> </config-property>
>
> Any help would be appreciated.
>
> Martin
>
>
>
------------------------------------------------------------------------
> *From:* Evans, Martin
> *Sent:* 07 August 2009 10:41
> *To:* users_at_genericjmsra.dev.java.net
> *Subject:* InvalidPropertyException when deploying MDB on Weblogic
>
>
> Hi,
>
> I'm getting an exception when deploying an MDB in Weblogic;
>
>
javax.resource.spi.InvalidPropertyExceptionweblogic.connector.external.E
ndpointActivationException:
> javax.resource.spi.InvalidPropertyException
>
> I set the debug level to finest and turned on debug in weblogic but
> still don't see what the invalid property is?
>
> I've set the appropriate properties in weblogic-ra.xml to enable JNDI.
>
> This is my ejb-jar.xml
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.1"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> _http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd_">
>
> <display-name>Message Processor Configuration</display-name>
> <enterprise-beans>
> <message-driven>
> <display-name>MessageProcessor</display-name>
> <ejb-name>MessageProcessor</ejb-name>
>
> <ejb-class>com.cs.dtacc.messaging.WeblogicJMS</ejb-class>
> <transaction-type>Container</transaction-type>
> <activation-config>
> <activation-config-property>
>
>
<activation-config-property-name>ConnectionFactoryJndiName</activation-c
onfig-property-name>
>
>
>
<activation-config-property-value>WMQ_QM1CF</activation-config-property-
value>
>
> </activation-config-property>
> <activation-config-property>
>
>
<activation-config-property-name>DestinationJndiName</activation-config-
property-name>
>
>
>
<activation-config-property-value>WMQ_MARTIN_TEST</activation-config-pro
perty-value>
>
> </activation-config-property>
> </activation-config>
> </message-driven>
> </enterprise-beans>
> <assembly-descriptor>
> <container-transaction>
> <method>
> <ejb-name>MessageProcessor</ejb-name>
> <method-name>*</method-name>
> </method>
>
<trans-attribute>NotSupported</trans-attribute>
> </container-transaction>
> </assembly-descriptor>
> </ejb-jar>
>
> Martin
>
>
>
>
>
========================================================================
======
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
>
========================================================================
======
>
>
>
>
========================================================================
======
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
>
========================================================================
======
>
>
>
>
========================================================================
======
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
>
========================================================================
======
>
>
>
>
========================================================================
======
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
>
========================================================================
======
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_genericjmsra.dev.java.net
For additional commands, e-mail: users-help_at_genericjmsra.dev.java.net


===============================================================================
 Please access the attached hyperlink for an important electronic communications disclaimer:
 http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
 ===============================================================================