Restarting foreign server, messages not picked up.

Hi,
I have a setup wherein a local weblogic 10 instance attempts to pull messages off a remote weblogic 10 queue, via Spring JMS.
The local weblogic has a JMS module configured with a 'Foreign Destination', via JNDI.
Both the local and the remote weblogic servers are clustered. When the local weblogic is started up, it picks messages normally and hums along. However, if the remote weblogic is restarted, messages remain on the remote weblogic queue and are not consumed.
If the local weblogic is then restarted, messages are consumed as normal.
I can provide more details as needed.
Does anyone have any ideas?
Thank You

Hi,
This question has come up before in this newsgroup. It's usually advantageous to use standard WebLogic JEE MDBs to consume from WebLogic destinations, as MDBs are specifically designed to work well in this use case: for one, they will automatically ensure that all members of a clustered destinations are serviced by consumers. Search this newsgroup for the keyword "Spring" for details.
Tom

Similar Messages

Server is not picking right RPD

Dear All,
I have following error while putting RPD under Repository folder.
1. I have installed OBIEE V 10.1.3.4.1
2. I have installed Oracle 32 bit client under ReadHAT Linux.
When I have first type the URL I got as the report as SampleSales which is corerct.
Then I have created another RPD say A.RPD and put under OracleBI/server/Repository.
Then I changed NQSCONFIG.INI file and put the file name as SET = A.RPD and default. And commented SAMPLESALES.RPD one.
I started OC4J, BI Server and BI Presentation Services, All the servers up and running fine.
When I clicked the URL I got the old samplesales one rather A.RPD.
Problem is my server is not picking A.RPD at all.
It will be great if you could tell me what all need to be changed to PICK A.RPD.
Thanks for your help.
Regards,
Jan

Hi,
Where do I change webcat files... I have changed OracleBIData\web\catalog files too
See I do not want Samplesales structure under RPD.
I have commented Samplesales under NQSCONFIG.INI like
#Star = Samplesales.RPD, Default
Star = A.RPD, Default
When I open the URL to get the structure of my new RPD, even it is not taking the me to the Oracle Interactive dashboard. It is still picking Samplesales credentials.
I do not know apart from NQSCONFIG.INI file.. which file again I need to change to take me the new RPD file.
Thanks for your help.

JMS Queue Messages not picked up.

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

Hello,
We are facing below issue frequently, any help in this regard would be highly appreciated.
We have 2 MDB's listening to the a queue on WLS 8.1 SP2. We are using Message Selector to identify which of the 2 MDB's should pick up the message.
The issue is that if too many messages are queued up, then the MDB at times doesn't pick them up, even when free instances of MDB are available in the Bean Pool.
But if we restart the server then all the messages are picked up instantly. Server restart acts as some kind of Trigger for the Queued Messages to be picked up instantly.
We have been trying to explore as to why this happens, but havent still resolved it.
Any ideas would be appreciated.
Thanks.
Khyati

DB Adapter: Message not picked up

Hi,
I have an iConnect 10g working fine with the FTP adapter. Messages come through no problem. But now I'm trying to use the DB adapter to publish a message. I have the adapter running and cannot see anything wrong in the logs, but whenever I create and publish a message (and commit afterwards) I can the message appearing in the MESSAGEOBJECTTABLE and the AOTABLE, but the adapter doesn't pick it up.
What can cause this?
Arjan

