[Installation, Configuration & DEPLOYMENT] - JBoss Native 2.0.1 Windows Server 2003 / AMD 64
by si_gee2000
Hi - apologies I have already posted this on Beginners Corner, but not sure its the right place as getting no replies - so I though I'd repost here...
I am new to the installation of JBoss in a production environment having been strictly a developer until recently. So, I decided instead of going for the usual Vanilla installation of JBoss I would try and optimize the install for once. I am running on a Windows 2003 server with AMDx2 CPU, so I dowloaded the package Windows 64/AMD64 2.0.1 native package from http://labs.jboss.com/jbossweb/downloads.
I followed the instructions and even installed JBoss as a service, using the exe in the package. So far so good. Then I started the new service, I noted that the native dir was found and the java.library.path setup correctly in the run.bat script, but still I got the message [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path
I have checked and double-checked, and even run the run.bat java startup cmd from the command line to see if I can fathom it out, but I cannot get the native lib to be found (ctnative et al all exist in the native lib folder) - I even copied the native libs into Windows\system32 to check the loookup.
Another thing too, when I try and Stop the new service for JBoss it hangs and will not stop. I have to kill it via a process monitor. Evidently I have done something wrong on the install - can anyone help who has maybe done this successfully on a similar server?
thanks!
si
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089213#4089213
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089213
18 years, 7 months
[JBoss Seam] - Question of the day: Stateless Session Beans
by JUnkie
Hi,
Certainly Stateless Session Beans are usually used to call its methods from clients like Stateful Session Beans. The method returns and that's it, the Stateless SB will not remember anything. In Seam you would normally not use a Stateless SB with bijection. However the following simplified Stateless SB that outjects a book works well for me. All instance variables are overwritten with each call of its only method. As Stateless SBs are 1) cached and pooled and 2) synchronized I believe this is 1) faster than a Stateful SB and 2) does not mix up data for concurrent users.
Could you please correct me if I'm wrong?
@Stateless
| @Name("bookDetails")
| public class BookDetailsAction implements BookDetails {
|
| @RequestParameter
| String bookid;
|
| @Out(required=false)
| private Book book;
|
| @PersistenceContext
| private EntityManager em;
|
| @Factory("book")
| public void findBook() {
| book = em.find(Book.class, id);
| }
|
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089208#4089208
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089208
18 years, 7 months
[JBossWS] - JBossWS and Axis2
by BCH
Hello,
First of all, i would apologize for my bad english.
I'm trying to generate a JBossWS client from the sample "Version" service of Axis2 but I have errors.
I'm using :
- JBoss AS 4.2.1 with jbossws-native-2.0.1.GA
- Axis2 1.3
I'm running this command line :
| <JBOSS421_DIR>\bin> wsconsume http://localhost:8085/axis2/services/Version?wsdl
|
And I obtains this error :
| parsing WSDL...
|
| [ERROR] A class/interface with the same name "sample.axisversion.Exception" is a
| lready in use. Use a class customization to resolve this conflict.
| line 11 of http://localhost:8085/axis2/services/Version?wsdl
|
| [ERROR] (Relevant to above error) another "Exception" is generated from here.
| line 6 of http://localhost:8085/axis2/services/Version?wsdl
|
| [ERROR] Two declarations cause a collision in the ObjectFactory class.
| line 11 of http://localhost:8085/axis2/services/Version?wsdl
|
| [ERROR] (Related to above error) This is the other declaration.
| line 6 of http://localhost:8085/axis2/services/Version?wsdl
|
| [ERROR] Two declarations cause a collision in the ObjectFactory class.
| line 14 of http://localhost:8085/axis2/services/Version?wsdl
|
| [ERROR] (Related to above error) This is the other declaration.
| line 8 of http://localhost:8085/axis2/services/Version?wsdl
|
This is the Version.wsdl :
| <?xml version="1.0" encoding="UTF-8"?>
| <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
| xmlns:ns0="http://axisversion.sample"
| xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
| xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
| xmlns:ns1="http://org.apache.axis2/xsd"
| xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
| xmlns:xs="http://www.w3.org/2001/XMLSchema"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| targetNamespace="http://axisversion.sample">
| <wsdl:documentation>Version</wsdl:documentation>
| <wsdl:types>
| <xs:schema xmlns:ns="http://axisversion.sample" attributeFormDefault="qualified"
| elementFormDefault="qualified" targetNamespace="http://axisversion.sample">
| <xs:complexType name="Exception">
| <xs:sequence>
| <xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
| </xs:sequence>
| </xs:complexType>
| <xs:element name="Exception">
| <xs:complexType>
| <xs:sequence>
| <xs:element minOccurs="0" name="Exception" nillable="true" type="ns:Exception"/>
| </xs:sequence>
| </xs:complexType>
| </xs:element>
| <xs:element name="getVersionResponse">
| <xs:complexType>
| <xs:sequence>
| <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
| </xs:element>
| </xs:schema>
| </wsdl:types>
| <wsdl:message name="getVersionRequest"/>
| <wsdl:message name="getVersionResponse">
| <wsdl:part name="parameters" element="ns0:getVersionResponse"/>
| </wsdl:message>
| <wsdl:message name="Exception">
| <wsdl:part name="parameters" element="ns0:Exception"/>
| </wsdl:message>
| <wsdl:portType name="VersionPortType">
| <wsdl:operation name="getVersion">
| <wsdl:input message="ns0:getVersionRequest" wsaw:Action="urn:getVersion"/>
| <wsdl:output message="ns0:getVersionResponse" wsaw:Action="urn:getVersionResponse"/>
| <wsdl:fault message="ns0:Exception" name="Exception" wsaw:Action="urn:getVersionException"/>
| </wsdl:operation>
| </wsdl:portType>
| <wsdl:binding name="VersionSOAP11Binding" type="ns0:VersionPortType">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
| <wsdl:operation name="getVersion">
| <soap:operation soapAction="urn:getVersion" style="document"/>
| <wsdl:input>
| <soap:body use="literal"/>
| </wsdl:input>
| <wsdl:output>
| <soap:body use="literal"/>
| </wsdl:output>
| <wsdl:fault name="Exception">
| <soap:fault use="literal" name="Exception"/>
| </wsdl:fault>
| </wsdl:operation>
| </wsdl:binding>
| <wsdl:binding name="VersionSOAP12Binding" type="ns0:VersionPortType">
| <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
| <wsdl:operation name="getVersion">
| <soap12:operation soapAction="urn:getVersion" style="document"/>
| <wsdl:input>
| <soap12:body use="literal"/>
| </wsdl:input>
| <wsdl:output>
| <soap12:body use="literal"/>
| </wsdl:output>
| <wsdl:fault name="Exception">
| <soap12:fault use="literal" name="Exception"/>
| </wsdl:fault>
| </wsdl:operation>
| </wsdl:binding>
| <wsdl:binding name="VersionHttpBinding" type="ns0:VersionPortType">
| <http:binding verb="POST"/>
| <wsdl:operation name="getVersion">
| <http:operation location="Version/getVersion"/>
| <wsdl:input>
| <mime:content type="text/xml" part="getVersion"/>
| </wsdl:input>
| <wsdl:output>
| <mime:content type="text/xml" part="getVersion"/>
| </wsdl:output>
| </wsdl:operation>
| </wsdl:binding>
| <wsdl:service name="Version">
| <wsdl:port name="VersionSOAP11port_http" binding="ns0:VersionSOAP11Binding">
| <soap:address location="http://localhost:8085/axis2/services/Version"/>
| </wsdl:port>
| <wsdl:port name="VersionSOAP12port_http" binding="ns0:VersionSOAP12Binding">
| <soap12:address location="http://localhost:8085/axis2/services/Version"/>
| </wsdl:port>
| <wsdl:port name="VersionHttpport" binding="ns0:VersionHttpBinding">
| <http:address location="http://localhost:8085/axis2/services/Version"/>
| </wsdl:port>
| </wsdl:service>
| </wsdl:definitions>
|
Is it possible to use JBossWS to invoke an Axis2 WebService ?
If yes, is it possible to use @WebServiceRef to point on a Axis2 WebService ?
Example :
| @Stateless
| @WebService
| public class MyService implements IMyService
| {
| @WebServiceRef(name="Version", wsdlLocation="http://localhost:8085/axis2/services/Version?wsdl")
| private Service axisService;
|
| @WebMethod
| public String myMethod()
| {
| ...
| }
| ...
| }
|
Any help will be appreciate
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089206#4089206
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089206
18 years, 7 months
[JBoss jBPM] - Decision expressions.
by ramsub
Hi,
I'm using jbpm 3.1.3,
I have a context variable that is a list, and I need to have a decision condition that evaluates by calling the contains() method on this list.
I'm trying :
<decision name="decision1" expression='#{MYLIST.contains("A") ? "a" : "b"}' >
However, this does not seem to work and throws an exception saying :
Caused by: org.jbpm.JbpmException: couldn't evaluate expression '#{MYLIST.contains("A") ? "a" : "b"}'
at org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator.evaluate(JbpmExpressionEvaluator.java:38)
at org.jbpm.graph.node.Decision.execute(Decision.java:108)
... 57 more
Caused by: org.jbpm.jpdl.el.ELException: Encountered "(", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and", "&&", "or", "||", "?"]
Has anyone done this before ? Can the contains method be called inside an expression ? If not, are there any ways out ( i do not want to write a decision handler)
Also, can i use a script inside a decision handler to take a decision, and how can i do that ?
That is, can I say :
| <script>
| <variable name='MYLIST' access='read' />
| <expression>
| if(MYLIST.contains("A")) {
| executionContext.leaveNode("a"); } else
| if(MYLIST.contains("B")) {
| executionContext.leaveNode("b"); } else {
| executionContext.leaveNode("Other"); }
| </expression>
| </script>
|
inside a decision handler ? even this does not seem to work for me
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089201#4089201
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089201
18 years, 7 months
[JBossCache] - Data gravitation synchronization issue
by fungrim
Hi,
We have isolated what we think is a synchronization issue during data gravitation over multiple nodes using buddy replication.We have a unit test demonstrating the issue which I can send to anyone interested.
What appears to happen is this: When two nodes are involved in a data gravitation sometimes multiple data gravitation cleanup commands are issued of which one blocks the other. The calling node then times out after "buddyCommunicationTimeout" milliseconds (a timeout which is only logged as debug?) and returns null, making it look like the requested data does not exist in the cache. Further investigation reveals two global transactions on the data holding cache, one which holds an identity lock (write) for a backup data node and the other waiting to lock the same node.
Depending on "LockAcquisitionTimeout" the blocked request may continue, but we have seen several consequences of this depending on whether a user transaction is involved or not. Sometimes the lock seems to disappear and sometimes it doesn't and the application is in effect completely blocked (as the jgroup thread will be holding a lock on a NakReceiverWindow).
This behavior only occurs (as far as we've seen) when there's quite a bit of concurrent access, in particular: when data is added to one node but accessed immediately on another, ie. when addition and gravitation occurs immediately. We have tried disabling auto gravitation and generally playing around with the configuration but with no effect.
This seems like a synchronization issue and the unit test I can send along also shows that it is intermittent, sometimes the test will go through only to fail the next time and sometime a particular test fails when run standalone only to succeed if another test was run immediately before making it look like burn-in affects the result (which it of course may do).
Our unit test tries to model high concurrency in three different variations, one with a simple data gravitation, one with gravitation followed by a modification (subsequent put on the cache) and one with gravitation and modification within a user transaction. The last of these scenarios is basically what our real application is doing.
I've spent considerable time looking at this so feel free to ask questions. Also, tell me where to send the unit test if you want to have a look at it. The unit test repeatedly fails on a java5/linux/dual core/cache 2.5.0.GA setup.
Regards
/Lars J. Nilsson
www.cubeia.com
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089200#4089200
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089200
18 years, 7 months
[JBoss Seam] - Re: warning using richfaces
by maanu
Maybe it's not related, but I've got a similiar issue that may interest you.
Basically, in case you're building your project with maven and the softeu maven repository, you end up with 2 JSF implementations (Jsf-Impl and myFaces) in your WEB-INF/lib because of the transitive dependencies of seam and rich-faces.
And for some reason (?), it causes to load the SeamPhaseListener twice.
If you're building your project that way, you have to choose which implementation you want to use, and exclude the other from the transitive dependency. For instance, to exclude jsf-impl from the transitive dependencies of richfaces, you can tweak it as follows:
...
| <dependency>
| <groupId>org.richfaces.ui</groupId>
| <artifactId>richfaces-ui</artifactId>
| <version>3.1.0</version>
| <exclusions>
| <exclusion>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-impl</artifactId>
| </exclusion>
| </exclusions>
| </dependency>
| ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089196#4089196
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089196
18 years, 7 months