Stopping DB-Polling-Adapter when failure in mediator
Hi
I have a DB-Polling-Adapter that posts data directly to a mediator. When data is readed mediator does a logical delete, e.g 2 for field readstatus. So during reading readstatus is 9 and before 1.
When a failure happens in mediator (during xsl-transformation) mediator throws failure back to DB-Polling-Adapter. The problem is now that state of readingstatus is still 9 and after each polling sequence adaptor reads and posts same data again and the failure happens also.
Is there any posibility to send failure into error hospital and to set readstatus to 2, so that adapter doesn't poll the same data on and on? Catching mediator fault in fault-policies doesn't work.
I found two solutions: 1. Send data from Polling-Adapter to BPEL, 2. Sematron validation but it doesn't cover all posible failures.
Example failure during transformaiton:
ORAMED-03303:[Unexpected exception in case execution]Unexpected exception in request response operation "execute" on reference "Convert_JDE-to-Common". Possible Fix:Check whether the reference service is properly configured and running or look at exception for analysing the reason or contact oracle support. Cause:oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01201:[Error in transform operation]Error occurred while transforming payload using "xsl/F0006Collection_To_ProjectsCollection.xsl" for target part "reply".Possible Fix:Review the XSL or source payload. Either the XSL defined does not match with the payload or payload is invalid
Thx a lot for help.
Pascal
Issue solved.
Setting jca.retry.count=unlimited causes the adapter to behave as we want.
We had set jca.retry.count = 1 on the mistaken understanding that this related only to a failure to query/poll the database, and that sequence number was updated in a separate context that needed a global transaction to coordinate/rollback.
We don’t even need to propagate our global transaction from polling adapter to bpel component since all our writes happen in an OSB transaction; Our bpel just (re)throws a fault back to the polling adapter which is enough to trigger retry.
Similar Messages
-
Can't enforce sequence with polling adapter when faults
I'm trying to process records in sequence using a polling adapter and the update sequence table strategy
I have a polling adapter that invokes a composite app which calls an OSB service over http/soap.
polling adapter -> composite app -> OSB -> db adapter
On successful processing, the polling adapter updates a sequence table.
In the event of a fault, I expect the sequence table not to be updated and the failed record to be tried again on the next polling interval. However, even on failure, the sequence table is being updated.
My bpel component has the property
<property name="bpel.config.transaction" many="false" type="xs:string">required</property>
.. and a catch clause which throws a rollback on remote faults
The next polling interval picks up the next record and the problem repeats. We have then 'lost' the unprocessed record(s).
How can I force the polling adapter to block on failed records?
Thanks
GarretIssue solved.
Setting jca.retry.count=unlimited causes the adapter to behave as we want.
We had set jca.retry.count = 1 on the mistaken understanding that this related only to a failure to query/poll the database, and that sequence number was updated in a separate context that needed a global transaction to coordinate/rollback.
We don’t even need to propagate our global transaction from polling adapter to bpel component since all our writes happen in an OSB transaction; Our bpel just (re)throws a fault back to the polling adapter which is enough to trigger retry. -
Hello,
My white McBook (2008 or 2009) recently stopped turning on. When I hook up the Magsafe power adapter, the light shows green, but the computer will not turn on, or make a sound. I've tried the re-boot option, but nothing works. I first thought I needed a new battery because the lights at the back are all off, but shouldn't the computer turn on once the power adapter is hooked up and the light on the Magsafe adapter shows green? I'm a computer doofus, so please be kind. Please advise! Thanks in advance.
SSTake it in for service.
-
How do I run a JCA adapter when I am calling it from an EJB?
How do I run a JCA adapter when I am calling it from an EJB? Do I need to create an EJB client and place it in a Client container? If my EJB and JCA adapter are deployed is there a way to call my EJB from the command line?
MikeHi. When you look at the code I provided for you in other thread you will see that connecting to adapter is done through JNDI lookup. The creation of the adapter is done in your J2EE server. Here is some code for you where you can find mapping from code to ejb-jar and orion-ejb-jar.
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee"
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_2_1.xsd"
version="2.1">
<!--
This file declares the interface (needs/promises) of the message-driven bean.
The MDB requires:
- a JMS queue (to receive messages from the client),
- a JMS exception queue (to send undeliverable messages back to the source), and
- a connection factory (to communicate with a JMS resource provider).
Note that communication with the resource provider may be (and for this
application is) via a JMS Connector rather than direct.
-->
<display-name>JMS Consume MDB - opp-ifs</display-name>
<enterprise-beans>
<entity>
<description>Entity Bean ( BMP )</description>
<display-name>EBEjbMecomsIFS</display-name>
<ejb-name>EBEjbMecomsIFS</ejb-name>
<local-home>EBEjbMecomsIFSLocalHome</local-home>
<local>EBEjbMecomsIFSLocal</local>
<ejb-class>EBEjbMecomsIFSBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>java.lang.Long</prim-key-class>
<reentrant>false</reentrant>
<service-ref>
<service-ref-name>service/interceptor</service-ref-name>
<service-interface>javax.xml.rpc.Service</service-interface>
<wsdl-file>META-INF/wsdl/MHS5_Jms_In_RS.wsdl</wsdl-file>
<service-qname xmlns:ns="http://oracle.com/esb/namespaces/PilotOWSM_MustHavesScenario5">ns:ESB_MHS5_Jms_In_RS_Service</service-qname>
</service-ref>
</entity>
<message-driven>
<display-name>JMS Consume MDB - MDB</display-name>
<ejb-name>MDBEjbMecomsIFS</ejb-name>
<!-- name of bean in deployment descriptor (including orion-ejb-jar.xml file) -->
<ejb-class>MDBEjbMecomsIFSBean</ejb-class>
<!-- bean's fully qualified Java class name -->
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<!-- allow incoming messages to be included in transactions -->
<!-- The ejb requires a connection factory to access an external resource (JMS). -->
<ejb-local-ref>
<ejb-ref-name>ejb/local/EBEjbopp_ifs</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>EBEjbMecomsIFSLocalHome</local-home>
<local>EBEjbMecomsIFSLocal</local>
<ejb-link>EBEjbMecomsIFS</ejb-link>
</ejb-local-ref>
<resource-ref>
<!-- The resource's connection factory must be accessible at jndi location "java:comp/env/jms/QueueConnectionFactory". -->
<res-ref-name>jms/QueueConnectionFactory</res-ref-name>
<!-- The resource's connection factory must implement the "javax.jms.ConnectionFactory" interface. -->
<res-type>javax.jms.ConnectionFactory</res-type>
<!-- container managed authorization -->
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<!--
Declare that a global transaction is required when the onMessage method of the ejb named
"MDBEjbName" is called. This will cause the app server to automatically initiate a
global (XA) transaction before calling onMessage (actually, before even receiving the JMS
message that triggers onMessage) and end the transaction after onMessage returns. The
JMS Connector will automatically rollback the transaction if onMessage throws an
exception. onMessage may also set the transaction to be "rollback only".
Participating in global transactions requires that the connection factory provided in the
activation spec (see the ConnectionFactoryJndiName property earlier in this file) must be
XA-capable (it must implement the javax.jms.XAConnectionFactory interface).
If this declaration is ommitted, then onMethod will not be part of any global
transaction. In that case the connection factory provided in the activation spec must
implement the javax.jms.ConnectionFactory interface.
-->
<container-transaction>
<method>
<ejb-name>MDBEjbMecomsIFS</ejb-name>
<method-name>onMessage</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>EBEjbMecomsIFS</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
orion-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<orion-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNameSpaceSchemaLocation="http://www.oracle.com/technology/oracleas/schema/orion-ejb-jar-10_0.xsd">
<enterprise-beans>
<entity-deployment name="EBEjbMecomsIFS">
<service-ref-mapping name="service/interceptor">
<wsdl-location>http://on-poc62.ontw.alfa.local:7777/event/PilotOWSM/MustHavesScenario5/MHS5_Jms_In_RS?wsdl</wsdl-location>
<service-qname localpart="ESB_MHS5_Jms_In_RS_Service" namespaceURI="http://oracle.com/esb/namespaces/PilotOWSM_MustHavesScenario5"/>
<port-info>
<wsdl-port namespaceURI="http://oracle.com/esb/namespaces/PilotOWSM_MustHavesScenario5"
localpart="__soap_MHS5_Jms_In_RS_execute_ppt"/>
<service-endpoint-interface>javax.xml.rpc.Service</service-endpoint-interface>
<call-property>
<name>javax.xml.rpc.service.endpoint.address</name>
<value>http://on-poc62.ontw.alfa.local:7777/event/PilotOWSM/MustHavesScenario5/MHS5_Jms_In_RS</value>
</call-property>
<call-property>
<name>javax.xml.rpc.soap.http.soapaction.uri</name>
<value>execute</value>
</call-property>
<call-property>
<name>javax.xml.rpc.soap.http.soapaction.use</name>
<value>true</value>
</call-property>
<call-property>
<name>javax.xml.rpc.soap.operation.style</name>
<value>document</value>
</call-property>
<runtime enabled="owsm">
<owsm init-home="/oracle/product/SoaAs/10.1.3/owsm/config/interceptors/C0003002"
init-file="confluent.properties"/>
</runtime>
</port-info>
</service-ref-mapping>
</entity-deployment>
<message-driven-deployment name="MDBEjbMecomsIFS"
resource-adapter="OEMSJMSDRAopp-ifs"
enabled="true" max-instances="10">
<!--
The ejb requires a connection factory implementing the "javax.jms.XAConnectionFactory"
interface to be accessible at jndi location "java:comp/env/jms/QueueConnectionFactory". (see ejb-jar.xml and ....)
A suitable connection factory is already accessible at jndi location "OEMSJMSDRASubcontext/MyXACF" (see oc4j-ra.xml)
-->
<resource-ref-mapping location="OEMSJMSDRASubopp-ifs/MyXACF"
name="jms/QueueConnectionFactory"/>
<!-- don't misspell this or you'll get an RP CF which doesn't work -->
<!-- Required activation-spec properties. -->
<!--
ConnectionFactoryJndiName (string, no default)
This should be the JNDI location of an RA connection factory.
The JMS Connector will use this connection factory to create the JMS
connection it uses to receive messages for this MDB's onMessage. If the
exception queue is enabled (see UseExceptionQueue), the JMS Connector will
also use a connection created from this connection factory for the production
of messages to the exception queue.
This connection factory must be compatible with the message domain(s). (For
example, if the MDB is receiving messages from a queue, the connection
factory should implement javax.jms.[XA]QueueConnectionFactory or
javx.jms.[XA]ConnectionFactory.)
For XA/non-XA considerations, see the <container-transaction> comments later
in this file.
-->
<config-property>
<config-property-name>ConnectionFactoryJndiName</config-property-name>
<config-property-value>OEMSJMSDRASubopp-ifs/MyXAQCF</config-property-value>
</config-property>
<!--
DestinationName (string, no default)
This is JNDI location of the queue or topic from which messages to be
delivered to the MDB's onMessage method should be received.
The JNDI locations for RA destinations are defined in the
oc4j-connectors.xml file.
-->
<config-property>
<config-property-name>DestinationName</config-property-name>
<config-property-value>OEMSJMSDRASubopp-ifs/MyQ</config-property-value>
</config-property>
<!--
DestinationType (string, no default)
This must be set to the type of the destination named by the above
"DestinationName" property.
The EJB 2.1 spec states that this must be set to either javax.jms.Queue or
javax.jms.Topic. OracleGJRA also allows it to be set to
javax.jms.Destination (which works for both queues and topics).
-->
<config-property>
<config-property-name>DestinationType</config-property-name>
<config-property-value>javax.jms.Queue</config-property-value>
</config-property>
<!--
Other activation-spec properties.
The following activation-spec properties supported by OracleGJRA are optional
except where otherwise noted:
-->
<!--
ListenerThreadMaxPollInterval (milliseconds, 5000)
Listener threads "poll" to see if there is a message waiting to be processed.
The more frequently this polling is performed, the faster (on average) a given
listener thread can respond to a new message. The price for frequent polling is
overhead - the resource provider must process a receive request each time it is
polled.
Oracle's JMS Connector implementation applies an adaptive algorithm which
uses shorter polling intervals (high polling rates) during periods of activity
(once activity is noticed) and longer polling intervals (lower polling rates)
during periods of inactivity. The ListenerThreadMaxPollInterval property places
an upper limit on the polling interval used by this adaptive algorithm.
-->
<config-property>
<config-property-name>ListenerThreadMaxPollInterval</config-property-name>
<config-property-value>5000</config-property-value>
</config-property>
<!--
AcknowledgeMode (string, default = Auto-acknowledge)
This should be set to Auto-acknowledge or Dups-ok-acknowledge. This
controls the quality-of-service provided by listener threads which
consume messages and call the MDB's onMessage method.
MessageSelector (string, default = no message filtering)
This is the selector expression used to filter messages sent to the
MDB's onMessage method. (I.e., this is used as the messageSelector for
the JMS sessions created for the listener threads.)
SubscriptionDurability (string, default = NonDurable)
For topics this should be set to Durable or NonDurable. (This should
not be set for queues.) This controls the durability of the topic
consumer used by the listener thread. When SubscriptionDurability is
set to Durable (and DestinationType is javax.jms.Topic or
javax.jms.Destination), the SubscriptionName property is required.
SubscriptionName (string, no default)
This property is required when SubscriptionDurability is Durable (and
DestinationType is javax.jms.Topic or javax.jms.Destination). (In all
other cases it is ignored.) This is the name used when creating the
durable subscriber used by the listener thread. For a given JMS server,
a given subscription name should be assigned to at most one MDB (which
must have most one listener thread).
ClientId (string, no default)
If set, connection(s) used by the listener threads will be set to use
this client ID.
TransactionTimeout (milliseconds, default = 300,000)
This limits the amount of time that the JMS Connector will wait for a
message to arrive before exiting the current transaction. The
transaction manager limits the amount of time a transaction can last
(see transaction-timeout in transaction-manager.xml).
TransactionTimeout should be set such that the transaction manager will
not timeout the transaction during the onMessage routine unless
something is wrong. For example, If the transaction mananager timeout
is set to 30 seconds, and the onMessage routine will never take more
than 10 seconds unless something is wrong, then this property could be
set to 20 seconds (20000 milliseconds).
EndpointFailureRetryInterval (milliseconds, default = 60,000)
If an endpoint can not be processed (due to the app server WorkManager
not accepting new work), it will be scheduled to be retried this many
milliseconds later.
ReceiverThreads (integer, default = 1)
This sets the maximum number of listener threads to create for this
endpoint. For queues, using more than one thread may be useful in
increasing the rate at which messages can be consumed. For topics this
value should always be 1. (Each listener thread gets its own session
and TopicSubscriber. For durable subscribers it would be an error to
have more than one subscriber with the same subscription name. For
nondurable subscribers having more than one thread will not help because
more threads translates into more subscribers which translates into more
copies of each message.) See also: ListenerThreadMinBusyDuration
UseExceptionQueue (boolean, default = false)
When "UseExceptionQueue" is true:
- Messages that would otherwise be discarded are sent to the
exception queue. (Currently the only case where this happens is
when the max delivery count is exceeded. See MaxDeliveryCnt
property.) Rather than sending the original message directly to
the exception queue, the following procedure is used:
o Create a new message of the same type.
o Copy the properties and body from the original message to the
new message.
o If the headers were copied, sending the message to the
exception queue would cause most of them to be lost
(over-written by the resource-provider). So instead,
translate headers in the original to properties in the copy,
assigning each header obtained via "getJMS{Header}" to
property "GJRA_CopyOfJMS{Header}". Since
javax.jms.Destination is not a valid property type, translate
destination headers into descriptive messages.
(Currently this same service is not provided for JMSX*
properties, most notably the JMSXDeliveryCount property.)
o If some part of the copy process (above) or augmentation
process (below) fails, do not abort. Attempt to complete the
rest of the procedure. (For Bytes/Map/Stream message types,
this can mean that part of the body is copied and the rest is
not.)
o If the copy process is 100% successful, add a boolean property
called "GJRA_CopySuccessful" with the value "true".
o Add a string property called "GJRA_DeliveryFailureReason" which
indicates why the message was not delivered.
o If the MDB onMessage method generated an exception immediately
prior to the delivery failure, add a string property called
"GJRA_onMessageExceptions" which contains exception information.
o Send the resulting message to the exception queue.
Note that only one attempt is made to send the message to the
exception queue. Should this attempt fail, the message will
be discarded without being placed in the exception queue.
See IncludeBodiesInExceptionQueue property for potential variations
of the above procedure.
- The ExceptionQueueName property is required.
- In addition to being used for the primary destination, the
connection factory specified by the ConnectionFactoryJndiName
property will also be used for the exception queue. If the primary
destination (specified by the DestinationName property) is a topic,
then the connection factory must support both queues and topics.
(I.e., the <connectionfactory-interface> [see oc4j-ra.xml] for the
given connection factory must be either javax.jms.ConnectionFactory
or javax.jms.XAConnectionFactory.)
ExceptionQueueName (string, no default)
This is the JNDI location of the javax.jms.Queue object to use as the
exception queue. (See UseExceptionQueue property for information about
the use of the exception queue.) This property is required when
UseExceptionQueue is true, and ignored when UseExceptionQueue is false.
IncludeBodiesInExceptionQueue (boolean, default = true)
This controls whether or not messages sent to the exception queue will
include a message body. (See UseExceptionQueue property for information
about the use of the exception queue.) If many messages are sent to the
exception queue during normal operation and the message body is of no
use in the exception queue, then this property may be set false to
improve performance. This property is ignored when UseExceptionQueue is
false. There are two cases where this property does not apply:
- If the original message did not have a message body, then the
message sent to the exception queue will not have one either.
- If a copy of the original message can not be created for any
reason, then the original may be sent to the exception queue
instead. This may result in a message body being sent to the
exception queue.
MaxDeliveryCnt (integer, default = 5)
If a message has the "JMSXDeliveryCount" property and the value of that
property is greater than MaxDeliveryCnt, then the message will be
discarded (and not sent to onMessage). If the exception queue is
enabled (see UseExceptionQueue), a copy of the message will be sent to
the exception queue. If MaxDeliveryCnt is set to 0, no messages will be
discarded. (Note that when an MDB responds to a message by throwing an
exception, the message is not considered delivered and it may be
redelivered. If the MDB might always respond to a given message by
throwing an exception, and MaxDeliveryCnt is set to 0 to prevent the
message from ever being discarded, the result may be an MDB stuck in an
"infinite loop" - failing to process the same message over and over
again.)
-->
<config-property>
<config-property-name>MaxDeliveryCnt</config-property-name>
<config-property-value>0</config-property-value>
</config-property>
<!--
LogLevel (string, no default)
This controls the level of detail of messages logged by the JMS
Connector. These messages are primarily intended for debugging the
JMS Connector itself, but may also be useful when debugging issues
related to the use of the JMS Connector. This property should not be
set in production code. (It should only be set temporarily for
debugging purposes - specific log messages and log levels may be and
will be added/removed/modified in future versions of the JMS
Connector.) Currently the allowed values are:
ConnectionPool
ConnectionOps
TransactionalOps
ListenerThreads
INFO
CONFIG
FINE
FINER
FINEST
SEVERE
WARNING
OFF
ListenerThreadMaxIdleDuration (milliseconds, default = 300,000)
This is how long a listener thread which is not receiving any messages
will be kept around. (At least one listener thread will remain as long
as the endpoint is active.)
ListenerThreadMinBusyDuration (milliseconds, default = 10,000)
If a listener thread has just received a message, has not been idle (had to
wait for a new message to arrive) at any point during the past
ListenerThreadMinBusyDuration milliseconds, and the current number of
listener threads for this endpoint is less than ReceiverThreads, then
(application server willing) an additional listener thread will be created.
ResUser (string, default = null)
ResPassword (string, default = null)
These properties allow a user/password to be passed to the resource
provider. When neither of these properties are set, connections used for
this MDB's inbound message handling (as well as for exception queue
handling, if enabled) are created using the no-argument version of the
create*Connection method. When one or both of these properties are set,
they are passed to the create*Connection method as the user/password
arguments. (If only one property is not set, then 'null' is used for that
particular create*Connection argument.) The ResPassword property supports
the standard password indirection options (e.g., using "->joeuser" to
represent the password of "joeuser").
Note that the commas used in many of the above default values and examples are
included here for readability but can not be used in the actual activation spec.
(I.e., integer/milliseconds values in the activation spec must not include
embedded commas.)
-->
</message-driven-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping name="<default-ejb-caller-role>"
impliesAll="true"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar> -
Server stopped due to start up failure
hi!
i have downloaded and installed j2ee sdk without any problems.
however when i start the server it closes itself.
at the end of the log file it says:
" [#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]"
the whole log file is below. can anybody help?
ps: i am a beginner.
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2005-07-13T09:52:32.438+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2005-07-13T09:52:36.413+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2005-07-13T09:52:37.104+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-07-13T09:52:46.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2005-07-13T09:52:46.187+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2005-07-13T09:52:46.237+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-07-13T09:52:54.299+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2005-07-13T09:52:59.106+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2005-07-13T09:53:02.210+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2005-07-13T09:53:05.565+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2005-07-13T09:53:05.856+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.956+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Selecting file [C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2005-07-13T09:53:05.986+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.007+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.017+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2005-07-13T09:53:07.097+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2005-07-13T09:53:07.117+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1022:Deployment failed - Detailed Message:
com.sun.enterprise.admin.common.exception.ServerInstanceException
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getVirtualServerHostAndPort(ApplicationsConfigMBean.java:2133)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.setHostAndPort(ApplicationsConfigMBean.java:3038)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:274)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
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:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.server.SystemAppLifecycle.deployToTarget(SystemAppLifecycle.java:180)
at com.sun.enterprise.server.SystemAppLifecycle.deploySystemApps(SystemAppLifecycle.java:155)
at com.sun.enterprise.server.SystemAppLifecycle.onStartup(SystemAppLifecycle.java:77)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:295)
at com.sun.enterprise.server.PEMain.run(PEMain.java:220)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:53:07.127+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Exception occures while invoking backend deployment service for file : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear. -- null -- null|#]
[#|2005-07-13T09:53:07.137+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Autodeploy failed : C:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2005-07-13T09:53:07.298+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2005-07-13T09:53:08.900+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2005-07-13T09:53:10.683+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2005-07-13T09:53:10.693+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-07-13T09:53:10.743+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2005-07-13T09:53:10.803+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2005-07-13T09:53:11.363+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2005-07-13T09:53:25.003+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2005-07-13T09:53:32.724+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:32.864+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2005-07-13T09:53:33.916+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:33.946+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2005-07-13T09:53:34.006+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:53:34.026+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Sun\AppServer\imq\var\instances|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.PEMain.run(PEMain.java:224)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
... 25 more
|#]
[#|2005-07-13T09:54:36.326+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
[#|2005-07-13T09:54:36.326+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Tomcat.|#]
[#|2005-07-13T09:54:36.336+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 8080 server:type=ThreadPool,name=http8080|#]
[#|2005-07-13T09:54:36.506+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 1043 server:type=ThreadPool,name=http1043|#]
[#|2005-07-13T09:54:36.536+0300|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Stoping http11 protocol on 4848 server:type=ThreadPool,name=http4848|#]
[#|2005-07-13T09:54:37.027+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2005-07-13T09:54:37.057+0300|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
[#|2005-07-13T09:54:37.057+0300|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:364)
at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
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:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
|#]
[#|2005-07-13T09:54:37.267+0300|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]Hi,
Did you resolve this issue? I have the same problem. I appreciate if you could please let me know what the problem was.
Thanks -
JCA Polling Adapter not picking up records
Hello All
I have been trying to configure a JCA polling adapter to pick up records from the Database, the first time I configured it, it read a whole bunch of records. Now I have configured the following in the database and am getting no records being polling.
1. Poll for new or changed records
2. Update a field in the table F40g02 for logical delete
3. Read value = READ, UNREAD value = UNREAD, Reserved value = RESERVED
4.Polling interval 5 seconds, Database XROWS per xml document 1, Database Rows per Transaction 10
I ran the SQL specified in the adapter and I get a record. Does anyone have any idea.
I have seen this warning in the EM
Database Adapter <oracle.tip.adapter.db.inbound.IPAddrPollingService getUniqueMarkReservedValue> The markReservedValue of distributed polling might not be a unique value. To make it so, you can add the last x digits (default = 2) of the host IP address using this format for the MarkReservedValue: [original_val]${IP[-x]}
RegardsHello
The problem I am facing is I can't get the records that are processed (already READ) to not poll again despite the value being changed to the READ value configured, if I set the READ value in the configuration it will poll every record all the time despite the fact it is equal to the READ value. Then if I set the READ value and any other value no records will poll.
Consider 4 records in the DB (currently in test I have 431 but I have used distributed locking and ReturnSingleResultSet to limit it)
ID = 1, STATUS = PROCESSED
ID = 2, STATUS = UNPROCESSED
ID = 3, STATUS = UNPROCESSED
ID = 4, STATUS = OTHER
Config 1: If READ = PROCESSED records 1,2,3,4 will poll
Config 2: If READ = PROCESSED, UNREAD = UNPROCESSED no records will poll
Config 3: If READ = PROCESSED, UNREAD = UNPROCESSED, RESERVED = OTHER no records will poll
Config 4: If READ = PROCESSED and TOPLINK STATUS not equal string "PROCESSED" then records 1,2,3,4 will poll
What I want is Record 2 and 3 to poll which I believe is config 3 should do. However I believe there have been some changes that relate to distributed polling for clusters in 11.1.1.3 onwards which means in jdeveloper (11.1.1.6) when I go to re-config the db adapter after setting the RESERVED value it disappears from the editor .
JCA properties obviously with a MarkReservedValueand MarkUnreadValue column jumping in.depending on which config I am trying
<property name="DescriptorName" value="dbPollBlockRecords.F40G02"/>
<property name="QueryName" value="dbPollBlockRecordsSelect"/>
<property name="MappingsMetaDataURL" value="dbPollBlockRecords-or-mappings.xml"/>
<property name="PollingStrategy" value="LogicalDeletePollingStrategy"/>
<property name="MarkReadColumn" value="STATUS"/>
<property name="MarkReadValue" value="PROCESSED"/>
<property name="PollingInterval" value="700"/>
<property name="MaxRaiseSize" value="1"/>
<property name="MaxTransactionSize" value="10"/>
<property name="NumberOfThreads" value="1"/>
<property name="ReturnSingleResultSet" value="true"/> (This property has been manually configured, will unfortunately poll all records that match without it)
Regards -
Lock on DB table due to polling adapter
hi
I have a DB table trans_xml and around 9 BPEL services have DB pollers pointing to this table. Poller picks the rows which have a flag set as "COMPLETE" and update it to "SENT". I have used logical delete.
Recently Our unix box restarted. now i can not update the flag column on this table as SENT. it automatically reverts back it to "COMPLETE". Although I am able to perform following tasks on this table
- insert a row
-delete a row
-update any other column
- update above specified column with any other value Except "SENT"
Please note that i am not able to update this column by any means as in writing update query from sql plus or through procedure or through this polling adapter.
It does not show any specific error and I have checked there are no locks at DB side.
Please help me with this issue. I am struggling with this from last 4 days.Hi vladodias
This behavior is visible for even newly inserted rows. And BPEL is not rolling back because after picking rows from DB further this BPEL is supposed to insert another row in same table which is happening.
So it is not rolling back complete transaction it only rolling back the rows picked by poller.
and yes i have tried this thing like redeploying the BPEL process and even restarting the OAS(I am using soa 10g).
when the OAS server is down then i can update the row but As soon as i restarted the server this problem started again. -
Apple TV stops streaming via AirPlay when iPhone 6 Display goes black
Hi,
when my iPhone gets locked and the Display goes black (standby) after 2 Minutes, my AirPlay stream to my Apple TV 3. Gen stops playing. Only when i set the standby/lock time time to never instead of 2 Minutes (and the screen is on all the time) the Stream wont stop.
Sometimes the stream does not stop, wenn my iPhone Screen goes black.
This also happens with an iPad Mini or using an Lightning to HDMI Adapter instead the Apple TV.
I have no idea why.
Please help.
Best regards
SebastianOn a sidenote, I also have an ipad and normally homesharing with the ipad works fine, but after having an apple tv incident, I have to restart the mac for homesharing to work with the ipad
-
My hp support assistance wont run. it keeps stopping during updates and when deleting the temporary
My hp support assistance wont run. It keeps stopping during updates and when deleting the temporary internet files. So it never finishes the process.. help
The failure to remove the Temporary Files could just be due to having your internet connection active during the removal process. For most folks, the amount of data in this directory is minimal. If you want / need to remove the files, you could close your browser(s), make sure your Internet music and TV connections are closed, and then try removing the files manually:
Path to Folder:
C:\Users\--YourAccountNameHere--\AppData\Local\Microsoft\Windows\Temporary Internet Files
Warning:
Do NOT remove the "Temporary Internet Folder" itself. Go "inside" the folder before removing anything.
====================================================================================
The HP Support Assistant is great when it works -- and not so great when it won't cooperate. You can try removing the program from your computer and installing it again. That may work.
Control Panel > icon view > Programs and Features >
Scroll down, find, and Uninstall HP Support Assistant.
Restart your computer after uninstalling the existing version of Support Assistant.
Install Support Assistant
HP Support Assistant
Using HP Support Assistant (Windows 8)
Troubleshooting HP Support Assistant
NOTE: At writing, there are possible issues with HPSA version 7.x -- you might want to sitck with version 6.x for now.
======================================================================================
If you have issues removing your version of HPSA:
Fix problems with programs that can't be installed or uninstalled
=====================================================================================
Workaround to get Updates:
If all avenues fail to bring joy and it just won't work, you can still get your updates from your computer's website.
Install Software and Drivers from HP Website
Go to the top of the HP forum page to Support and Drivers
If prompted, Enter your Country or Region and
Enter your Computer Model information,
Go to Software and Drivers...
Enter your Operating System in the Drop-down menu... Scroll down
Select desired Category
Expand and decide if you need to install that package.
Assure that you download and install only the most recent versions of each driver or program.
Save the appropriate *.exe installation package on your computer
NOTE the name and the location - the *.exe file will likely save to "Downloads “
Install the Software / Driver installation package: If you have ‘Admin’ control, you may highlight the package(s) and “double-click” to install, else Right-Click, Select ‘run as Administrator’ and install.
NOTE: There is sometimes a lot of information at the computer’s website. Be sure to take an extended look at what’s available.
======================================================================================
Good Luck!
Kind Regards,
Dragon-Fur -
im having trouble connecting my macbookpro to the tv. im using a mini display port to hdmi adapter, when i switch tv/video to hdmi on the tv nothing pops up, and i dont have the arrangement tap on the display settings, please help!
I've found that the order of operations, so-to-speak, can be important when hooking up mini display port to HDMI. I have the most success with the following operations in this order:
1) Plug HDMI cable into mini displayport adapter (the cable should not be plugged into either the TV or the computer at this point)
2) Plug the mini displayport end of your new super-cable to the computer.
3) Plug the HDMI end into your TV.
4) Switch inputs on your TV to the proper input.
5) If still nothing on the TV, try a different HDMI port on your TV.
Hopefully this helps! Good luck. -
Win 8.1 BUG: ReadyBoost "Stop retesting this device when I plug it in"
Win 8/Win 8.1:
There is an error in the ReadyBoost Tab. the "Stop retesting this device
when I plug it in" is gone.
Can someone help me where do i edit it in the Registry.
Thankyou,
JaneHi,
That depends on your USB device. If this USB device is not available for using ReadyBoost, then it will show you a message like this under the ReadyBoost tab:
For more information regarding ReadyBoost, please check this article:
Using memory in your storage device to speed up your computer
Best regards
Michael Shao
TechNet Community Support -
Error when opening iTunes : iTunes has stopped working '' A problem caused the program to stop working correctly''.
When I repaired damaged files the problem still exists and also after uninstalling, redownloading and reinstalling iTunes.
My pc is working with windos 8.
Is there a solution?Hey there Rodney274,
It sounds like you are getting an error from iTunes when you launch it. I would try the troubleshooting in this article named:
iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues
http://support.apple.com/kb/ts1717
Start with troubleshooting for 3rd party plug ins section, then the rest of the article if needed:
Start iTunes in Safe Mode
Open iTunes in Safe Mode to isolate any interference from plug-ins or scripts not manufactured by Apple.
Hold down Shift–Control while opening iTunes. You should see a dialog that says "iTunes is running in safe mode" before iTunes finishes starting up.
Click Continue.
See if the issue you're experiencing persists in Safe Mode.
If you have the same issue while iTunes is in Safe Mode, proceed to the "Create a new user account" section. If you don't experience the same issue, follow these steps to remove third-party plug-ins.
Thank you for using Apple Support Communities.
Take care,
Sterling -
Error message "Itunes has stopped working" and closes when opening itunes store
I had problems with the latest itunes freezing up that i installed itunes 10.53 and it works fine now except when i go to the itunes store,itunes stops working and the whole program closes.I checked the diagnosics and everything comes up green lights.What could be the problem?
Let's try the following user tip with that one:
iTunes for Windows 10.7.0.21: "iTunes has stopped working" error messages when playing videos, video podcasts, movies and TV shows -
How to stop a process chain when its running?
Dear Experts,
How to stop a process chain when its running? is it that a chain can be stoppend when we open an info package of that chain ?
Thank you,
RajHi,
Goto the main menu process chain --> choose the remove from the Schudule...
Regards
sathis
I hope it helps to u... please assign the points -
I have an Iphone $S, when I am on the phone and I get a new message my phone vibrates and rings, How can I stop this from happneing when I am on the phone
Flip the Ring/Silent switch. Make sure Vibrate when silent is off in Settings>Sound.
Maybe you are looking for
-
Bought a used HP Coler Laserjet 4700N and don't know how to hook up.
I just bought a HP Color Laserjet 4700n printer from a place that just sold out. I didn't any cords to connect it to my Del Dimensions E520 couputer. I am just a computer user and connecting this printer sounds a bit complicated. I didn't get any
-
Space issue in Firefox related to Flash banner
I have a website with validated XHTML and CSS that displays an unwanted space only in Firefox under a Flash banner. The site has been tested in IE6/7/8, Firefox, Chrome, Safari, Opera, AOL, and Netscape. Firefox is the only problem. After posting
-
How to prevent color banding in AVCHD files on import?
Hi! I am trying to import some 1080 60i AVCHD files from my Panasonic G3 camera into iMovie '11. Once the files are imported they show very strong color banding/pixelation, that does not show up if I play the clips on the same computer/screen directl
-
Hi, I'm a little bit confused by the help on NW 7.10 SP7. I normally use RFC connections from web Dynpro but this time I have to use RFC from an EJB. As before I tried "SAP Enterprise Connector" which seems to be depricated. I followed the example ho
-
Hi please help me I'm useles with these thing. I've had cydia put on my device didn't like it so deleted ap and now I cant get back into Icloud it's gone very faded in couler the icon in settings. Facebook Twitter and a few others have done the same.