Message EJB using Weblogic JMS Server

Hi,
I trying get some working logic about using JMS with weblogic. I have created a JMS Server instance with all the necessary Connection Factories and Destinations. I am able to connect to from a normal Java class, but i want to deploy a message driven ejb in weblogic and connect to the same JMS Server instance. When i deploy my EJB i get an error about unable to connect to the JMS Server in the weblogic.log . Could any please refer me to any resourcce that may help me.

          Thanks, i got it sorted out.
          Tom Barnes <[email protected]> wrote:
          >Unless you're descriptors make use of the weblogic extensions to specify
          >the jndi URL, make sure that the MDB and the JMS Server instance are
          >either
          >both located on the same WL server or are both in the same cluster.
          >
          >If this doesn't help, please post the stack trace for you're error
          >and attach your config.xml and MDB descriptor xml.
          >
          >Tom
          >
          >Riaan Minne wrote:
          >
          >> Hi,
          >>
          >> I trying get some working logic about using JMS with weblogic. I have
          >created a JMS Server instance with all the necessary Connection Factories
          >and Destinations. I am able to connect to from a normal Java class,
          >but i want to deploy a message driven ejb in weblogic and connect to
          >the same JMS Server instance. When i deploy my EJB i get an error about
          >unable to connect to the JMS Server in the weblogic.log . Could any
          >please refer me to any resourcce that may help me.
          >

Similar Messages

Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server

Hi,
I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
<Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
nect to the JMS destination: FMAContractOutboundQueue. The Error was:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
:weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
-Sreekanth

I recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
* The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
* The connection factory doesn't exist.
* The object in JNDI with the specified connection factory name isn't actually a connection factory.
* The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
Tom

Using WebLogic JMS Wrappers with Spring

Hi,
I was just wondering if anyone used WebLogic JMS wrappers with Spring?
I am using WebLogic configured to have Sonic as my Foreign JNDI Provider. Weblogic provide me with specific entries on the admin console to set information such as the JNDI name of the Sonic Connection Factory. If I specify this JNDI name in the Spring config, and call getConnection() then I will get back a new connection each time.
I don't want this, I want to cache the connection (as connections are expensive in Sonic). This is where the WebLogic JMS wrappers come in, they can handle the pooling for me but the only way I can see to use them is via a resource-ref. It is possible for Spring to get a handle onto these wrappers or should I use Spring's own pooling mechanism instead?
P.S. I've also asked this question on the Spring forum
Thanks for any help
Mandy

Maybe you have already tried the following:
<beans xmlns:jee="http://www.springframework.org/schema/jee" ... >
<jee:jndi-lookup id="connectionFactory" jndi-name="jms.ConnectionFactory">
<jee:environment>
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:7001
</jee:environment>
</jee:jndi-lookup>
</beans>
an alternative is to use the JNDI template
<beans ... >
<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
<prop key="java.naming.provider.url">t3://localhost:7001</prop>
</props>
</property>
</bean>
<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate" />
<property name="jndiName"><value>jms.ConnectionFactory</value></property>
</bean>
</beans>

Using Weblogic jms message id for unique id

Hi All,
We have a requirement to generate random unique id for each message processed by the application. We are planning to leverage weblogic jms message id for this purpose rather than building our own application logic for this purpose . Will there be any issue adopting this ? We think weblogic jms message id will be unique across the cluster as id is a hash of current timestamp + jms server name + wl server name + ?? .. is this correct ?
TIA
Atheek

