BEA - 010061 InvalidDestinationException
Environment:
Sun Solaris
BEA 8.1 SP2 (direct upgrade to SP2, never used SP1 on this machine)
Websphere MQ 5.3
Startup class defined MQConnectionFactory and MQQueue in JNDI, as per BEA white-paper.
MDB references this queue and simply prints the message content to console.
At Server Startup the startup class runs OK.
When the MDB is deployed it reports the error below.
<Jul 29, 2004 9:38:02 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-DrivenEJB: OscarMessageReceiverBean is unable to connect to the JMS destination: OscarM
QReceiverQueue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: OscarMQReceiverQueue could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is cor
rect, and the JMS destination has been deployed.>
Native Queue works for get and put.
JMS Queue access from outside the BEA environment works for get and put.
Within the BEA managed-server the objects defined in JNDI are also OK, I know
this because I changed the startup class to test the newly defined ConnectionFactory
and Queue from BEA's JNDI tree to read the queue contents, which all worked fine.
Exactly the same application and startup class worked fine with BEA 7.0 SP4 and MQ 5.3 - I copied the "start" script and classes from the old directory to the new one and have always had this problem.
I have opened a ticket with BEA, but they are researching this. I have found quite a few hits on this error, all pertaining to weblogic-ejb-jar.xml, however I have modeled the documentation. I am not using Workshop.
HELP!!!
As Greg mentioned, one thing that might help is deferring start of the MDB. There is an application descriptor setting just for this purpose - see the 8.1 EJB MDB docs:
start-mdbs-with-application
http://edocs.bea.com/wls/docs81/ejb/message_beans.html#1162449
Does the MDB eventually connect?
Tom Barnes, BEA
FYI: Very likely, the "startup" class method for integrating MDBs is no longer needed. This is due to new integration features built into 8.1 - which simplify things. There are some notes on the topic that I've posted fairly frequently to this newsgroup, search for "MQ+tom", and note that the EJB MDB docs now delve into this issue in detail:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html#1156059
Similar Messages
-
BEA-010061 + BEA-010096 JCaps queue set up via annotations
Hi,
I was trying to set up jcaps queue but unable to do so. Have created a wl jms queue and it works.Was trying to port over the configuration from the xmls to annotations.
Spec: WL v 10
xmls:
ejb.xml:
<message-driven>
<ejb-name>xxxBean</ejb-name>
<ejb-class>xxxClass</ejb-class>
<transaction-type>Bean</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
</activation-config>
<resource-ref>
<res-ref-name>jms/SeebeyondFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<res-ref-name>jms/QCF</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</message-driven>
weblogic.ejb.xml:
<weblogic-enterprise-bean>
<ejb-name>xxxBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>SeeBeyond.Queues.TestQ</destination-jndi-name>
<connection-factory-jndi-name>SeeBeyond.QueueConnectionFactories.QueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<resource-description>
<res-ref-name>jms/SeebeyondFactory</res-ref-name>
<jndi-name>SeeBeyond.QueueConnectionFactories.QueueConnectionFactory</jndi-name>
</resource-description>
<resource-description>
<res-ref-name>jms/QCF</res-ref-name>
<jndi-name>javax.jms.QueueConnectionFactory</jndi-name>
</resource-description>
</weblogic-enterprise-bean>
Code:
@MessageDriven(mappedName = "SeeBeyond.Queues.TestQ", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName="connectionFactoryJndiName",propertyValue="SeeBeyond.QueueConnectionFactories.QueueConnectionFactory"),
@ActivationConfigProperty(propertyName="destinationJndiName", propertyValue="Queues.TestQ"),
@ActivationConfigProperty(propertyName="destinationName", propertyValue="Queues.TestQ")
Error:
<Oct 17, 2011 10:19:29 AM SGT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:xxxMDB is unable to connect to the JMS destination: SeeBeyond.Queues.TestQ. The Error was:
weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, Queue[Queue.TestQ]>
<Oct 17, 2011 10:19:39 AM SGT> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: xxxMDB is unable to connect to the JMS destination or bind to JCA
resource adapter: SeeBeyond.Queues.TestQ. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds.
This log message will repeat every 600 seconds until the condition clears.>
What should be the right annotation? Thanks.Hi,
I was trying to set up jcaps queue but unable to do so. Have created a wl jms queue and it works.Was trying to port over the configuration from the xmls to annotations.
Spec: WL v 10
xmls:
ejb.xml:
<message-driven>
<ejb-name>xxxBean</ejb-name>
<ejb-class>xxxClass</ejb-class>
<transaction-type>Bean</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
</activation-config>
<resource-ref>
<res-ref-name>jms/SeebeyondFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<res-ref-name>jms/QCF</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</message-driven>
weblogic.ejb.xml:
<weblogic-enterprise-bean>
<ejb-name>xxxBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>SeeBeyond.Queues.TestQ</destination-jndi-name>
<connection-factory-jndi-name>SeeBeyond.QueueConnectionFactories.QueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<resource-description>
<res-ref-name>jms/SeebeyondFactory</res-ref-name>
<jndi-name>SeeBeyond.QueueConnectionFactories.QueueConnectionFactory</jndi-name>
</resource-description>
<resource-description>
<res-ref-name>jms/QCF</res-ref-name>
<jndi-name>javax.jms.QueueConnectionFactory</jndi-name>
</resource-description>
</weblogic-enterprise-bean>
Code:
@MessageDriven(mappedName = "SeeBeyond.Queues.TestQ", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName="connectionFactoryJndiName",propertyValue="SeeBeyond.QueueConnectionFactories.QueueConnectionFactory"),
@ActivationConfigProperty(propertyName="destinationJndiName", propertyValue="Queues.TestQ"),
@ActivationConfigProperty(propertyName="destinationName", propertyValue="Queues.TestQ")
Error:
<Oct 17, 2011 10:19:29 AM SGT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB:xxxMDB is unable to connect to the JMS destination: SeeBeyond.Queues.TestQ. The Error was:
weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, Queue[Queue.TestQ]>
<Oct 17, 2011 10:19:39 AM SGT> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: xxxMDB is unable to connect to the JMS destination or bind to JCA
resource adapter: SeeBeyond.Queues.TestQ. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds.
This log message will repeat every 600 seconds until the condition clears.>
What should be the right annotation? Thanks. -
Problems setting up Weblogic Server 9.2 with Oracle AQ
We are in the process of upgrading from WLS81 to WLS92 and I'm currently trying to set up the environment. We have applications communicating with 3 different JMS-servers; Sonic, WMQ and Oracle AQ. For both Sonic and WMQ the connection seem to work fine. We get an active application, and the beans connecting to queues on those servers reports as 'connected'.
For Oracle AQ I must be doing something wrong, but I can't for the life of me figure out what it is.
Our setup is as follows:
We have a domain-scoped startup class that binds the AQ-queues and a custom QueueConnectionFactory to the WL default context. Giving them a name like aqadapter-AQ_ARE_PING.
We have defined a System Resource, within which we have defined AQ as a Foreign Server. Within this foreign server we have each queue mapped to the queue-names bound through the Startup class. Likewise we have a qcf mapped to the qcf bound through the startup class.
The application contains message-driven beans which are supposed to be listening to the AQ-queues. In weblogic-ejb-jar.xml each target queue is mapped within each bean to the same name mapped within the Foreign Server element.
All this results in MDB's that report as 're-connecting' and 'initializing' and the following message in Server1.stdout for each MDB:
<Mar 28, 2007 4:27:58 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ARE_Ping is unable to connect to the JMS destination: AQ_ARE_PING. The Error was:
javax.jms.InvalidDestinationException: JMS-125: Invalid Queue specified>
Any ideas what I am doing wrong? It seems to me that all the settings are as similar as the way they are set up on WLS81 as we could get them.
Anyone reading this that have done this before? Setting up WLS92 or WLS90 to interact with Oracle AQ?
Regards,
Frode Laukus
Edited by laukus at 03/28/2007 7:53 AMHi Frode
Have you managed to find a solution to this issue?
We are trying to do something very similar and encountering all sorts of issues.
Are you using the DIPSStartup classes to register your queues & qcf with the WL JNDI? I haven't managed to get these classes to work with the AQJmsSession in the latest release of the aqapi13.jar files.
Hopefully we can sort out a workable solution between us :)
Andy -
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:40I 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. -
Invalid Destinatinon Exception--Foreign Destination
Hello,
I am using Weblogic Server 8.1 and OpenJMS (openjms.sourceforge.net) as my JMS
server. I have configured a Foreign JMS server, a Foreign TopicConnectionFactory,
and a Foreign Destination. I have an MDB that is configured to find the local
jndi topic name that points to the foreig jndi topic destination. When I deploy
my application with the MDBs, the Foreign JMS server is found, but I am getting
and InvalidDestinationException. The topic type is specified as a javax.jms.Topic
in the MDB's deployment descriptor. I also noticed that in the error output,
the topic name appears as <topicName>-true.
Has anyone encountered this problem before and, if so, do you have a suggested
workaround? It appears that Weblogic is having a conflict with the openJMS topic
and I am assuming that this could be a "type" issue.
Thanks,
Chris
There is likely a configuration error. Did you remember
to create a foreign connection factory wrapper as well? Did you
specify the jndi name for this factory in the weblogic descriptor
for the MDB? Otherwise the MDB will use a WL connection factory,
which will generate a WL client instead of the desired foreign
vendor client.
If this doesn't help, please post your config.xml and
your weblogic-ejb-jar.xml
chris wrote:
> sorry!
>
> the error is listed below. i have two MDBs, each subscribing to a particular
> topic on a foreign JMS server (in this case, an OpenJMS instance). i have attached
> my ejb-jar deployment descriptor as well. please let me know what other info
> you might need, if any.
>
> thanks!
>
>
> <Aug 26, 2003 4:07:36 PM EDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
> EJB: SensorDataMessageDrivenBean is unable to connect to the JMS destination:
> openJMSTestSensorTopic. Connection failed after 548 attempts. The MDB will attempt
> to reconnect every 10 seconds. This log message will repeat every 600 seconds
> until the condition clears.>
> <Aug 26, 2003 4:07:36 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
> EJB: SensorDataMessageDrivenBean is unable to connect to the JMS destination:
> openJMSTestSensorTopic. The Error was:
> weblogic.jms.common.InvalidDestinationException: Foreign destination, christine-true
> weblogic.jms.common.InvalidDestinationException: Foreign destination, christine-true
> at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
> at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
> at weblogic.jms.client.JMSSession.createDurableSubscriber(JMSSession.java:1415)
> at weblogic.ejb20.internal.JMSConnectionPoller.setUpTopicSessions(JMSConnectionPoller.java:1451)
> at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1823)
> at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
> at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
> at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
> at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
> at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
> at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
> <Aug 26, 2003 4:07:36 PM EDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
> EJB: TrackDataMessageDrivenBean is unable to connect to the JMS destination: openJMSTestTrackTopic.
> Connection failed after 548 attempts. The MDB will attempt to reconnect every
> 10 seconds. This log message will repeat every 600 seconds until the condition
> clears.>
> <Aug 26, 2003 4:07:36 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
> EJB: TrackDataMessageDrivenBean is unable to connect to the JMS destination: openJMSTestTrackTopic.
> The Error was:
> weblogic.jms.common.InvalidDestinationException: Foreign destination, test-true
> weblogic.jms.common.InvalidDestinationException: Foreign destination, test-true
> at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
> at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
> at weblogic.jms.client.JMSSession.createDurableSubscriber(JMSSession.java:1415)
> at weblogic.ejb20.internal.JMSConnectionPoller.setUpTopicSessions(JMSConnectionPoller.java:1451)
> at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1823)
> at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
> at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
> at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
> at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
> at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
> at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
>
>
> Tom Barnes <[email protected]> wrote:
>
>>Please post the full error message and stack trace.
>>
>>chris wrote:
>>
>>
>>>Hello,
>>>I am using Weblogic Server 8.1 and OpenJMS (openjms.sourceforge.net)
>>
>>as my JMS
>>
>>>server. I have configured a Foreign JMS server, a Foreign TopicConnectionFactory,
>>>and a Foreign Destination. I have an MDB that is configured to find
>>
>>the local
>>
>>>jndi topic name that points to the foreig jndi topic destination.
>>
>>When I deploy
>>
>>>my application with the MDBs, the Foreign JMS server is found, but
>>
>>I am getting
>>
>>>and InvalidDestinationException. The topic type is specified as a
>>
>>javax.jms.Topic
>>
>>>in the MDB's deployment descriptor. I also noticed that in the error
>>
>>output,
>>
>>>the topic name appears as <topicName>-true.
>>>
>>>Has anyone encountered this problem before and, if so, do you have
>>
>>a suggested
>>
>>>workaround? It appears that Weblogic is having a conflict with the
>>
>>openJMS topic
>>
>>>and I am assuming that this could be a "type" issue.
>>>
>>>
>>>Thanks,
>>>Chris
>>
>>
>>------------------------------------------------------------------------
>>
>><?xml version="1.0"?>
>><!-- edited with XMLSPY v5 rel. 4 U (http://www.xmlspy.com) by christine (osec) -->
>><!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
>>'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
>><ejb-jar>
>> <enterprise-beans>
>> <session>
>> <display-name>InputManager</display-name>
>> <ejb-name>InputManagerSessionBean</ejb-name>
>> <home>com.osec.lsas.demo.common.InputManagerSessionHome</home>
>> <remote>com.osec.lsas.demo.common.InputManagerSession</remote>
>> <ejb-class>com.osec.lsas.demo.common.InputManagerSessionBean</ejb-class>
>> <session-type>Stateless</session-type>
>> <transaction-type>Container</transaction-type>
>> </session>
>> <entity>
>> <display-name>UserEntityBean</display-name>
>> <ejb-name>UserBean</ejb-name>
>> <local-home>com.osec.lsas.demo.domain.UserLocalHome</local-home>
>> <local>com.osec.lsas.demo.domain.UserLocal</local>
>> <ejb-class>com.osec.lsas.demo.domain.UserBean</ejb-class>
>> <persistence-type>Container</persistence-type>
>> <prim-key-class>com.osec.lsas.demo.domain.UserPK</prim-key-class>
>> <reentrant>False</reentrant>
>> <cmp-version>2.x</cmp-version>
>> <abstract-schema-name>UserBean</abstract-schema-name>
>> <cmp-field>
>> <field-name>userID</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>firstName</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>lastName</field-name>
>> </cmp-field>
>> <query>
>> <query-method>
>> <method-name>findByUserID</method-name>
>> <method-params>
>> <method-param>java.lang.String</method-param>
>> </method-params>
>> </query-method>
>> <ejb-ql>SELECT OBJECT(o) FROM UserBean AS o WHERE o.userID = ?1</ejb-ql>
>> </query>
>> </entity>
>> <entity>
>> <display-name>SalEntityBean</display-name>
>> <ejb-name>SalBean</ejb-name>
>> <local-home>com.osec.lsas.demo.domain.SalLocalHome</local-home>
>> <local>com.osec.lsas.demo.domain.SalLocal</local>
>> <ejb-class>com.osec.lsas.demo.domain.SalBean</ejb-class>
>> <persistence-type>Container</persistence-type>
>> <prim-key-class>com.osec.lsas.demo.domain.SalPK</prim-key-class>
>> <reentrant>False</reentrant>
>> <cmp-version>2.x</cmp-version>
>> <abstract-schema-name>SalBean</abstract-schema-name>
>> <cmp-field>
>> <field-name>salID</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>salIP</field-name>
>> </cmp-field>
>> </entity>
>> <entity>
>> <display-name>SensorEntityBean</display-name>
>> <ejb-name>SensorBean</ejb-name>
>> <local-home>com.osec.lsas.demo.domain.SensorLocalHome</local-home>
>> <local>com.osec.lsas.demo.domain.SensorLocal</local>
>> <ejb-class>com.osec.lsas.demo.domain.SensorBean</ejb-class>
>> <persistence-type>Container</persistence-type>
>> <prim-key-class>com.osec.lsas.demo.domain.SensorPK</prim-key-class>
>> <reentrant>False</reentrant>
>> <cmp-version>2.x</cmp-version>
>> <abstract-schema-name>SensorBean</abstract-schema-name>
>> <cmp-field>
>> <field-name>sensorID</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>location</field-name>
>> </cmp-field>
>> </entity>
>> <entity>
>> <display-name>TrackEntityBean</display-name>
>> <ejb-name>TrackBean</ejb-name>
>> <local-home>com.osec.lsas.demo.domain.TrackLocalHome</local-home>
>> <local>com.osec.lsas.demo.domain.TrackLocal</local>
>> <ejb-class>com.osec.lsas.demo.domain.TrackBean</ejb-class>
>> <persistence-type>Container</persistence-type>
>> <prim-key-class>com.osec.lsas.demo.domain.TrackPK</prim-key-class>
>> <reentrant>False</reentrant>
>> <cmp-version>2.x</cmp-version>
>> <abstract-schema-name>TrackBean</abstract-schema-name>
>> <cmp-field>
>> <field-name>trackID</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>camera_type</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>latitude</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>longitude</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>altitude</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>course</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>speed</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>type</field-name>
>> </cmp-field>
>> <cmp-field>
>> <field-name>status</field-name>
>> </cmp-field>
>> <query>
>> <query-method>
>> <method-name>findByTrackID</method-name>
>> <method-params>
>> <method-param>java.lang.String</method-param>
>> </method-params>
>> </query-method>
>> <ejb-ql>SELECT OBJECT(o) FROM TrackBean AS o WHERE o.trackID = ?1</ejb-ql>
>> </query>
>> </entity>
>> <session>
>> <display-name>LoginManager</display-name>
>> <ejb-name>LoginManagerSessionBean</ejb-name>
>> <home>com.osec.lsas.demo.workflow.accessControl.LoginManagerSessionHome</home>
>> <remote>com.osec.lsas.demo.workflow.accessControl.LoginManagerSession</remote>
>> <ejb-class>com.osec.lsas.demo.workflow.accessControl.LoginManagerSessionBean</ejb-class>
>> <session-type>Stateless</session-type>
>> <transaction-type>Container</transaction-type>
>> </session>
>> <session>
>> <display-name>SensorData</display-name>
>> <ejb-name>SensorDataSessionBean</ejb-name>
>> <local-home>com.osec.lsas.demo.workflow.sa.SensorDataSessionLocalHome</local-home>
>> <local>com.osec.lsas.demo.workflow.sa.SensorDataSessionLocal</local>
>> <ejb-class>com.osec.lsas.demo.workflow.sa.SensorDataSessionBean</ejb-class>
>> <session-type>Stateless</session-type>
>> <transaction-type>Container</transaction-type>
>> </session>
>> <session>
>> <display-name>TrackData</display-name>
>> <ejb-name>TrackDataSessionBean</ejb-name>
>> <local-home>com.osec.lsas.demo.workflow.sa.TrackDataSessionLocalHome</local-home>
>> <local>com.osec.lsas.demo.workflow.sa.TrackDataSessionLocal</local>
>> <ejb-class>com.osec.lsas.demo.workflow.sa.TrackDataSessionBean</ejb-class>
>> <session-type>Stateless</session-type>
>> <transaction-type>Container</transaction-type>
>> </session>
>> <session>
>> <display-name>VideoSession</display-name>
>> <ejb-name>VideoSessionBean</ejb-name>
>> <local-home>com.osec.lsas.demo.workflow.video.VideoSessionLocalHome</local-home>
>> <local>com.osec.lsas.demo.workflow.video.VideoSessionLocal</local>
>> <ejb-class>com.osec.lsas.demo.workflow.video.VideoSessionBean</ejb-class>
>> <session-type>Stateless</session-type>
>> <transaction-type>Container</transaction-type>
>> </session>
>> <message-driven>
>> <ejb-name>SensorDataMessageDrivenBean</ejb-name>
>> <ejb-class>com.osec.lsas.demo.workflow.sa.SensorDataMessageDrivenBean</ejb-class>
>> <transaction-type>Container</transaction-type>
>> <message-driven-destination>
>> <destination-type>javax.jms.Topic</destination-type>
>> <subscription-durability>Durable</subscription-durability>
>> </message-driven-destination>
>> </message-driven>
>> <message-driven>
>> <ejb-name>TrackDataMessageDrivenBean</ejb-name>
>> <ejb-class>com.osec.lsas.demo.workflow.sa.TrackDataMessageDrivenBean</ejb-class>
>> <transaction-type>Container</transaction-type>
>> <message-driven-destination>
>> <destination-type>javax.jms.Topic</destination-type>
>> <subscription-durability>Durable</subscription-durability>
>> </message-driven-destination>
>> </message-driven>
>> </enterprise-beans>
>> <assembly-descriptor>
>> <container-transaction>
>> <method>
>> <ejb-name>UserBean</ejb-name>
>> <method-name>*</method-name>
>> </method>
>> <method>
>> <ejb-name>SalBean</ejb-name>
>> <method-name>*</method-name>
>> </method>
>> <method>
>> <ejb-name>SensorBean</ejb-name>
>> <method-name>*</method-name>
>> </method>
>> <method>
>> <ejb-name>TrackBean</ejb-name>
>> <method-name>*</method-name>
>> </method>
>> <trans-attribute>Required</trans-attribute>
>> </container-transaction>
>> </assembly-descriptor>
>></ejb-jar>
>>
-
Using WLS8.1:
I'm currently trying to set up a MDB listening directly on a JMS queue, provided
by Sonic.
I registered my queue through the Sonic JMS console in the WLS JNDI repository,
and can browse to the object successfully in the JNDI browser.
However, when I deploy my MDB, I get an exception:
<Feb 28, 2004 3:27:09 PM MET> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJB: SomeMDB is unable to connect to the JMS destination: myforeigndestination.
The Error was:
weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
The only way to get it working is setting up an additional internal WL queue,
connected by a Messaging Bridge, but that's not what I want.
It seems like weblogic JMS implemenation only accepts weblogic Queue's as valid
Queue objects.
Thanks for any pointers.
Rgrds,
Klaas van der Ploeg
Klaas van der Ploeg wrote:
> Using WLS8.1:
>
> I'm currently trying to set up a MDB listening directly on a JMS queue, provided
> by Sonic.
>
> I registered my queue through the Sonic JMS console in the WLS JNDI repository,
> and can browse to the object successfully in the JNDI browser.
> However, when I deploy my MDB, I get an exception:
> <Feb 28, 2004 3:27:09 PM MET> <Warning> <EJB> <BEA-010061> <The Message-Driven
> EJB: SomeMDB is unable to connect to the JMS destination: myforeigndestination.
> The Error was:
> weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
> weblogic.jms.common.InvalidDestinationException: Foreign destination, q_external
> at weblogic.jms.common.Destination.checkDestinationType(Destination.java:106)
> at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1580)
> at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1484)
> at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1609)
> at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1844)
> at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
> at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
> at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
> at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
> at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
> at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
>
> The only way to get it working is setting up an additional internal WL queue,
> connected by a Messaging Bridge, but that's not what I want.
>
>
> It seems like weblogic JMS implemenation only accepts weblogic Queue's as valid
> Queue objects.
Emphatically not true. In pointed fact, WebLogic has gone through
great pains over the years to ensure integration works with multiple
JMS vendors - sending out fix requests to them as needed (including
Sonic).
Anyhow, you are trying to use a non-WebLogic destination with a
WebLogic JMS session. No vendor supports this. Instead, you
must make sure that the MDB creates a Sonic JMS session. So
configure a foreign connection factory, and configure the
MDB to refer to this connection factory. You can find
this information in WebLogic's JMS developer guide.
This is the first time I've gotten a Sonic question in quite a
while, but I know that they have step-by-step doc on how to
integrate their product with WebLogic. You might want to try
looking there for more help. I don't know if their doc
leverages 8.1 foreign destination wrapper feature.
Tom Barnes, BEA
>
> Thanks for any pointers.
>
> Rgrds,
> Klaas van der Ploeg
-
XML Message Body Selector in Automation
Hi,
I'm having some trouble implementing a XML Message Body Selector in an automated task. I'm running OSM 7.2.0.7 in a Unix environment and using Design Studio 7.2.1.
I'm sendind in my request to an external system a request tthe following string: OSM-TaskName-%{CARTRIDGE_VERSION}
<Request>
<Header>
<dueDate>20131128</dueDate>
<application>OSM-MSS_Lookup-1.0.0.0.5</application>
</Header>
</Request>
The response of MSS is:
<Response>
<Header>
<dueDate>20131128</dueDate>
<application>OSM-MSS_Lookup-1.0.0.0.5</application>
</Header>
In the selector I've tried different XPath expressions:
Select:
/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']/text()
*[local-name() ='Responset']/*[local-name()='Header']/*[local-name()='application']/text()
//*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']/text()
/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
//*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
/Response/Header/application
/Response/Header/application/text()
Compare: OSM-MSS_Lookup-%{CARTRIDGE_VERSION}
I keep getting the following error in the log file for the differente selectors:
####<Nov 28, 2013 10:34:31 AM CST> <Info> <oms> <hostname> <SOM_ManagedServer_1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'
> <sceadmin> <BEA1-49AB960B7AE5258D5CC8> <0710a255d6bbb54d:-1d6ed94c:142960580fb:-8000-0000000000026363> <1385656471431> <BEA-000000> <api.e:
namespace/version: SOM_Cartridge/1.0.0.0.5
automator type: taskAutomator
plugin JNDI name: MSS_Lookup.automatedtask.somprovisioning.MSS_LookupReceiverBean
plugin class name: oracle.communications.ordermanagement.automation.plugin.XQueryReceiver
run plugin as: oms-automation receiver:
type: external
JMS source: sky/MSS/Product/WebServiceResponseQueue
message [property|body] selector: JMS_BEA_SELECT('xpath', '/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']')='OSM-MSS_Lookup-1.0.0.0.5'
####<Nov 28, 2013 10:34:31 AM CST> <Warning> <EJB> <hostname> <SOM_ManagedServer_1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <oms-automation> <> <0710a255d6bbb54d:-1d6ed94c:142960580fb:-8000-000000000002650a> <1385656471454> <BEA-010061> <The Message-Driven EJB: MSS_Lookup.automatedtask.somprovisioning.MSS_LookupReceiverBeanMDB is unable to connect to the JMS destination: sky/MSS/Product/WebServiceResponseQueue. The Error was:
javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "JMS_BEA_SELECT('xpath', '/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']')='OSM-MSS_Lookup-1.0.0.0.5'"
Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "JMS_BEA_SELECT('xpath', '/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']')='OSM-MSS_Lookup-1.0.0.0.5'"
I would appreciate any help or ideas.
CheersHi,
Could you confirm on below:
1 ) Are you using multiple automation plug-in external event receivers in the same automation task ?
2 ) And are you having the default Correlation Message property set to 'JSMCorrelationID' in external event receiver?
If your answer for the first question is No, they i would suggest to use Correlation XML Body as
*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
The value of the field(application) in request must match the value of the field in response, in your case it is matching. And you will be reading this correlation id in response processing xquery.
Regards
Srinivas -
Not able to connect to a queue under a foreign server.
Not able to connect to a queue under a foreign server.
I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
OS used is AIX 6.0 on both servers.
Tried restarting the local server but nothing helps. Same error continues.
HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
It throws following errors:
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
at javax.naming.InitialContext.internalInit(InitialContext.java:286)
at javax.naming.InitialContext.<init>(InitialContext.java:211)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at weblogic.jms.common.CDS$2.run(CDS.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
... 46 more
>
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
<Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
Truncated. see log file for complete stacktrace
Edited by: 942523 on Jun 24, 2012 11:38 PMThanks René van Wijk for the reply.
I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
This page displays details about this bound object.
Failed to create InitialContext using factory specified in hashtable
Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:436)
at weblogic.jms.common.CDS$2.run(CDS.java:503)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
... 36 more
Caused by: java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
Let me know if any other thing i'm missing or it can be something else like network or some other issue. -
What is wrong with the migrated project? (8.1 to 10.3)
Hi all,
I've "inherited" an old WebLogic 8.1 app that is to be migrated to WebLogic 10.3. I've run it through the migration/upgrade functionality in Workshop 10.3, fixed the compile errors, and dealt with the most obvious (to me) cases of deprecated class use. The app, from what I've been told, was originally coded using the old non-eclipse-based workshop 8.1, using PageFlows.
The app, however, when I run it, still produces some warnings, and does not behave correctly. I've probably missed some crucial step in the migration process. Though I've worked a great deal with (Non-j2EE) Java before, I'm very green when it comes to the intricacies of WebLogic applications. I'm hoping that someone wiser than I can shed some light on what I've missed.
At startup:
<17-09-2009 10:07:43 CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MessageBufferTopicBean is unable to connect to the JMS destination: weblogic.Otribaby.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC. The Error was:
Can not get distribute destination information. The destination JNDI name is weblogic.Otribaby.WlwRuntimeAppScopedJMS#MSG_BUFFER_TOPIC, the provider URL is null>
<17-09-2009 10:07:43 CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MessageBufferBean is unable to connect to the JMS destination: weblogic.Otribaby.WlwRuntimeAppScopedJMS#MSG_BUFFER_QUEUE. The Error was:
Can not get distribute destination information. The destination JNDI name is weblogic.Otribaby.WlwRuntimeAppScopedJMS#MSG_BUFFER_QUEUE, the provider URL is null> then when accessing order page
<[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "622" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@18bcbb[
GET //pub/order.jsp HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, */*
Accept-Language: da
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)
Connection: Keep-Alive
Cookie: JSESSIONID=Lvp3KxndMydGSq6RP4pPH2Krvy05NGkx0120Wp1G3W1kdmWGLP72!-738502403
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-33 "[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, waiting, priority=1, DAEMON> {
-- Waiting for notification on: weblogic.jsp.internal.client.JobWaiter@2edf62[fat lock]
java.lang.Object.wait(Object.java:???)
java.lang.Object.wait(Object.java:485)
weblogic.jsp.internal.client.JobWaiter.blockUntilFinished(JobWaiter.java:45)
weblogic.jsp.internal.client.ClientUtilsImpl.build(ClientUtilsImpl.java:353)
weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:67)
weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:191)
weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:182)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
^-- Holding lock: weblogic.servlet.jsp.JavelinxJSPStub@58c61b[thin lock]
weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:352)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:349)
^-- Holding lock: pub.PubController@4cd2ed[thin lock]
org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:100)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3468)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2116)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2038)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1372)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
>
<17-09-2009 10:23:12 CEST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "688" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@18bcbb[
GET //pub/order.jsp HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, */*
Accept-Language: da
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)
Connection: Keep-Alive
Cookie: JSESSIONID=Lvp3KxndMydGSq6RP4pPH2Krvy05NGkx0120Wp1G3W1kdmWGLP72!-738502403
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-33 "[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, waiting, priority=1, DAEMON> {
-- Waiting for notification on: weblogic.jsp.internal.client.JobWaiter@2edf62[fat lock]
java.lang.Object.wait(Object.java:???)
java.lang.Object.wait(Object.java:485)
weblogic.jsp.internal.client.JobWaiter.blockUntilFinished(JobWaiter.java:45)
weblogic.jsp.internal.client.ClientUtilsImpl.build(ClientUtilsImpl.java:353)
weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:67)
weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:191)
weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:182)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
^-- Holding lock: weblogic.servlet.jsp.JavelinxJSPStub@58c61b[thin lock]
weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:352)
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:198)
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
org.apache.beehive.netui.pageflow.PageFlowPageFilter.runPage(PageFlowPageFilter.java:349)
^-- Holding lock: pub.PubController@4cd2ed[thin lock]
org.apache.beehive.netui.pageflow.PageFlowPageFilter.doFilter(PageFlowPageFilter.java:100)
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3468)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)
weblogic.security.service.SecurityManager.runAs(Unknown Source)
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2116)
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2038)
weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1372)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
>
<17-09-2009 10:23:47 CEST> <Warning> <com.bea.wlw.netui.script.el.CompatImplicitObjectUtil> <BEA-000000> <Could not create a ContextFactory for type "com.bea.netuix.servlets.script.PortalVariableResolver$PortalContextFactory" because the ContextFactory implementation class could not be found.> and when trying to progress to the next step in a pageflow
<17-09-2009 10:58:13 CEST> <Error> <org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler> <BEA-000000> <Could not find exception handler method handleException for java.lang.NullPointerException.>
<17-09-2009 10:58:13 CEST> <Error> <org.apache.beehive.netui.pageflow.internal.DefaultExceptionsHandler> <BEA-000000> <Could not find exception handler method handleException for java.lang.RuntimeException.>
[] Unhandled exception caught in Global.app:
java.lang.NullPointerException
at pub.PubController.OrderStepOne(PubController.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2121)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:159)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:527)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
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:176)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3495)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)I have experienced the same problem in which I finally give up trying LookOut connection browser. After few follows, you can not even see the display on the screen anymore. Close the connection browser and reopen again then everything goes fine, but it will crap out again after few follows.
Frank Nguyen -
InvalidClientIdException while creating Durable subscription in weblogic
Hi,
We have scenario to create a durable subscription for an MDB. Here application in weblogic is a subscriber to a Topic present on the Progress Sonic. For integrating to independent platforms we are using Foreign Server mechanism under JMS Modules.
For creating durable subscription, we have changed the MDB code . Below is the MDB code,
package com.test;
import java.util.Enumeration;
import javax.annotation.Resource;
import javax.annotation.Resources;
import javax.ejb.MessageDriven;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
import javax.ejb.ActivationConfigProperty;
* Message-Driven Bean implementation class for: TestMDB
@MessageDriven(description = "mdb for Airline Schedule Change MDB",
name = "AirlineScheduleMDB",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Topic"),
@ActivationConfigProperty(propertyName = "subscriptionDurability",
propertyValue = "Durable")
@TransactionManagement(value = TransactionManagementType.CONTAINER)
@Resources( { @Resource(name = "ConnectionFactoryRef",
mappedName = "TopicConnectionFactory",
type = javax.jms.ConnectionFactory.class) })
public class TestMDB implements MessageListener {
* @see MessageListener#onMessage(Message)
@TransactionAttribute(value = TransactionAttributeType.NOT_SUPPORTED)
public void onMessage(Message message) {
System.out.println("Inside message : ");
try {
Enumeration<Object> messageProperty = message.getPropertyNames();
System.out.println("The request : "+message);
if(message != null){
System.out.println("TestMDB : onMessage : Start");
}else{
System.out.println("Received Input message is empty");
} catch (Exception e) {
System.out.println("Exception Occurred in TestMDB : ");
e.printStackTrace();
System.out.println("TestMDB : onMessage : End.Time taken is :");
Also the following change was included in the weblogic-ejb-jar.xml.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
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-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>TestMDB</ejb-name>
<message-driven-descriptor>
<pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>DurableJNDI</destination-jndi-name>
<connection-factory-jndi-name>TopicConnectionFactory</connection-factory-jndi-name>
<jms-polling-interval-seconds>30</jms-polling-interval-seconds>
<generate-unique-jms-client-id>true</generate-unique-jms-client-id>
<jms-client-id>DurableTest</jms-client-id>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Exception we got :
<03-Apr-2012 18:11:02 o'clock UTC> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TestMDB is unable to connect to the JMS destination: DurableJNDI. The Error was:
javax.jms.InvalidClientIDException: Invalid client id: DurableTest_drdevwls_TestDomain-wls1_CLEARCF.jarTestMDB
Weblogic is automatically creating a unique id based on the combination of Adminserver/Managedserver/Projectname etc.
However the id created by weblogic seems to have a dot(.) which as per Sonic spec is an invalid character.
eg:- DurableTest_test_domain_AdminServer_CLEARCF.jarTestMDB
Hence we changed the parameter to false and provided our own value.
<generate-unique-jms-client-id>false</generate-unique-jms-client-id>
<jms-client-id>DurableTest</jms-client-id>
At this point of time we were able to see that MDB have created a Durable subscription successfully and it worked as expected.
However when we tried to scale this change to multiple managed servers, there were errors thrown from sonic side.
javax.jms.JMSException: [129] progress.message.client.EUserAlreadyConnected: Administrator/$DURABLE$DurableTest$DurableTest
So we cannot have same clientid for multiple clients(managed server). We arent sure how to proceed with this.
We need to find a way to remove the dot from the dynamic id weblogic creates.
Any help on this is highly appreciated.Hi Tom,
We have found the solution to this problem and thanks for your suggestion that has partially helped us in solving the problem.
As you have suggested we have defined client-id on the connection factory however we will be having only connection factory instead of multiple with different client-ID's.
Along with the client-id configured at the connection factory level we are now setting the attributes generate-unique-client-id as true at the weblogic end.
By doing this way, I assume that weblogic while making the durable subscription connection is passing the uniquely generated client ID (which has dots '.' included in it ) as subscription name and client-id will be same, that is defined on the connection factory.
A question may arise that - 'why is sonic accepting subscription name with dots but not the client-id ?' - When observed from the sonic end the dots in the subscription name are replaced by '@@@' .
Sonic need to answer the question of why the dots are being replaced for subscription name but not for client-id.
Regards,
Bharat K -
Configuration Issue in connecting oracle AQ in weblogic server 10.3.5
Hi,
I am working in Message driven bean and want to receive the message from queue called IEDWM_QUEUE and
have made all the necessary configurations for connecting oracle AQ in weblogic .... Created Foriegnserver,connections factories,destination in JMS Module(weblogic).
But Still i couldn't able to connect to JMS Destination, getting the below error
Jan 16, 2012 12:40:15 PM GMT+05:30> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: CandidateConsumer is unable to connect to the JMS destination: Queues
IEDWM_QUEUE. The Error was:
avax.naming.NamingException: The configuration of the AQjmsInitialContext is not complete. The configuration must contain datasource or (db_url,java.naming.security.principal,java.naming.security.credentials) or both
Kindly tell me if you need any further information and I request you to provide the solution, it will be more helpful for us..
With Regards,
Sridhar.THi,
If I recall correctly:
1 - Ensure you have configured and targeted a Data Source for Oracle, and check your statistics or logs to make sure that it is working.
2 - Reference this Data Source as per the AQ instructions. I think this involves using a specific property name in the context properties for the AQ initial context, where the context properties are set as part of foreign server configuration.
Tom -
Problems starting Server on OSB 11g
Hi Everybody,
I have a problem, I just installed the Service Bus 11g on Red Hat and I have problems when I start the server.
I particular first I start the Admin_Server without any exception and then I start the Server but I get this excedption:
PATH=/app/olg/wlserver-10.3/wlserver_10.3/server/bin:/app/olg/wlserver-10.3/modules/org.apache.ant_1.7.1/bin:/app/jrmc-3.1.2-1.6.0//jre/bin:/app/jrmc-3.1.2-1.6.0//bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
Starting WLS with line:
/app/jrmc-3.1.2-1.6.0//bin/java -jrockit -Xms256m -Xmx512m -Xmanagement -Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=10.31.57.61 -Dcom.sun.management.jmxremote.port=17001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder -Djava.awt.headless=true -Dweblogic.Name=Server_1 -Djava.security.policy=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/app/olg/wlserver-10.3/wlserver_10.3 -Dwls.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Dweblogic.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Ddomain.home=/app/olg/bea-olgfwdomain/olgfwdomain -Dcommon.components.home=/app/olg/wlserver-10.3/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/app/olg/wlserver-10.3/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig -Doracle.server.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/servers/Server_1 -Doracle.security.jps.config=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/carml -Digf.arisidstack.home=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/app/olg/wlserver-10.3/oracle_common/modules/oracle.ossoiap_11.1.1,/app/olg/wlserver-10.3/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://10.31.57.61:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/olg/wlserver-10.3/patch_wls1033/profiles/default/sysext_manifest_classpath:/app/olg/wlserver-10.3/patch_ocp353/profiles/default/sysext_manifest_classpath weblogic.Server
[JRockit] Management server started on port 17001, ssl=false, authenticate=false.
<Dec 1, 2010 1:00:03 PM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
<Dec 1, 2010 1:00:05 PM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Dec 1, 2010 1:00:07 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 1, 2010 1:00:07 PM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 1, 2010 1:00:07 PM CET> <Notice> <Log Management> <BEA-170019> <The server log file /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/logs/Server_1.log is opened. All server side log events will be written to this file.>
<Dec 1, 2010 1:00:12 PM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 1, 2010 1:00:14 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
<Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 1, 2010 1:00:23 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "Reporting-FileStore_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
<Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
<Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
<Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'Message Reporting Purger' is not targeted>
<Dec 1, 2010 1:00:29 PM CET> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.>
<Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398316> <Error getting the Result Cache /osb/service/ResultCache because the OSB Coherence Cache Provider has not been initialized.
Additional error messages at server startup should point to the root cause for this error.>
<Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398315> <Service Result Caching functionality is disabled because the result cache is unavailable.
Additional error messages at server startup should point to the root cause for this. If you require Service Result Caching functionality, please fix the errors and restart the server.>
<Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Ftp Transport Provider/elek28]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: emailtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Email Transport Provider/tbi712]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: filetransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/File Transport Provider/qwi4ym]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/EJB Transport Provider/kyabv]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: tuxedotransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Tuxedo Transport Provider/9oa5mj/APP-INF/lib/tuxedo_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: aldsp_transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALDSP Transport Provider/i3u01o/APP-INF/lib/aldsp_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: sftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SFTP Transport Provider/d4v5rl]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: wstransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/WS Transport Provider/wuaaoy]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: flow-transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/FLOW Transport Provider/kgaw7k]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: bpel10gtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/BPEL 10g Transport Provider/7iyhcx]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jcatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: wsif, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: JCAFrameworkImpl, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JCA Transport Provider' due to error java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType.
java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
Truncated. see log file for complete stacktrace
>
<Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad], [Extension-Name: jejbtransport-jar, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JEJB Transport Provider' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: com.bea.wli.sb.transports.jejb.JEJBTransportAppListener
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:140)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
Truncated. see log file for complete stacktrace
>
<Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: soatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SOA-DIRECT Transport Provider/16k7ar/APP-INF/lib/soa_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: xbusrouting-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Routing' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
Truncated. see log file for complete stacktrace
>
<Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: xbustransform-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Transform' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
Truncated. see log file for complete stacktrace
>
<Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: xbuslogging-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3]. Make sure the referenced optional package has been deployed as a library.>
<Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Logging' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
Truncated. see log file for complete stacktrace
>
<Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Test Framework' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
Truncated. see log file for complete stacktrace
>
<Dec 1, 2010 1:00:36 PM CET> <Emergency> <Deployer> <BEA-149259> <Server 'Server_1' in cluster 'Cluster-1' is being brought up in administration state due to failed deployments.>
Dec 1, 2010 1:00:37 PM oracle.dms.app.ServerInitializer oracle.dms.app.ServerInitializer
INFO: DMS startup class is not started. DMS runs with reduced functionality.
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.ftp, the provider URL is null>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.email, the provider URL is null>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.file, the provider URL is null>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
<Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.sftp, the provider URL is null>
<Dec 1, 2010 1:00:41 PM CET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster-1.>
I tried to find something on internet but nothing suitable for me.
ThanksFrom the error messages it does not seem to find any of the transport related jars (ftp, jca, email, etc..). Looks like there was an issue while creating the domain.
Can you retry creating the domain and let us know if you are still getting the same error?
Regards,
Patrick -
JMS Module, Foreign Server: Destination unreachable
Hi,
In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging.
Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with following config:
* JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
* JNDI Connection URL: t3://fsb-jms1-dev:7901,fsb-jms2-dev:7901
After deploying an EJB that makes use of this module we see following error in our log files every time when starting a Managed Server:
####<Jun 8, 2011 11:36:48 AM CEST> <Warning> <EJB> <esddev148> <osbms1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <11d1def534ea1be0:-27013fcb:1306e9a12ac:-8000-0000000000000016> <13075
25808959> <BEA-010061> <The Message-Driven EJB: MessageLogWriter is unable to connect to the JMS destination: fsb.jms.MessageLoggingQueue. The Error was:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java
.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
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)
Caused by: java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java.rmi.ConnectException: Destination unreachab
le; nested exception is:
java.io.IOException: Empty server reply; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:352)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:612)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:563)
at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:789)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:341)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:194)
... 4 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:402)
at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:306)
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:350)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:613)
... 30 more
>
I've allready ensured that the managed servers of the jms cluster are reachable by issuing a connect command from WLST (although making the connection can be time consuming)
wls:/offline> connect('weblogic','******','t3://fsb-jms1-dev:7901')
Connecting to t3://fsb-jms1-dev:7901 with userid weblogic ...
Successfully connected to managed Server 'jmsms1' that belongs to domain 'jmsdevdomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/jmsdevdomain/serverConfig> disconnect()
Disconnected from weblogic server: jmsms1
wls:/offline> connect('weblogic','******','t3://fsb-jms2-dev:7901')
Connecting to t3://fsb-jms2-dev:7901 with userid weblogic ...
Successfully connected to managed Server 'jmsms2' that belongs to domain 'jmsdevdomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
In my search for a solution I've also read that this could be caused by a bad configured DNS server. Therefore I configured my /etc/nsswitch.conf file to contain only the property files under the parameter hosts.
Following is an extraction of my /etc/hosts file:
10.16.85.50 fsb-jms1-dev.localdomain fsb-jms1-dev
10.16.85.51 fsb-jms2-dev.localdomain fsb-jms2-dev
10.16.85.52 fsb-osb1-dev.localdomain fsb-osb1-dev
10.16.85.53 fsb-osb2-dev.localdomain fsb-osb2-dev
Does anybody have an idea how I can further debug this problem?
Kind Regards,
DavyMaybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html
-
[EJB:010112] - error with WLI8.1 Event Generator for foreign JMS/MQ provider
I'm getting following error in weblogic server log when starting a JMS Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect
every 10 seconds. This log message will repeat every 600 seconds until the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted, but the pro
vider defined in the EJB is not transacted. Provider should be transacted if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly. QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
ScottHi Scott,
I need a transaction from the MDB since I am not using an EJb to pursue the action.
Hence I need to retain the <trans-attribute>Required</trans-attribute> at the
MDB.
Have any answers?
Pradip
"Scott Yen" <[email protected]> wrote:
>
It's resolved.
The MDB automatically created by JMS Event Generator defaults to be deployed
with
“transacted”. That requires the foreign JMS provider to be “XA”.
The deployment descriptor is created as <domain-directory>/WLIJmsEG_<event_gen_name>.jar
e.g. C:\bea812\user_projects\domains\jmsInterop\WLIJmsEG_mqQueueEventGen.jar
Since MQ in the localhost and remote SLUDV18 are not XA-enabled, we had
to manually
change the <container-transaction> section in ejb-jar.xml:
From :
<trans-attribute>Required</trans-attribute>
To:
<trans-attribute>NotSupported</trans-attribute>
"Scott Yen" <[email protected]> wrote:
I'm getting following error in weblogic server log when starting a JMS
Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to
reconnect
every 10 seconds. This log message will repeat every 600 seconds until
the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted,
but the pro
vider defined in the EJB is not transacted. Provider should be transacted
if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator
for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly.
QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign
JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott -
Problems Starting Weblogic Server for Tutorials (Fresh install)...
Hi guys, need a little help here.
I'm trying to startup Weblogic Server for Java Control Tutorial application and I get all sorts of errors, mostly seeming to deal with JMS/JNDI network stuff. Here's the error dump I get:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
Starting WLS with line:
C:\bea\JDK142~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket
,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:Com
pileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da
:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls
.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.con
figuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.managem
ent.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ign
oreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.log
ErrorsToConsole=true -Dweblogic.Name=cgServer -Djava.security.policy=C:\bea\WEBL
OG~1\server\lib\weblogic.policy weblogic.Server
<Oct 30, 2005 2:33:31 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting Web
Logic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Micro
systems Inc.>
<Oct 30, 2005 2:33:31 PM PST> <Info> <Configuration Management> <BEA-150016> <Th
is server is being started as the administration server.>
<Oct 30, 2005 2:33:31 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877>
<Oct 30, 2005 2:33:32 PM PST> <Notice> <Management> <BEA-140005> <Loading domain
configuration from configuration repository at C:\bea\WEBLOG~1\samples\domains\
workshop\.\config.xml.>
<Oct 30, 2005 2:33:33 PM PST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\bea\weblogic81\samples\domains\workshop\cgServer\cgServer.log is op
ened. All server side log events will be written to this file.>
<Oct 30, 2005 2:33:34 PM PST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Oct 30, 2005 2:33:34 PM PST> <Notice> <WebLogicServer> <BEA-000327> <Starting W
ebLogic Admin Server "cgServer" for domain "workshop">
<Oct 30, 2005 2:33:38 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:40 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:42 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:44 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:46 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgJMSPool-nonXA": SQL-server rejected establ
ishment of SQL-connection. Pointbase Server may not be running on localhost at p
ort 9093.>
<Oct 30, 2005 2:33:47 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgJM
SPool-nonXA" deployment failed with the following error: 0:Could not create pool
connection. The DBMS driver exception was: SQL-server rejected establishment of
SQL-connection. Pointbase Server may not be running on localhost at port 9093..
>
<Oct 30, 2005 2:33:48 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:50 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:52 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:54 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:56 PM PST> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "cgPool": SQL-server rejected establishment o
f SQL-connection. Pointbase Server may not be running on localhost at port 9093.
>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001150> <Connection Pool "cgPo
ol" deployment failed with the following error: 0:Could not create pool connecti
on. The DBMS driver exception was: SQL-server rejected establishment of SQL-conn
ection. Pointbase Server may not be running on localhost at port 9093..>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
urce" deployment failed with the following error: DataSource(cgDataSource;cgSamp
leDataSource) can't be created with non-existent Pool (connection or multi) (cgP
ool).>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JDBC> <BEA-001151> <Data Source "cgDataSo
urce-nonXA" deployment failed with the following error: DataSource(cgDataSource-
nonXA;weblogic.jdbc.jts.ebusinessPool) can't be created with non-existent Pool (
connection or multi) (cgJMSPool-nonXA).>
<Oct 30, 2005 2:33:57 PM PST> <Alert> <JMS> <BEA-040052> <JMSServer "cgJMSServer
" store failed to open java.io.IOException: JMS JDBC store, connection pool = <c
gJMSPool-nonXA>, prefix = <weblogic>: connection pool does not exist.
java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
= <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Oct 30, 2005 2:33:57 PM PST> <Error> <JMS> <BEA-040123> <Failed to start JMS Se
rver "cgJMSServer" due to weblogic.jms.common.JMSException: JMS can not open sto
re cgJMSStore.
weblogic.jms.common.JMSException: JMS can not open store cgJMSStore
at weblogic.jms.backend.BEStore.start(BEStore.java:163)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Caused by: java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-non
XA>, prefix = <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
... 29 more
>
<Oct 30, 2005 2:33:57 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090170> <Loading the priv
ate key stored under the alias DemoIdentity from the jks keystore file C:\bea\we
blogic81\server\lib\DemoIdentity.jks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090171> <Loading the iden
tity certificate stored under the alias DemoIdentity from the jks keystore file
C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.j
ks.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <Security> <BEA-090169> <Loading trusted
certificates from the jks keystore file C:\bea\JDK142~1\jre\lib\security\cacerts
.>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000331> <Started We
bLogic Admin Server "cgServer" for domain "workshop" running in Development Mode
>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server sta
rted in RUNNING mode>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
<Oct 30, 2005 2:33:58 PM PST> <Warning> <WebLogicServer> <BEA-000372> <HostName:
0.0.0.0, maps to multiple IP addresses:192.168.0.1,70.34.104.139>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "Li
stenThread.Default" listening on port 7001, ip address *.*>
<Oct 30, 2005 2:33:58 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SS
LListenThread.Default" listening on port 7002, ip address *.*>
<Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 2 attempts. The MDB will attempt to
reconnect every 10 seconds. This log message will repeat every 600 seconds until
the condition clears.>
<Oct 30, 2005 2:34:07 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 2 attempts. The MDB will attempt to reconnect every
10 seconds. This log message will repeat every 600 seconds until the condition
clears.>
<Oct 30, 2005 2:34:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 62 attempts. The MDB will attempt to reconnect ever
y 10 seconds. This log message will repeat every 600 seconds until the condition
clears.>
<Oct 30, 2005 2:44:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 63 attempts. The MDB will attempt to
reconnect every 10 seconds. This log message will repeat every 600 seconds unti
l the condition clears.>
<Oct 30, 2005 2:44:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
<Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. Connection failed after 122 attempts. The MDB will attempt to reconnect eve
ry 10 seconds. This log message will repeat every 600 seconds until the conditio
n clears.>
<Oct 30, 2005 2:54:08 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.qu
eue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue could not be found
. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and t
he JMS destination has been deployed.>
<Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010096> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. Connection failed after 123 attempts. The MDB will attempt t
o reconnect every 10 seconds. This log message will repeat every 600 seconds unt
il the condition clears.>
<Oct 30, 2005 2:54:17 PM PST> <Warning> <EJB> <BEA-010061> <The Message-Driven E
JB: CreditScoreTutorial is unable to connect to the JMS destination: tutorial.cr
edit.request.topic. The Error was:
[EJB:011010]The JMS destination with the JNDI name: tutorial.credit.request.topi
c could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.x
ml is correct, and the JMS destination has been deployed.>
THANK YOU for any help you can provide!These are errors/warning because of incorrect connection pool settings.Either the database parameters were not configured correctly or there were some issues with the configuration itself.
Your server did start up correctly though.
"<Server started in RUNNING mode>"
Maybe you are looking for
-
Footer on each pages and last page
I need to develop a template which has a header , body and footer. The Body has order lines. If the order lines exceeds the 1st page, it should overflow in the 2nd page , so the 1st page will have just signature as footer and 2nd page will have the m
-
Launch a specific file on startup
Hello everyone, Is there a way to automatically launch a specific file on startup? I would like to have an image pop up on my wife's computer when she logs in in the morning. Is this possible? Is there an app to automate this sort of thing? I've look
-
*Hi Friends,* *Thanks in Advance.* *After saving my Sale Order... the system giving the Message 'Sale Order Saved' and remains in the Same Screen in a Refresh Mode.* *Actually my client requirement is .that they want to navigate to VA01 Transaction a
-
Windows7 hanging when shutting down applying updates
Whenever I shut down or reboot Windows7 I get a message that Windows is applying update 9 of 13, but the "update" never gets "applied" and Windows7 just hangs supposedly trying to apply it. Yet when I subsequently boot into Windows7 and look a Window
-
Hi all, I made a game by flash and projected it into .exe file. It runs correctly excepte one thing. In this game, I used onEnterFrame and setInterval to make counters to coundown and do something. But when player holds down the movie's title bar by