[JBoss Cache: Core Edition] - Re: Exception when a cluster node joins under load
by kringdahl
Just to loop back on my efforts to integrate JBoss Cache 2.1.1.GA with AS 4.2.2.GA. I have this mostly working. It required upgrading the AOP deployer in the AS to JBoss AOP 2.0.0 (I used CR8) and also using the new pluggable-instrumentor.jar as the javaagent. JBoss Cache 2.1.1.GA appears to have solved the startup issue I was previously seeing...at least I have not been able to reproduce it since and it was regularly reproducible in my environment in the past. Just a couple of questions regarding 2.1.1.GA though:
1) Is 2.1.0.GA the latest Pojo Cache release? Right now, I have taken Pojo Cache 2.1.0.GA and Core Cache 2.1.1.GA. I do not see any newer releases in the SF downloads page or the maven repositories, not even for 2.2.0.
2) (Maybe this should go to the Pojo Cache forum but it's all sort of related) We are seeing a new problem where Lists and Sets are not working properly following the upgrade. Specifically, we use a JDBC cache loader. The lists work fine until we bring the cluster down and back up again. When we do, all of the lists and sets appear as empty. What's weirder, if we execute .size() or take some other action on the collection, the list attributes come in. Has anyone seen this before? I'm fairly certain this is related to the AOP switch. I've triple checked that the aop config file is correct.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159427#4159427
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159427
17 years, 10 months
[JCA/JBoss] - changing conn parameters in -ds.xml file !!!urgent!!!
by sankul123
I have tried to explain using these two cases -
ora-ds.xml -> oracle ds xml file.
CASE 1:
If I place the ora-ds.xml file under ${JBOSSHOME}/server/default i,e
${JBOSSHOME}/server/default
| |
| |------- myApp.ear
| |
| |-------ora-ds.xml
| |
|
and I update the ora-ds.xml file manually with new connection params to the same JNDI name, I can see the following in log file -
[06/19/08 12:08:49,879 PM] [ConnectionFactoryBindingService] [INFO] [Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=OracleDS' from JNDI name 'java:OracleDS']
[06/19/08 12:08:49,957 PM] [ConnectionFactoryBindingService] [INFO] [Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=OracleDS' to JNDI name 'java:OracleDS']
This gives me confirmation that connection obj is according to changed conn parameters.
CASE 2:
I am trying to achieve the above thing through a program and just move the ora-ds.xml inside the ear[few of the customers are not interested giving our program any permissions[java security perm] outside our context].
So now I have placed the ora-ds.xml file inside ear and specify the path in jboss-app.xml file.
myApp.ear
| |
| |-----META-INF
| | |
| | |-jboss-app.xml [ <module><service>ora-ds.xml</service></module>]
| | |
| | |
| |
| |------- web1.war
| |
| |------- web2.war
| |
| |
| |-------ora-ds.xml
| |
| |
And I am updating the ora-ds.xml file from my program. Even after updating I still get old conn object if I make a JNDI call.
I dont see any events as mentioned in case 1 , when I update the ora-ds.xml file in second case.
Bottom Line :
anonymous wrote : I want to update the connection parameters in ora-ds.xml and get new conn obj accordingly
Please answer whether what I am trying to do is either possible or NOT possible
Sandeep
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159411#4159411
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159411
17 years, 10 months
[JBoss jBPM] - Re: job executor explained in a nutshell
by kadlecp
Hello Alex,
anonymous wrote :
| No updates will be ever lost with higher isolation levels. The database will ensure that no two transactions that update the same data item can proceed.
|
Yes, I agree. But the db will block the second update until transaction with first update commits. There is no need to use optimistic locking with repeatable read isolation level because optimistic locking does not work with repeatable read.
If I understand it well, we have optimistic locking to prevent conflicting updates. We do not want to send two conflicting updates to db because db (in my case Oracle) will block the second update. We want application could see that another committed tx changed our row (that we already read) and we want to rollback our tx immediately (without blocking).
If we set transaction to repeatable read isolation level, in my opinion optimistic locking does not work, because during whole transaction we always read same version of our row. The application can not see that another commited tx updated some row. (bacause we have repeatable read).
I think that optimistic locking needs non-repeatable read to work but jbpm docs says opposite.
Regards
Pavel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159410#4159410
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159410
17 years, 10 months
[JBossWS] - Schema Validation - Failed to read schema document
by bbucy
Trying to turn on Schema Validation for a webservice I have created. All is ok running without validation, wsconsume has no issues generating artifacts on the server side, nor any issues running wsconsume on client side, nor any issue running the client and getting a response from the server when schema validation is NOT enabled. But, as soon as I turn on schema validation, I get the following error on the server.
17:03:59,347 INFO [SOAPBodyElementDoc] Validating: XML_VALID
17:03:59,363 WARN [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'OneCardTxnRequest.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
17:03:59,363 WARN [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'OneCardTxnResponse.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
17:03:59,363 ERROR [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'ocreq:OCReq' to a(n) 'element declaration' component.
17:03:59,363 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.WSException: org.xml.sax.SAXException: src-resolve: Cannot resolve the name 'ocreq:OCReq' to a(n) 'element declaration' component.
at org.jboss.ws.WSException.rethrow(WSException.java:68)
at org.jboss.ws.core.soap.SOAPBodyElementDoc.validatePayload(SOAPBodyElementDoc.java:130)
at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:82)
at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:173)
at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263)
........
My wsdl does import two xml schemas that represent the request and response documents. Actually, had this as a single schema, but thought I'd break it up too see if the issue was dealing with both elements. Anways, a snippet of the wsdl is as follows.
<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ocreq="http://request.doc.onecard.exchange.hps.com/"
xmlns:ocrsp="http://response.doc.onecard.exchange.hps.com/"
xmlns:tns="http://ws.onecard.exchange.hps.com/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
targetNamespace="http://ws.onecard.exchange.hps.com/">
<wsdl:types>
<xs:schema targetNamespace="http://ws.onecard.exchange.hps.com/" version="1.0" xmlns:tns="http://ws.onecard.exchange.hps.com/" xmlns:ocreq="http://request.doc.onecard.exchange.hps.com/" xmlns:ocrsp="http://response.doc.onecard.exchange.hps.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import schemaLocation="OneCardTxnRequest.xsd" namespace="http://request.doc.onecard.exchange.hps.com/"/>
<xs:import schemaLocation="OneCardTxnResponse.xsd" namespace="http://response.doc.onecard.exchange.hps.com/"/>
<xs:element name="doTransaction" type="tns:doTransaction"/>
<xs:element name="doTransactionResponse" type="tns:doTransactionResponse"/>
<xs:complexType name="doTransaction">
<xs:sequence>
<xs:element minOccurs="0" ref="ocreq:OCReq"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="doTransactionResponse">
<xs:sequence>
<xs:element minOccurs="0" ref="ocrsp:OCRsp"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
.................
</wsdl:definitions>
And a snippet of my Service implementation class is as follows.
@WebService(serviceName="OneCardService", portName = "OneCardInterface", endpointInterface="com.hps.exchange.onecard.ws.OneCardInterfaceType",
targetNamespace = "http://ws.onecard.exchange.hps.com/", wsdlLocation = "WEB-INF/wsdl/OneCard.wsdl" )
@SchemaValidation
public class OneCardInterface extends SpringBeanAutowiringSupport implements OneCardInterfaceType
{
......
}
I do actually generate my artifacts using wsconsume in a different project and then copy my wsdl and the two xml schemas to my WAR's WEB-INF/wsdl directory. Not sure, if that could be effecting anything. Kind of running around in circles at this point. Any ideas would be greatly, greatly appreciated. Thanks, Bob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159403#4159403
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159403
17 years, 10 months