Hi Atheek,
It depends on what are you planning to do with that id, as there are some gotchas on Weblogic's JMSMessageID generation.
I guess the msg id could be considered statiscaly unique as Tom says, but the msg id will change during the livecycle of your message, surprise! (yea, the JMS spec allows the JMS server to modify the msg ids).
So if you want to use that id to correlate messages id, or to group info related to one message, using JMSMessageID could be a problem.
You can consider to generate a UUID, using Java 1.5 support (java.util.UUID) or a external library (JUG http://jug.safehaus.org for instance), and attach that id as a JMSCorrelationId or a user defined property.
Hope this helps

Error occurred when use foreign Jms server[JMSClientExceptions:055142].

I want to use a foreign Jms server(Tibco EMS), after I have config the JNDI of foreign server,connectionfactory and destinations, the correct JNDI name can be find on the JNDI tree.
Then I deploy a demo mdb ear on the weblogic(version is 10.3),there's warnning tag on the ear application, and there is error message in the log:
<2011-1-10 上午10时15分07秒 CST> <Warning> <EJB> <BEA-010061> <The Message-Drive
n EJB: MDBDemo is unable to connect to the JMS destination: NotifyAlertAlertQueue. The Error was:
weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, Queue[notify.alert.alertQueue]>
NotifyAlertAlertQueue is the JNDI name of the destination defined on the weblogic console,and the same as ems jndi name for queue notify.alert.alertQueue.
It seems that the application has find the queue correctly, but why it throw that exception[JMSClientExceptions:055142]?
Thanks for any help.
Edited by: 826761 on 2011-1-9 下午6:40

I suspect that somehow your configuration is messed up and the MDB ended up using a WebLogic connection to access a TIBCO EMS destination.
Please make sure that your JMS server configuration maps a TIBCO connection factory jndi name to a jndi name in WebLogic server JNDI tree, a TIBCO destination jndi name to a jndi name in WebLogic server JNDI tree, and your MDB configuration refers to the jndi names in the WebLogic JNDI tree.
Regards.

Using Weblogic JMS for internal delivery channel

hi,
I want my B2B to talk to back-end application through Weblogic JMS queues. I have configured internal delivery channel for this. I am getting error message 'Max retry exceeded' in b2b_idc_transport.log
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) JMSReceiver.init() started ....
2008.09.24 at 12:09:53:713: B2BStarter thread: (DEBUG) Establishing JMS Connection.
2008.09.24 at 12:10:03:704: B2BStarter thread: (DEBUG) Establishing JMS Connection.
2008.09.24 at 12:15:03:428: B2BStarter thread: (ERROR) Max retry exceeded, closing everything
java.lang.Exception: Max retry exceeded
     at oracle.tip.transport.basic.jms.JMSMonitor.reconnect(JMSMonitor.java:833)
     at oracle.tip.transport.basic.JMSReceiver.init(JMSReceiver.java:333)
     at oracle.tip.transport.b2b.B2BTransport.init(B2BTransport.java:379)
     at oracle.tip.adapter.b2b.transport.AppTransportInterface.initialize(AppTransportInterface.java:282)
     at oracle.tip.adapter.b2b.engine.Engine.initialize(Engine.java:512)
     at oracle.tip.adapter.b2b.init.B2BServer.initialize(B2BServer.java:280)
     at oracle.tip.adapter.b2b.init.B2BStarter.startB2B(B2BStarter.java:297)
     at oracle.tip.adapter.b2b.init.B2BStarter.run(B2BStarter.java:143)
     at java.lang.Thread.run(Thread.java:534)
I have applied latest patch 7322333.
kindly let me know what is workaround for this? also, how can do debugging of this issue in B2B.
Thanks in advance.
Regards,
Vaibhav
Edited by: vaibs on Sep 26, 2008 12:15 AM

