Weblogic to Tibco using foreign server Error!!!
Hi,
I am integrating Weblogic 11g server with Tibco EMS using the foreign jms server.
I have created a foreign jms server, foreign connection factory and a foreign destination in the jms module.
but while sending the message to foreign destination queue i am getting the following error::
[JMSClientExceptions:055014] Error Sending Message
Could anyone help me on this?
Thanks in advance,
Uday
Hi,
To help you I need the class.java, xslt or xquery from where you are trying to send the message and the settings you gave to the queue in the foreing server.
Make sure you are giving up the correct security parameters .
Regards.
Lucas.
Similar Messages
-
OSB to MQ, using Foreign Server
Hi All,
I am working on OSB to MQ connectivity, using Foreign Server. I was able to establish the connectivity using Sun JDK 1.6. However when I JRockit 1.6 is used, connectivity is not working. There are stuck threads in Weblogic, when weblogic has to invoke the MQ Jars. Any suggestions, will be greatly appreciated.
Regards.Hi
Thats very strange behavioural diffrerence between Sun & Jrockit.
Take it you have gone through the stuck threads and realised threads were marked stuck when trying to invoke / load MQ jars? can you copy the stuck threads referring that please.
Have you tried loading those MQ jars in the classpath of the server .. That way all the necessary jars/classes will be available local to the instance
and can be located by classloader without much delay.
HTH
Sri -
Intermittent "Cannnot send message using the server" error
I've been getting an intermittent "Cannnot send message using the server" error for a couple of months now. It happens every 3 or 4 e-mails I try to send or reply to. I select "Try Again Later" and then open the message from the Outbox and resend with no problem.
My setup is;
Mail 2.1.1
OSX 10.4.9
MacBookPro
CableVision is my provider
It's a POP account
My incoming server is pop.secureserver.net
My outgoing server is smtpout.secureserver.net
Server port 3535
Authentication - Password
SSL is off
Any help would be appreciatedHi Dave, and a warm welcome to the forums!
No expert on this, but I wonder since your using the secureserver, if SSL might not work better.
Or maybe try...
Incoming Mail Server Name (POP3): pop3.optonline.net
Outgoing Mail server Name (SMTP): smtp.optonline.net
or mail.optonline.com for both!?
Nearly impossible to find any help on Cablevision's site.
Also, I wonder if this might have something to do with Tiger's Mail also...
http://discussions.apple.com/thread.jspa?threadID=1372763 -
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 AM1 - 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 -
MDB cannot connect to JMS destination using Foreign Server
Hi everyone,
I have configured foreign jms server in weblogic but when MDB tries to connect to specific queue, it gets the following exception:
I would really appreciate if anyone could help me.
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination or bind to JCA resource adapter: xcg2/smsInQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination: xcg2/smsInQueue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jmsxcg.out could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.
javax.naming.InvalidNameException: jmsxcg.out: [LDAP: error code 34 - Invalid DN]; remaining name 'jmsxcg.out' NestedException Message is :jmsxcg.out: [LDAP: error code 34 - Invalid DN]>
MDB annotation looks like this:
@MessageDriven(name="SmsReceiver", mappedName="xcg2/smsInQueue",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public class SmsReceiverBean implements MessageListener
weblogic-ejb-jar.xml excerpt:
<weblogic-enterprise-bean>
<ejb-name>SmsReceiver</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<connection-factory-jndi-name>echoQueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>600</trans-timeout-seconds>
</transaction-descriptor>
<dispatch-policy>MdbSmsWorkManager</dispatch-policy>
</weblogic-enterprise-bean>
and the configuration of foreign-server:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms">
<foreign-server name="serverr">
<sub-deployment-name>Subdeployment</sub-deployment-name>
<foreign-destination name="sms queue>
<local-jndi-name>xcg2/smsInQueue</local-jndi-name>
<remote-jndi-name>jmsxcg.out</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="Connection Factory">
<local-jndi-name>echoQueueConnectionFactory</local-jndi-name>
<remote-jndi-name>QueueConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
<connection-url>tibjmsnaming://xx.xx.xx.xx:7222</connection-url>
</foreign-server>
</weblogic-jms>
PS. I'm able to connect to the weblogic jndi, get connectionFactory echoQueueConnectionFactory, then lookup queue and grab messages so that's i suspect there is something wrong with configurationHmm - I'm not sure what's going on. Two thoughts --
Thought 1 - According to my (admittedly minimal) research, Tibco is complaining about a syntax error in the lookup name. Perhaps the problem has something to do with your use of a "." in the queue name "jmsxcg.out": WL or Tibco JNDI might be interpreting the "." as a subcontext or some-such. Perhaps try renaming the queue to "jmsxcg_out" throughout (in Tibco and in your Foreign JMS reference).
Thought 2 - It probably won't make a difference, but you might want try specifying the source destination via the "destinationJndiName" config property instead of via "mappedName".
@MessageDriven(
name = "MyMDB",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destinationJndiName",
propertyValue = "MyQueue") // Ext. JNDI Name
)HTH,
Tom -
Weblogic: problem with JMS foreign server and Transaction
Hello everyone,
I am working with an enterprise application with Web Application Server Logic 10.3. L 'application uses the following components:
1) MDB 2.0
2) FOREIGN JMS SERVER -> WebSpereMQ
3) EJB SESSION
L 'MDB calls the session bean which uses in its ejb-jar.xml using a Wrapper for JMS QueueConnectionFactory with res-ref:
<resource- ref>
<res-ref-name> jms / iss / QCFIXP </ res-ref-name>
<res-auth> Container </ res-auth>
<res-sharing -scope> Shareable </ res-sharing-scope>
<resource- ref>
The MDB is CMT
<transaction-type> Container </ transaction-type>
while the session bean is BMT
<transaction-type> Bean </ transaction-type>
to call the QCFIXP in its transaction.
The QCFIXP ii an XA resource
When there is a rollback operation in SessionBean also in 'MDB
There 'an operation setRollbackOnly:
getMessageDrivenContext (). setRollbackOnly ();
After this operation on the MDB I do a JNDI look up the QueueConnectionFactory but sending the message on a queue I get the following exception:
javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA:
But if not using the "wrapper jms" in the session bean I did not take any exception and the application don' t have any error.
My doubt is :
Why if I use the JMS wrapper I get an error javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA?
Thanks in advance.
Michele
Edited by: user3501731 on 11-mag-2011 3.16Hi Tom,
Thanks very much for your responses and careful analysis you've done.
Following the source code of the MDB where error occurs.
Marked In bold the line where the exception is thrown.
public void onMessage(Message msg) {
// Utility.logger(AP.DEBUG, "Partito MDB 2");
processa(msg);
protected void processa(Message msg) {
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa(Message msg) partito");
try {
long start = System.currentTimeMillis();
/* Utility.logger(
AP.DEBUG,
"IXPReceiverMDB.processa(Message msg) effettuo lookup");*/
ejb = myEjbLocalHome.create();
// individuo l'identificativo del messaggio in ricezione
String msgid = msg.getJMSMessageID();
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa(Message msg) elaboro messaggio:"
+ msgid);
String charset = msg.getStringProperty("JMS_IBM_Character_Set");
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa Charset:" + charset );
// invoco il processo di ricezione
boolean commitRequested = ejb.processa(ctlReq, encoding, msg);
// il valore di ritorno del processo di ricezione identifica o meno
// la necessita' di effettuare il rollback dell'intero processo
if (!commitRequested) {
getMessageDrivenContext().setRollbackOnly();
if (ctlReq) {
Utility.logger(
AP.INFO,
"IXPReceiverMDB7.processa(Message msg) spedisco il messaggio pilota del 'cleaning' con JMSCorrelationID = '"
+ msgid
+ "'");
msg.setJMSCorrelationID(msgid);
// Viene creata la QueueConnection
QueueConnectionFactory factory =
JmsFactoryDispenser.getSingleton().getFactory();
QueueConnection connection = factory.createQueueConnection();
// Viene ottenuta la 'session'
QueueSession session =
connection.createQueueSession(
false,
Session.AUTO_ACKNOWLEDGE);
// spedisco il messaggio sulla coda abbinata al processo di 'cleaning'
// della coda di controllo
IXPMessageManager msgManager = new IXPMessageManager(session);
msgManager.spedisci(msg, AP.PILOTQUEUE, "J", AP.STD_MESSAGE); session.close();
connection.close();
long end = System.currentTimeMillis();
Long durata = new Long (end - start);
Utility.logger(
AP.INFO,
"IXPReceiverMDB7 Tempo totale elaborazione messaggio: " +
msgid + " " +
durata.toString() + " mill" );
Utility.logger(
AP.DEBUG,
"IXPReceiverMDB7.processa(Message msg) terminato");
} catch (Throwable e) {
getMessageDrivenContext().setRollbackOnly();
try {
Utility.myExceptionHandler(
"E",
"1",
"4028",
"IXPReceiverMDB.onMessage()",
e);
} catch (Throwable ex) {
ex.printStackTrace();
Thanks in advance.
Edited by: serpichetto on 16-mag-2011 1.24 -
What's new in Weblogic 8.1 using MQ
We will use MQseries 5.3 as are Queuing-system and Weblogic Server 8.1
as our appication server.
We don't have to use transactions in our messages.
I've the following questions.
In weblogic documentation Using Foreign JMS Providers with Weblogic
Server from May 2002 is written For Weblogic 7.
What are the differences with 8 and is there a document written for
version 8.
Must we still write a startup class?
I'll hope someone can give more info about the new features of
WebLogic 8 for using Foreign JMS Providers and the differences with
Weblogic Server 7.
greetings,
Andre Torensma
Developer
Friesland Bank
The document is still valid. That is, you can do what the document says and
they'll still work. However, there are a few new features:
-- "Foreign JMS Server" pages in the console (and config MBeans) let you set
up JNDI "symbolic links" between objects in the WLS JNDI name space and your
own JNDI provider, like the one you use for MQ. This may make it easier to
set up MQ in many cases.
-- The EJB "resource-reference" feature, which you use to bind a JMS
ConnectionFactory into an EJB or servlet's private JNDI tree, wraps the JMS
objects so that it can provide automatic transaction enlistment and pooling.
This means it's a lot easier to send an MQ message from inside an EJB or
servlet. There's a section on "Using JMS with EJBs and Servlets" in the JMS
programming guide that explains how to use this.
-- The startup class that people used in the past was one possible way to
create an MQ connection factory and use it inside WLS. In 7.0, you had the
option of setting up a JNDI provider (like the "filesystem" provider) and
storing your MQ JMS objects in there using the IBM "jmsadmin" tool. The
white paper describes this. You can still do this in 8.1. The difference is
that once you do that, you can use the "Foreign JMS Provider" support so
that you don't have to copy the information about that JNDI provider into
every EJB and MDB that needs to talk to MQ.
greg
"Andre Torensma" <[email protected]> wrote in message
news:[email protected]...
> We will use MQseries 5.3 as are Queuing-system and Weblogic Server 8.1
> as our appication server.
> We don't have to use transactions in our messages.
>
> I've the following questions.
> In weblogic documentation Using Foreign JMS Providers with Weblogic
> Server from May 2002 is written For Weblogic 7.
> What are the differences with 8 and is there a document written for
> version 8.
>
> Must we still write a startup class?
>
> I'll hope someone can give more info about the new features of
> WebLogic 8 for using Foreign JMS Providers and the differences with
> Weblogic Server 7.
>
> greetings,
>
> Andre Torensma
> Developer
> Friesland Bank
-
Error occurred when use foreign Jms server[JMSClientExceptions:055142].
I want to use a foreign Jms server(Tibco EMS), after I have config the JNDI of foreign server,connectionfactory and destinations, the correct JNDI name can be find on the JNDI tree.
Then I deploy a demo mdb ear on the weblogic(version is 10.3),there's warnning tag on the ear application, and there is error message in the log:
<2011-1-10 上午10时15分07秒 CST> <Warning> <EJB> <BEA-010061> <The Message-Drive
n EJB: MDBDemo is unable to connect to the JMS destination: NotifyAlertAlertQueue. The Error was:
weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, Queue[notify.alert.alertQueue]>
NotifyAlertAlertQueue is the JNDI name of the destination defined on the weblogic console,and the same as ems jndi name for queue notify.alert.alertQueue.
It seems that the application has find the queue correctly, but why it throw that exception[JMSClientExceptions:055142]?
Thanks for any help.
Edited by: 826761 on 2011-1-9 下午6:40I suspect that somehow your configuration is messed up and the MDB ended up using a WebLogic connection to access a TIBCO EMS destination.
Please make sure that your JMS server configuration maps a TIBCO connection factory jndi name to a jndi name in WebLogic server JNDI tree, a TIBCO destination jndi name to a jndi name in WebLogic server JNDI tree, and your MDB configuration refers to the jndi names in the WebLogic JNDI tree.
Regards. -
Hi,
We were trying to integrate Tibco EMS with WLS 10.3 (using Foreign JMS Server). We are using Spring as our app container (the one which basically creates/manages connections, sessions etc)
I am able to listen to the topics both durably and non-durable mode by hardcoding the username/passwords in the spring config directly.
We didnt want this hardcoding of credentials, so moved to using the Foreign JMS Provider implementation from Weblogic. To access the ConnectionFactories I now use resource-ref in the web.xml and have wired spring to use the JNDI lookup using these resource-refs to lookup the topic and connection factories. This works fine for non-durable subscription.
Issue: For durable subscriptions, using Foreign JMS Providers (like mentioned above) I get this error
java.lang.ClassCastException: com.tibco.tibjms.TibjmsXASession cannot be cast to javax.jms.TopicSession
at weblogic.deployment.jms.PooledSession.createDurableSubscriber(PooledSession.java:348)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.createConsumer(AbstractPollingMessageListenerContainer.java:469)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.createListenerConsumer(AbstractPollingMessageListenerContainer.java:221)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:305)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1002)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:994)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:896)
at java.lang.Thread.run(Thread.java:619)
The issue isnt with non-XA or XA connectionFactories either. When I tried using a non-XA conn factory I get a similar error but the cast exception is between TopicSessionImpl and TopicSession.
My spring config is -
<jms:listener-container container-type="default"
connection-factory="jmsTopicConnectionFactory"
cache="none"
acknowledge="auto"
destination-resolver="gadgetDestinationResolver" destination-type="durableTopic" client-id="testClientId" >
<jms:listener destination="jms/GL.GADGET.IN" ref="publishThumbnailListener" subscription="localhost7001durable" />
</jms:listener-container>
Not sure if I need to set anything other than client-id, durableSubscriptionName while subscribing.
Any idea what might be wrong or if theres anything else I need setting up?
Thanks
PdkThe stack trace seems to indicate that the TIBCO client library that you are using supports JMS 1.1 only, although JMS 1.1 Spec requires JMS providers to support both 1.0.2 and 1.1 APIs. You can check and see if there is a client library from TIBCO that supports JMS 1.0.2 as well.
Meanwhile, Weblogic JMS pooling code is supposed to support both JMS 1.0.2 and 1.1. It looks like it doe not support 1.1 for creating a durable subscriber on a javax.jms.Sessiom. You can contact Oracle support for a fix. -
RJVM has already been shutdown error while looking upto Foreign Server
Hi,
I am trying to set up 2 new servers in a clustered environment. In this I have configured a Foreign Server which is looking up to queues in different server.
The structure is like this: 1 Foreign Server with 2 Queues and 1 Connection factory with exactly same name as they present on the host server.
While starting the server, I am getting an exception:
<Nov 5, 2012 7:39:58 PM EET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ClonedQueueAnonymousWaiter is unable to connect to the JMS destination: MDB_QUEUE_RESPONSE. The Error was:
javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: RJVM has already been shutdown; nested exception is:
java.io.IOException: RJVM has already been shutdown]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.rmi.UnmarshalException: RJVM has already been shutdown; nested exception is:
java.io.IOException: RJVM has already been shutdown
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:360)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
... 21 more
Caused by: java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
... 24 more
Caused by: java.io.IOException: RJVM has already been shutdown
at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:513)
at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:900)
at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:404)
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
... 24 more
>
Weblogic is installed in Solaris machine and welogic's version is 10.3.4.0 with Java version 1.6.0 update 33. I have checked the firewall, /etc/hosts but there are no issues with that.
The JNDI Connection URL is configure like: t3://xx.xxx.x.xx,xx.xxx.x.xx:7001/
I have tried giving like this also: t3://xx.xxx.x.xx:7001,xx.xxx.x.xx:7001/ or t3://hostname1,hostname2:7001/ or t3://hostname1:7001,hostname2:7001/
but nothing worked.
The foreign servers are accessible from my Application Server when I do the telnet on the port. There is no cross domain security required. Funny thing is I have a same set-up in two other application server (in cluster again) and there on configuring the Foreign server to same IPs, I am not facing any issues at all.
Can anyone please help me with this. Searched all over the place but have no clue regarding this. Many forums mentioned about firewall and etc/hosts but that is also not case it seems.
Regards,
Priyam809364 wrote:
You can apply the below debug flags to check t he RJVM Communication in detail and figure out what's going wrong and do apply it at both the side
-Dweblogic.kernel.debug=true
-Dweblogic.debug.DebugConnection=true
-Dweblogic.StdoutDebugEnabled=true
-Dweblogic.log.LogSeverity=Debug
-Dweblogic.log.LoggerSeverity=DebugI added the debug as you mentioned and I get the below information there:
<Nov 6, 2012 11:41:16 AM EET> <Debug> <RJVM> <BEA-000500> <RJVMFinder trying to find rjvm for t3://moon1,moon2:7001->moon1,moon2:[7001, -1, -1, -1, -1, -1, -1]->[]
Active RJVMs:
{-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer on [10.160.1.115:7001]=weblogic.rjvm.RJVMImpl@4320d68d - id: '-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer' connect time: 'Tue Nov 06 11:40:26 EET 2012'}
Synonyms:
{}>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Bootstrapping connection to: 'moon1/10.160.1.40:7001' using: 't3'>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Looking for a new connection for channel Default[t3]:t3(t3):venus1:7001:null:-1 to remote server 0B:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1,-1,-1] active connections: {}>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <New connection for protocol t3, remote address moon1/10.160.1.40, remote port 7001, over channel Default[t3]>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Added: 'Default[t3]:t3(t3):venus1:7001:null:-1' connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'. Connections list size 1>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Bootstrapping using a: 't3', connection to: 'moon1/10.160.1.40' on port: '7001'>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Created RJVM for: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1 on [10.160.1.40:7001]', Active RJVMs:
{-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer on [10.160.1.115:7001]=weblogic.rjvm.RJVMImpl@4320d68d - id: '-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer' connect time: 'Tue Nov 06 11:40:26 EET 2012', -3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1 on [10.160.1.40:7001]=weblogic.rjvm.RJVMImpl@7bb8a8c6 - id: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' connect time: 'Tue Nov 06 11:41:17 EET 2012'}
Synonyms:
{}>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Remote heartbeat: '60000', local heartbeat: '60000'>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Setting heartbeat for RJVM: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' to: '60000' milliseconds>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Added: 'Default[t3]:t3(t3):venus1:7001:null:-1' connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'. Connections list size 1>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000517> <Error on connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'
java.io.EOFException
java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:826)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:760)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:941)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
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)
>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Signaling peer: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' gone - weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Closed and removed: 't3' connection to: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1'. Connections list size 0>
<Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Closing: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1'>
<Nov 6, 2012 11:41:17 AM EET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ClonedQueueAnonymousWaiter is unable to connect to the JMS destination: MDB_QUEUE_RESPONSE. 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:470)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: 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_1034_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
... 21 more
Caused by: java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:826)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:760)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:941)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
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)
>
Seems like Peer gone exception is the root cause of this. Any idea for this ?
Regards,
Priyam
Edited by: Priyam Srivastava on Nov 6, 2012 2:49 AM -
Issue with osb + weblogic foreign server AQ configuration
Hi ,
I am trying out a scenario wherein, OSB publishes a message onto an Oracle AQ JMS Topic.
I have created the Foreign Server and have used the Local JNDIs of the connection factory and the destination within my OSB business service. But then, my business service fails to publish the message onto the AQ giving below exception in the server logs:
"<BEA-169807>There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_-541341947 from within an EJB or a servlet. The server will attempt the connection again later. The error was oracle.jms.AQjmsException: Error creating the db_connection"
Below are the configurations that I have used for configuring the foreign server
Connection Factory - LocalCF | Local JNDI - LocalCF | Remote JNDI - XATopicConnectionFactory
Destination - ETASNIN | Local JNDI - ETASNIN | Remote JNDI - Topics/ETASNIN
The Business Service URL: jms://xxxxhost:7011/LocalCF/ETASNIN
**P.S:** I have tried out the same scenario of interfacing OSB with AQ JMS on a Windows box it works fine... But the above is the case on a UNIX box. Also, I am using PS3 of OSB with 10.3.4 of weblogic server.
Any Suggestions on this would really help and is much appreciated...
Thanks,
Manoj NairHi Manoj,
how it was solved? -
Error 500--Internal Server Error when using BI Publisher within OBIEE 11g
I'm using OBIEE 11.1.1.6.2BP1 on a Linux x86-64 server and it has been working just fine. We recently started playing around with the BI Publisher component of that installation and every time i go to http://hostname:port/xmlpserver and try to log in with an Administrator username and password, the following error shows up:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
*10.5.1 500 Internal Server Error*
The server encountered an unexpected condition which prevented it from fulfilling the request.
I have looked around for solutions and tried a couple of them (created a new Admin user in Weblogic Console and checked the opmnctl status) and they did not help. I'm looking for an answer other than upgrade to the latest and greatest
Any help is appreciated.Do you have any SSO setup as that might be preventing the ability of the user to log into BI Publisher, hence the Internal 500 error message.
Are you using FMW security model for BIP and OBIPS integration which is by default. Check the xmlp-server-config.xml file from the repository [\Middleware\Oracle_BI1\clients\bipublisher\repository\Admin\Configuration\xmlp-server-config.xml] and see what your security model is pointing to?
Also what happens when you try to access from Administration>BI Publisher >Manager BI Publisher ?
Follow : http://docs.oracle.com/cd/E23943_01/bi.1111/e22255.pdf
Oracle Fusion MiddlewareAdministrator's Guide for Oracle Business Intelligence Publisher 11g Release 1
HTH,
SVS -
Cannot run PAPI in Weblogic Server 10g - Error 500--Internal Server Error
I use Jdev 11g to create an ADF (PAPI) and deploy it to Weblogic 10g.
The code is copied from Jdev 10g. The PAPI works fine in when running in Jdev 10g
However, after I deploy the ADF (PAPI) created using Jdev 11g to the Weblogic server. The following error appears.
How to modify the code? Should I add the fuego lib to the weblogic domain?
I try to add the fuegopapi-client.jar to Weblogic Server. But it shows error: Unable to access the selected application. java.lang.NullPointerException
BPM is running in BPM standalone. I do not use PAPI webservice
Sincerely
Error 500--Internal Server Error
javax.faces.el.EvaluationException: fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:51)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:458)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:763)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:640)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:275)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:175)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:61)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:279)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:239)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:196)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:139)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
at fuego.directory.exception.DirectoryNotAvailableException.wrapDNAException(DirectoryNotAvailableException.java:33)
at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:81)
at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:34)
at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:437)
at fuego.directory.provider.jdbc.JDBCPersistenceManager.checkConnectivity(JDBCPersistenceManager.java:91)
at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:242)
at fuego.directory.provider.Factory.startSession(Factory.java:405)
at fuego.directory.Directory.startAnonymousSession(Directory.java:214)
at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:193)
at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
at fuego.papi.ProcessService.create(ProcessService.java:335)
at hypapai2.view.backing.P1.commandButton1_action(P1.java:54)
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.sun.el.parser.AstValue.invoke(AstValue.java:157)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:46)
... 32 more
Caused by: fuego.connector.ConnectorException: External resource [fuego] of type [SQL] is not initialized.
Detail:External resource [fuego] cannot be used because it failed to initialize correctly at service startup.
That failure generated a warning in the server log.
Check the logs for the details on the failure.
at fuego.connector.ConnectorException.connectorNotInitialized(ConnectorException.java:60)
at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:527)
at fuego.connector.CompositeConnectorService.getDirectoryConnectorInterface(CompositeConnectorService.java:446)
at fuego.connector.CompositeConnectorService.getConnectorInterface(CompositeConnectorService.java:293)
at fuego.connector.ConnectorTransaction.registerConnectorInterfaceCoordinator(ConnectorTransaction.java:656)
at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:315)
at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:68)
... 50 moreWhile still using PAPI, try also adding b1oracle.jar, b1base.jar and b1util.jar to your ADF project.
These jars could be found from your BPM Studio installation.
HTH -
Weblogic 8.1 - Error 500 Internal Server Error
Please advise,
Often we encounter this problem in our Weblogic application server. It is configured as node manager running 4 ports.
The only solution is to restart port with error. 1 or more ports start giving error on Web Page as mentioned below:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Server trace log shows the following:
####<Nov 24, 2010 10:57:21 PM GMT+04:00> <Error> <HTTP> <dxbap01> <MAXSERVER02> <ExecuteThread: '23' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101017> <[ServletContext(id=29550756,name=maximo,context-path=/maximo)] Root cause of ServletException.
psdi.util.MXSystemException: Error getting maxmessage value for group login and key username.
at psdi.server.MXServer.getMessage(MXServer.java:2552)
at psdi.server.MXServer.getMessages(MXServer.java:2582)
at psdi.util.RMISession.getMessages(Unknown Source)
at jsp_servlet._webclient._login.__login._jspService(__login.java:364)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Server thread Dump shows the following:
25 Nov 2010 06:17:40:405 [ERROR] A major exception has occurred.
Closed Connection
psdi.util.MXSystemException: A major exception has occurred.
Closed Connection
at psdi.server.MaxSession.getServerInfo(Unknown Source)
at psdi.server.MaxSessionThread.run(Unknown Source)
Caused by: java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.privatePrepareStatement(OracleConnection.java:962)
at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:869)
at psdi.server.ConRef.prepareStatement(Unknown Source)
... 2 more
[Full GC 113478K->113433K(250872K), 0.9796708 secs]
25 Nov 2010 06:18:40:408 [ERROR] Error getting server information in MAXSESSION
java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.privatePrepareStatement(OracleConnection.java:962)
at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:869)
at psdi.server.ConRef.prepareStatement(Unknown Source)
at psdi.server.MaxSession.getServerInfo(Unknown Source)
at psdi.server.MaxSessionThread.run(Unknown Source)
25 Nov 2010 06:18:40:408 [ERROR] A major exception has occurred.
Closed Connection
psdi.util.MXSystemException: A major exception has occurred.
Closed Connection
at psdi.server.MaxSession.getServerInfo(Unknown Source)
at psdi.server.MaxSessionThread.run(Unknown Source)
Caused by: java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.privatePrepareStatement(OracleConnection.java:962)
at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:869)
at psdi.server.ConRef.prepareStatement(Unknown Source)
... 2 more
[Full GC 113493K->113434K(250872K), 1.0056559 secs]Hi,
Thanks for the reply.
Yes you are correct, i compiled using jdk1.5.
but my servlet code will not compile in jdk1.4 version since i used advanced vaector classes in that.
Is there any settings like script file that need to be changed so that i can point to my jdk1.5 compiler rather than the default one pointed by weblogic.
Thanks in advance
Ram -
Weblogic Server error - OutOfMemoryError: PermGen space
Dear All,
For Oracle BPM 11g (Implement the Process Model) implementation on windows
I am using windows 7 64 Bit OS. I have
Installed 10g DB
Run the RCU Utility for SOAINFRA, ORABAM, SSPDM and MDS schemas successfully.
Installed Weblogic Server 11gr1(10.3.5)
Installed Oracle Jdeveloper 11g - 11.1.1.6.0
Installed SOA 11g using \Java\jdk1.6.0_24
From Jdeveloper I installed the extensions for SOA Composite Editor and BPM studio.
Created Domain for SOA server
All installations, utitlities and configurations completed successfully.
After starting the Weblogic Admin. server (server is up and OK)
The Problem starts here
When I login to weblogic Admin console I get the following error
javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space on
the command prompt window and even on the browser window.
I am able to trace the problem. To get the Idea following are some details of
$MW_HOME/user_projects/domains/soa_domain/bin/setDomainEnv.cmd
call "%WL_HOME%\common\bin\commEnv.cmd"
call "%DOMAIN_HOME%\bin\setSOADomainEnv.cmd"
call "%DOMAIN_HOME%\bin\setSOADomainEnv.cmd"
set WLS_HOME=%WL_HOME%\server
set XMS_SUN_64BIT=256
set XMS_SUN_32BIT=256
set XMX_SUN_64BIT=512
set XMX_SUN_32BIT=512
set XMS_JROCKIT_64BIT=256
set XMS_JROCKIT_32BIT=256
set XMX_JROCKIT_64BIT=512
set XMX_JROCKIT_32BIT=512
if "%JAVA_VENDOR%"=="Sun" (
set WLS_MEM_ARGS_64BIT=-Xms256m -Xmx512m
set WLS_MEM_ARGS_32BIT=-Xms256m -Xmx512m
) else (
set WLS_MEM_ARGS_64BIT=-Xms512m -Xmx512m
set WLS_MEM_ARGS_32BIT=-Xms512m -Xmx512m
if "%JAVA_VENDOR%"=="Oracle" (
set CUSTOM_MEM_ARGS_64BIT=-Xms%XMS_JROCKIT_64BIT%m -Xmx%XMX_JROCKIT_64BIT%m
set CUSTOM_MEM_ARGS_32BIT=-Xms%XMS_JROCKIT_32BIT%m -Xmx%XMX_JROCKIT_32BIT%m
) else (
set CUSTOM_MEM_ARGS_64BIT=-Xms%XMS_SUN_64BIT%m -Xmx%XMX_SUN_64BIT%m
set CUSTOM_MEM_ARGS_32BIT=-Xms%XMS_SUN_32BIT%m -Xmx%XMX_SUN_32BIT%m
set MEM_ARGS_64BIT=%CUSTOM_MEM_ARGS_64BIT%
set MEM_ARGS_32BIT=%CUSTOM_MEM_ARGS_32BIT%
if "%JAVA_USE_64BIT%"=="true" (
set MEM_ARGS=%MEM_ARGS_64BIT%
) else (
set MEM_ARGS=%MEM_ARGS_32BIT%
set MEM_PERM_SIZE_64BIT=-XX:PermSize=128m
set MEM_PERM_SIZE_32BIT=-XX:PermSize=128m
After taking the backup
I tried changing the Permsize to 256, 512 and even 1024.
started the Weblogic Admin server and tried to login, but the same error.
Details of setSOADomainEnv.cmd
set JAVA_OPTIONS=%JAVA_OPTIONS%
set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
what are the recommended values I need to put for Permsize in setDomainEnv.cmd?
Do I also need to change the values in setSOADomainEnv.cmd ?
Please correct me where I am wrong. How can the OutOfMemoryError: PermGen space
issue be resolved ?
Thanks
Ajaz AhmedHi Lakshman,
Thanks for the prompt resonse.
1. How many managed servers do you have in your domain ?
I have only one managed server (soa_server1)
2. If yes, How you are starting the Managed server ? Is that by Nodemanager or Startscript ?
Yes. I start the managed server by startscript (using startmanagedweblogic)
3. Can you check the <managed_server1>.out log file what java heap size is mentioned ?
I have not reached the managed server startup (though it starts and gives
the last line as SOA platform is accepting and running the requiests.
My problem is with weblogic server, which after login I get the Permgen out of memory error.
4. Can you show us the start up arguements of your each managed server ?
AdminConsole-->Environments---.Servers--->YourManagedServer--->Configuration (TAB)--->ServerStart (SubTab)---> Arguments:(TextArea)
I am not able to get the console. Because when I login the weblogic console,
Immediately I get the error as
javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space
Please clear my doubt as which of the files
setDomainEnv.cmd or setSOADomainEnv.cmd, I should change the values and
into which file and which step.
My priority is weblogic console to be working without any errors. So Far Managed server is OK.
Thanks
Ajaz Ahmed
Maybe you are looking for
-
Not able to get Image dimensions
I am using this code to get the java.awt.Image object Image inImage = Jimi.getImage(inputStream, Jimi.SYNCHRONOUS); I am using Jimi because I am running my code on jdk 1.3 and cannot use JAI. For some images, when I do inImage.getHeight(null); I get
-
Production Support for Multiple BI roll-outs
Hello BI Experts, This might be more of an administrative question, but I will need inputs from Developer's perspective. We are having 2 implemenation projects going on at the moment. They are sharing same ECC 6.0 & BI 7.0 landscape. But as the 2 pro
-
As i have said guys with my Xp 2000 set to the propper high end settengs it just wont boot, Im fairly sure the drivers that were found after flashing to 2.7 on my 6737 board were. APCI button & APCI bios configeration, not 100% sure though. i saved m
-
I have been toying with the idea of purchasing an iPad 2. Me and my wife both have separate iTunes accounts as we both have iPhones. I just wondered if it's possible to log into more than one iTunes account on one iPad, or if not would we have to se
-
Is Developer 6.0 stable and useful enough to upgrade?
with Developer2.0, one would have saved a lot of heartache by delaying the upgrade till 2.1 Do people have similar experiences with Dev 6.0? How can one justify migrating from dev2.x to dev6.x? (any must have features, major performance improvements,