MDB deployment issue
Hi,
I am developing j2ee application, my MDB needs some helper code which was loaded in the init of a load-on-startup servlet. If the queue has some accumulated messages, when I restart the app server(weblogic), the MDBs are pretty quick get deployed and starts hard wroking, but the servelet takes a bit longer, so the helper code is not available yet, that caused problem. Tha same thing happened when shut down the server. Any suggestion? How can I prevent the MDB to work until the servlet is fully loaded?
Thanks
Hi
You could try and move the 'helper code' from the servlet into the MDB. If you put the code into the ejbCreate() method of the MDB, you can be sure that the code gets executed before the MDB tries to process any messages from a JMS destination.
As far as I can see, this amounts to about the same thing as putting code that is required to run before a servlet's doGet() or doPost() method in the init() method of that servlet. I've done this before with good results.
Hope it helps
Daniel
Similar Messages
-
EJB 3.0 MDB deployment issue with weblogic 10.0
Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyushhere is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
activationConfig = { @ActivationConfigProperty(
propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush -
Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)
Hi,
I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
[10:57:54 AM] ---- Deployment started. ----
[10:57:54 AM] Target platform is (Weblogic 10.3).
[10:57:54 AM] Running dependency analysis...
[10:57:54 AM] Building...
[10:57:58 AM] Deploying profile...
[10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Preparing to send HTTP request for deployment
[10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
[10:57:59 AM] Sending internal deployment descriptor
[10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
[10:58:00 AM] Received HTTP response from the server, response code=500
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] HTTP error code returned [500]
[10:58:00 AM] Error message from server:
#;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
#;: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
[10:58:00 AM] Check server log for more details.
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] #### Deployment incomplete. ####
[10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
And the following is the SOA Server Side log file status:-
####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
{rootCauses=[]}
at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
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.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy314.load(Unknown Source)
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: BINDING.JCA-12600
Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
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.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy314.load(Unknown Source)
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Kindly help me in this regardSolution:
Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
For example:
From:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
To:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="BAPI_COMPANYCODE_GETDETAIL"/>
Regards,
Shaheer Badar -
Adobe Acrobat 9 Pro deployment issue
Hello. I am having a deployment issue with Adobe Acrobat 9 using Altiris. I create the rip which is bassically an image of the install. My facility has pruchased 50 seats for this software so I know we are covered for the users that we have to use this software. The issue that I am having after I make the rip, and deploy it to a machine it asks for the CD key again in order to use. Am I having an issue with my installation or is Adobe put some kind of security into their software so that when you try to make a rip of the installation is asks for teh CD Key again after the install? Is this an issue that can be resolved?
SOLUTION:
The issue was somehow related to DPI (START > Settings > Control Pannel > Display > Settings Tab > Advanced button). Eventhough the DPI was set to normal, I switched it to LARGE, restarted the machine, logged in after the reboot, changed it back to normal size, restarted again, logged in once more, checked the Printer Preferences and PRESTO --- a properly displayed window. -
Deploy issue from JDeveloper 10.1.3.5 to OAS 10.1.2
I have written an application using ADF on JDeveloper 10.1.3.5 and need to deploy it to our OAS 10.1.2. I have run the adfinstaller on the linux server to upgrade the ADF libraries to the correct versions, updated the web.xml files to have the correct versions, changed to J2SE 1.4.2_19 for the application and have still got deployment issues.
Error
An error occurred while redeploying application "FormsSiebelIntegration". See base exception for details.
Resolution:
See base exception for details.
Base Exception:
java.lang.UnsupportedClassVersionError
com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0). com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0)
Removing the jsf-impl.jar file allows the application to deploy, but when running on the app server I get the following errors:
OracleJSP: oracle.jsp.parse.JspParseException:
/codename.jspx: Line # 6, <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces" xmlns:afh="http://xmlns.oracle.com/adf/faces/html">
Help! I'm starting to have total mind block as to what to do next.
Error: Unable to load taghandler class: http://java.sun.com/jsf/htmlI had already applied all of this before trying to deploy.
The error seems to be a versioning error in the jsf-impl.jar file as the ApplicationAssociate class is found there. I have changed the JDK and J2EE to 1.4.2 and 1.3 respectively, rebuilt everything, updated all the settings to the right versions for 10.1.2 but it still keeps failing on the deploy. -
A very urgent deployment issue about DBAdapter
Hello All,
I have a very urgent deployment issue about DBAdapter.
That DBAdapter is connect to DB2 AS400 Database. I have a developing database (jdbc:as400://server01/TEST) and a production database (jdbc:as400://server01/PROD).
During developing, I used DBAdapter wizard to create it, and import some tables, and set the Adapter to use jabc/DB2DS as connection information for easily deployment later.
Then I deploy to Production. I configured Data-source.xml and oc4j-ra.xml rightly; I set DB connection point to production database. But the DBAdapter still write into developing Database.
I checked the DBAdapter, the imported tables are something like this, TEST.table1, TEST.table2. And there are a lot "TEST" located in DB2Writer_toplink_mapping.xml, DB2Writer.xml, TEST.schema, DB2Writer.table1.ClassDescriptor.xml.
This TEST is refrer to the TEST in connect String jdbc:as400://server01/TEST.
I think this might be the reason cause the problem. As to production database, "TEST" should replaced by "PROD". If I changed it manually, I have to change every time when switch between TEST and PROD. And I also don't know if it is safe to do it? (I tried, and bring some toplink mapping problem)
By the way, for Oracle Database, because we use 2 instances for testing and production with same schema name, and do not have this issue.
Anyone could help and many thanks.
Kerr
Message was edited by:
KerrHi Kerr,
The idea is to set up all connections in the BPEL or ESB services with logical names, e.g. typically of the form eis/DB/MyFinancialSystem or eis/DB/MyLogisticsSystem. This way, you do not have to modify code when deploying it onto different environments that serve different purposes.
When moving your services through their lifecyle, on every environment you deploy these to you will have the same logical connections configured on each instance, e.g. for DEV, QA, SIT, UAT and PROD. Only, in case of QA the actual physical connection is configured to point to the QA instance of the systems that your services interact with whereas in case of UAT it points to the UAT instance of the same system.
Maybe your problem is caused by connecting as user "SomeUser" when running the DB Adapter wizard during development and actually selecting objects from a different schema than you used to connect with, e.g. "Test" in your case.
Hth,
Sjoerd -
Hi Dale;
We have the similar situation. We wrote an application to be able to send
alert message before we shut down the Forte application. When we upgrade our
applications, we will send alert message to all users before we shut down the
Forte application through ECONSOLE which forces all users to log out, and then
overwrite the files.
Our client files are sitting at one of our network servers instead of
individual user's PC, so the user accesses the files through network. So we
are facing the same issue that we have to shut all users down before we
upgrade our applications. If you install those files on your individual user's
PC, you may try to use "compatible level" to update your application.
Hope this helps.
Lu Wang
Eli Lilly and Company
[email protected]My problem lies more in the way that we update the Forte software. We are
controlled enough with a new distribution from the application side that
there are not problems there.
My question is: how is everyone updating their client PC's from say Forte
R2 to R3. This was not a problem before because we didn't have very many
clients. Now we have quite a few and we can't just copy the proper files
because of the registry updates that are required.
Does anyone have any suggestions? Can I run the Forte client software off
the Novell server?
Thanks,
Tony
-----Original Message-----
From: Lu Wang X1 <[email protected]>
To: Dale V. Georg <[email protected]>
Cc: Forte Users <[email protected]>; Gardner, Steve
<[email protected]>
Date: Wednesday, November 19, 1997 11:17 AM
Subject: Re: Deployment Issues
You are right. Through econsole, we can only shut down the serverpartitions,
even though we can uninstall the application, as long as the clientpartition
is running, we can't overwrite the files. We were probably lucky that nouser
was running the application when we upgraded it.
Since our applications can capture the system alert message, probably wecan
make changes to our application to be able to shut itself down when it
receives certain type of alert message. Just a thought. Don't know ifthere
is any better way to handle it.
Lu
"Dale V. Georg" <[email protected]> on 11/19/97 03:02:27 AM
Please respond to "Dale V. Georg" <[email protected]>
To: Lu Wang X1/AM/LLY
cc: Forte Users <[email protected]>, "Gardner, Steve"
<[email protected]>
Subject: Re: Deployment Issues
On Tue, 18 Nov 1997 11:04:53 -0500, Lu Wang X1 wrote:
Hi Dale;
We have the similar situation. We wrote an application to be able to send
alert message before we shut down the Forte application. When we upgradeour
applications, we will send alert message to all users before we shut down
the
Forte application through ECONSOLE which forces all users to log out, andthen
overwrite the files.If I remember correctly, econsole will only forcibly close down the
server partitions, not the client partitions.
Our client files are sitting at one of our network servers instead of
individual user's PC, so the user accesses the files through network. So
we
are facing the same issue that we have to shut all users down before we
upgrade our applications. If you install those files on your individualuser's
PC, you may try to use "compatible level" to update your application.We did think about using the compatibility level at one point, but that
introduces extra maintenence whenever a new version of the application
is rolled out. On the other hand, if that's the cost of a smooth and
reliable upgrade, then it may be worth paying.
Dale
================================================
Dale V. Georg
Systems Analyst
Indus Consultancy Services
[email protected]
================================================ -
when i put MDB deployment jar file in JBOSS deploy folder i am getting
these exception.
11:10:46,765 WARN [JMSContainerInvoker] JMS provider failure detected:
javax.jms.JMSException: Error creating the dlq connection: XAConnectionFactory not bound
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:171)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:542)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:764)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.onException(JMSContainerInvoker.java:1267)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$1.run(JMSContainerInvoker.java:776)According to ur deployment descriptors u have to create QueueConnectionFactory and Queue .
-
Hi,
i am using jdev Studio Edition Version 11.1.1.4.0
I have created EAR of my application and trying to depoly it on Weblogic server.
I have following entry in weblogic-application.xml
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
[03:12:39 PM] ---- Deployment started. ----
[03:12:39 PM] Target platform is (Weblogic 10.3).
[03:13:07 PM] Retrieving existing application information
[03:13:07 PM] Running dependency analysis...
[03:13:07 PM] Building...
[03:13:28 PM] Deploying 3 profiles...
[03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
[03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
[03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
[03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
[03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
[03:13:55 PM] Entering Oracle Deployment Plan Editor
[03:15:53 PM] Deploying Application...
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
[03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
[03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
*[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
[03:16:41 PM] See server logs or server console for more details.
[03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
[03:16:41 PM] #### Deployment incomplete. ####
[03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I am getting above exception while i am trying to depoly the my ear. please see bold lines.
Please give me some guide line .
Regards,
Kiran.Hi John,
Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
For my installations:
On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
Thank you,
Gavin
Edited by: GavinWoods on Feb 14, 2012 6:25 AM -
EPMA Deployment Issues (Rollback Database)
I have seen some posts where users were able to rollback their EPMA databases. This could be helpful when running into deployment issues. Can anyone outline the steps that are needed to rollback an EPMA database?
Thank youspring_patel wrote:
i really appreciate you trying to solve my problem..
but i think...my estion is fairly simple and straight forward...and i've provided every detail of my problem(if uv'e read my opening post of this thread)....
and as far as that link goes...i've already checked it b4 u guys mentioned it... as it is provided right there in the tutorial i've provided link of...
and i've tried my options b4 making use of this forum...and i didnt find a solution that's why i'm taking ur help..
nevertheless...i repeat my question...
there's a tutorial at this link...[http://www.netbeans.org/kb/docs/java/gui-db.html]...in it is described how to create a java desktop database applicaiton...
at the end of the tuorial there is a section called: "Building and Deploying the Application"
in that section they have instructed to exit netbeans IDE and try and run the application outside it...which is not happening
the reason they say is that i've to start Java DB from outside of the IDE...that is wat my problem is ..
i dont know how to start Java DB from outside the Netbeans ide...You are not telling us anything.
If I tell you "my automobile doesn't work" how do you know what is wrong. Instead I need to tell you one of the following.
1. The engine didn't start.
2. The wheel fell off.
3. The engine caught fire.
4. When I went to the driveway the car wasn't even there.
When you "run" something then something happens. When I run notepad from a console window if notepad is not in the path then I will get an error about command not found. if it is in the path then the command executes and notepad pops up. Even if I don't see notepad pop up I know that the command seemed to execute from the command window.
The above are examples of describing what you did and what did happen. In detail.
"It doesn't work" provides neither detail about how you ran it nor what did happen when you did attempt to run it. -
Deployment issue: compatiblity issue with ODP, instant vs full client on PC
After a lot of deployment issues with full client, we thought we had the solution with Instant Client.
It worked great for a while, but now some of our users have full Oracle 11 client installed after installing our Instant Client because of other software that requires full client.
As soon as they install full client, our Instant Client breaks:
Exception has been thrown by the target of an invocation. (mscorlib)
The type initializer for 'Oracle.DataAccess.Client.OracleClientFactory' threw an exception.
The provider is not compatible with the version of Oracle client (Oracle Data Provider for .NET)
Our instant client is compiled with 2.111.6.20, the client is installing a different version (though I tried installing exactly same version does not seem to work either)
I've been experimenting to redirect the version to another assembly but no success.
How can I make Instant Client and Full client co-exist? The whole idea of using Instant was to be independent of other software who needs ODP.NET...
What do you do when 2 apps need different versions of ORacle ODP.NET (e.g. 2.111.6.0 vs. 2.112.1.0)?
Note that I don't have source code access to "our" app, so if it is at all possible through configuration, that is a prefered solution.
I also don't control our customers deployment strategy, they roll out apps over 1000's of PC'sAccording to documentation at [http://docs.oracle.com/cd/E20434_01/doc/win.112/e23174/featConfig.htm]
>
Configuration File Support
For customers who have numerous applications on a computer that depends on a single version of ODP.NET, the Windows Registry settings for a given version of ODP.NET may not necessarily be applicable for all applications that use that version of ODP.NET. To provide more granular control, ODP.NET Configuration File Support allows developers to specify ODP.NET configuration settings in an application config, web.config, or a machine.config file.
If a computer does not require granular control beyond configuration settings at the ODP.NET version level, there is no need to specify ODP.NET configuration settings through configuration files.
The following is an example of a web.config file for .NET Framework 2.0 and higher:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<oracle.dataaccess.client>
<settings>
<add name="DllPath" value="C:\oracle\bin"/>
<add name="FetchSize" value="131072"/>
<add name="PromotableTransaction" value="promotable"/>
<add name="StatementCacheSize" value="10"/>
<add name="TraceFileName" value="C:\odpnet2.trc"/>
<add name="TraceLevel" value="63"/>
<add name="TraceOption" value="1"/>
</settings>
</oracle.dataaccess.client>
</configuration> -
i have an MDB deployed to a weblogic cluster(weblogic10).
My requirement is i need MDB failover in case one server goes down. so i have no choice of deploying the MDB to any of the manged server. i ahve set the maximum pool size as 1 for MDB,but the MDB is instantiated from each managed server. I need only one MDB to service the queue ,but needs failover in case the any of the servere fails. Any option to do this in weblogic server.If not possible by waht way i can accomplish this task.Is there any special reason why you only want one MDB to consume messages fro the queue?
-
EJB deployment issue in websphere
EJB deployment issue in websphere
I have created an EJB project in eclipse and created a stateless session bean successfully.
I created Enterprise application project and added the EJB project.
I tried to check it using Universal test client.
When I click the JNDI explorer>>sample.HelloWorldEJBHome
I get error IWAD0401E Unknown type of JNDI object
But when I install an EJB jar using administrator console after exporting the jar file for the EJB project
It is working file
I like to reduce the number of steps by right clicking the server publish and test.
Do any one have come across the same issue please help me
Thanks in advance.Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their. -
MDB Deployment Problem in JBoss 4.0.3SP1
Hi All,
I am upgrading my App Server from JBoss 323 to JBoss 403.
I had some MDBs, that are running successfully in JBoss 323.
But when I tried to redeploy them(after recompiling with jdk1.5), I am facing few issues with them.
First of all, I have a MDB whose destination was in some other Jboss server instance. That means I am trying to connect my destination "Queue" as remotely. At that time it is thorowing exception like as follows at my server startup time.......
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/Server1JMSProvider
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JNDIProviderAdapter@20dcb7
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory: org.jboss.mq.SpyXAConnectionFactory@1ebe8ec
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection: Connection@10751758[token=ConnectionToken:null/b3e21fe26fd3b44f4a0c5bb69995e669 rcvstate=STOPPED]
2006-04-17 07:17:15,472 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: QUEUE.DLQ
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@106989e
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: [u]xxxQueue[/u]
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for LifecycleMDB
2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory: org.jboss.mq.SpyXAConnectionFactory@1ebe8ec
2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/null
2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created XAQueueConnection: Connection@13605872[token=ConnectionToken:null/ea8d256e12a297e358803b37d7bfee4d rcvstate=STOPPED]
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
2006-04-17 07:17:15,488 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not find the queue destination-jndi-name=queue/[u]xxxQueue[/u]
2006-04-17 07:17:15,488 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destination not found: queue/[u]xxxQueue[/u] reason: javax.naming.NameNotFoundException: [u]xxxQueue[/u] not bound
2006-04-17 07:17:15,488 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] creating a new temporary destination: queue/[u]xxxQueue[/u]
2006-04-17 07:17:15,488 DEBUG [org.jboss.mq.server.jmx.DestinationManager] Attempting to create destination: jboss.mq.destination:service=Queue,name=xxxQueue; type=org.jboss.mq.server.jmx.Queue
2006-04-17 07:17:15,488 INFO [org.jboss.mq.server.jmx.Queue.xxxQueue] Registration is not done -> stop
2006-04-17 07:17:15,488 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected:
org.jboss.deployment.DeploymentException: Error during queue setup; - nested throwable: (javax.management.MBeanException)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)My jboss.xml was
<jboss>
<enterprise-beans>
<message-driven>
<ejb-name>LifecycleMDB</ejb-name>
<destination-jndi-name>queue/xxxQueue</destination-jndi-name>
<invoker-bindings>
<invoker>
<invoker-proxy-binding-name>server1-message-driven-bean</invoker-proxy-binding-name>
</invoker>
</invoker-bindings>
<resource-ref>
<res-ref-name>jms/QueueFactory</res-ref-name>
<jndi-name>UIL2XAConnectionFactory</jndi-name>
</resource-ref>
</message-driven>
</enterprise-beans>
<invoker-proxy-bindings>
<invoker-proxy-binding>
<name>server1-message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>Server1JMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<CreateJBossMQDestination>true</CreateJBossMQDestination>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
</invoker-proxy-bindings>
</jboss>and my deployment file consist of the following code
<server>
<!-- The JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=Server1MQProvider">
<attribute name="ProviderName">Server1JMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>
<!-- The combined connection factory -->
<attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
<!-- The queue connection factory -->
<attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
<!-- The topic factory -->
<attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
<!-- Uncomment to use HAJNDI to access JMS-->
<attribute name="Properties">
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=jnp://SERVER:1499
</attribute>
</mbean>
</server>Did you find a solution to this problem?
-
Application Deployment Issue on JBoss 4.2.3
Hi,
I am trying to deploy a Java Application on JBoss 4.2.3 AS. This application run seamlessly on JBoss 3.0.5. After deploying, I could see errors below.
Could any one please suggest what could be the issue? Were there any changes in the deployment file structure? Please advice.
Thanks,
2009-09-29 15:43:41,112 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/ejb-management.jar
org.jboss.deployment.DeploymentException: expected one container-name tag
2009-09-29 15:43:41,128 ERROR [org.jboss.deployment.MainDeployer] DeploymentException while trying to deploy a package with a new deployer
org.jboss.deployment.DeploymentException: expected one container-name tag
2009-09-29 15:43:41,165 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/jmx-ejb-adaptor.jar
org.jboss.deployment.DeploymentException: expected one container-name tag
2009-09-29 15:43:41,177 ERROR [org.jboss.deployment.MainDeployer] DeploymentException while trying to deploy a package with a new deployer
org.jboss.deployment.DeploymentException: expected one container-name tag
2009-09-29 15:43:41,198 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/notification-listener.jar
org.jboss.deployment.DeploymentException: expected one container-name tag
2009-09-29 15:43:41,208 ERROR [org.jboss.deployment.MainDeployer] DeploymentException while trying to deploy a package with a new deployer
org.jboss.deployment.DeploymentException: expected one container-name tag
2009-09-29 15:43:41,256 ERROR [org.jboss.system.server.Server] Root deployment has missing dependencies; continuing
Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@cad26b26 { url=file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/ejb-management.jar }
deployer: org.jboss.ejb.EJBDeployer@ab835a
status: Deployment FAILED reason: expected one container-name tag
state: FAILED
watch: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/ejb-management.jar
altDD: null
lastDeployed: 1254203021081
lastModified: 1254203019961
mbeans:
org.jboss.deployment.DeploymentInfo@7888101a { url=file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/jmx-ejb-adaptor.jar }
deployer: org.jboss.ejb.EJBDeployer@ab835a
status: Deployment FAILED reason: expected one container-name tag
state: FAILED
watch: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/jmx-ejb-adaptor.jar
altDD: null
lastDeployed: 1254203021154
lastModified: 1254203020008
mbeans:
org.jboss.deployment.DeploymentInfo@8d818653 { url=file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/notification-listener.jar }
deployer: org.jboss.ejb.EJBDeployer@ab835a
status: Deployment FAILED reason: expected one container-name tag
state: FAILED
watch: file:/D:/Java/jboss-4.2.3.GA/server/grmbs/deploy/notification-listener.jar
altDD: null
lastDeployed: 1254203021190
lastModified: 1254203020008
mbeans:
--- MBeans waiting for other MBeans ---
ObjectName: jboss:service=invoker,type=jrmp
State: FAILED
Reason: java.lang.AbstractMethodError: org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(Ljava/lang/String;)V
I Depend On:
jboss:service=TransactionManager
ObjectName: jboss:service=invoker,type=http
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss:service=invoker,type=httpHA
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss:service=invoker,type=http,target=Naming
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss:service=invoker,type=http,target=Naming,readonly=true
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss.jca:service=LocalTxCM,name=hsqldbDS
State: CONFIGURED
I Depend On:
jboss.jca:service=LocalTxDS,name=hsqldbDS
jboss.jca:service=LocalTxPool,name=hsqldbDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss.jca:service=RARDeployer
ObjectName: jboss.jca:service=LocalTxDS,name=hsqldbDS
State: CONFIGURED
I Depend On:
jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
jboss:service=Hypersonic
Depends On Me:
jboss.jca:service=LocalTxCM,name=hsqldbDS
ObjectName: jboss.jca:service=XaTxCM,name=jmsra
State: CONFIGURED
I Depend On:
jboss.jca:service=RARDeployer
jboss.jca:service=XaTxDS,name=jmsra
jboss.jca:service=XaTxPool,name=jmsra
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
ObjectName: jboss.jca:service=XaTxDS,name=jmsra
State: CONFIGURED
I Depend On:
jboss.jca:service=RARDeployment,name=JMS Adapter
Depends On Me:
jboss.jca:service=XaTxCM,name=jmsra
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=RARDeployment,name=JMS Adapter
State: NOTYETINSTALLED
Depends On Me:
jboss.jca:service=XaTxDS,name=jmsra
ObjectName: jboss:service=invoker,type=http
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss:service=invoker,type=http,target=Naming,readonly=true
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss:service=invoker,type=jrmp
State: FAILED
Reason: java.lang.AbstractMethodError: org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(Ljava/lang/String;)V
I Depend On:
jboss:service=TransactionManager
ObjectName: jboss:service=invoker,type=http,target=Naming
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;
ObjectName: jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
State: NOTYETINSTALLED
Depends On Me:
jboss.jca:service=LocalTxDS,name=hsqldbDS
ObjectName: jboss:service=invoker,type=httpHA
State: FAILED
Reason: java.lang.NoSuchMethodError: org.jboss.util.Strings.replaceProperties(Ljava/lang/String;)Ljava/lang/String;continued....
<!-- ==================================================================== -->
<!-- Security -->
<!-- ==================================================================== -->
<mbean code="org.jboss.security.plugins.SecurityConfig"
name="jboss.security:name=SecurityConfig">
<attribute name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute>
</mbean>
<mbean code="org.jboss.security.auth.login.XMLLoginConfig"
name="jboss.security:service=XMLLoginConfig">
<attribute name="ConfigResource">login-config.xml</attribute>
</mbean>
<!-- JAAS security manager and realm mapping -->
<mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
name="jboss.security:service=JaasSecurityManager">
<attribute name="SecurityManagerClassName">
org.jboss.security.plugins.JaasSecurityManager
</attribute>
</mbean>
<!-- ==================================================================== -->
<!-- Transactions -->
<!-- ==================================================================== -->
<mbean code="org.jboss.tm.XidFactory"
name="jboss:service=XidFactory">
</mbean>
<mbean code="org.jboss.tm.TransactionManagerService"
name="jboss:service=TransactionManager">
<attribute name="TransactionTimeout">300</attribute>
<depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
</mbean>
<!--
| Uncomment to use Tyrex (tyrex.exolab.org) transaction manager plugin
| instead of the org.jboss.tm.TransactionManagerService and comment out
| the TransactionManagerService above.
| Make sure you have Xerces in lib/. At the moment JBoss does not
| ship Xerces as part of distribution. Version 1.x seems to work fine,
| though 2.x should as well, use whichever you like.
|
<mbean code="org.jboss.tm.plugins.tyrex.TransactionManagerService"
name="jboss:service=TransactionManager">
<attribute name="ConfigFileName">../conf/default/domain.xml</attribute>
</mbean>
-->
<!--commented to run grmbs on JBoss 4.2.3, comment removed -->
<mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
name="jboss:service=ClientUserTransaction">
</mbean>
<!-- The CachedConnectionManager is used partly to relay started UserTransactions to
open connections so they may be enrolled in the new tx-->
<mbean code="org.jboss.resource.connectionmanager.CachedConnectionManager" name="jboss.jca:service=CachedConnectionManager">
</mbean>
<!-- ==================================================================== -->
<!-- The deployers... -->
<!-- ==================================================================== -->
<!-- Main Deployer and SARDeployer are provided by main -->
<!-- EJB deployer, remove to disable EJB behavior-->
<mbean code="org.jboss.ejb.EJBDeployer" name="jboss.ejb:service=EJBDeployer">
<attribute name="VerifyDeployments">true</attribute>
<attribute name="ValidateDTDs">false</attribute>
<attribute name="MetricsEnabled">false</attribute>
<attribute name="VerifierVerbose">true</attribute>
<!-- Add a dependency on the JMS provider(jms-service.xml) for MDBs. If
you are not using MDBs and JMS remove these.
-->
<depends>jboss.mq:service=JMSProviderLoader,name=JBossMQProvider</depends>
<depends>jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool</depends>
</mbean>
<!-- EAR deployer -->
<mbean code="org.jboss.deployment.EARDeployer" name="jboss.j2ee:service=EARDeployer">
</mbean>
<!-- WAR Deployer is provided by tomcat or jetty -->
<!-- RAR Deployer is provided by the rar.sar package -->
<!-- Uncomment to activate the BeanShell script sub-deployer -->
<!--mbean code="org.jboss.varia.deployment.BeanShellSubDeployer"
name="jboss.scripts:service=BSHDeployer">
</mbean-->
<!-- ==================================================================== -->
<!-- JBoss Server Management -->
<!-- ==================================================================== -->
<!-- ==================================================================== -->
<!-- Monitoring and Management -->
<!-- ==================================================================== -->
<!-- Uncomment to enable JMX monitoring of the entity bean locking
<mbean code="org.jboss.monitor.EntityLockMonitor"
name="jboss.monitor:name=EntityLockMonitor"/>
-->
<!-- ==================================================================== -->
<!-- Invokers to the JMX node -->
<!-- ==================================================================== -->
<!-- RMI/JRMP invoker -->
<mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
name="jboss:service=invoker,type=jrmp">
<attribute name="RMIObjectPort">4444</attribute>
<attribute name="ServerAddress">${jboss.bind.address}</attribute>
<attribute name="RMIClientSocketFactory">custom</attribute>
<attribute name="RMIServerSocketFactory">custom</attribute>
<attribute name="RMIServerSocketAddr">custom</attribute>
<!-- Added as per JBoss 4.2.3 Server defaults, starts -->
<depends>jboss:service=TransactionManager</depends>
<!-- Added as per JBoss 4.2.3 Server defaults, ends -->
</mbean>
<mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
name="jboss:service=invoker,type=pooled">
</mbean>
<mbean code="org.jboss.invocation.local.LocalInvoker"
name="jboss:service=invoker,type=local">
</mbean>
<!-- ==================================================================== -->
<!-- Deployment Scanning -->
<!-- ==================================================================== -->
<!-- Uncomment to enable caching of deployment units
<mbean code="org.jboss.deployment.cache.FileDeploymentStore"
name="jboss.deployment:type=DeploymentStore,flavor=File">
<attribute name="DirectoryName">data/deployment-cache</attribute>
</mbean>
<mbean code="org.jboss.deployment.cache.DeploymentCache"
name="jboss.deployment:type=DeploymentCache">
<depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
<depends optional-attribute-name="Store">jboss.deployment:type=DeploymentStore,flavor=File</depends>
</mbean>
-->
<!-- An mbean for hot deployment/undeployment of archives.
-->
<mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
name="jboss.deployment:type=DeploymentScanner,flavor=URL">
<!-- Uncomment (and comment/remove version below) to enable usage of the
DeploymentCache
<depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends>
-->
<depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
Maybe you are looking for
-
Hi there, I'm trying to install the trial version of Fireworks CS4 on my laptop. I keep on getting the error message "Please insert CD". I've Googled this problem, and one sugestion was to delete the "<Media></Media>" tags in the Setup.xml file. Tr
-
Need to embed document (xls, doc) to InfoView dashboard
Tell me please is it possible to embed xls (from MS Excel) or doc (from MS Word) file to InfoView dashboard with dashboard builder? The file is published - it is placed in InfoView directory structure. Thanks, Olga
-
Download error. Tap to retry. on iTunes match
I have been using iTunes Match for a couple of weeks now with an iPhone 4S and I am severly disappointed. There are a couple of tracks (that I've noticed, at least) which I purchased from iTunes, but when I try to load them into my iPhone 4S I repeat
-
CS4 Reduce Image Size w/out increased density
I worked on a poster graphic in a larger 8-1/2 x 11 size. Now I have to reduce the size for basic logo size item of about 3" or so. Still fairly new to Illustrator and can't figure out how to reduce the size of the graphic without increasing the dens
-
Data not set when class is called
can some one help me identify the mistake i made when i called new RMStorage("b1", 20000) in a file which is located at a subfolder of where this RMStorage.class is saved), the object is created, but given name=null and quantity=0. thanks in advance.