hi Sinkar,
Thanks for reply. I have checked connectivity from b2b server to weblogic server, using java stub. Stub can connect to the Q successfully.
here is my b2b.log
2008.09.24 at 12:09:49:233: main: B2B - (DEBUG) B2B initialize
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) This is Main thread executing..
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start
2008.09.24 at 12:09:49:233: Main thread: B2B - (DEBUG) B2B start - context started
2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG) B2BStarter - This is B2BStarter thread executing..
2008.09.24 at 12:09:49:233: B2BStarter thread: B2B - (DEBUG)
Maximum Heap Size = 530907136
Memory Allocated = 8323072
Free Memory = 842560
2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) ExecutionContextManager initialization is done
2008.09.24 at 12:09:50:544: B2BStarter thread: BusinessLogicLayer - (INFORMATION) User's maxCachedSessions is set to 0
2008.09.24 at 12:09:50:560: B2BStarter thread: B2B - (DEBUG) B2BStarter - Context Initialized
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Start B2B
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - Starting B2B
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - configuration oained
2008.09.24 at 12:09:51:762: B2BStarter thread: B2B - (DEBUG) B2BStarter - clear global cache
2008.09.24 at 12:09:51:793: B2BStarter thread: B2B - (DEBUG) XEngine not running. So no need to clear cached objects inside XEngine.
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [0] HL7 over MLLP Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [1] EDI X12 over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [2] Custom Document over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [3] EDI EDIFACT over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [4] RosettaNet over RNIF
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [5] EDI X12 over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [6] Custom Document over MLLP Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [7] Custom Document over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [8] EDI EDIFACT over AS1
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [9] HL7 over Generic Exchange
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (NIFORMATION) Repository:print: [10] Custom Document over Internet
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [11] Custom Document over ebMS
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [12] EDI X12 over Internet
2008.09.24 at 12:09:51:824: B2BStarter thread: B2B - (INFORMATION) Repository:print: [13] EDI EDIFACT over Internet
2008.09.24 at 12:09:51:981: B2BStarter thread: B2B - (DEBUG) Repository:constructCertSQL SELECT cert.ID, cert.CLASSTYPE FROM TIP_Certificate_ra cert, TIP_Party_ra party, TIP_DocumentExchange_ra docex WHERE cert.ID = docex.signingcredential AND cert.tradingpartner = party.ID AND party.ishosted != 'Y'
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Enter
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Envelope
2008.09.24 at 12:09:52:355: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:header name: ebXML SOAP Message Header
2008.09.24 at 12:09:52:386: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:initialize Exit
2008.09.24 at 12:09:52:402: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Enter
2008.09.24 at 12:09:52:433: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:initialize Exit
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Enter
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize resetListener = true
2008.09.24 at 12:09:52:511: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initdcx = true
2008.09.24 at 12:09:52:543: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize TPAProcessor
2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Clear TPA Cache
2008.09.24 at 12:09:52:558: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize DataContext. Pool Size 0
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Treat Response as Request = false
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:initialize Exit
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize initialize Transport
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Initialize Transport Logger.
2008.09.24 at 12:09:52:574: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:initialize Transport LogLevel = STATUS
2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) Repository:getDeliveryEndPointList: Putting http://localhost
2008.09.24 at 12:09:52:605: B2BStarter thread: B2B - (INFORMATION) oracle.tip.adapter.b2b.transport.TransportInterface:initialize: Props: http://localhost port = 7777
PROTOCOL_ENDPOINT = null
2008.09.24 at 12:09:52:636: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [Wholesale_Transport_Server < http > < Wholesale >]
2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize Initialize AppTransport Logger.
2008.09.24 at 12:09:53:682: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize AppTransport LogLevel = WARNING
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (INFORMATION) Repository:getInternalDeliveryEndPointList: Putting jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize main Endpoint loop jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize looping through transport Endpoint: jms://[email protected]
2008.09.24 at 12:09:53:698: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.AppTransportInterface:initialize add jms transport Endpoint: jms://[email protected] {Destination Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.destination_password=weblogic, Connection Factory Location=weblogic.jws.jms.QueueConnectionFactory, jms.receiver.jndi_connection_factory_location=weblogic.jws.jms.QueueConnectionFactory, isTopic=false, Message Type=bytes, jms.receiver.is_topic=false, jms.receiver.factory_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, transport_callout_waittime=30, jms.receiver.jndi_destination_provider_properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.polling_interval=10, polling_interval=10, Factory Provider Properties=java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://10.76.168.156:7010, jms.receiver.jndi_destination_location=[email protected], jms.receiver.destination_username=weblogic}
2008.09.24 at 12:09:53:713: B2BStarter thread: B2B - (DEBUG) initialize TransportReceiver: [WLIOutbound_TServer < jms > < Wholesale >]
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2008.09.24 at 12:35:52:276: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2008.09.24 at 12:35:52:276: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
2008.09.24 at 12:35:52:884: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize Enter
2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run initialize B2BListen turned off, will not listen on IP_OUT_QUEUE for messages
2008.09.24 at 12:35:53:087: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run start listening on message
Thanks,
Vaibhav
Edited by: vaibs on Sep 28, 2008 3:20 AM

Web services with Jdeveloper using weblogic as server