Hi,
Did you see any errors in the DB adapter log file? Connection errors?
What is your logging level on the adapters set to? In the adapter.ini file, set the "agent_log_level=2".
Merlin is correct regarding when your DB Adapter message is not published.
Some other checks to make are these:-
Log on via SQL*Plus to your publishing database, connecting to the OAI user (usually OAI/OAI) and do:-
select count(*) from oai.aotable;
and
select count(*) from oai.messageobjecttable;
If there is the same number of records on there, and your publishing adapter hasn't pick them up, then run this:-
select APPLICATIONTYPE from oai.messageobjecttable;
This should be the same as your publishing adapter name.
Hint: in adapter.ini check the entry for "application= "
e.g.
// Application (as created in iStudio) that this Adapter corresponds to.
application=DB1
If they are different, or if APPLICATIONTYPE is null, then this is caused because you need to specify the "srcAppName" when you call your publish
procedure.
If you send me a mail to [email protected] I'll send you a complete worked, yet simple, DB Adapter to DB Adapter example and code which may help you.
Rene,
It is worth noting that ordinarily, the OAI schema has absolutly nothing to do with a subcribing DB adapter. The OAI schema contains the AOTABLE and MESSAGEOBJECTTABLE (MOTABLE), and the AGENT package which creates the message for the publishing event. That is it. The OAI schema does not usually "consume" the subcribed message, and therefore should never end up in the AOTABLE or MOTABLE.
The target schema to where the subcribed DB message will be posted to is the schema you will define in the DB Adapters "adapter.ini" file.
Specifically the entries below this line in your adapter.ini
// Application (spoke) database schema #1 writer information
Do you have any errors in your log files? The message cannot have just disappeared. Your FTP Adapter must be throwing an error somewhere, or your DB Adapter must be complaining.
Please can you check you log files for both adapters. If there are any strange errors let us know.
What type of document are you trying to publish using the FTP Adapter? XML? D3L? If XML, then check out the post "istudio publish event & xml ftp adapter" on this forum.
Again, if you drop me an email, then I can send you my DB Adapter to DB Adapter example which may help.
Yan

Workcenter message not picking contract

Hi All,
I am working solman 7.0 configured incident management serives desk and support notification messages are getting logged from ECC to Solman workcenter along with contract determination . But as we know message can be logged directly from workcenter while i am logging from workcenter contract determination not happening .
Regards
subbaraju

Hi samantha,
              I installed Solman7.0 Ehp1, sucessfully finished after i configured SAPROUTER, MOPZ,SERVICE DESK, Now i am activating SOLMAN_WORKCENTER, unfortunately could not displaying " I activated "AGS*" related all the services above 25 services. but page could not displaying
then check all the services for "TEST SERVICES" this also "CONNECTION TIME OUT ERROR showing"
          1. smicm t-code value is 6000 there.
          2. I activated all the servies also
          3. added roles also 3 roles.
anybody giveme solution please.

Foreign currency conversion not picking up rate or time period

I am running the standard FX conversion (standard stored procedure - fxtrans.lgx) on SAP BPC MS version 7.5 , but everytime I run the package, even though I choose a particular day, it seems to run for multiple time periods.
In the formula log I get more than 50 of the following:
10000400 - 4 rows calculated
10000400 - 0 rows updated
10000400 is the TIMEID for my currency conversion.
Also, when I look at the result, even though I have entered 1 as my conversion fator I get a multiple of 18. I tried to change the conversion factor, but no matter what I do for no matter what entity and no matter what LC I always end up with a multiple of 18.
Any ideas for me?
Thanks

Hi,
This sounds strange. Can you post your script logic file and a small extract from your time dimension please?
Tom.

Xi server not picking up the file

Hi,
My Scenario is flat file to xml.I have declared all the file content conversion parameters and placed the input file in server.But the thing is XI server is not picking up the file.What could be the error.Does any error in content conversion has to do with XI-Server not picking up the file.
Thanks,
Srinadh

Hi Bhargav,
go to SXMB_IFR -> Runtime Workbench -> component monitoring -> adapter engine -> adapter engine monitoring or to communication channel monitoring to see the error in your sender file adapter..........rectify this error in comm channel in ID.......set filemode to delete..........then activate yur comm channel.........then your source file will be picked by XI........
Thanks,
Rajeev Gupta

Weblogic Server not picking the jar files in WEB-INF/lib folder

we are facing a strange problem where Weblogic App Server is not picking the jar files present inside the WEB-INF/lib folder if we update the jar file path in the classpath of the start script then the classes get loaded properly.
Is there any specific setting which I need to do in weblogic to pick these jars ?

Class loaders associated with a Web application can be configured to locate local classes first. To enable this we have to set the <prefer-web-inf-classes> to true in the deployment override weblogic.xml, for example
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
http://blog.transfer-solutions.com/2010/12/weblogic-class-loading/

SAP web AS not picking up my custom actions defined jar

Hi,
I added some custom actions in the config.xml of the SAP Internet Sales Application, but noticed that this server is not picking up the jar file in which I defined my custom actions. This happens even though I placed the jar file directly under the WEB-INF/lib folder.
When I go through the logs, I see that under the resources, it picked up all the jars except mine. Is there a place where you define what jars to pick up with in the WEB-INF/lib folder.
Thanks
SK

