XE on remote Debian: Timeout on webconsole

Hi Friends,
This one has been bothering me for a week, and no luck searching the forum.
Hope anyone can help me with this:
I successfully managed to install XE on a remote VPS.
It tells me to access through http://127.0.0.1:8080/apex but typing this into the browser is giving me a timeout in both Firefox and IE
(in dutch the message is :
De wachttijd voor de verbinding is verstreken
De server op [IP-ADDRESS] doet er te lang over om te antwoorden. )
the link I use in the browser is http://[IP-ADDRESS]:8080/apex the only response i get is using http://[IP-ADDRESS] --> this returns I think the Debian default message 'It Works !'
I tried
EXEC DBMS_XDB.SETLISTENERLOCALACCESS(FALSE);
and then restarting the DB but didn't help.
A former install on a Windows machine worked fine for me, any help by Linux guru's would be highly appreciated.
Thanks in advance,
Marco

mak wrote:
Not quite,
The server running debian is hosted by another party, I only have FTP and SSH access to it (and http through my local browser, of course). So there is no way I can check the console through 'localhost', is there ?
The other party delivered me a 'clean' install and the only thing I installed was XE, following the Oracle install guide.
Since you have 'ssh', you have 'ssh -X'. WHich should give you access to the GUI and therefore the broiwser on that machine. SO you CAN test browser against localhost.
The only way for me to get an actual http response is when I fill in the IP-address in my browser. It shows me a HTML page stored in /var/www (Displaying 'It works!').
The call to apex results in the timeoutUntil you have a way to verify that Apex is working properly on the far end, you will have issues.
>
+even though you can ping {apex-machine}, can telnet to apex-machine port 8080, have turned off any firewalls (and disabled SELinux if applicable) and nothing else is running on 8080 on the Apex machine.+
I can ping the machine OK.
I use PuTTY to work on the server (have not tried telnet, please advise)Command line: "telnet {host} 8080" ... if it responds with any gobbeldygooik, you can get there. http://lmgtfy.com/?q=using+telnet+on+windows for help.
I have no knowledge of firewalls or SELinux, let alone whether they are turned offFirewall on your (Windows) machine? (Look at the Control Panel ...)
How can I check what all is running on 8080 ?Windows and Linux COmmand line: Netstat http://lmgtfy.com/?q=using+netstat+on+windows and http://lmgtfy.com/?q=using+netstat+on+linux for help for help