Hi,
I try to test creating PL/SQL web services by using a connection hosted by weblogic server instead of OC4J. The problem is what I try to publish a package of the database in the second stage when it asks for the connection to use, in the list I don't found the connection I create to weblogic . It presents as choice only connections used the server OC4J.
I do not Know if it is possible to publish a package as web service by using weblogic server connection, and how to do it.
can anyone help me please .
Nawal

Web services can only be published to BEA if you install Apache SOAP on BEA and use the Apache SOAP option of JDeveloper. The J2EE Web Services implementation framework is specific to Oracle9iAS.
The PL/SQL Web Services server implementation is based on the J2EE Web Services option and as a result is not really portable to BEA.
To publish a PL/SQL Web service on BEA with JDeveloper you would have to write the Java wrapper code to invoke the stored procedure using standard JDBC and then publish that Java class as a Web service using Apache SOAP. Then if you had Apache SOAP installed on BEA you would be set.
Portability of Web services implementations is a big feature coming with JAX-RPC - currently what most vendors have is interoperability between implementations because of things like SOAPBuilders and WS-I. When JAX-RPC becomes part of J2EE 1.4 roughly in June and vendors start putting out implementations on it you should get closer to portability.
In the meantime, the easiest way to get portability is to use the same SOAP server on both servers - Apache SOAP is a good example.
Hope this helps.
Mike

Processing large message payload with weblogic JMS

Hi,
I have a requirement in my project to process 50MB-500MG-1GB file using the JMS queue.
We could able to process 50MB payload but it's talking almost 2-3min to post the message and 2-4min to consume the message. Are there any configurable parameters available to fine tune the JMS queue to handle large payload? or is there any limitation on the size of the queue to process ?
Please advise.
Thanks,
Sri

There is a way to defer large messages from the rest and process them using a job in a specific queue.
Please check this configuration :
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm</a><a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/14/8024">Message Selection Filter</a>
in this path:
Under Runtime - > Integration engin ->
Prioritized Message Processing
Queues for Prioritized Message
Good luck
Nimrod

Creating new domain using weblogic app server V 7.0

Hi,
I've installed Weblogic Server V7 (beta) and facing a problem. Here is it:
What I want to do
=================
I want to create a new domain parallel to mydomain in weblogic application server
V 7.0 beta.
What are the steps taken
========================
(1) Started "myserver". (2)Opened browser and go to localhost:7001/console. (3)
logged in into the server using default username and password "installadministrator".
(4) Right click on mydomain in the left pane and click on "Create or edit other
domains". (5) entered new domain name and new console contex path, accept other
default values. (6) Apply it.
Problem
=======
(1) The new domain is not being shown in the left pane. (2) If I restart myserver,
it is not started and giving error :
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000349> <Not all the
ListenPort(s) started properly.>
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
The WebLogic Server did not start up properly. Reason: Fatal initialization exception
(3) No directory structure is being created parallel to myserver, and moreover
it is rewriting bea\user_domains\mydomain\config.xml file.
Please help.
Thanks and regards,
Sarmila

Hi,
I've installed Weblogic Server V7 (beta) and facing a problem. Here is it:
What I want to do
=================
I want to create a new domain parallel to mydomain in weblogic application server
V 7.0 beta.
What are the steps taken
========================
(1) Started "myserver". (2)Opened browser and go to localhost:7001/console. (3)
logged in into the server using default username and password "installadministrator".
(4) Right click on mydomain in the left pane and click on "Create or edit other
domains". (5) entered new domain name and new console contex path, accept other
default values. (6) Apply it.
Problem
=======
(1) The new domain is not being shown in the left pane. (2) If I restart myserver,
it is not started and giving error :
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000349> <Not all the
ListenPort(s) started properly.>
<Mar 21, 2002 5:35:12 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
The WebLogic Server did not start up properly. Reason: Fatal initialization exception
(3) No directory structure is being created parallel to myserver, and moreover
it is rewriting bea\user_domains\mydomain\config.xml file.
Please help.
Thanks and regards,
Sarmila

Error when trying to enqueue message on to weblogic JMS queue