Oh yes, there is.
In NetWeaver never place any files into directories and expect them to work. You MUST deloy them regularly.
On every start the server checks the files against what is in the DB and I don't know what it does in case of no file in DB, but it may even delete it...
Regards,
Benny

Not able to connect to a queue under a foreign server.

Not able to connect to a queue under a foreign server.
I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
OS used is AIX 6.0 on both servers.
Tried restarting the local server but nothing helps. Same error continues.
HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
It throws following errors:
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
     at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
     at javax.naming.InitialContext.internalInit(InitialContext.java:286)
     at javax.naming.InitialContext.<init>(InitialContext.java:211)
     at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
     at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
     at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
     at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
     ... 46 more
>
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
<Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
     at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
     at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
     at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
     at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
     Truncated. see log file for complete stacktrace
Edited by: 942523 on Jun 24, 2012 11:38 PM

Thanks René van Wijk for the reply.
I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
This page displays details about this bound object.
Failed to create InitialContext using factory specified in hashtable
Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.io.EOFException]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:436)
     at weblogic.jms.common.CDS$2.run(CDS.java:503)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
     java.io.EOFException
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
     at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
     ... 36 more
Caused by: java.io.EOFException
     at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
     at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
     at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
     at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
     at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
     at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
Let me know if any other thing i'm missing or it can be something else like network or some other issue.

Weblogic 8.1: Remote/Foreign Server JMS - Destination not found error

Hi
This is our current setup: Weblogic Server 8.1 with JMS module running on the same instance as the application. We would like to move JMS out into its own box. I am currently setting up my development environment to test the new setup. These are the steps I followed:
* Setup the server instance running the application on one box (Box1). Removed the existing JMS Connection Factory and Destination JNDI setup
* Setup a server instance on another box (Box2) without the application. Created the necessary JMS Connection Factories and Destinations. Started the server instance on Box2
* Added a Foreign Server configuration on Box1. Created the connection factory and destinations under this foreign server pointing to Box2
* The Foreign JNDI names are being bound correctly (I verified the JNDI tree on Box1). Restarted the server instance of Box1
Message-Driven Beans deployed on Box1 are unable to retrieve messages from Box2. The exception thrown is given below. Any help in troubleshooting and resolving this issue is appreciated.
<Warning> <EJB> <myserver> <main> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: MyBean is unable to connect to the JMS destination: jms/my.application.firstQueue. The Error was:
weblogic.jms.common.JMSException: Destination not found
weblogic.jms.common.JMSException: Destination not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
at weblogic.jms.backend.BESession.createConsumer(BESession.java:153)
at weblogic.jms.backend.BESession.invoke(BESession.java:1457)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:232)
at weblogic.jms.frontend.FESession$3.run(FESession.java:1058)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:1054)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2552)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:179)
at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1860)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1691)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1530)
at weblogic.ejb20.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1720)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2019)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1180)
at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSConnectionPoller.java:846)
at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBeanPoolInfoImpl.java:234)
at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1660)
at weblogic.ejb20.deployer.EJBDeployer.startMessageDrivenBeans(EJBDeployer.java:1555)
at weblogic.t3.srvr.T3Srvr.startMDBs(T3Srvr.java:948)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:1024)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Edited by: user8773992 on Sep 2, 2009 11:31 AM

1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
Tom

Urgent: Message not transmitted from AFW to Integration server

We have trouble with some settings where the message is picked up by the communication channel and passed to the AFW. But, it gets stuck here with an error message "Transmitting the message to endpoint http://<J2EEServer>:<J2EE-Server-Port>/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
We have the "Pipeline URL" in our Business system to point to the HTTP port 8xxx but it is still going to the J2EE port such as 50xxx. Is there anyother place we need to change the port settings?
Any help would be appreciated.
Thx

No other place to define the pipeline url.
Check the HTTP Port by using tcode SMICM if it starts with 80xx.
>http://<J2EEServer>:<J2EE-Server-Port>/sap/xi/engine?type=entry
You should use HTTPport not J2EE-Server-Port
Like this: http://<host>:<HTTPport>/sap/xi/engine?type=entry
One more thing have u select the "Integration Server" as a business system role while defining the pipeline url.
In my point of view you first refresh the Cache and then try. If still you face the problem then probabily you can restart the server (if possible) & then try.
Regards,
Sarvesh