Similar Messages

  • WebLogic Builder remote-client-timeout

    Just wondering if anyone has encountered this before.
    After using WebLogic Builder to make and save changes to an EAR file the weblogic-ejb-jar.xml file is updated to include the remote-client-timeout tag. This tag causes warning messages in the weblogic console.
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldEJB</ejb-name>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>test.HelloWorldHome</jndi-name>
    <remote-client-timeout>0</remote-client-timeout>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Warning Messages
    <Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.>

    I think the tool sets the default value for this flag. The default value
    should not have any effect. However, I would expect the tool (weblogic
    builder) not to insert this element in the descriptor.
    More details on this setting can be found here -
    http://e-docs.bea.com/wls/docs81/rmi/rmi_api.html#rmi_timeout
    --Sathish
    <Colin Yeung> wrote in message news:[email protected]..
    Just wondering if anyone has encountered this before.
    After using WebLogic Builder to make and save changes to an EAR file the
    weblogic-ejb-jar.xml file is updated to include the remote-client-timeout
    tag. This tag causes warning messages in the weblogic console.
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldEJB</ejb-name>
    <transaction-descriptor>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>test.HelloWorldHome</jndi-name>
    <remote-client-timeout>0</remote-client-timeout>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Warning Messages
    <Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB
    HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout
    specifies a rmi level timeout in seconds for remote clients that call the
    home and remote methods of the ejb. The method call(s) timeout on the
    client side after the specified number of seconds. The server will
    continue to process the request(s) and may change the state. The rmi level
    timeout shall be set by the container only for non-transactional methods
    (i.e,
    method with tx-attributes of Never or Not-Supported). Please ensure that
    the parameter is used only for methods that are idempotent in nature.>

  • WAP Remote Console Timeout

    We are experiencing users getting timed out of the Remote Console after 1 hour.  Normally I would go into the RD Gateway server and change the timeout policy but I do not see the policy folder on the RD Gateway nor can I locate anywhere to increase
    the Remote Console time.
    Does anyone know where to change this setting so users can keep a remote console window open for more than an hour?

    Hi,
    To modify the RDS timeout settings, please refer to the link below:
    https://social.technet.microsoft.com/Forums/en-US/00c2252b-8ec0-489f-8da2-07a434a9b5a2/forum-faq-restrict-number-of-active-sessions-in-rds-2012-and-2012-r2?forum=winserverTS
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Remote Connection Timeouts - ORA-03113 Errors

    I have two Sun Solaris servers running Oracle 10.1.0.4. One is our production server, the other is our test server. Both servers are using the same parameters in the SQLNET.ORA file located on each server. All Oracle Net files are located under /var/opt/oracle. The TNS_ADMIN environmental variable is set to /var/opt/oracle on both servers.
    When I connect to the production server via TOAD, OEM, or SQL*Plus from my desktop, I can remain connected as long as I like. If after two hours, I want to run another SQL, I type it in and it runs.
    When I connect to the test server via TOAD, OAM, or SQL*Plus from my desktop, I can remain connected for only 30 mins of inactivity. After which, if I issue a new SQL statement, I receive an ORA-03113 end-of-file communication channel error.
    I believe I've checked everything on both servers and they appear identical. Both of these server sit behind a firewall. So my feeling is that only the firewall could be causing the idle timeout connections to be dropped on the test server.
    Anyone have any ideas on this??
    P.S. - I realize that killing idle connections is actually a good thing, but I'm trying to verify the reason for the difference and not whether this is or is not a good networking practice.

    user583592 wrote:
    I have two Sun Solaris servers running Oracle 10.1.0.4. One is our production server, the other is our test server. Both servers are using the same parameters in the SQLNET.ORA file located on each server. All Oracle Net files are located under /var/opt/oracle. The TNS_ADMIN environmental variable is set to /var/opt/oracle on both servers.
    When I connect to the production server via TOAD, OEM, or SQL*Plus from my desktop, I can remain connected as long as I like. If after two hours, I want to run another SQL, I type it in and it runs.
    When I connect to the test server via TOAD, OAM, or SQL*Plus from my desktop, I can remain connected for only 30 mins of inactivity. After which, if I issue a new SQL statement, I receive an ORA-03113 end-of-file communication channel error.
    I believe I've checked everything on both servers and they appear identical. Both of these server sit behind a firewall. So my feeling is that only the firewall could be causing the idle timeout connections to be dropped on the test server.
    Anyone have any ideas on this??
    P.S. - I realize that killing idle connections is actually a good thing, but I'm trying to verify the reason for the difference and not whether this is or is not a good networking practice.The firewall could very well be the culprit. I had that problem at a previous employer. Why not check with your network guys and find out?

  • IPhone remote app disconnects, iPad does not

    Environment Info
    Windows 7 64-bit
    iTunes 12.1.2.27
    Latest update on iPhone and iPad
    Remote app
    Single network, single wireless access point
    I have home sharing turned on in iTunes, I play my music throughout my entire house from my PC and control via the remote app. I migrated my iTunes library to another PC and I am now having remote issues. Now the remote app frequently disconnects after my phone locks and the only way I can get it to reconnect is by turning off home sharing and back on again. I've made sure to turn off sharing on the other PC, and uninstalled iTunes.
    After some testing it seems that the disconnect does not happen on my iPad, only my iPhone. I've gone through the home sharing troubleshooting page, obviously my home sharing is working, just not all the time. I have to turn it off and on again to kick in the head. I've also disabled IPv6 as well.

    Hmmm interesting, I'll have to see if I can change that option. This isn't my setup, its a friends.
    I may have been running into a different issue. I got down and dirty and pulled out Wireshark to see what was happening and found some interesting things. My friend has two wireless access points and I was wondering if we were running into an issue with WiFi going into sleep mode on the phone and the remote app timeout while waiting for the wireless connection.
    I disabled the second AP and things seemed to work better, but the remote would still fail to connect once in a while. Thats when I saw that the remote app makes a DNS SRV request looking for a PC on the network that has iTunes, so I looked at the DNS settings on the iPhone and noticed that DNS was pointing to two ISP DNS servers first, then the internal router DNS. I swapped the internal DNS first, and ISP DNS second, renewed the DHCP lease on the phone and things are working great now.
    Either way it seems like the remote app is a bit tempermental with its timeout, it seems like it either gets stuck looking while it waits for WiFi or a DNS response. But at least its working much better now, sorry for the long post.

  • Redelivery limit not working for transaction timeout?

    hi,
              we have a redelivery limit on a queue that works, except for when there is a transaction timeout. in this case, the message seems to be redelivered infinitely. Is this a bug? a feature?
              we are using Weblogic Server 8.1 SP4. we don't have the source code, so i am not sure how the error handling is done or what exceptions are thrown.
              ------------------ejb-jar.xml------------
              <message-driven>
              <ejb-name>ImporFileReceiver</ejb-name>
              <ejb-class>au.com.auspost.pcms.common.integration.ejb.mdb.ImporFileReceiverMdb</ejb-class>
              <transaction-type>Container</transaction-type>
              <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
              <message-driven-destination>
              <destination-type>javax.jms.Queue</destination-type>
              <subscription-durability>NonDurable</subscription-durability>
              </message-driven-destination>
              </message-driven>
              <container-transaction>
              <method>
              <ejb-name>ImporFileReceiver</ejb-name>
              <method-intf>Local</method-intf>
              <method-name>onMessage</method-name>
              <method-params>
              <method-param>javax.jms.Message</method-param>
              </method-params>
              </method>
              <trans-attribute>NotSupported</trans-attribute>
              </container-transaction>
              <container-transaction>
              <method>
              <ejb-name>ImporFileReceiver</ejb-name>
              <method-intf>Remote</method-intf>
              <method-name>onMessage</method-name>
              <method-params>
              <method-param>javax.jms.Message</method-param>
              </method-params>
              </method>
              <trans-attribute>NotSupported</trans-attribute>
              </container-transaction>
              ------------------------ weblogic-ejb-jar.xml ---------
              <weblogic-enterprise-bean>
              <ejb-name>ImporFileReceiver</ejb-name>
              <message-driven-descriptor>
              <pool>
              <max-beans-in-free-pool>10</max-beans-in-free-pool>
              <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>jms/pcmsImportFileQueue</destination-jndi-name>
              <connection-factory-jndi-name>jms/pcmsConnectionFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <transaction-descriptor>
              <trans-timeout-seconds>3600</trans-timeout-seconds>
              </transaction-descriptor>
              <reference-descriptor>
              </reference-descriptor>
              <dispatch-policy>pcms.execute.queue.mdb.internal</dispatch-policy>
              <remote-client-timeout>0</remote-client-timeout>
              </weblogic-enterprise-bean>
              ------------------------ config.xml -----------------
              <JMSServer Name="eParcel JMS server"
              Store="eParcel JMS Server File Store" Targets="wls_pcms_prod1">
              <JMSQueue CreationTime="1190981682976"
              ErrorDestination="PCMS Import File Error Queue"
              JNDIName="jms/pcmsImportFileQueue"
              Name="PCMS Import File Queue" RedeliveryLimit="2"/>
              <JMSQueue CreationTime="1208347415759"
              JNDIName="jms/pcmsImportFileErrorQueue" Name="PCMS Import File Error Queue"/>
              </JMSServer>
              <JMSConnectionFactory JNDIName="jms/pcmsConnectionFactory"
              Name="eParcel JMS Connection Factory" Targets="wlc_pcms_prod"/>
              <JMSConnectionFactory JNDIName="jms/pcmsXAConnectionFactory"
              Name="eParcel JMS XA Connection Factory" Targets="wlc_pcms_prod" XAConnectionFactoryEnabled="true"/>
              -------------- weblogic log ---------------
              ####<24/04/2008 01:53:58 PM EST> <Warning> <EJB> <HX415> <wls_pcms_prod1> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <project_admin> <> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
              javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
              Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+)
              at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(I)V(ServerTransactionImpl.java:1614)
              at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Ljava/util/List;I)V(ServerTransactionManagerImpl.java:1117)
              at weblogic.transaction.internal.TransactionManagerImpl.wakeUp()V(TransactionManagerImpl.java:1881)
              at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp()V(ServerTransactionManagerImpl.java:1034)
              at weblogic.transaction.internal.WLSTimer.trigger(Lweblogic/time/common/Schedulable;)V(WLSTimer.java:31)
              at weblogic.time.common.internal.ScheduledTrigger.run()Ljava/lang/Object;(Optimized Method)
              at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(Optimized Method)
              at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;(SecurityManager.java:121)
              at weblogic.time.common.internal.ScheduledTrigger.executeLocally()V(ScheduledTrigger.java:229)
              at weblogic.time.common.internal.ScheduledTrigger.execute(Lweblogic/kernel/ExecuteThread;)V(ScheduledTrigger.java:223)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(Optimized Method)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread;)V(Unknown Source)
              ; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 3599 seconds
              Name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)],Xid=BEA1-696C9947A48195BA18DC(68926234),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3599,seconds left=60,activeThread=Thread[ExecuteThread: '12' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@447373e,re-Registered = false),SCInfo[wlsd_auspost_prod+wls_pcms_prod1]=(state=active),properties=({weblogic.transaction.name=[EJB au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean.handleMessage(org.apache.xmlbeans.XmlObject)], weblogic.jdbc=t3://10.3.2.35:7003}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+, XAResources={JMS_eParcel JMS Server File Store, weblogic, wlsd_auspost_prod, com},NonXAResources={})],CoordinatorURL=wls_pcms_prod1+10.3.2.35:7003+wlsd_auspost_prod+t3+).

    Thanks Tom,
              Good point. The timeout exception is on ImportFileHandlerBean.handleMessage()....which is a session bean. The MDB must call this session bean, which also has a 3600 second timeout. It is confusing since the descriptor for the MDB has the transaction-timeout set, but i assume this is ignored for 'not-supported').
              I guess you would need to look at the code, but is there anyway a message go back on the queue, and not get the redelivery incremented?
              (I just had an evil thought...maybe the code could be physically sending the message onto the queue again when there is a timeout on the session bean.....hence would not get the redelivery incremented.....)
              -------------- ejb-jar.xml ----------------
              <session>
              <ejb-name>ImportFileHandler</ejb-name>
              <local-home>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocalHome</local-home>
              <local>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerLocal</local>
              <ejb-class>au.com.auspost.pcms.common.integration.ejb.ImportFileHandlerBean</ejb-class>
              <session-type>Stateless</session-type>
              <transaction-type>Container</transaction-type>
              </session>
              ----------- weblogic-ejb.jar.xml -----------
              <weblogic-enterprise-bean>
              <ejb-name>ImportFileHandler</ejb-name>
              <stateless-session-descriptor>
              </stateless-session-descriptor>
              <transaction-descriptor>
              <trans-timeout-seconds>3600</trans-timeout-seconds>
              </transaction-descriptor>
              <reference-descriptor>
              </reference-descriptor>
              <enable-call-by-reference>True</enable-call-by-reference>
              <local-jndi-name>ejb/ImportFileHandlerLocal</local-jndi-name>
              <remote-client-timeout>0</remote-client-timeout>
              </weblogic-enterprise-bean>

  • Web service client timeout

    Hi,
    I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
    I am using weblogic 10.3.2, with Java 1.6.
    ============
    Properties propSys = System.getProperties();
    propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
    Stub stub = (Stub)portObject;
    BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
    bindingInfo.setTimeout(1);
    Iterator itr = stub._getPropertyNames();
    while (itr.hasNext()){
    Object element = itr.next();
    log("\n properties that can be set: "+element);
    stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
    ===========
    I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
    ===========
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>ExternalEntryEJB</ejb-name>
    <transaction-descriptor>
    <trans-timeout-seconds>1</trans-timeout-seconds>
    </transaction-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>ExternalEntry</jndi-name>
    <remote-client-timeout>1</remote-client-timeout>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>InternalEJB</ejb-name>
    <local-jndi-name>Internal</local-jndi-name>
    <enable-call-by-reference>True</enable-call-by-reference>
    <remote-client-timeout>1</remote-client-timeout>
    <transaction-descriptor>
    <trans-timeout-seconds>1</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    ===========
    in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
    ============
    <clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
    keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
    <classpath refid="build.classpath.builddir"/>
    </clientgen>
    ============
    I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
    I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
    Thanks,
    Walter

    Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
    <taskdef name="clientgen"
    classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    ((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
    ((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
    Hope that helps.

  • How to configure timeouts in wls 9.2?

    Hello,
    i have two problems i cannot resolve by myself or simply browsing through the net and I hope you can help me.
    Both the questions are about web applications on WeblogicServer 9.2
    1)
    I have a web application with a web service client inside. I use axis 2 and Http Client for the transport.
    I need to configure the connection timeout (not the socket timeout) but i cannot find any method to do this.
    The SSLSocketFactory does not expose a method to create the socket with a connection timeout as input parameter. The only way I figured out is to use the method without input parameters to obtain an unconnected socket, configure it as i wish and establish the connection:
    Socket socket = socketfactory.createSocket();
    SocketAddress localaddr = new InetSocketAddress(localAddress, localPort);
    SocketAddress remoteaddr = new InetSocketAddress(host, port);
    socket.bind(localaddr);
    socket.connect(remoteaddr, timeout);
    Unfortunately the methos createSocket() is not implemented by any socketFactory implementation i have available.
    What can I do?
    2)
    I have a web application with an EJB client inside. I need to configure a sort of timeout to break the connection if the server is taking too long.
    I have no control on the server side, so I can't use the <remote-client-timeout> to get the point.
    Is there any way to configure connection and socket timeout for the RMI call of an EJB client?
    Alternatively I have wrapped the client call in a separate thread, launched by a Timeout Controller.
    The controller waits for some time, then, if the Task is still alive , send it an interrupt and continue. The trick seems work fine, but the thread executing the task remains waiting for the EJB response and i risk to saturate the application server.
    Which is the best way to overcome the problem?
    Thank you.

    For the first question, have you tried using this:
    options.setProperty(HTTPConstants.CONNECTION_TIMEOUT, new Integer(timeOutInMilliSeconds));
    It seems to be explained well over here:
    http://ws.apache.org/axis2/1_3/http-transport.html#timeout_config
    This uses the axis2 http transport and not the jakarta commons httpclient.
    I have used some other properties of the axis2 http transport- but have not specifically used the connection_timeout property before.
    Is there a reason why you would use the httpclient over the axis2 http transport for a web service client?

  • Shared Memory Provider: Timeout error [258]

    Hi All,
    Hopefully there is somebody that can help me...
    When running the etl I'm getting the error: <SSIS Task>: Shared Memory Provider: Timeout error [258] ; followed by the message "Communication link failure".
    What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.
    When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 - 15 min. Statements are stored procedures that puts an index on 3 mil. records or update
    statements,...
    I had a look to all my (SSIS-etl) timeouts and they have the default value 0, the "remote query timeout" of the server is set to 10 minutes. According to me, these are the only one that exists?
    There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I'm working with the oledb \sql server native client 11.0 provider:
    SQLNCLI11.1.
    It is frustrating because I don't have a clear error message. Maybe there or other places to look? I had a look on the application log & sql server log but it did not made me any wiser...
    Any help is appriciated,
    Bram

    This is a part of the sql error log at the same time of the error, I'm not sure if it's related but you never know:
    Date,Source,Severity,Message
    04/01/2014 20:00:21,spid14s,Unknown,last target outstanding: 358<c/> avgWriteLatency 20
    04/01/2014 20:00:21,spid14s,Unknown,average throughput:   5.08 MB/sec<c/> I/O saturation: 5995<c/> context switches 14539
    04/01/2014 20:00:21,spid14s,Unknown,FlushCache: cleaned up 72812 bufs with 3099 writes in 112026 ms (avoided 476 new dirty bufs) for db 9:0
    04/01/2014 19:53:56,spid14s,Unknown,last target outstanding: 708<c/> avgWriteLatency 33
    04/01/2014 19:53:56,spid14s,Unknown,average throughput:  35.88 MB/sec<c/> I/O saturation: 25622<c/> context switches 43694
    04/01/2014 19:53:56,spid14s,Unknown,FlushCache: cleaned up 640748 bufs with 25437 writes in 139511 ms (avoided 59488 new dirty bufs) for db 9:0
    04/01/2014 19:44:13,spid14s,Unknown,last target outstanding: 682<c/> avgWriteLatency 75
    04/01/2014 19:44:13,spid14s,Unknown,average throughput:  55.22 MB/sec<c/> I/O saturation: 24846<c/> context switches 43655
    04/01/2014 19:44:13,spid14s,Unknown,FlushCache: cleaned up 646031 bufs with 25310 writes in 91397 ms (avoided 118 new dirty bufs) for db 9:0
    04/01/2014 18:34:03,spid14s,Unknown,last target outstanding: 194<c/> avgWriteLatency 16
    04/01/2014 18:34:03,spid14s,Unknown,average throughput:   9.68 MB/sec<c/> I/O saturation: 4396<c/> context switches 8644
    04/01/2014 18:34:03,spid14s,Unknown,FlushCache: cleaned up 78398 bufs with 3367 writes in 63280 ms (avoided 77538 new dirty bufs) for db 10:0

  • Third question - Using parameters in powershell recovery - Alert description

    Hi guys,
    With help i created powershell recovery in a management pack. Once again thanks very much, this is new to me. Now i know these parameters (variables):
    http://blogs.technet.com/b/kevinholman/archive/2009/09/23/alert-notification-subscription-variables-and-linking-that-to-the-console-database-and-sdk.aspx
    But how can i implement this in this XML? I think i must declare them in the XML, because when i put the variable there, it doesn't work. I would like to get the alert description in the message variable (see xml below)
    </Recovery>
    <Recovery ID="MomUIGenaratedRecovery28e1547022254ccbb82784c60d51b1d2" Accessibility="Public" Enabled="true" Target="Type603f92b7b83945598af55495615db953" Monitor="UIGeneratedMonitor0cd347f57f3949deb958cebb02d25555" ResetMonitor="false" ExecuteOnState="Error" Remotable="true" Timeout="300">
    <Category>Custom</Category>
    <WriteAction ID="MomUIGenaratedModule75df98fbfc5b48e39fd605cccd97d29b" TypeID="Windows!Microsoft.Windows.PowerShellWriteAction">
    <ScriptName>sendSMS.ps1</ScriptName>
    <ScriptBody>
    # function SendSMS
    # PowerShell function to send SMS messages via the CM SMS Gateway.
    function SendSMS{
    param([string]$url, [int]$customer, [string]$login, [string]$password, [string]$recipient, [string]$sender,[string]$reference)
    $xml = New-Object XML
    $messages = $xml.CreateElement("MESSAGES")
    $customerxml = $xml.CreateElement("CUSTOMER")
    $customerxml.SetAttribute("ID", $customer)
    $messages.AppendChild($customerxml)|Out-Null
    $user = $xml.CreateElement("USER")
    $user.SetAttribute("LOGIN", $login)
    $user.SetAttribute("PASSWORD", $password)
    $messages.AppendChild($user) |Out-Null
    if (!($reference.Equals(''))) {
    $refxml = $xml.CreateElement("REFERENCE")
    $refxml.Innertext = $reference
    $messages.AppendChild($refxml) |Out-Null
    $tariff = $xml.CreateElement("TARIFF")
    $tariff.InnerText = 0
    $messages.AppendChild($tariff) |Out-Null
    $msg = $xml.CreateElement("MSG")
    $from = $xml.CreateElement("FROM")
    $from.InnerText = $sender
    $msg.AppendChild($from) |Out-Null
    $to = $xml.CreateElement("TO")
    $to.InnerText = $recipient
    $msg.AppendChild($to) |Out-Null
    $body = $xml.CreateElement("BODY")
    $body.SetAttribute("TYPE", "TEXT")
    $body.InnerText = $message
    $msg.AppendChild($body) |Out-Null
    $messages.AppendChild($msg) |Out-Null
    $xml.AppendChild($messages) |Out-Null
    Write-Output $xml.OuterXml
    $webClient = New-Object net.WebClient
    return ($webClient.UploadString($url, $xml.OuterXml))
    # test
    SendSMS -url 'https://website.sms.nl/webservice.ashx' -recipient 0031612345678 -customer 1 -login 1 -password 'password' -sender 'Standby' -message 'Here i want the alert description' -reference '1234'
    </ScriptBody>
    <TimeoutSeconds>60</TimeoutSeconds>
    </WriteAction>
    Kind regards,
    André

    Parameters are defined between ScriptBody and TimeoutSeconds like this:
    <Parameters>
    <Parameter>
    <Name>param1</Name>
    <Value>$Config/param1$</Value>
    </Parameter>
    <Parameter>
    <Name>param2</Name>
    <Value>$Config/param2$</Value>
    </Parameter>
    </Parameters
    This information is available on MSDN.
    Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

  • Message Driven Bean reading multiple times from a jms queue

    Hi,
    I am facing a strange problem with my message driven bean. Its configured to read message from a jms queue. But sometimes it read the same message multiple times from the jms queue.
    We are using weblogic server 8.1 sp5.
    Please find below our descriptor files
    ejb-jar.xml  
    <ejb-jar>  
      <display-name>ClarifyCRM_Process_Manager_13.1</display-name>  
      <enterprise-beans>  
        <session>  
          <display-name>ProcessManager</display-name>  
          <ejb-name>ProcessManager</ejb-name>  
          <home>com.clarify.procmgr.ejb.ProcessManagerHome</home>  
          <remote>com.clarify.procmgr.ejb.ProcessManagerRemote</remote>  
          <ejb-class>com.clarify.procmgr.ejb.ProcessManagerEJB</ejb-class>  
          <session-type>Stateless</session-type>  
          <transaction-type>Container</transaction-type>  
        </session>  
        <message-driven>  
          <display-name>ProcessManagerListener</display-name>  
          <ejb-name>ProcessManagerListener</ejb-name>  
          <ejb-class>com.clarify.procmgr.ejb.ProcessManagerMDB</ejb-class>  
          <transaction-type>Bean</transaction-type>  
          <acknowledge-mode>Auto-acknowledge</acknowledge-mode>  
          <message-driven-destination>  
            <destination-type>javax.jms.Queue</destination-type>  
          </message-driven-destination>  
        </message-driven>  
      </enterprise-beans>  
      <assembly-descriptor>  
        <container-transaction>  
          <method>  
            <ejb-name>ProcessManager</ejb-name>  
            <method-name>*</method-name>  
          </method>  
          <trans-attribute>Required</trans-attribute>  
        </container-transaction>  
      </assembly-descriptor>  
    </ejb-jar>  
    weblogic-ejb-jar.xml  
    <weblogic-ejb-jar>  
      <weblogic-enterprise-bean>  
        <ejb-name>ProcessManager</ejb-name>  
        <stateless-session-descriptor>  
          <pool>  
            <max-beans-in-free-pool>100</max-beans-in-free-pool>  
            <initial-beans-in-free-pool>10</initial-beans-in-free-pool>  
          </pool>  
        </stateless-session-descriptor>  
        <enable-call-by-reference>False</enable-call-by-reference>  
        <jndi-name>ProcessManagerHome</jndi-name>  
        <dispatch-policy>PMExecuteQueue</dispatch-policy>  
        <remote-client-timeout>0</remote-client-timeout>  
      </weblogic-enterprise-bean>  
      <weblogic-enterprise-bean>  
        <ejb-name>ProcessManagerListener</ejb-name>  
        <message-driven-descriptor>  
          <pool>  
            <max-beans-in-free-pool>100</max-beans-in-free-pool>  
            <initial-beans-in-free-pool>10</initial-beans-in-free-pool>  
          </pool>  
          <destination-jndi-name>clarify.procmgr.jms.queue.Execution</destination-jndi-name>  
          <connection-factory-jndi-name>clarify.procmgr.jms.factories.ExecConnection</connection-factory-jndi-name>  
        </message-driven-descriptor>  
        <enable-call-by-reference>True</enable-call-by-reference>  
        <dispatch-policy>PMListenerExecuteQueue</dispatch-policy>  
        <remote-client-timeout>0</remote-client-timeout>  
      </weblogic-enterprise-bean>  
    </weblogic-ejb-jar>   The MDB is sometimes reading multiple times from clarify.procmgr.jms.queue.Execution
    Also i would like to add here that the connection factory we are using clarify.procmgr.jms.factories.ExecConnection is having the following properties
    ServerAffinity Enabled=true
    XA connection factory enabled=false.
    Please help me out here!!

    Maybe, your MDB "sometimes" throws an Exception in onMessage.
    Check if this happens when you set <max-beans-in-free-pool>1</max-beans-in-free-pool>.

  • Oracle RAC 2 node architecture-- Node -2 always gets evicted

    Hi,
    I have Oracle RAC DB with simple 2 node architecture( Host RHEL5.5 X 86_64) . The problem we are facing is, whenever there is network failure on either of nodes, always node-2 gets evicted (rebooted). We do not see any abnormal errors on alert.log file on both the nodes.
    The steps followed and results are:
    **Node-1#service network restart**
    **Result: Node-2 evicted**
    **Node-2# service network restart**
    **Result: Node-2 evicted**
    I would like to know why node-1 never gets evicted even if the network is down or restarted on node-1 itself?? Is this normal.
    Regards,
    Raj

    Hi,
    Please find the output below:
    2011-06-03 16:36:02.817: [    CSSD][1216194880]clssnmPollingThread: node prddbs02 (2) at 50% heartbeat fatal, removal in 14.120 seconds
    2011-06-03 16:36:02.817: [    CSSD][1216194880]clssnmPollingThread: node prddbs02 (2) is impending reconfig, flag 132108, misstime 15880
    2011-06-03 16:36:02.817: [    CSSD][1216194880]clssnmPollingThread: local diskTimeout set to 27000 ms, remote disk timeout set to 27000, impending reconfig status(1)
    2011-06-03 16:36:05.994: [    CSSD][1132276032]clssnmvSchedDiskThreads: DiskPingMonitorThread sched delay 760 > margin 750 cur_ms 1480138014 lastalive 1480137254
    2011-06-03 16:36:07.493: [    CSSD][1226684736]clssnmSendingThread: sending status msg to all nodes
    2011-06-03 16:36:07.493: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:08.084: [    CSSD][1132276032]clssnmvSchedDiskThreads: DiskPingMonitorThread sched delay 850 > margin 750 cur_ms 1480140104 lastalive 1480139254
    2011-06-03 16:36:09.831: [    CSSD][1216194880]clssnmPollingThread: node prddbs02 (2) at 75% heartbeat fatal, removal in 7.110 seconds
    2011-06-03 16:36:10.122: [    CSSD][1132276032]clssnmvSchedDiskThreads: DiskPingMonitorThread sched delay 880 > margin 750 cur_ms 1480142134 lastalive 1480141254
    2011-06-03 16:36:11.112: [    CSSD][1132276032]clssnmvSchedDiskThreads: DiskPingMonitorThread sched delay 860 > margin 750 cur_ms 1480143124 lastalive 1480142264
    2011-06-03 16:36:12.212: [    CSSD][1132276032]clssnmvSchedDiskThreads: DiskPingMonitorThread sched delay 950 > margin 750 cur_ms 1480144224 lastalive 1480143274
    2011-06-03 16:36:12.487: [    CSSD][1226684736]clssnmSendingThread: sending status msg to all nodes
    2011-06-03 16:36:12.487: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:13.840: [    CSSD][1216194880]clssnmPollingThread: local diskTimeout set to 200000 ms, remote disk timeout set to 200000, impending reconfig status(0)
    2011-06-03 16:36:14.881: [    CSSD][1205705024]clssgmTagize: version(1), type(13), tagizer(0x494dfe)
    2011-06-03 16:36:14.881: [    CSSD][1205705024]clssgmHandleDataInvalid: grock HB+ASM, member 2 node 2, birth 21
    2011-06-03 16:36:17.487: [    CSSD][1226684736]clssnmSendingThread: sending status msg to all nodes
    2011-06-03 16:36:17.487: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:22.486: [    CSSD][1226684736]clssnmSendingThread: sending status msg to all nodes
    2011-06-03 16:36:22.486: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:23.162: [ GIPCNET][1205705024]gipcmodNetworkProcessRecv: [network] failed recv attempt endp 0x2eb80c0 [0000000001fed69c] { gipcEndpoint : localAddr 'gipc://prddbs01:80b3-6853-187b-4d2e#192.168.7.1#33842', remoteAddr 'gipc://prddbs02:gm_prddbs-cluster#192.168.7.2#60074', numPend 4, numReady 1, numDone 0, numDead 0, numTransfer 0, objFlags 0x1e10, pidPeer 0, flags 0x2616, usrFlags 0x0 }, req 0x2aaaac308bb0 [0000000001ff4b7d] { gipcReceiveRequest : peerName '', data 0x2aaaac2e3cd8, len 10240, olen 0, off 0, parentEndp 0x2eb80c0, ret gipc
    2011-06-03 16:36:23.162: [ GIPCNET][1205705024]gipcmodNetworkProcessRecv: slos op : sgipcnTcpRecv
    2011-06-03 16:36:23.162: [ GIPCNET][1205705024]gipcmodNetworkProcessRecv: slos dep : Connection reset by peer (104)
    2011-06-03 16:36:23.162: [ GIPCNET][1205705024]gipcmodNetworkProcessRecv: slos loc : recv
    2011-06-03 16:36:23.162: [ GIPCNET][1205705024]gipcmodNetworkProcessRecv: slos info: dwRet 4294967295, cookie 0x2aaaac308bb0
    2011-06-03 16:36:23.162: [    CSSD][1205705024]clssgmeventhndlr: Disconnecting endp 0x1fed69c ninf 0x2aaab0000f90
    2011-06-03 16:36:23.162: [    CSSD][1205705024]clssgmPeerDeactivate: node 2 (prddbs02), death 0, state 0x80000001 connstate 0x1e
    2011-06-03 16:36:23.162: [GIPCXCPT][1205705024]gipcInternalDissociate: obj 0x2eb80c0 [0000000001fed69c] { gipcEndpoint : localAddr 'gipc://prddbs01:80b3-6853-187b-4d2e#192.168.7.1#33842', remoteAddr 'gipc://prddbs02:gm_prddbs-cluster#192.168.7.2#60074', numPend 0, numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x1e10, pidPeer 0, flags 0x261e, usrFlags 0x0 } not associated with any container, ret gipcretFail (1)
    2011-06-03 16:36:32.494: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:37.493: [    CSSD][1226684736]clssnmSendingThread: sending status msg to all nodes
    2011-06-03 16:36:37.494: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:40.598: [    CSSD][1216194880]clssnmPollingThread: node prddbs02 (2) at 90% heartbeat fatal, removal in 2.870 seconds, seedhbimpd 1
    2011-06-03 16:36:42.497: [    CSSD][1226684736]clssnmSendingThread: sending status msg to all nodes
    2011-06-03 16:36:42.497: [    CSSD][1226684736]clssnmSendingThread: sent 5 status msgs to all nodes
    2011-06-03 16:36:43.476: [    CSSD][1216194880]clssnmPollingThread: Removal started for node prddbs02 (2), flags 0x20000, state 3, wt4c 0
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmDoSyncUpdate: Initiating sync 178830908
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssscUpdateEventValue: NMReconfigInProgress val 1, changes 57
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmDoSyncUpdate: local disk timeout set to 27000 ms, remote disk timeout set to 27000
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmDoSyncUpdate: new values for local disk timeout and remote disk timeout will take effect when the sync is completed.
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmDoSyncUpdate: Starting cluster reconfig with incarnation 178830908
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSetupAckWait: Ack message type (11)
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSetupAckWait: node(1) is ALIVE
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSendSync: syncSeqNo(178830908), indicating EXADATA fence initialization complete
    2011-06-03 16:36:43.476: [    CSSD][1237174592]List of nodes that have ACKed my sync: NULL
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSendSync: syncSeqNo(178830908)
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmWaitForAcks: Ack message type(11), ackCount(1)
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmHandleSync: Node prddbs01, number 1, is EXADATA fence capable
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssscUpdateEventValue: NMReconfigInProgress val 1, changes 58
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmHandleSync: local disk timeout set to 27000 ms, remote disk timeout set t:
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmQueueClientEvent: Sending Event(2), type 2, incarn 178830907
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmQueueClientEvent: Node[1] state = 3, birth = 178830889, unique = 1305623432
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmQueueClientEvent: Node[2] state = 5, birth = 178830907, unique = 1307103307
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmHandleSync: Acknowledging sync: src[1] srcName[prddbs01] seq[73] sync[178830908]
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmSendAck: node 1, prddbs01, syncSeqNo(178830908) type(11)
    2011-06-03 16:36:43.476: [    CSSD][1240850064]clssgmStartNMMon: node 1 active, birth 178830889
    2011-06-03 16:36:43.476: [    CSSD][1247664448]clssnmHandleAck: src[1] dest[1] dom[0] seq[0] sync[178830908] type[11] ackCount(0)
    2011-06-03 16:36:43.476: [    CSSD][1240850064]clssgmStartNMMon: node 2 active, birth 178830907
    2011-06-03 16:36:43.476: [    CSSD][1240850064]NMEVENT_SUSPEND [00][00][00][06]
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSendSync: syncSeqNo(178830908), indicating EXADATA fence initialization complete
    2011-06-03 16:36:43.476: [    CSSD][1240850064]clssgmUpdateEventValue: CmInfo State val 5, changes 190
    2011-06-03 16:36:43.476: [    CSSD][1237174592]List of nodes that have ACKed my sync: 1
    2011-06-03 16:36:43.476: [    CSSD][1240850064]clssgmSuspendAllGrocks: Issue SUSPEND
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmWaitForAcks: done, msg type(11)
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSetMinMaxVersion:node1 product/protocol (11.2/1.4)
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSetMinMaxVersion: properties common to all nodes: 1,2,3,4,5,6,7,8,9,10,11,12,13,14
    2011-06-03 16:36:43.476: [    CSSD][1237174592]clssnmSetMinMaxVersion: min product/protocol (11.2/1.4)
    2011-06-03 16:36:43.476: [    CSSD][1240850064]clssgmQueueGrockEvent: groupName(IG+ASMSYS$USERS) count(2) master(1) event(2), incarn 22, mbrc 2, to member 1, events 0x0, state 0x0
    2011-06-03 16:36:43.477: [    CSSD][1237174592]clssnmSetMinMaxVersion: max product/protocol (11.2/1.4)
    2011-06-03 16:36:43.477: [    CSSD][1237174592]clssnmNeedConfReq: No configuration to change
    etc.etc....
    Let me know if any other logfile required. No unususal messages on /var/log/messages.
    Regards,
    Raj

  • Sample weblogic-ejb-jar.xml for Resource-ref EJB 3.0

    I am trying to create an MDB that can be re-used under different names.
    @MessageDriven(description = "An MDB that transfers messages from one Queue to another", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
    @TransactionAttribute(TransactionAttributeType.REQUIRED)
    public class TransferMdb implements MessageListener {
    private static final Logger LOG = Logger.getLogger(TransferMdb.class);
    @Resource(name = "jms/connfactory")
    private ConnectionFactory connectionFactory;
    @Resource(name = "jms/targetDestination")
    private Queue targetDestination;
    <ejb-jar version="3.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_3_0.xsd">
    <enterprise-beans>
    <message-driven>
    <ejb-name>TransferMdb</ejb-name>
    <ejb-class>TransferMdb</ejb-class>
    </message-driven>
    </enterprise-beans>
    </ejb-jar>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>TransferMdb</ejb-name>
    <message-driven-descriptor>
    <pool>
    <max-beans-in-free-pool>200</max-beans-in-free-pool>
    <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
    </pool>
    <destination-jndi-name>test_queue</destination-jndi-name>
    <transaction-descriptor>
    <trans-timeout-seconds>20</trans-timeout-seconds>
    </transaction-descriptor>
    </message-driven-descriptor>
    <reference-descriptor>
    <resource-description>
    <res-ref-name>jms/connectionfactory</res-ref-name>
    <jndi-name>connectionfactory</jndi-name>
    </resource-description>
    <resource-description>
    <res-ref-name>jms/targetDestination</res-ref-name>
    <jndi-name>reply_queue</jndi-name>
    </resource-description>
    </reference-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    However when I deploy the above, I get exceptions such as:
    problem: cvc-complex-type.2.4a: Expected elements 'initial-context-factory@http://www.bea.com/ns/weblogic/weblogic-ejb-jar provider-url@http://www.bea.com/ns/weblogic/weblogic-ejb-jar connection-factory-jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jms-polling-interval-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jms-client-id@http://www.bea.com/ns/weblogic/weblogic-ejb-jar generate-unique-jms-client-id@http://www.bea.com/ns/weblogic/weblogic-ejb-jar durable-subscription-deletion@http://www.bea.com/ns/weblogic/weblogic-ejb-jar max-messages-in-transaction@http://www.bea.com/ns/weblogic/weblogic-ejb-jar distributed-destination-connection@http://www.bea.com/ns/weblogic/weblogic-ejb-jar use81-style-polling@http://www.bea.com/ns/weblogic/weblogic-ejb-jar init-suspend-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar max-suspend-seconds@http://www.bea.com/ns/weblogic/weblogic-ejb-jar security-plugin@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' instead of 'transaction-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' here in element message-driven-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'transaction-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar iiop-security-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar resource-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar resource-env-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar ejb-reference-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar service-reference-description@http://www.bea.com/ns/weblogic/weblogic-ejb-jar enable-call-by-reference@http://www.bea.com/ns/weblogic/weblogic-ejb-jar network-access-point@http://www.bea.com/ns/weblogic/weblogic-ejb-jar clients-on-same-server@http://www.bea.com/ns/weblogic/weblogic-ejb-jar run-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar create-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar remove-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar passivate-as-principal-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar local-jndi-name@http://www.bea.com/ns/weblogic/weblogic-ejb-jar dispatch-policy@http://www.bea.com/ns/weblogic/weblogic-ejb-jar remote-client-timeout@http://www.bea.com/ns/weblogic/weblogic-ejb-jar stick-to-first-server@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' instead of 'reference-descriptor@http://www.bea.com/ns/weblogic/weblogic-ejb-jar' here in element weblogic-enterprise-bean@http://www.bea.com/ns/weblogic/weblogic-ejb-jar:<null>
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    Truncated. see log file for complete stacktrace
    I am clearly missing items in the weblogic-ejb-jar.xml. If anyone has a sample or tips, that would be awesome as a starting point.

    Those tags just declare that you are using our CMP provider and that
    your descriptor is in META-INF/weblogic-cmp-rdbms-jar.xml.
    FWIW, you might also want to check out EJBGen. It tends to keep more up
    to date with WLS than xdoclet.
    -- Rob
    Gen wrote:
    I am using xdoclets to generate descriptor file weblogic-ejb-jar.xml
    for a BMP entity bean. Xdoclet is generating the descriptor file
    alright, but is putting the following extra tags. This happens even
    for samples which come with the download, so my tags in java file are
    not wrong.
    My question is, are the extra tags below harmless, or should I
    manually go to each desciptor file and remove them?
    Thanks.
    ----------- EXTRA TAGS GENERATED START ---------
    persistence> <persistence-type>
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
    <type-version>6.0</type-version>
    <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
    </persistence-type>
    <persistence-use>
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
    <type-version>6.0</type-version>
    </persistence-use>
    </persistence>
    ----------- EXTRA TAGS GENERATED END ---------
    ----------- TAGS I PUT IN JAVA CLASS START --------
    * @ejb:bean name="com.ejb.entity.Customer"
    * jndi-name="com.ejb.entity.CustomerHome"
    * view-type="remote"
    * type="BMP"
    * primkey-field="com.ejb.entity.CustomerPK"
    * reentrant="false"
    * @weblogic:cache
    * max-beans-in-cache="1000"
    * read-timeout-seconds="900"
    * concurrency-strategy="ReadOnly"
    ----------- TAGS I PUT IN JAVA CLASS END --------

  • [Forum FAQ] Restrict number of Active Sessions in RDS 2012 and 2012 R2

    As everyone knows with the introduction of Windows Server 2012 & 2012 R2, there are various changes and no more availability for RDSH configurations or Remote Desktop Service Manager;
    now we can manage all the settings under Server Manager and group policy.
    Configuration 1: Remote Desktop Timeout settings:
    Here, we will see the Remote Desktop timeout settings. You can maintain the settings under below mention path (Figure 1 and Figure 2).
    Open the
    Server Manager, select Remote Desktop Services.
    In Remote desktop Services, in right side you can drop down to
    collections.
    Select the
    collection which you want to edit the settings.
    Under
    collections Properties, select Task and then Edit Properties.
    In Properties dialog box, select
    Session.
    You can find all the
    timeout settings under session collection properties; edit according to your requirements and then
    OK.
    Figure 1: Selecting Collection Properties
    Figure 2: Configuring screen for Timeout and reconnection Settings
    Group policy setting:
    The same settings can also be applied by Group Policy.
    You can also configure timeout and reconnection settings by applying the following Group Policy settings, you can check the figure 3 for graphical view.
    Set time limit for disconnected sessions
    Set time limit for active but idle Remote Desktop Services sessions
    Set time limit for active Remote Desktop Services sessions
    End session when time limits are reached
    In addition to this another group policy available with the help of which you can bale to set time limit for logging off the RemoteApp according to our desired time. This setting
    can be applied with addition to above mentioned policy.
    Set time limit for logoff of RemoteApp Sessions
    These Group Policy settings are located in the following locations:
    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
    User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
    These Group Policy settings can be configured by using either the Local Group Policy Editor or the Group Policy Management Console (GPMC).
    Note:
    These Group Policy settings will take precedence over the settings configured in Remote Desktop Session Host Configuration. If both the Computer Configuration and the User Configuration policy
    settings are configured, the Computer Configuration policy settings take precedence.
    Figure 3: Group Policy for setting Timeout and reconnection setting
    Configuration 2:
    Restrict & Enable user to a single & multiple session
    Under Windows Server 2012 & 2012 R2, there is no specific setting under RDP-TCP as it is not available.
    Restrict User to Single session:
    To restrict the user to single session (Disable Multiple RDP Session) you can configure the setting under group policy (Figure 4).
    Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Connections
    Restrict Remote Desktop Services users to a single Remote Desktop Services session     Enabled
    Figure 4: Group policy for Restrict user to Single session
    Enable user to multiple session:
    To enable the user to multiple session you can configure the setting under below (Figure 5).
    Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Connections
    Restrict Remote Desktop Services users to a single Remote Desktop Services session     Disabled
    Figure 5: Group Policy for Enable user to Multiple Session
    In addition you can also edit the registry setting for allowing multiple RDP session as per below (Figure 6).
    HKEY_Local_Machine\SYSTEM\CurrentControlSet\Control\Terminal Server
    fSingleSessionPerUser     REG_DWORD     0x00000000
    Note: By default the registry value is set to 1, but you need to change to 0.
    Figure 6: Display the registry settings
    Also you can edit the policy “Limit number of connections” and set RD Maximum collection as per your company
    requirements (Maximum limit: 999999) for above mention group policy path (Figure 7).
    Figure 7: Group Policy for Limit number of Connections
    Apart from this, if you have not specified any policy or registry setting and still you want to restrict the new session, then in Windows Server 2012 & 2012 R2 there is option where you
    need to follow below steps (Figure 8 and Figure 9).
    Right click a Remote Desktop Session Host in specified location of Host Server and select “Do not allow new connections”.
    After clicking that it will ask you for your confirmation, click yes and no new connection will be allowed.
    Figure 8: Setting displaying “Do not allow new connections”
    Figure 9: Confirmation popup
    RD Gateway Connection Properties:
    If you have deployed RD Gateway under your environment you can also limit the number of simultaneous connections through RD Gateway by configuring
    policy under RD Gateway Manager. For this you need to follow below mention path.
    Open RD Gateway Manager, select the server which you want to modify.
    Right click Properties.
    Under General Tab
    -Limit maximum allowed simultaneous
    connections to:Specify the number of connection you want to able to provide connection.
    -Allow the maximum
    supported simultaneous connections:This
    setting will allow maximum supported connections at a time.
    -Disable new connections:This
    setting will not allow new connections through RD Gateway but Active connection will not be automatically disconnected.
    Select the option as per requirement which able to allow the connection
    Figure 10: Connections setting under RD Gateway Manager
    Configuration 3: Configure keep-alive connection interval
    As per above mention in initial post you can able to change the setting for Keep alive connection interval. In addition to this also verify the
    registry setting must be set as per following (Figure 11 and Figure 12).
    HKEY_Local_Machine \ SOFTWARE \ Policies \ Microsoft \ Windows NT \ Terminal Services
    KeepAliveEnable       REG_DWORD           0x00000001 (1)
    KeepAliveInterval     
    REG_DWORD           0x00000001 (1)
    Figure 11: Group Policy setting for Keep alive
    Figure 12: Registry setting for keep alive
    If you need further assistance, welcome to post your questions in our
    Remote Desktop Services (Terminal Services) forum.
    If you would like to achieve this in Windows Server 2008 or Windows Server 2008 R2, please move on to the next post.

    Applies to Windows Server 2008 and Windows Server 2008 R2
    Configuration 1: Remote Desktop Timeout settings:
    1. Open the property dialog for RDP-Tcp connection in Remote Desktop Services Manager.
    2. In the Sessions tab, you can configure the following settings:
    Active Session Limit
    Idle session limit
    Action when session limit is reached or connection is broken
    End a disconnected session
    Additionally, you can configure the settings with the help of Group Policy also by below mention path.
    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
    User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
    Configuration 2: Restrict each user to a single session
    By using this configuration or policy setting, each user can only maintain one session to the certain terminal server; when another session is started by the same user, the original one will
    lose the connection. In that way, the total number of possible active sessions won’t exceed the total remote users. You can implement this as below mention steps.
    Remote Desktop Host (RDP-Tcp) configuration:
    Edit Settings – Restrict each user to a single session: Yes
    Group Policy: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop
    Services (Terminal Services)\Remote Desktop Services Session Host (Terminal Server)\Connections\
    Restrict Remote Desktop Services (Terminal Services) users to a single remote session:    Enabled
    Configuration 3: Configure keep-alive connection interval
    By specifying the minutes that the TS holds a remote session actually disconnected, the server will detect the session status after each period. The session that are actually offline will
    be changed to disconnected status:
    Group Policy:  
    Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services (Terminal Services)\Remote Desktop Services Session Host (Terminal Server)\Connections\
    Configure keep-alive connection interval:         Enabled and Specify the Value
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

  • Wls 10.3 versus websphere 6.1 performance problem

    Hi all,
    we migrate a j2ee application (involving web services based on axis 2 framework) from a websphere 6.1 to weblogic 10.3.3 without any particular tuning or refining
    The rilying databse is DB2 on As400 SYSTEM IN BOTH SCENARIOS.
    What we are experiencing is that in was 6.1 the timing request/response was x while in wls 10.3.3 is 2x.
    Any idea?
    Is there a problem with the jdbc driver?
    Any particular configuration missed for dealing with DB2?
    Thanks in advance
    N.

    No.There is no lower limit as such and it should time-out within the time specified based on my attempts with remote client timeout.
    Range of values:
    0 to maxSeconds, where maxSeconds is the maximum value of an int.
    Default value:
    0
    Can you try to restart the Weblogic managed server instance after making the changes in weblogic-ejb-jar.xml?
    -Sandeep

Maybe you are looking for