Hi,
I have developed a BPEL process to enqueue message on to a JMS queue in weblogic 10.3.1.BPEL process manager version is 10.1.3.4. I have referred the Oracle note 549016.1 for configuring the Jms adapter for BEA Weblogic JMS Provider.
In the invoke activity, I am getting the following error:
"Missing class: weblogic.security.acl.UserInfo
Dependent class: weblogic.jndi.WLInitialContextFactory
Loader: JmsAdapter:0.0.0
Code-Source: /D:/product/10.1.3.1/orasoa/j2ee/oc4j_soa/connectors/JmsAdapter/JmsAdapter/weblogic.jar
Configuration: <code-source> in D:\product\10.1.3.1\orasoa\j2ee\oc4j_soa\connectors\JmsAdapter\JmsAdapter
The missing class is not available from any code-source or loader in the system."
I could not find a resolution. Please provide your inputs.
Thanks.
John

Could be this, if the above fix was by generating a wlfull client jar:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/jarbuilder.htm#BABCGHFH
Edited by: atheek1 on Jul 28, 2010 9:39 PM

Help !! how to redeploy only an ejb using weblogic.Deployer ?

Hi everyone, how to redeploy only one ejb (not the entire application) using weblogic.Deployer ? I executed the following command and getting wiered error !!! :
java weblogic.Deployer -adminurl http://myadmin:7000 -username system -password weblogic -name myApp.ear -activate -targets testEJB.jar@jytServer -source myApp.ear
I am getting the following error :
weblogic.management.ApplicationException:
[J2EE:160043]Missing deployment descriptor "META-INF/application.xml" at myApp.ear".
The ear file very much contains the application.xml under META-INF directory and in the application.xml, there is an entry for myBean.jar.
However if i try the following command, it will redeploy the EJB but it will deploy it as a separate application :
java weblogic.Deployer -adminurl http://myadmin:10720 -username system -password weblogic -targets jytServer deploy testEJB.jar
But I want to redeploly it as a part of .ear application.
I would highly appreicate your help. (assume that admin console access is denied and i will have to use weblogic.Deployer to redeploy).
thanks,
jyothi

Where do I specify the order of deployment? I have 2 EJB jar files and Web module, the order need to be Web module first, 2 EJB then EAR. In WebSphere it is defined in Deployment.xml file, where do I define Deployment.xml in WebLogic

How to use external JMS server.

Hi,
I am working with JMS adapter. we have installed BPEL 10.1.3 .1 in one system and in another system we have installed Oracle Application server. Please provide the configuration steps to connect to this external JMS server.

Hi,
take a look at
http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28994/adptr_jms.htm#BABJCCHI
You have to specify ormi://remotehost.domain.com:23795

Warning message when starting Weblogic BPM server in SOA Suite 11G