Nodemanager does not restart managed server after Linux OS reboot

Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
Things I've tried:
+ When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
+ The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
+ A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
Things I'm curious about:
+ Is there some way to see in what state the nodemanager believes the managed server to be?
+ Is there some value in some doc somewhere that might say the server should not be restarted?
+ Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
Thanks,
Kevin
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=false
CrashRecoveryEnabled=true
JavaHome=/appl/java/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1

can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
From Official documentation:
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
*/

Error message received: The iTunes update server could not be contacted

Please help! I'm using a windows 7 laptop. The iTunes store is not displaying images, and if I try to import a CD it will not access the gracenote database for track info.Tried updating but got the error message 'the itunes update server could not be contacted'. I'm accessing the internet via a Tmobile dongle and all other web content is working . I have uninstalled and reinstalled itunes, checked my driver are up to date and that my AVG firewall allows iTunes through.I have disabled the windows firewall.I tried disabling the AVG one completely too but that had no effect so I'm stuck - can anyone help?

Not sure if you already fixed this problem or not, but I recently upgraded my laptop to Win7 and ran into the same issue. My Internet connection was working fine, I could even browse the store within iTunes, just couldn't download any software or firmware updates. I fixed it by editing the "hosts" file located in the C:\Windows\System32\drivers\etc folder. Open it in notepad with admin rights (right click notepad & select "Run as administrator"). Uncomment (delete the hash symbol "#") the last 2 lines or the ones that consist of "127.0.0.1 localhost" and "::1 localhost". Restart iTunes and see if this works (if you haven't already found a solution).

The user or users have been added successfully, but there was an error in sending the e-mail message. The server may not be set up correctly to send e-mail. To verify that e-mail is configured correctly, contact your server administrator

I got this problem when I tried to configure out-going email and add an account to farm administrator group.
I configure out-going email according to this website http://technet.microsoft.com/en-us/library/cc288949.aspx
Here are the screen shots.
The SMTP server and email accounts work out OK when I use Outlook 2010 to test.
Anyone can help me about it? Thanks.
Here is the log.
09/20/2012 09:21:00.36 w3wp.exe (0x1F7C)
0x1138
SharePoint Foundation E-Mail
8gsf
High
#160008: The e-mail address 'admin3.sharepoint@domain' contains illegal
characters. df98555c-612f-4a58-9443-ab6e9a4fcc53
09/20/2012 09:21:00.36 w3wp.exe (0x1F7C)
0x1138
SharePoint Foundation General
8kh7 High
Cannot complete this action. Please try again.
df98555c-612f-4a58-9443-ab6e9a4fcc53
09/20/2012 09:21:00.36 w3wp.exe (0x1F7C)
0x1138
SharePoint Foundation E-Mail
7946 Critical
Cannot complete this action. Please try again.
df98555c-612f-4a58-9443-ab6e9a4fcc53
09/20/2012 09:21:00.36 w3wp.exe (0x1F7C)
0x1138
SharePoint Foundation Runtime
tkau Unexpected
Microsoft.SharePoint.SPException: The user or users have been added successfully, but there was an error in sending the e-mail message. The server may not be set up correctly to send e-mail. To verify that e-mail is configured correctly, contact your
server administrator. at Microsoft.SharePoint.ApplicationPages.AclInv.SendEmailInvitation(EntityEditor picker, String subject, String message) at Microsoft.SharePoint.ApplicationPages.AclInv.BtnOK_Click(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String
eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStage...
df98555c-612f-4a58-9443-ab6e9a4fcc53
The e-mail address I have tested it for several times and there is no problem.
Anyone has any clue about this error?

Hi.
This I have seen before...
It can be that the SMTP relay server is configured to only allow certain IP ranges or addresses.
It can be that the firewall on the SP server does not allow for SMTP traffic (normally 25, for example for Exchange).
It can be that there is an Antivirus on the SP server(Client AV) that prohobits the Timer service to send email from this server. I have seen MacAfee do this. Needed an policy change.
If, its the builtin SMTP service you are using, check this link:
http://blog.sharepointrx.com/2010/11/18/setting-up-the-iis-smtp-server-for-sending-email-from-sharepoint-2010-on-server-2008-r2/
Check that and try again.
Regards
Thomas Balkeståhl - Technical Specialist - SharePoint -
http://blog.blksthl.com
Download the SharePoint Branding Project here
Download the SharePoint 2010 Site Settings Explained here

Restarting foreign server, messages not picked up.

Similar Messages

Maybe you are looking for