Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Error During Deployment

Avatar

Former Community Member
I got the following error while deploying the adobe-livecycle-websphere.ear file.



Can anyone please help me...



Installing...

If there are enterprise beans in the application, the EJB deployment process can take several minutes. Please do not save the configuration until the process completes.



Check the SystemOut.log on the Deployment Manager or server where the application is deployed for specific information about the EJB deployment process as it occurs.



ADMA5016I: Installation of LiveCycle8 started.



ADMA0115W: Resource Assignment of name jms/PELongLivedQueue and type javax.jms.Queue, with JNDI name queue/adobe_PELongLivedQueue is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/PEScheduledMsgQueue and type javax.jms.Queue, with JNDI name queue/adobe_PEScheduledMsgQueue is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/POFSchemaTopic and type javax.jms.Topic, with JNDI name topic/adobe_POFSchemaTopic is not found within scope of module POF Components with URI adobe-pof.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/POFObjectTopic and type javax.jms.Topic, with JNDI name topic/adobe_POFObjectTopic is not found within scope of module POF Components with URI adobe-pof.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/TemplateEventTopic and type javax.jms.Topic, with JNDI name topic/adobe_TemplateEventTopic is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/PEScheduledMsgQueue and type javax.jms.Queue, with JNDI name queue/adobe_PEScheduledMsgQueue is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/ProcessEventTopic and type javax.jms.Topic, with JNDI name topic/adobe_ProcessEventTopic is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/PEDLongLivedQueue and type javax.jms.Queue, with JNDI name queue/adobe_PEDLongLivedQueue is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/TemplateEventTopic and type javax.jms.Topic, with JNDI name topic/adobe_TemplateEventTopic is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/POFObjectTopic and type javax.jms.Topic, with JNDI name topic/adobe_POFObjectTopic is not found within scope of module POF Components with URI adobe-pof.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/ProcessEventTopic and type javax.jms.Topic, with JNDI name topic/adobe_ProcessEventTopic is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=chnmc,node=chnmc,server=server1.



ADMA0115W: Resource Assignment of name jms/PELongLivedQueue and type javax.jms.Queue, with JNDI name queue/adobe_PELongLivedQueue is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ej
1 Reply

Avatar

Level 4
Prabha:



A possible cause is that adobe-livecycle-websphere.ear is being deployed to a server, or cluster while all of the queues and topics have been defined to a Default JMS Provider with a different scope (server/cluster) and are not "visible" to the EAR being deployed.



There has been changes to LiveCycle's JMS architecture between beta and final GA release - the number of queues and topics needed have been drastically reduced. Many of the queues and topics mentioned in your message are no longer required. So chances are that the 8.0.1 GA release will not give you these problems.



However, if you still get the following exceptions, you can safely ignore them. This is a known problem that is being fixed:



ADMA0115W: Resource assignment of name jms/ProcessEventTopic and type javax.jms.Topic, with JNDI name topic/adobe_ProcessEventTopic is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=InttstAdobeCell01,cluster=intAdobeLiveCycleCluster.



ADMA0115W: Resource assignment of name jms/ProcessEventTopic and type javax.jms.Topic, with JNDI name topic/adobe_ProcessEventTopic is not found within scope of module adobe-wkf.jar with URI adobe-wkf.jar,META-INF/ejb-jar.xml deployed to target WebSphere:cell=InttstAdobeCell01,cluster=intAdobeLiveCycleCluster.



ADMA0115W: Resource assignment of name jms/POFSchemaTopic and type javax.jms.Topic, with JNDI name topic/adobe_POFSchemaTopic is not found within scope of module Platform Bootstrapper with URI adobe-bootstrapper.war,WEB-INF/web.xml deployed to target WebSphere:cell=InttstAdobeCell01,cluster=intAdobeLiveCycleCluster.



- Jayan Kandathil