XA Connection Factory
Not sure if this should be posted here or in the "Management" topic:
It seems that when creating a connection factory (and accepting all default values),
setting the "XAConnection Factory Enabled" checkbox results in an exception (see
attached error.txt).
ONLY, if the following order is followed, will the setting of this value succeed:
1) "User Transactions Enabled" is checked.
2) Click "Apply".
3) settting "XAConnection Factory Enabled" checked
4) Click "Apply".
If done in any other order (ie setting both at the same time) it will result in the
attached error.
I am not sure if I have missed something...
Cheers,
Nick
[error.txt]
Cheers,
Thanks.
Rajesh Mirchandani <[email protected]> wrote:
>Follow up with [email protected] and refer CR078549.
>
>Nick Minutello wrote:
>
>> Not sure if this should be posted here or in the "Management" topic:
>>
>> It seems that when creating a connection factory (and accepting all default
>values),
>> setting the "XAConnection Factory Enabled" checkbox results in an exception
>(see
>> attached error.txt).
>>
>> ONLY, if the following order is followed, will the setting of this value
>succeed:
>> 1) "User Transactions Enabled" is checked.
>> 2) Click "Apply".
>> 3) settting "XAConnection Factory Enabled" checked
>> 4) Click "Apply".
>>
>> If done in any other order (ie setting both at the same time) it will
>result in the
>> attached error.
>>
>> I am not sure if I have missed something...
>>
>> Cheers,
>> Nick
>>
>> ------------------------------------------------------------------------
>> Name: error.txt
>> error.txt Type: Plain Text (text/plain)
>> Encoding: base64
>
>--
>Rajesh Mirchandani
>Developer Relations Engineer
>BEA Support
>
>
Similar Messages
-
Connection pool and Connection factory difference?
Hi,
Can someone clarify the difference between connection pool and connection factory.
I know connection pool is some thing like a pool of database connection manitained at one place so that an application or client can use it when it requires.
Then wat exactly is connection factory..say in 10g we always put a connection factory name in all adapters and acces the data sources like DB ,FTP,AQ ..etc
can someone clarify??
regards,To conserve system resources and to improve the performance of transactional applications, WebLogic allows you to define a pool of client connections (generally database but may be a FTP,FILE etc. as well)
A Connection Factory object encapsulates a set of connection configuration parameters that has been defined by an administrator. A client uses it to create a connection with a service provider (generally JMS).
Regards,
Anuj -
Problem with transacted JMS connection factory and transaction timeouts
We encountered an interesting problem using transacted JMS connection factories.
An EJB starts a container managed transaction and tries to validate a credit card
before creating some information to a database for the user, in case of success
an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
duration is about the same as the transactions timeout (in this case the default
30 seconds) sometimes the database inserts is committed but the JMS insert is
rollbacked. How can this be?
If the authorization duration is much longer than 30 seconds everything works
fine (both database and JMS inserts rollbacked), the same is true if a rollback
is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
if the duration is approximately the same as the transaction timeout, it appears
that the database insert is not timeouted but the JMS insert is. How can this
be if they are both participating in the same transaction.
The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
is the same also with the default "javax.jms.QueueConnectionFactory" and if we
configure our own factory with user transactions enabled.
Any help appreciated!
Tomas Granö wrote:
> We encountered an interesting problem using transacted JMS connection factories.
> An EJB starts a container managed transaction and tries to validate a credit card
> before creating some information to a database for the user, in case of success
> an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
> duration is about the same as the transactions timeout (in this case the default
> 30 seconds) sometimes the database inserts is committed but the JMS insert is
> rollbacked. How can this be?
It should not be.
>
> If the authorization duration is much longer than 30 seconds everything works
> fine (both database and JMS inserts rollbacked), the same is true if a rollback
> is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
> if the duration is approximately the same as the transaction timeout, it appears
> that the database insert is not timeouted but the JMS insert is. How can this
> be if they are both participating in the same transaction.
>
> The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
> is the same also with the default "javax.jms.QueueConnectionFactory" and if we
> configure our own factory with user transactions enabled.
>
> Any help appreciated!
Make sure that your session is not "transacted". In other words,
the first parameter to createSession() must be false. There is an
unfortunate name re-use here. If a session is "transacted", it
maintains an independent "inner transaction" independent of the
outer transaction. From the above description, it seems unlikely
that your application has this wrong, as you say that
"setRollbackOnly" works - but please check anyway.
Make sure that you are using a true XA capable driver and database
(XA "emulation" may not suffice)
Beyond the above, I do not see what can be going wrong. You
may want to try posting to the transactions and jdbc newsgroups. Note
that JMS is appears to be exhibiting the correct behavior, but the
JDBC operation is not. The JDBC operation appears to have
its timeout independent of the transaction monitor's timeout.
Tom
-
JMS proxy and XA connection factory
Hi all,
I would like to ask you what is the best practice to adopt about the scenario described below.
A JMS proxy retrieves a message and processes it.
Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
(later another app will check failed messages for fixing & republishing them into ALSB).
In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
Or XA connection factory is not needed and could I use
Routing Options with exactly once or both are needed ?
Thanks
ferpHi all,
I did some tests and follow what I've achieved.
Scenario 1.
- Precondition
-- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
-- A business service BS with XA factory that publishes into MyOutboundQueue
-- No "exactly once" routing option used calling BS
-- an error is forced in the pipeline
- Flow
-- proxy retrieves a message and try to publish it using BS
-- an error is forced in the pipeline:
--- transaction is rolled back, message redelivered to proxy
--- the message is posted to the error destination after all the retries failed
Scenario 2.
- Precondition
-- As 1. but no error is forced in the pipeline
-- the MyOutboundQueue destination queue is paused
- Flow
-- proxy retrieves a message and try to publish it using BS
-- BS fails to publish it on MyOutboundQueue (because it is paused)
--- transaction is rolled back, message redelivered to proxy
--- the message is posted to the error destination after all the retries failed
Scenario 2A.
- Precondition
-- As 2. with MyOutboundQueue paused and resumed
- Flow:
-- proxy retrieves a message and try to publish it using BS
-- BS fails to publish it on MyOutboundQueue (because it is paused)
--- transaction is rolled back, message redelivered to proxy
--- before all the retries failed the queue is resumed
--- BS succeeds to publish the message
Scenario 3.
- Precondition
-- A JMS proxy with NO XA factory + Error Destination
-- A business service BS with NO XA factory
-- No "exactly once" routing option used calling BS
-- an error is forced in the pipeline
- Flow
-- proxy retrieves a message and try to publish it using BS
-- an error is forced in the pipeline:
--- transaction is NOT rolled back, message NOT redelivered to proxy
-- so
--- no message delivered to MyOutboundQueue2 destination
--- no message delivered to MyRecoveryQueue2 destination
--- message consumed from MyQueue2 and now is lost!
To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
So both my proxy service and business service use an XA factory.
Regards
ferp -
2013-06-24 21:16:28,551 [bxapp2.healthnet.com] [ STANDARD] [ ] (l.access.RuleCandidateIterator) INFO - Single candidate rule resolution optimization is enabled
Error retrieving JNDI initial context:
2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [ STANDARD] [ ] ( pegarules.resadap.RAClient) ERROR - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
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:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
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 com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
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 com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
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.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
... 94 more
2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [ STANDARD] [ ] (tener.ListenerStateManagerImpl) ERROR - Unexpected exception.
java.lang.NullPointerException
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
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 com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
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 com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
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.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [ STANDARD] [ ] ( internal.async.Agent) INFO - Agents will be executed via the enterprise tier.
2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [ STANDARD] [ ] ( internal.async.Agent) INFO - Passivation will be done on a per-page basis.
2013-06-24 21:16:30,023 [bxapp2.healthnet.com] [ STANDARD] [ ] ( pegarules.resadap.RAClient) ERROR - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
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:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
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 com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
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.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
... 84 more
2013-06-24 21:16:30,038 [bxapp2.healthnet.com] [ STANDARD] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:387)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
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 com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
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.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1045)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
... 60 more
Caused by: java.lang.reflect.InvocationTargetException
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 com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
... 62 more
Caused by: java.lang.NullPointerException
at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
... 67 more
2013-06-24 21:16:30,051 [bxapp2.healthnet.com] [ STANDARD] [ ] ( etier.impl.EngineStartup) INFO - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
2013-06-24 21:16:30,164 [bxapp2.healthnet.com] [ STANDARD] [ ] (ervlet.WebAppLifeCycleListener) ERROR - Enterprise tier failed to initialize properly, PegaRULES not available
2013-06-24 21:16:30,190 [bxapp2.healthnet.com] [ STANDARD] [ ] (ervlet.WebAppLifeCycleListener) INFO - Web Tier initialization is complete.
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 167.238.162.41:8008 for protocols iiop, t3, ldap, snmp, http.>
<Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "pegamanaged2" for domain "sbxdomain8" running in Production Mode>
<Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>Greetings,
javax.naming.NameNotFoundException. Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound
=================
Below is the line of my LoginServlet class which is
referred to in the stack trace - Object object =
context.lookup
( "java:comp/env/ejb/WarehouseClerk" );The root of the naming context is 'java:comp/env' and this is where lookup automatically begins for EJBs and resources. IOW, by specifying "java:comp/env/ejb/WarehouseClerk" as the EJB lookup name the server is actually treating this as "java:comp/env/java:comp/env/ejb/WarehouseClerk". Specify only the ejb context ("ejb/WarehouseClerk") in your lookup and you should be fine.
Any help would be most appreciated.
SeanRegards,
Tony "Vee Schade" Cook -
Error when creating a new JMS connection factory in GlassFish V3 b57
When I use the admin console and try to create a new JMS connection factory in GlassFish V3 b57, the operation fails with the error message
An error has occurred: Can't find ConfigModel.Property for attr -connection-validation-required on interface com.sun.enterprise.config.serverbeans.ConnectorConnectionPool
Should I better report this in the GlassFish news forum (http://forums.java.net/jive/forum.jspa?forumID=56&start=0)?
p.s. I launch the admin console from within NetBeans 6.7.1 (the server started before the IDE). WIth version b 56, creating a JMS connection factory worked fine.
Best regards,
Michael JustinThis bug does not apear in the nightly build (b58) now so everything looks fine again.
Greetings,
Michael -
Error in looking up the JMS Connection Factory
Hi,
I am using weblogic6.1. I created a JMS Connection factory from administrator
console with the name QueueConnectionFactory..But when i restart the server and
try to look up that factory its giving an NameNotFoundException...This is the
entry of the factory in config.xml
<JMSConnectionFactory JNDIName="QueueConnectionFactory"
Name="QueueConnectionFactory" Targets="myserver"/>
But if i change reapply the target server to myserver from admin console whenever
restart the server it works fine..
I dont know where is the problem..Can u please update me on the problem if u people
have any idea.
The trace of the exceptions i got is as below:
java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
resolve QueueConnectionFactory. Resolved
: '' Unresolved:'QueueConnectionFactory' ; remaining name ''
java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to resolve
QueueConnectionFactory. Resolved: '' Unr
esolved:'QueueConnectionFactory' ; remaining name ''
Thanx
Regards,
Narayan
Hi Zach,
No, I dont think ur interpretation is right..Once the entry corresponding
to JMS Connection Factory is there in config.xml, the server should automatically
bind it at the time of booting.. right. Why should this administrator server come
into the picture.
Thanx
"Zach" <[email protected]> wrote:
>Don't know. Sounds like the admin server is not notifying JMS of the
>changes under certain situations. You might post in the management.console
>newsgroup.
>
>_sjz.
>
>"Narayan" <[email protected]> wrote in message
>news:[email protected]...
>>
>> Hi,
>> I am using weblogic6.1. I created a JMS Connection factory from
>administrator
>> console with the name QueueConnectionFactory..But when i restart the
>server and
>> try to look up that factory its giving an NameNotFoundException...This
>is
>the
>> entry of the factory in config.xml
>>
>> <JMSConnectionFactory JNDIName="QueueConnectionFactory"
>> Name="QueueConnectionFactory" Targets="myserver"/>
>> But if i change reapply the target server to myserver from admin console
>whenever
>> restart the server it works fine..
>> I dont know where is the problem..Can u please update me on the problem
>if
>u people
>> have any idea.
>> The trace of the exceptions i got is as below:
>> ****************
>> java.rmi.RemoteException: javax.naming.NameNotFoundException:
>Unable to
>> resolve QueueConnectionFactory. Resolved
>> : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
>> java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable
>to
>resolve
>> QueueConnectionFactory. Resolved: '' Unr
>> esolved:'QueueConnectionFactory' ; remaining name ''
>>
>> **********************
>>
>> Thanx
>> Regards,
>> Narayan
>>
>>
>
>
-
How to access local connection factory created within Foreign Server in OSB
Hi All
I am facing an issue in my config plan. We have a RIB Foreign server with the following local connection factory:
jms/RibAqJmsXATopicConnectionFactory
I am using the below in my configuration plan:
<cus:envValueAssignments>
<xt:envValueType>Service URI</xt:envValueType>
<xt:location xsi:nil="true"/>
<xt:owner>
<xt:type>ProxyService</xt:type>
<xt:path>RLTPReturnToWarehouse/ProxyServices/ConsumeRIBRTWMessages</xt:path>
</xt:owner>
<xt:value xsi:type="xs:string" xmlns:xs="http://www.w3.org/2001/XMLSchema">jms://localhost:7001/jms.RibAqJmsXATopicConnectionFactory/jms.etASNInFromRIBToWH1</xt:value>
</cus:envValueAssignments>
and i am getting the below error:
[java]
[java] Loading customization File ./dev/OSBCustomizationFile.xml
[java] Customization applied to the created resources only []
[java] com.bea.wli.config.customization.EnvValueCustomization@553c13
[java] Unexpected error: com.bea.wli.sb.transports.TransportException
[java] Problem invoking WLST - Traceback (innermost last):
[java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 200, in ?
[java] File "D:\VFUKScripts\DeploymentScripts\osb\import.py", line 122, in importToALSBDomain
[java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
what am i missing here?[java] com.bea.wli.sb.transports.TransportException: Failed to lookup connection factory jms.RibAqJmsXATopicConnectionFactory
Looks like the JNDI that you created for the ConnectionFactory is not reflected in the server.
Login to WLS Console> Summary of Servers > server_name > View JNDI Tree
Browse to the JNDI tree and see if your JNDI is visible there. If it is not then, please restart the server and recheck.
Once you are able to find it in the JNDI tree, then execute the customization file.
If you have modified the existing JNDI properties (that have a small exclamatory symbol) then any changes to those are not reflected till all the servers in the cluster are restarted.
If it still does not work, then recreate a new Connection with a different name and then retry. It should work then.
Thanks,
Patrick -
10.1.3.4 - db Adapter connection factory has been stopped.
I created a process which had a custom sql operation to read data from a db table. It was working fine, but now I am getting a weird error
file:/apps/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_SiebelRMAShipmentIn_bpel_1.0_d9f7e6fe5e3f4daf12e5a856c48d4ff9.tmp/getShipmentRecords.wsdl [ getShipmentRecords_ptt::getShipmentRecords(getShipmentRecordsInput_msg,getShipmentRecordsOutputCollection) ] - WSIF JCA Execute of operation 'getShipmentRecords' failed due to: Pure SQL Exception. Pure SQL Execute of select a.row_id, a.asset_num, a.SERIAL_NUM, o.ORDER_NUM, oi.LN_NUM from s_asset a, s_order_item oi, s_order o where a.REF_NUMBER_2 = o.ORDER_NUM and oi.X_SHIP_ASSET_ID is null and oi.STATUS_CD <> 'Closed' and oi.ORDER_ID = o.row_id and a.X_ORDER_LN_NUM = oi.LN_NUM and a.ship_dt >= sysdate - 10 and a.X_ORDER_LN_NUM >= 1 failed. Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0. [Caused by: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.] ; nested exception is: ORABPEL-11633 Pure SQL Exception. Pure SQL Execute of select a.row_id, a.asset_num, a.SERIAL_NUM, o.ORDER_NUM, oi.LN_NUM from s_asset a, s_order_item oi, s_order o where a.REF_NUMBER_2 = o.ORDER_NUM and oi.X_SHIP_ASSET_ID is null and oi.STATUS_CD <> 'Closed' and oi.ORDER_ID = o.row_id and a.X_ORDER_LN_NUM = oi.LN_NUM and a.ship_dt >= sysdate - 10 and a.X_ORDER_LN_NUM >= 1 failed. Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0. [Caused by: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.] The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. </summary>
<detail>Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0</detail>
I don't get it, whats happening ? why does the adapter care what i am running inside a custom sql step. all it is supposed to do is execute the sql and return the values. Why is it forcing me to rewrite the operation which was working before ?well as always...nothing works like restart of the server. Issue resolved.
-
Cannot bind tibco's jms connection factory to wls jndi
we are using wls 6.1 sp2. I am trying to bind tibco's jms connection factory
and queue from a standalone client to weblogic's jndi tree so that apps on wls
can lookup these object in wls jndi locally. I have included the required classes
in the classpath for both the client and wls. I am able to bind the queue successfully
and am able to use it successfully too, but I am not able to bind the tib's queue
or topic connection factory. I am getting the following errors. I checked and
double checked the classpath and
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationExcep
tion
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.n
aming.TibjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.naming.Ti
bjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
anybody any ideas.
I am also trying to bind the tib's jndi tree in wls jndi tree through a reference
object and am passing a composite name for lookup. I am getting a cannotproceedexception.
I wonder if the weblogic jndi can be federated.
anybody any ideas or pointers
thanks
Devaraju, SushantSeems there is a bug in the tibco jms software.
thanks
Devaraju, Sushant
"sushant" <[email protected]> wrote:
>
we are using wls 6.1 sp2. I am trying to bind tibco's jms connection
factory
and queue from a standalone client to weblogic's jndi tree so that apps
on wls
can lookup these object in wls jndi locally. I have included the required
classes
in the classpath for both the client and wls. I am able to bind the queue
successfully
and am able to use it successfully too, but I am not able to bind the
tib's queue
or topic connection factory. I am getting the following errors. I checked
and
double checked the classpath and
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception
is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationExcep
tion
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.n
aming.TibjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.naming.Ti
bjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
anybody any ideas.
I am also trying to bind the tib's jndi tree in wls jndi tree through
a reference
object and am passing a composite name for lookup. I am getting a cannotproceedexception.
I wonder if the weblogic jndi can be federated.
anybody any ideas or pointers
thanks
Devaraju, Sushant -
Error saving JCA Connection factory in PI NWA
Hi All,
I am facing an issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XD1_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration failed, reason: "Can not set authentication user store "null" in security context "CF_XD1_180" for connector "CF_XD1_180" in application "sap.com/tc~sapjra".".
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.addComponent(ConnectorContainerImpl.java:1005
i posted this in SAP PI forum also...
Error saving connection factory
Regards
ashutosh rHello Carme,
From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
This beautiful blog by William will surely help you rectify the problem.
/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
Kindly check if you have done the following in your configuration:
1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15"
2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
I hope this should solve your problem.
Regards, Gaurav. -
Warning message about non XA connection factory
Hi,
I'm using 10.0 MP2 and deployed an MDB which uses TransactionManagementType.CONTAINER with TransactionAttributeType.NOT_SUPPORTED. As I don't need a transaction I am referencing a non XA Connection Factory.
I am seeing this message in the logs..
<04-Nov-2010 10:29:54 o'clock GMT> <Warning> <JMSPool> <BEA-169817> <The JMS connection factory resource localconnFactory declared in the EJB "WLPooledSonicJmsTransactionNotSupportedMessageDrivenBean" as part of application "sampleejbs-ear-0" does not support XA. It cannot be used inside a transaction context.>
Can I safely ignore this warning?
Thanks
MandyAs long as you do not use it inside a transaction, you do not have to worry.
-
Error saving connection factory
I was trying to create a JCA connection factory so that I can use the user module to convert IDOCs to flat file. But I was encountering this problem when saving
Saving JCA Connection Factory: CF_ID1_800 failed due to: Can not add connection factory
I use NWA_SUPERADMIN role.. But seems like even that can't save it correctly.
THanksHi Brian,
I am also facing the same issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
error details : CF_XX_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
The logs details : Can not set authentication user store "null" in security context "CF_XX_XX0" for connector "CF_XX_XX0" in application "sap.com/tc~sapjra".".
could you share info, how your issue got solved..
Regards
ashutosh r -
A stale Connection Factory or Connection Handle may be used in SOA 11g
Hi all,
I am working on a outbound process from oracle apps to BPEL. I am using SOA 11.1.1.3 version. I have created connection pool in admin server.
But BPEL does not pick the messages from ecx_outqueue present in apps.
Also when i update the Aqadapter in the admin server i get the following message
Selected Deployments were updated.
You must also activate the pending changes to commit this, and other updates, to the active system.
The soa diagonostic log is provided below
[2011-02-14T02:29:21.248-07:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ohsadmin] [ecid: 004b3eilKBAE4UVQu2q2TH0006H0000Fay,1:30378] [APP: soa-infra] [dcid: 49c8ed318246db94:41013faa:12d7ab8287f:-7fff-0000000000002a49] [URI: /em/faces/ai/soa/composite] JCABinding=> Invoice_OracleApps *Error while performing endpoint Activation: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/AQ/ExtEBizConn_Factory from JNDI and get a new Connection Handle.*
[2011-02-14T02:29:21.248-07:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ohsadmin] [ecid: 004b3eilKBAE4UVQu2q2TH0006H0000Fay,1:30378] [APP: soa-infra] [dcid: 49c8ed318246db94:41013faa:12d7ab8287f:-7fff-0000000000002a49] [URI: /em/faces/ai/soa/composite] JCABinding=> Invoice_OracleApps [[
javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/AQ/ExtEBizConn_Factory from JNDI and get a new Connection Handle.
Can anyone provide some inputs on this?Hi Anuj,
I have followed the following steps mentioned in the metalink ID 1235943.1 but still it is throwing the same error.
1.Log on to your Admin console and navigate to Domain -> Deployments -> <adapter name> -> Configuration Tab -> Outbound Connection Pools Tab -> Under Groups and Instances expand the javax.resource.cci.ConnectionFactory
2.Locate and select the adapter JNDI and click on the Connection Pool Tab.
3.Please check to see if Shrinking is enabled. If not, please enable it.
4.Please check the value for Shrink Frequency Seconds. The default for some connection pools is as high as 900 seconds. Please reset this to 120 seconds or less.
5.Activate your changes.
6.If this does not improve the situation, please also try increasing the max size of your connection pool.
Please advice if any other solution is there.
Thanks,
Dhiraj Mishra -
The connection factory name for jobs must be "JobQueueFactory
Hi Experts
Can you plase help me to reslove this issue
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Deployment of jobs in application [backgrounjobear] failed, reason is : [Job "BackGroundJob" of bean "BackGroundJob" does not have a connection factory name. The connection factory name for jobs must be "JobQueueFactory".]
while depling MessageDrivenBean 3.0 getting this.
Any help would Greatly appricated.
Thanks
ABHi All,
I am also getting similar error i.e.
Job "TestScheduler" of bean "TestScheduler" does not have a connection factory name. The connection factory name for jobs must be "JobQueueFactory".
Steps that I have followed are bit different from what is mentioned in document "SAP NW Scheduler for Java" as I am working in 7.3
a) Created EJB Project
b) Created Message Driven Bean(JobSchedulerMDB.jav)
c) Created SchedulerJob(TestScheduler.java)
I dont see application-j2ee-engine.xml ; but have
ejb-j2ee-engine.xml
ejb-jar.xml
job-defination.xml
with following xml in them
ejb-j2ee-engine.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ejb-j2ee-engine_3_0.xsd">
<enterprise-beans>
<enterprise-bean>
<ejb-name>JobSchedulerMDB</ejb-name>
<jndi-name>JobSchedulerMDB</jndi-name>
<bean-props>
<property>
<property-name>destination-name</property-name>
<property-value>JobQueue</property-value>
</property>
<property>
<property-name>connection-factory-name</property-name>
<property-value>JobQueueFactory</property-value>
</property>
</bean-props>
</enterprise-bean>
</enterprise-beans>
</ejb-j2ee-engine>
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:ejb="http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0">
<display-name>
JobSchedulerEJBProject </display-name>
<ejb-client-jar>JobSchedulerEJBProjectClient.jar</ejb-client-jar>
</ejb-jar>
job-defination.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<job-definitions>
<job-definition name="TestScheduler"/>
<enterprise-beans>
<enterprise-bean>
<ejb-name>JobSchedulerMDB</ejb-name>
<jndi-name>JobSchedulerMDB</jndi-name>
<resource-ref>
<res-ref-name>JobQueueFactory</res-ref-name>
</resource-ref>
<message-destination-ref>
<message-destination-ref-name>JobQueue</message-destination-ref-name>
<jndi-name>JobQueue</jndi-name>
</message-destination-ref>
</enterprise-bean>
</enterprise-beans>
</job-definitions>
Please help me in this -
How to annotate connection factory name in MDB?
How do I annotate connection factory name in Message Driven Bean?
@MessageDriven(ejbName = "MyMessageDrivenBean",
destinationJndiName = "MyMessageDrivenBeanJndiName",
destinationType = "javax.jms.Queue")
//I want to annotate the below in MDB
<connection-factory-jndi-name>local-jndi-name-of-queue-connection-factory</connection-factory-jndi-name>I think the problem is in the activation config properties
@MessageDriven(name = "MyMessageDrivenBean", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "jms/MyQueue") })
public class MyMDB implements MessageListener
take a look at http://download.oracle.com/javaee/5/api/javax/ejb/ActivationConfigProperty.html
Maybe you are looking for
-
Lock Screen Group Policy - Error code 0X80070002
Hi I'm trying to update the workstation policy (2008R2) to show a new Lock Screen for our users. I have two policies: -Windows 7 Workstation Policy -Windows 8.1 Workstation Policy It was no problem for our Windows 7 machines. Windows 8.1 however woul
-
Hi I'm editing a DV Pal sequence, 16:9 I've got to incorporate some PDF,s no problem. When I view the in canvas they look OK. However when I make freeze frame form each slide, they go a little fuzzy, any way round thi, the aspect ratio isnt aproblem
-
Hi, I get the error OLE error code 0x80040154
OLE error code 0x80040154. Class is not registered. OLE Object is being ignored Record number 24. I get this error when i run a form which has a table with data ,DLL and happen just sometimes.
-
Is there any way we can update an entity if its maintenance object only allows read only option. I tried updating the status of deposit control using an algorithm but it gave an error like "Illegal attempt to modify read only entity". Can I update th
-
My iPod Nano is stuck on the Apple logo
My iPod Nano is stuck on the Apple logo. I have reset and restored it multiple times to no avail. When I slide my finger of the scroll wheel I can hear the clicking meaning that it's actually navigating the menus behind that logo, it even plays music