Weblogic-ra.xml for resource adapter
Hi
We are trying to deploy Oracle Centraloffice on weblogic 10.3
But after configuring resource adapter which resides inside Central office application's EAR file, are application stops working.
It give us No classdef found error, basically it stops finding the JAR files which resides inside the application.
Resource adapter is configured to read file system for incoming JAR files and then process them, but if it starts working then are application stops working.
We are configuring the resource adapter's weblogic-ra.xml with the weblogic 9.10 schema in which everything is bundled inside <outbound-resource-adapter> tag
What is the correct way of looking up a resource adapter from another resource adpater? The JNDI name of my resource adapter is "StorageFactory" and I am doing a lookup like:
Context ctx = new InitialContext();
ctx.lookup("StorageFactory")
Is this a correct way to lookup?
Similar Messages
-
Sample weblogic-ejb-jar.xml for Resource-ref EJB 3.0
I am trying to create an MDB that can be re-used under different names.
@MessageDriven(description = "An MDB that transfers messages from one Queue to another", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class TransferMdb implements MessageListener {
private static final Logger LOG = Logger.getLogger(TransferMdb.class);
@Resource(name = "jms/connfactory")
private ConnectionFactory connectionFactory;
@Resource(name = "jms/targetDestination")
private Queue targetDestination;
<ejb-jar version="3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_3_0.xsd">
<enterprise-beans>
<message-driven>
<ejb-name>TransferMdb</ejb-name>
<ejb-class>TransferMdb</ejb-class>
</message-driven>
</enterprise-beans>
</ejb-jar>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>TransferMdb</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>200</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>test_queue</destination-jndi-name>
<transaction-descriptor>
<trans-timeout-seconds>20</trans-timeout-seconds>
</transaction-descriptor>
</message-driven-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jms/connectionfactory</res-ref-name>
<jndi-name>connectionfactory</jndi-name>
</resource-description>
<resource-description>
<res-ref-name>jms/targetDestination</res-ref-name>
<jndi-name>reply_queue</jndi-name>
</resource-description>
</reference-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
However when I deploy the above, I get exceptions such as:
problem: cvc-complex-type.2.4a: Expected elements 'initial-context-factory@http://www.bea.com/ns/weblogic/weblogic-ejb-jar provider-url@http://www.bea.com/ns/weblogic/weblogic-ejb-jar connection-factory-jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jms-polling-interval-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jms-client-id@http://www.bea.com/ns/weblogic/weblogic-ejb-jar generate-unique-jms-client-id@http://www.bea.com/ns/weblogic/weblogic-ejb-jar durable-subscription-deletion@http://www.bea.com/ns/weblogic/weblogic-ejb-jar max-messages-in-transaction@http://www.bea.com/ns/weblogic/weblogic-ejb-jar distributed-destination-connection@http://www.bea.com/ns/weblogic/weblogic-ejb-jar use81-style-polling@http://www.bea.com/ns/weblogic/weblogic-ejb-jar init-suspend-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar max-suspend-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar security-plugin@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' instead of 'transaction-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' here in element message-driven-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar:<null>
problem: cvc-complex-type.2.4a: Expected elements 'transaction-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar iiop-security-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar resource-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar resource-env-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar ejb-reference-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar service-reference-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar enable-call-by-reference@http://www.bea.com/ns/weblogic/weblogic-ejb-jar network-access-point@http://www.bea.com/ns/weblogic/weblogic-ejb-jar clients-on-same-server@http://www.bea.com/ns/weblogic/weblogic-ejb-jar run-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar create-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar remove-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar passivate-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar local-jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar dispatch-policy@http://www.bea.com/ns/weblogic/weblogic-ejb-jar remote-client-timeout@http://www.bea.com/ns/weblogic/weblogic-ejb-jar stick-to-first-server@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' instead of 'reference-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' here in element weblogic-enterprise-bean@http://www.bea.com/ns/weblogic/weblogic-ejb-jar:<null>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
Truncated. see log file for complete stacktrace
I am clearly missing items in the weblogic-ejb-jar.xml. If anyone has a sample or tips, that would be awesome as a starting point.Those tags just declare that you are using our CMP provider and that
your descriptor is in META-INF/weblogic-cmp-rdbms-jar.xml.
FWIW, you might also want to check out EJBGen. It tends to keep more up
to date with WLS than xdoclet.
-- Rob
Gen wrote:
I am using xdoclets to generate descriptor file weblogic-ejb-jar.xml
for a BMP entity bean. Xdoclet is generating the descriptor file
alright, but is putting the following extra tags. This happens even
for samples which come with the download, so my tags in java file are
not wrong.
My question is, are the extra tags below harmless, or should I
manually go to each desciptor file and remove them?
Thanks.
----------- EXTRA TAGS GENERATED START ---------
persistence> <persistence-type>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-type>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
</persistence-use>
</persistence>
----------- EXTRA TAGS GENERATED END ---------
----------- TAGS I PUT IN JAVA CLASS START --------
* @ejb:bean name="com.ejb.entity.Customer"
* jndi-name="com.ejb.entity.CustomerHome"
* view-type="remote"
* type="BMP"
* primkey-field="com.ejb.entity.CustomerPK"
* reentrant="false"
* @weblogic:cache
* max-beans-in-cache="1000"
* read-timeout-seconds="900"
* concurrency-strategy="ReadOnly"
----------- TAGS I PUT IN JAVA CLASS END -------- -
Can't Find Custom Work Manager For Resource Adapter
I'm creating an inbound resource adapter and wish to throttle the number of connections via a custom work manager.
If I understand the BEA docs, I can declare and define a resource adapter's work manager inside of its entry in weblogic-ra.xml .
For example:
<?xml version = "1.0"?>
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90">
<jndi-name>InboundRA</jndi-name>
<!-- WM declared below -->
<work-manager>
<name>CustomWM</name>
<max-threads-constraint>
<name>maxthreads</name>
<count>3</count>
</max-threads-constraint>
</work-manager>
However, upon startup I see :
<BEA-002919> <Unable to find a WorkManager with name CustomWM . Dispatch policy CustomWM will map to the default WorkManager for the application appsdirCustom_ear> .
So it uses the default work manager.Well, I did it again. Solved my own problem two hours after I posted it. Which, I guess, is better than not solving it.
I mistakenly thought that the <work-manager> entry in weblogic-ra.xml is a declaration. It is apparently a reference.
I declared a WorkManager of the same name in the WLS 9 console, restarted the server, and it appears that I am now using the custom work manager.
The max-threads constraint also works. -
Call another WebLogic's EJBs from resource adapter?
Is it possible to call another WebLogic's EJBs from a resource adapter?
A call to the javax.naming.InitialContext(Hashtable environment) results in a
VersioningError:
weblogic.common.internal.VersioningError: Incompatible service packs in CLASSPATH:
(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 , 6.1.4.0)
not compatible with
(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:122)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at java.lang.reflect.Constructor.newInstance(Native Method)
I'm not sure it will always be possible to match the version, although here upgrading
the SP3 to SP4 will probably be done soon.
Does anyone have experience with this?
Or better: is there any documentation on this issue?
Hi Hans,
Here is the link for Weblogic SP3 / SP4 vulnerability and comparison for
http://216.239.53.104/search?q=cache:RqqaQ3HZdwoJ:www.nipc.gov/cybernotes/2003/cyberissue2003-06.pdf+Versioning+Error+in+BEA+weblogic+6.1+SP3+and+SP4&hl=en&ie=UTF-8
Hope this will help you.
Let me know if u have any further problems.
rgds
KSK
"Hans Bausewein" <[email protected]> wrote:
>
>
>Is it possible to call another WebLogic's EJBs from a resource adapter?
>
>A call to the javax.naming.InitialContext(Hashtable environment) results
>in a
>VersioningError:
>
>weblogic.common.internal.VersioningError: Incompatible service packs
>in CLASSPATH:
>(BEA Systems, WebLogic Server 6.1 SP4 11/08/2002 21:50:43 #221641 ,
>6.1.4.0)
>not compatible with
>(BEA Systems, WebLogic Server 6.1 SP3 06/19/2002 22:25:39 #190835 , 6.1.3.0)
> at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:128)
> at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
> at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
> at weblogic.kernel.Kernel.initialize(Kernel.java:122)
> at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:101)
> at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:166)
> at java.lang.Class.newInstance0(Native Method)
> at java.lang.Class.newInstance(Class.java:232)
> at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
> at javax.naming.InitialContext.init(InitialContext.java:217)
> at javax.naming.InitialContext.<init>(InitialContext.java:193)
> at java.lang.reflect.Constructor.newInstance(Native Method)
>
>
>
>I'm not sure it will always be possible to match the version, although
>here upgrading
>the SP3 to SP4 will probably be done soon.
>
>Does anyone have experience with this?
>
>Or better: is there any documentation on this issue?
>
-
Hi there,
is it possible to create a XML for the administrator to edit the Agent propreties.. like CSQ the Agent should handle and skill level for the Agent?
I want to provide this for the Supervisor can handle they r agent without me...
Thanks.
Andrei.Try to ask a more general question, as supposed to getting right into an XML based solution.
Just have your supervisors log into AppAdmin, they will be able to manage their agents just like you are asking.
Make sure the system parameter for : Supervisor Access is Access To Supervisor's Team Only -
Mapping to simplify structure of XML for File Adapter
Hi everybody
Here is a short question regarding the restructuring of an incoming IDoc message to an outgoing file.
The IDoc has the structure:
-IDoc
___-->Segment A1
______--> Segment B1
_________-->Segment C1
_________-->Segment C2
_________-->Segment C3
______--> Segment B2
_________-->Segment C4
_________-->Segment C5
_________-->Segment C6
___-->Segment D1
You can see that Segment A1 occurres only ones, but can have several child nodes B. Also Segment B can have several Child nodes.
To transfer this Idoc to a flat file we have to create a flat structure as I understood form several Threads. So the target should look like this:
-->root
_____-->Segment A1
_____-->Segment B1
_____-->Segment C1
_____-->Segment C2
_____-->Segment C3
_____-->Segment B2
_____-->Segment C4
_____-->Segment C5
_____-->Segment C6
_____-->Segment D1
If I map the structure just one by one, I loose the last segments of C and it look like:
-->root
_____-->Segment A1
_____-->Segment B1
_____-->Segment C1
_____-->Segment C2
_____-->Segment C3
_____-->Segment B2
_____-->Segment D1
How can I manage to get the needed target structure. I thought of using function <i>sortbykey</i> or <i>sort</i>, because I have values in C and B which are equal.
Any help?
Regards OliverHi Again on this topic
yes stefan, obviously we have to have a flat structure. Based on our frustration we tried to send our structure from an Idoc directly to the file adapter and the following intresting thing came out:
The Idoc structure looked like this
-->root
_____-->EDIC_040
_____-->Segment A1
________-->Segment B1
___________-->Segment C1
___________-->Segment C2
___________-->Segment C3
________-->Segment B2
___________-->Segment C4
___________-->Segment C5
___________-->Segment C6
_____-->Segment D1
After sending this structure to the file adapter and ignoring that the stucture is not flat one we got this in our file:
Segment A1Segment B1
Segment C1
Segment C2
Segment C3
Segment B2
Segment C4
Segment C5
Segment C6
Segment D1
We got nearly what we wanted, just that a new line is missed between Segment A1 and Segment B1. We tried to use 'nl' but it does not work. Any Ideas on how to get Segment B1 into the next row??
Regards Oliver -
Deploying J2E CA 1.0 Resource Adapter on 11g
I am currently only supplying an ra.xml file since I have not been able to get the same RAR file that worked with WLS 8 to install correctly on 11g with my weblogic-ra.xml. I receive the following error even though I do not supply a weblogic-ra.xml file as the error message states. Are 1.0 resource adapters supported? I have included a copy of the ra.xml at the bottom of message.
Any ideas?
Eric
<Nov 24, 2010 2:37:04 PM MST> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1290634624475' for task '0'. Err
or is: 'weblogic.application.ModuleException: A <jndi-name> is specified for the
resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> el
ement is specified in ra.xml'
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149004> <Failures were d
etected while initiating deploy task for application 'BullHooXG8Line'.>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149078> <Stack trace for
message 149004
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Error> <Console> <BEA-240003> <Console encountere
d the following error weblogic.application.ModuleException: A <jndi-name> is spe
cified for the resource adapter bean in weblogic-ra.xml, however no <resourceada
pter-class> element is specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo
duleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN' 'http://java.sun.com/dtd/connector_1_0.d
td'>
<connector>
<display-name>HooXG8 Line NoTxn Adapter</display-name>
<vendor-name>Bull</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>GCOS</eis-type>
<version>2.1</version>
<resourceadapter>
<managedconnectionfactory-class>com.bull.HooX.GcosManagedConnectionFactoryImpl</managedconnectionfactory-class
>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.bull.HooX.GcosConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.bull.HooX.GcosConnectionImpl</connection-impl-class>
<transaction-support>NoTransaction</transaction-support>
<config-property>
<description>IP name or address</description>
<config-property-name>ipAddress</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>DSA node name</description>
<config-property-name>dsaNode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Mailbox name</description>
<config-property-name>mailbox</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Protocol to use(EGATE, LINE, NONE)</description>
<config-property-name>protocol</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>LINE</config-property-value>
</config-property>There should be a weblogic-ra.xml file in your deployment plan somewhere. The structure of the deployment plan is as follows:
somewhere/Plan.xml
somewhere/plan/META-INF/weblogic-ra.xml
The resource adapter does not support you specifying a <jndi-name> for the resource adapter. You can however specify <jndi-name> for the connection instances you create after deploying the adapter. If you have a <jndi-name> for the recource adapter, simply delete it from weblogic-ra.xml (also delete empty element such as <jndi-name></jndi-name> or <jndi-name /> ). Then update the adapter from the Deployments page in Admin console.
Here is my weblogic-ra.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-connector xmlns="http://xmlns.oracle.com/weblogic/weblogic-connector" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-connector http://xmlns.oracle.com/weblogic/weblogic-connector/1.0/weblogic-connector.xsd">
<native-libdir>C:\dev\wls_domains\domain1\lib</native-libdir>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<security></security>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params></pool-params>
<logging></logging>
</default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<default-connection-properties>
<pool-params></pool-params>
<logging>
<logging-enabled>false</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>false</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>500</file-size-limit>
<rotate-log-on-startup>true</rotate-log-on-startup>
<log-file-rotation-dir></log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
</default-connection-properties>
<connection-instance>
<jndi-name>hoox</jndi-name>
<connection-properties>
<pool-params></pool-params>
<logging>
<log-filename>C:\dev\wls_domains\domain1\servers\AdminServer\logs\hoox.log</log-filename>
<logging-enabled>true</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>10000</file-size-limit>
<rotate-log-on-startup>false</rotate-log-on-startup>
<log-file-rotation-dir>C:\dev\wls_domains\domain1\servers\AdminServer\logs</log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
<properties>
<property>
<name>mailbox</name>
<value>XXXXXXXXXXXXXX</value>
</property>
<property>
<name>dsaNode</name>
<value>XXXXXXXXXXXXX</value>
</property>
<property>
<name>ipAddress</name>
<value>XXXXXXXXXXXXXXX</value>
</property>
<property>
<name>options</name>
<value>-TL FULL -MCMDSIZE 5</value>
</property>
<property>
<name>protocol</name>
<value>EGATE</value>
</property>
<property>
<name>serviceMapPath</name>
<value>C:\dev\wls_domains\domain1\lib\vdirmap.xml</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector> -
Connectivity from ejb to Resource Adapter at run time
I am facing a problem regarding the look-up of the Resource Adapter from the Ejb.
To explain :
1.I have The <resource-ref> tag in ejb-jar.xml set at follows :
<resource-ref>
<description>The Resource Adapter</description>
<res-ref-name>eis/RitResourceAdapter</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
and the <resource-description> tag in weblogic-ejb-jar.xml as follows:
<resource-description>
<res-ref-name>eis/RitResourceAdapter</res-ref-name>
<jndi-name>eis/RitResourceAdapterConnectorJNDINAME</jndi-name>
</resource-description>
2.Even though I have mentioned the res-ref-type as javax.sql.Datasource , in my
code I have done :
rcf = (RitConnectionFactory) c.lookup ("java:comp/env/eis/RitResourceAdpapter");
Where rcf is the my Resource Adapter specific Connection Factory (one which
I have prepared and not
the javax.resource.cci.ConnectionFactory). So this means the connection
object which I get is casted to
get my own application specific connection object.
3.When I run my servlet (which looks up the Ejb and which in turn looks-up the
Resource Adapter) it works fine to the point that it looks-up the bean successfully
but fails when it tries to do so for Resource Adapter. The Server exception is
as follows :
javax.ejb.EJBException
- with nested exception:
[javax.naming.NameNotFoundException: Unable to resolve comp/env/eis/RitResourceAdpapter/
Resolved: 'comp/env/eis' Unresolved:'RitResourceAdpapter' ; remaining name '']
It will be great to hear about any solution from you people.
For your information :
I am using Weblogic 6.1, both the ejb jar and the RitResourceAdapter.rar has been
deployed and the relevant portion of the weblogic-ra. xml is :
<connection-factory-name>LogicalNameOfRitResourceAdapter</connection-factory-name>
<jndi-name>eis/RitResourceAdapterConnectorJNDINAME</jndi-name>
Regards,
Ritwik
> My question here is that is there any way where I do not put the queue name in the sender adapter at design time and based on the data availability in the queue let the sender adapter know the queue name to be processed at run time.
Unfortunately for JMS Sender CC it is not possible, but other way around is possible. I.e. you can dynamically choose the receving queue names by using ASMA "JMSReplyTo" in JMS Sender CC.
Regards,
Sarvesh -
Commit error of resource adapter in Application Resources of nwa
Hi All,
I am trying to configure SAP RFC with MII Message Listener XMIIRFC02
While i am updating(XMIIRFC01) SAP details in Resource Adapter of Application Resource in nwa(SAP NetWeaver )
And when i click the save button its showing below error.
"Saving Resource Adapter: XMIIRFC02 failed due to: Configuration changes for resource adapter not committed"
And if i check the Log Details, its showing below exception
Exception:
[EXCEPTION]
com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration exception.
Any idea regarding this error
Thanks in advance
Kind Regards,
Praveen Reddy M
Edited by: praveen2425 on Feb 27, 2012 1:57 PMHi Michael,
Thanks for your responses,
Its showing for all and here i am trying to update SAP details in the XMIIRFC02 properties of Resource Adapters
@Sarathi
I have checked all the things, even i have reentered all the SAP details but no luck
Before doing all this i have done in SAP netweaver for XMIIRFC02 in below navigation
Configuration Management --> Infrastructure --> Application Resources --> select Resource Adapter --> select XMIIRFC02 --> go to properties and update all the details of SAP
Is this process can work and update the message listener XMIIRRC02 with SAP server and client
And while i am clicking update button of message listener XMIIRFC02 from MII Menu Screen, Its showing popup error message
"Cannot update Configuration; JRA XMIIRFC02 must be configured in SAP NetWeaver Administrator before it is used"
Thanks,
Kind Regards,
Praveen Reddy M
Edited by: praveen2425 on Feb 29, 2012 7:48 AM -
Weblogic Deployment weblogic-applciation.xml
Hello,
Do i need weblogic-application.xml for ordinary deployment keeping .war, .ear, .jar files in applications folder under webglogic, if so what is the structure of my source file i have to keep ?. I mean where i have to keep the application.xml and weblogic-application.xml in conjunction with my beans META-INF/ejb-jar.xml, weblogic-ejb-jar.xml
thanks,
kuruweblogic-application.xml file is not mandatory for deploying application. It is used for setting additional vendor specific options.
For example in your 'Test' directory, there are three folder 1) web 2) META-INF 3) ejb
Put weblogic.xml and weblogic-application.xml inTest / META-INF.
Put ejb-jar.xml and weblogic-ejb-jar.xml in test / ejb / META-INF directory.
+ Mihir -
Inqmy resource adapter for SAP with Bea Weblogic Server
Hi everybody,
Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic server
It works well with INQMY server, but with BEA I'm getting a lot of problems creating
the connections.
Thanks in advance.
Xavi.
All,
Here are the steps we (used for internal testing) had to perform to get
IN-Q-MY adapter for SAP to work with WebLogic:
The wli.adapter.inqmy.sapr3.spi package contains extensions to the
In-Q-My J2EE Connector Architecture classes to overcome some limitations
in the base implementation classes. To get around these issues, we had
to extend their R3ManagedConnectionFactory, R3ConnectionManager, and
R3ConnectionFactory classes.
* The javax.resource.spi.ManagedConnectionFactory implementation
does not over-ride the equals and hashCode methods correctly. This
causes problems with WLS 6.1.
* There is a bug in their javax.resource.spi.ConnectionManager
implementation for non-managed uses of the adapter. Consequently, their
adapter cannot be used in a non-managed scenario.
* The javax.resource.cci.ConnectionFactory class does not support
the getConnection() method that does not take any arguments (it throws a
null pointer exception).
I am attaching the classes discussed above.
Cheers,
Chris
Torsten Friebe wrote:
> Hi,
>
> does anybody know where to get a trail version - if one exists - of IN-Q-MY
> application server or the resource adapter?
>
> Thanks, regards
> Torsten
>
> "Xavi" <[email protected]> schrieb im Newsbeitrag
> news:[email protected]...
>
>>Hi everybody,
>>
>>Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic
>>
> server
>
>>?
>>
>>It works well with INQMY server, but with BEA I'm getting a lot of
>>
> problems creating
>
>>the connections.
>>
>>Thanks in advance.
>>Xavi.
>>
>>
>
>
package wli.adapter.inqmy.sapr3.spi;
import java.io.Serializable;
import javax.resource.ResourceException;
import javax.resource.cci.Connection;
import javax.resource.cci.ConnectionSpec;
import javax.resource.spi.ConnectionManager;
import javax.resource.spi.ConnectionRequestInfo;
import javax.resource.spi.ManagedConnection;
import javax.resource.spi.ManagedConnectionFactory;
import com.inqmy.r3adapter.R3ConnectionSpec;
import com.inqmy.r3adapter.R3ManagedConnectionFactory;
* Extends the In-Q-My implementation to allow for getConnection() with no
* connection spec, i.e. use the default configured connection parameters.
public class R3ConnectionFactory
extends com.inqmy.r3adapter.R3ConnectionFactory
implements com.bea.connector.IProxyMarker {
private R3ConnectionSpec m_cspec;
public R3ConnectionFactory(ConnectionManager cm, R3ManagedConnectionFactory mcf)
throws ResourceException {
super(cm, mcf);
String strClientNumber = mcf.getClientNumber();
if (strClientNumber == null) {
throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+mcf);
String strLanguage = mcf.getLanguage();
if (strLanguage == null) {
throw new javax.resource.spi.IllegalStateException("Language not set for "+mcf);
String strUserName = mcf.getUserName();
if (strUserName == null) {
throw new javax.resource.spi.IllegalStateException("UserName not set for "+mcf);
String strPassword = mcf.getPassword();
if (strPassword == null) {
throw new javax.resource.spi.IllegalStateException("Password not set for "+mcf);
m_cspec = new R3ConnectionSpec(strClientNumber, strLanguage, strUserName, strPassword);
public Connection getConnection(ConnectionSpec connectionSpec)
throws ResourceException {
if (connectionSpec == null) connectionSpec = m_cspec;
return super.getConnection(connectionSpec);
package wli.adapter.inqmy.sapr3.spi;
import java.io.Serializable;
import javax.resource.ResourceException;
import javax.resource.spi.ConnectionManager;
import javax.resource.spi.ConnectionRequestInfo;
import javax.resource.spi.ManagedConnection;
import javax.resource.spi.ManagedConnectionFactory;
* Extends the In-Q-My implementation to over-ride the
* allocateConnection method to return a CCI connection vs. a ManagedConnection
public class R3DefaultConnectionManager
implements ConnectionManager, Serializable {
public R3DefaultConnectionManager() {}
public Object
allocateConnection(ManagedConnectionFactory mcf, ConnectionRequestInfo cri)
throws ResourceException {
ManagedConnection mc = mcf.createManagedConnection(null, cri);
return mc.getConnection(null, cri);
package wli.adapter.inqmy.sapr3.spi;
import javax.resource.spi.ConnectionManager;
import javax.resource.spi.ConnectionRequestInfo;
import javax.resource.spi.ManagedConnection;
import javax.security.auth.Subject;
* Extends the In-Q-My implementation to get around some problems encountered
* while running on WebLogic:
* <ul>
* <li>Must over-ride default implementation of equals and hashCode method</li>
* <li>Needed to provide my version of the CCI ConnectionFactory</li>
* <li>Needed to provide my version of the default ConnectionManager for the
* non-managed scenario use case</li>
* </ul>
public class R3ManagedConnectionFactory
extends com.inqmy.r3adapter.R3ManagedConnectionFactory {
private int m_iHashCode;
transient private com.inqmy.r3adapter.R3ConnectionRequestInfo t_cri = null;
public R3ManagedConnectionFactory() {
super();
java.rmi.server.UID uid = new java.rmi.server.UID();
m_iHashCode = uid.hashCode();
public Object createConnectionFactory() {
// need to install our own default connection manager because In-Q-My
// version causes a ClassCastException in CCI ConnectionFactory
// getConnection
return createConnectionFactory(new R3DefaultConnectionManager());
public ManagedConnection createManagedConnection(Subject subject, ConnectionRequestInfo cri)
throws javax.resource.ResourceException {
// need to check for null on the ConnectionRequestInfo object because the
// In-Q-My R3ManagedConnection ctor does not check for null
if (cri == null) cri = getDefaultConnectionRequestInfo();
return new com.inqmy.r3adapter.R3ManagedConnection(this, subject, cri);
public Object createConnectionFactory(ConnectionManager connectionManager) {
// need to supply a connection factory that can deal with getConnection
// that does not take a ConnectionSpec
try {
return new R3ConnectionFactory(connectionManager, this);
} catch (javax.resource.ResourceException re) {
re.printStackTrace();
throw new java.lang.IllegalStateException(re.getMessage());
com.inqmy.r3adapter.R3ConnectionRequestInfo getDefaultConnectionRequestInfo()
throws javax.resource.spi.IllegalStateException {
if (t_cri == null) {
String strClientNumber = this.getClientNumber();
if (strClientNumber == null) {
throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+this);
String strLanguage = this.getLanguage();
if (strLanguage == null) {
throw new javax.resource.spi.IllegalStateException("Language not set for "+this);
String strUserName = this.getUserName();
if (strUserName == null) {
throw new javax.resource.spi.IllegalStateException("UserName not set for "+this);
String strPassword = this.getPassword();
if (strPassword == null) {
throw new javax.resource.spi.IllegalStateException("Password not set for "+this);
t_cri = new com.inqmy.r3adapter.R3ConnectionRequestInfo(strClientNumber, strLanguage, strUserName, strPassword);
return t_cri;
public boolean equals(Object obj) {
if (obj == null) return false;
if (obj == this) return true;
if (!this.getClass().isInstance(obj)) return false;
R3ManagedConnectionFactory mcf = (R3ManagedConnectionFactory)obj;
return compare(getClientNumber(), mcf.getClientNumber()) &&
compare(getLanguage(), mcf.getLanguage()) &&
compare(getUserName(), mcf.getUserName()) &&
compare(getPassword(), mcf.getPassword()) &&
compare(getServerName(), mcf.getServerName()) &&
compare(getSystemNumber(), mcf.getSystemNumber());
protected final boolean compare(final Object obj1, final Object obj2) {
if (obj1 == obj2) return true;
if (obj1 != null) {
return obj1.equals(obj2);
} else {
if (obj2 == null) {
return true;
} else {
return false;
public int hashCode() { return m_iHashCode; }
-
Multiple EARs packaging the same resource adapter -- Weblogic Application S
Hello,
I had a question regarding JNDI and deploying multiple applications (EAR's) which package the same resource adapter running on Webloigc Application Server 9.1. I have an EAR file, ear1, which contains a resource adapter with connection factory with JNDI name say 'xyz' specified in the weblogic-ra.xml file. I have another EAR file, ear2, which again packages the same resource adapter with the same connection factory with JNDI name 'xyz'. Upon activating the 2nd EAR file, I get an exception 'javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.', as seen below:
<May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application 'JMS2JMS_eInsightweblogic2'.>
<May 8, 2006 10:29:27 AM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.AssertionError: Internal Error occurred, Assertion Failed: No Initial Context for Jndi: javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:217)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
Truncated. see log file for complete stacktrace
javax.naming.NoPermissionException: A Resource Adapter may only be accessed from within the same application from which it was deployed.
at weblogic.connector.outbound.RAOutboundManager.getConnectionFactory(RAOutboundManager.java:721)
at weblogic.connector.deploy.JNDIHandler.getConnectionFactory(JNDIHandler.java:1017)
at weblogic.connector.deploy.JNDIHandler.lookupObject(JNDIHandler.java:871)
at weblogic.connector.deploy.JNDIHandler.getObjectInstance(JNDIHandler.java:845)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
Truncated. see log file for complete stacktrace
It seems like the 2nd EAR is trying to go across and lookup the connection factory from the 1st EAR. Does weblogic bind the RA's connection factory jndi name in the global jndi and is not specific to each EAR? Is there some flag or switch I can turn on to make the JNDI specific to each EAR?
My weblogic deployment descriptor for the ra looks like the following:
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ra.xsd">
<jndi-name>JMS2JMS_eInsightDeployment4_stcbpelra</jndi-name>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>false</enable-global-access-to-classes>
<outbound-resource-adapter>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<connection-instance>
<b><jndi-name>BPELConnectionFactory</jndi-name></b>
<connection-properties>
<pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>10000</max-capacity>
<capacity-increment>1</capacity-increment>
<shrinking-enabled>true</shrinking-enabled>
<shrink-frequency-seconds>60</shrink-frequency-seconds>
<match-connections-supported>false</match-connections-supported>
</pool-params>
<properties>
<property>
<name>BPELConnectionFactory</name>
<value>BPELConnectionFactory</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>Thanks for the reply... in my case this would be done by the active synch process so no GUI form is required. I will be getting a list of application ID for the user by LDAP AS. One i get it i will have to parse it and get the list of application user id. I am passing those ID;s to a workflow where I am forming the resource name as you mentioned
for example:
If i get user1#user2#user3 from AS i am separating them based on # using split and getting 3 different user id;s
now i am forming a string with the resource name and passing it to the sub process in which i am checking out the user object, setting the user attributes and checking in the new view.
user1#LDAP
user2#LDAP|1
user3#LDAP|2
Problem ; When i run this user1 is getting created in LDAP but user2 and user3 are not. There entry is getting created in IDM.
When I open the IDM object I get a yellow triangle (warning) and if I open the user object and hit save button IDM creates the user account on the LDAP.
any help for further solving this problem would be appreciated.
Regards, -
Resource Adapter errors in WebLogic 10.3
Hi,
I'm getting ClassCastException from coherence 3.5.3 resource adapter in WebLogic 10.3.
I've already tried to install resource adapter as a separate deploy and inside ear file, but get same errors.
Has anybody already managed to use this adapter along with weblogic 10.3 ? The error occurs when I try to get a NamedCache object. The distributed cache named "cache" is up and running since I manage to get and put objects into cache by using NamedCache from CacheFactory (CacheFactory.getCache("cache")).
ctx = new InitialContext();
// the transaction manager from container
tx = (UserTransaction) ctx.lookup("java:comp/UserTransaction");
tx.begin();
adapter = new CacheAdapter(ctx, "tangosol.coherenceTx", CacheAdapter.CONCUR_PESSIMISTIC ,CacheAdapter.TRANSACTION_REPEATABLE_GET, 300);
NamedCache cache = adapter.getNamedCache("cache", getClass().getClassLoader());
cache.put(1, 11);
Integer estoqueGet = (Integer)cache.get(1);
2010-06-05 20:24:02.859/96.703 Oracle Coherence GE 3.5.3/465 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/
a
2010-06-05 20:24:02.969/96.813 Oracle Coherence GE 3.5.3/465 <Info> (thread=Cluster, member=n/a): Failed to satisfy the variance: allowed=16, actual=47
2010-06-05 20:24:02.969/96.813 Oracle Coherence GE 3.5.3/465 <Info> (thread=Cluster, member=n/a): Increasing allowable variance to 19
2010-06-05 20:24:03.344/97.188 Oracle Coherence GE 3.5.3/465 <Info> (thread=Cluster, member=n/a): This Member(Id=2, Timestamp=2010-06-05 20:24:03.078, Address=1
0.10.10.10:8089, MachineId=2570, Location=machine:ACCENTUR-1FAF0A,process:8036, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1) joined cluste
r "cluster:0xDDEB" with senior Member(Id=1, Timestamp=2010-06-05 20:23:06.562, Address=10.10.10.10:8088, MachineId=2570, Location=machine:ACCENTUR-1FAF0A,proces
s:6300, Role=CoherenceServer, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1)
2010-06-05 20:24:03.438/97.282 Oracle Coherence GE 3.5.3/465 <D5> (thread=Cluster, member=n/a): Member 1 joined Service Management with senior member 1
2010-06-05 20:24:03.438/97.282 Oracle Coherence GE 3.5.3/465 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistributedCache with senior member 1
2010-06-05 20:24:03.656/97.500 Oracle Coherence GE 3.5.3/465 <D5> (thread=Invocation:Management, member=2): Service Management joined the cluster with senior se
rvice member 1
2010-06-05 20:24:04.125/97.985 Oracle Coherence GE 3.5.3/465 <D5> (thread=TcpRingListener, member=2): TcpRing: connecting to member 1 using TcpSocket{State=STAT
E_OPEN, Socket=Socket[addr=/10.10.10.10,port=3748,localport=8089]}
2010-06-05 20:24:04.141/97.985 Oracle Coherence GE 3.5.3/465 <Info> (thread=[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)', memb
er=2): Loaded cache configuration from "zip:D:/Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/tmp/_WL_user/coherenceapp/v3byxq/war/WEB-
INF/lib/coherence.jar!/coherence-cache-config.xml"
2010-06-05 20:24:04.438/98.282 Oracle Coherence GE 3.5.3/465 <D5> (thread=DistributedCache, member=2): Service DistributedCache joined the cluster with senior s
ervice member 1
2010-06-05 20:24:04.453/98.297 Oracle Coherence GE 3.5.3/465 <D5> (thread=DistributedCache, member=2): Service DistributedCache: received ServiceConfigSync cont
aining 258 entries
2010-06-05 20:24:04.547/98.391 Oracle Coherence GE 3.5.3/465 <D4> (thread=DistributedCache, member=2): Asking member 1 for 128 primary partitions
2010-06-05 20:24:04.828/98.672 Oracle Coherence GE 3.5.3/465 <Error> (thread=DistributedCache, member=2): An exception (java.io.IOException) occurred reading Me
ssage Response Type=21 for Service=DistributedCache{Name=DistributedCache, State=(SERVICE_STARTED), LocalStorage=enabled, PartitionCount=257, BackupCount=1, Ass
ignedPartitions=0, BackupPartitions=0}
2010-06-05 20:24:04.828/98.672 Oracle Coherence GE 3.5.3/465 <Error> (thread=DistributedCache, member=2): Terminating DistributedCache due to unhandled exceptio
n: java.io.IOException
2010-06-05 20:24:04.828/98.672 Oracle Coherence GE 3.5.3/465 <Error> (thread=DistributedCache, member=2):
java.io.IOException: Class initialization failed: java.lang.ClassCastException: com.tangosol.run.xml.SimpleElement
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:1946)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2273)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2219)
at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:60)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
at com.tangosol.coherence.component.net.message.DistributedCacheResponse.read(DistributedCacheResponse.CDB:2)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:123)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Class: com.tangosol.run.xml.SimpleElement
ClassLoader: weblogic.utils.classloaders.ChangeAwareClassLoader@15fe77a finder: weblogic.utils.classloaders.CodeGenClassFinder@2a865b8 annotation: coherenceapp@
WebAppCoherence
ContextClassLoader: weblogic.utils.classloaders.ChangeAwareClassLoader@15fe77a finder: weblogic.utils.classloaders.CodeGenClassFinder@2a865b8 annotation: cohere
nceapp@WebAppCoherence
at com.tangosol.util.ExternalizableHelper.readExternalizableLite(ExternalizableHelper.java:1961)
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2273)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2219)
at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:60)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
at com.tangosol.coherence.component.net.message.DistributedCacheResponse.read(DistributedCacheResponse.CDB:2)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:123)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
2010-06-05 20:24:04.844/98.688 Oracle Coherence GE 3.5.3/465 <D5> (thread=DistributedCache, member=2): Service DistributedCache left the cluster
java.lang.RuntimeException: Failed to start Service "DistributedCache" (ServiceState=SERVICE_STOPPED)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:8)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:29)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:39)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache$Router(SafeCacheService.CDB:1)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache(SafeCacheService.CDB:46)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:878)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1088)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:304)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
at com.tangosol.coherence.ra.component.connector.resourceAdapter.cciAdapter.CacheAdapter$ManagedConnection$Connection$Interaction.execute(CacheAdapter.C
DB:35)
at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:329)
at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:271)
at ServletCoherence.doGet(ServletCoherence.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Exception: java.lang.RuntimeException: Failed to start Service "DistributedCache" (ServiceState=SERVICE_STOPPED)
java.lang.RuntimeException: Failed to start Service "DistributedCache" (ServiceState=SERVICE_STOPPED)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:8)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.poll(Grid.CDB:11)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:29)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.ensureCache(DistributedCache.CDB:39)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache$Router(SafeCacheService.CDB:1)
at com.tangosol.coherence.component.util.safeService.SafeCacheService.ensureCache(SafeCacheService.CDB:46)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:878)
at com.tangosol.net.DefaultConfigurableCacheFactory.configureCache(DefaultConfigurableCacheFactory.java:1088)
at com.tangosol.net.DefaultConfigurableCacheFactory.ensureCache(DefaultConfigurableCacheFactory.java:304)
at com.tangosol.net.CacheFactory.getCache(CacheFactory.java:735)
at com.tangosol.coherence.ra.component.connector.resourceAdapter.cciAdapter.CacheAdapter$ManagedConnection$Connection$Interaction.execute(CacheAdapter.C
DB:35)
at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:329)
at com.tangosol.run.jca.CacheAdapter.getNamedCache(CacheAdapter.java:271)
at ServletCoherence.doGet(ServletCoherence.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)The problem may be related to having more than one coherence.jar and tangosol.jar in the classpath. Can you verify that you only have one of those in the classpath?
/Christer -
WebLogic Server 10.0 MP1: Error in resource adapter deployment
When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
An error occurred during activation of changes, please see the log for details.
weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
java.util.logging.LoggingPermission.(java.lang.String)
The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
permission javax.management.MBeanTrustPermission "register";
permission java.util.logging.LoggingPermission "control";
When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
For me this seems to be a bug in WebLogic 10.0MP1.
Best,
ManfredRe: Installation error: Weblogic Server 10.0 MP2
-
WebSphere MQ resource adapter and Weblogic - how?
Hi,
has anybody managed to get the WebSphere MQ resource adapter to run with Weblogic 10.3 ?
(http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzaw.doc/uj40010_.htm)
I got it deployed, but it never triggers. I only made changes to the ra.xml, do I also need a weblogic-ra.xml?
Has anybody a sample for the WebSphere MQ resource adapter?
Thanks very much,
JuergenHere's an example resource adapter configuration you can use
* weblogic-ra.xml - http://pastie.org/294590
* note: you have to edit ra.xml manually to change transaction type from Local to XA, etc.
This configures:
* the resource adapter (needed for MDBs) to the jndi name wmq/Connector
* a queue for outbound messages to the jndi name wmq/Queue1
a connection factory for outbound messages to the jndi name wmq/ConnectionFactory
Here's an example MDB that uses the above adapter
* ejb-jar.xml - http://pastie.org/294594
* weblogic-ejb-jar.xml - http://pastie.org/294597
* note: useJNDI doesn't seem to work on WLS. Otherwise, you could setup the queue in your weblogic-ra.xml and then reference the jndi name in the ejb-jar.xml. This limitation clutters the ejb-jar.xml with implementation details of websphere, which are tricky to inject (deployment plan, xslt, etc.). That said, this does work.
* note: If you want consistent control of the amount of consumers you have on a queue, set the ejb-jar.xml activation-config maxPoolDepth == weblogic-ejb-jar.xml max-beans-in-free-pool
This configures:
* an mdb instance listening on a specific WMQ destination
I hope this helps. It is the result of may months of effort between Bea and IBM, and with me in the middle! ;)
Cheers,
-Adrian
Edited by: ferncam1 on Oct 17, 2008 5:31 AM
Maybe you are looking for
-
Nokia 808 gallery button not working whilst in cam...
Hi all Had my 808 for a week, and I have been delighted with it, in fact I had no issues with it until an hour ago! I was taking some pics of my kids when the screnen when black, it would still take photos but I cannot see anything on screen. This is
-
Restriction of S_ALR_87012172 business area wise
Report S_ALR_87012172 - Customer Balances in Local Currency is working fine. but how it can be restricted on business area wise in order to recoincile the same. anya
-
I have tried to submit a dissatisfaction report following your instructions from my invoice for the recent purchase of smart office 2. I can get no further as a report code keeps appearing saying too many http redirects so I can not get any further.
-
RAM Preview error: Ram Preview needs 2 or more frames to playback
Hi, I recently started getting error messages (saying the discussion's title) whenever I pressed "0" to RAM Preview my work. I've disabled multiprocessing, tried enabling/disabling all my footage and corresponding effects, but to no avail. It's a 5-s
-
I just purchased, downloaded and installed PSE 12. I am running Windows 7. Everything seems to be working fine. My question is this: Why are the titles in tlhe menu bar (task bar?) at the top so small? When you actually pull down the menu it is fine