Hi There,
I understand that most of the warning message we can ignore it but why at first the warning is generated? Anyone can delighted me for this warnings, I don't want this to be show in production mode because of the production policy from most of the clients.
Below are some of the warning message that shows in my Weblogic with BPM.
<Warning> <Connector> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486532106> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566020> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.load(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566036> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.unload(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567018> <BEA-010001> <While deploying EJB 'FacadeFinderBean', class oracle.soa.management.internal.ejb.FacadeFinderBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567034> <BEA-010001> <While deploying EJB 'SOATestBean', class oracle.soa.management.internal.ejb.SOATestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceEx was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.SOADirectInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.Invoker was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567736> <BEA-010001> <While deploying EJB 'ContextAwareBean', class oracle.integration.platform.ejb.ContextAware was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569358> <BEA-015036> <In the EJB MessageDispatcherBean(Application: soa-infra, EJBComponent: sdpmessagingclient-ejb.jar), the value for the activation config property 'connectionFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFactory';>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569499> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarter was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTest was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtility was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <J2EE> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486592774> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application BPMComposer is not versioned.>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>

Hi There,
I understand that most of the warning message we can ignore it but why at first the warning is generated? Anyone can delighted me for this warnings, I don't want this to be show in production mode because of the production policy from most of the clients.
Below are some of the warning message that shows in my Weblogic with BPM.
<Warning> <Connector> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486532106> <BEA-190110> <Resource Adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance/operation of WebLogic Server.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566020> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.load(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486566036> <BEA-012035> <The Remote interface method: 'public abstract void oracle.bpm.analytics.measurement.metadata.IMeasurementMetadataService.unload(oracle.fabric.composite.model.ComponentModel)' in EJB 'MeasurementMetadataService' contains a parameter of type: 'oracle.fabric.composite.model.ComponentModel' which is not Serializable. Though the EJB 'MeasurementMetadataService' has call-by-reference set to false, this parameter is not Serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is Serializable.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567018> <BEA-010001> <While deploying EJB 'FacadeFinderBean', class oracle.soa.management.internal.ejb.FacadeFinderBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567034> <BEA-010001> <While deploying EJB 'SOATestBean', class oracle.soa.management.internal.ejb.SOATestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.SOAServiceInvokerEJB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOAServiceInvokerEJB', class oracle.integration.platform.blocks.sdox.ejb.api.SOAServiceInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'CompositeMetadataServiceBean', class oracle.integration.platform.blocks.cmds.CompositeMetadataServiceEx was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.SOADirectInvokerBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567720> <BEA-010001> <While deploying EJB 'SOADirectInvokerBean', class oracle.integration.platform.blocks.direct.Invoker was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486567736> <BEA-010001> <While deploying EJB 'ContextAwareBean', class oracle.integration.platform.ejb.ContextAware was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569358> <BEA-015036> <In the EJB MessageDispatcherBean(Application: soa-infra, EJBComponent: sdpmessagingclient-ejb.jar), the value for the activation config property 'connectionFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFactory';>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569499> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarter was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'B2BStarterBeanWLS', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BStarterLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569514> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestBean was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTestHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'oracle.tip.b2b.test.runtime.ServerTestBean', class oracle.tip.b2b.test.runtime.ServerTest was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569530> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtility was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocalHome was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <EJB> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486569546> <BEA-010001> <While deploying EJB 'B2BUtilityBean', class oracle.tip.b2b.j2ee.ejb.interfaces.IB2BUtilityLocal was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Warning> <J2EE> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1367486592774> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application BPMComposer is not versioned.>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>
<Warning> <WorkManager> <server1> <BPM_MS1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1367486651383> <BEA-002919> <Unable to find a WorkManager with name wm/B2BWorkManager. Dispatch policy wm/B2BWorkManager will map to the default WorkManager for the application soa-infra>

Getting the below error while using the JMS server.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

[EJB:015001] error while deploying an ejb on weblogic app server

Hi,
I'm trying to deploy an ear which has lot of modules and it is failing for one of the ejb module. The exception is as follows:
<Mar 22, 2011 7:47:01 PM GMT+05:30> <Error> <Deployer> <WL-149265> <Failure occurred in the execution of deployment request with ID '1300803398704' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
Error processing annotations: .'
weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
Error processing annotations: .
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     Truncated. see log file for complete stacktrace
>
<Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149004> <Failures were detected while initiating deploy task for application 'ear'.>
<Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
Error processing annotations: .
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
     Truncated. see log file for complete stacktrace
>
There are two scenarios one of which is working and the other is not. The details are below:
Scenario 1: (Working)
There is an ejb module in the ear (say ModA) which has two session beans (SessionA and SessionB having Remote interfcaes RemoteIntA and RemoteIntB).
There is another ejb module in the ear (say ModB) which has few more session beans.
Now I want to add an ejb which will extend from SessionA.
So, I did following changes:
i. added a remote interface in ModB - RemoteIntPA implements RemoteIntA
ii. added session bean SessionPA extends SessionA implements RemoteIntPA
iii. added ejb related annotations in SessionPA and removed the annotations from SessionA (i.e., SessionA is just a normal class by itself)
Now in the application.xml I declare both modules (ModA and ModB) as ejb modules.
I deploy the application everything works fine.
Scenario 2: (Not Working)
For some reason, I didn't required SessionB in ModA (which was the only ejb bean left in that module as SessionA was converted to normal java class). So I removed SessionB and RemoteIntB.
Now as there are no ejb beans in ModA, I cannot define this as ejb module in application.xml and hence I defined it as java module.
Now if I deploy the same application, I get the exception mentioned above.
I think it has to do with the classpath issue. But how is that the classpath issue is arising when I declaring a module as java and not when I declare it as ejb. I have this module in classpath of ModB. So it doesn't matter what type of module it is.
Am I missing something?
Please help me in this regards.

java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
The JAR with the class trivnet/service/svams/SVAMService is not in the classpath.

Message EJB using Weblogic JMS Server

Similar Messages

Maybe you are looking for