[JBoss jBPM] - Re: SQL error executing test process
by ajvarela
Thank you all for replies.
I dont know how I can prevent the recreation of DB schema. I have tried comment the tearDown mehod code and the test run well but
residual information is saved on DB when I reactive the tearDown code the error appear again.
This is my config for MySQL. Is correct dialect??
<property name="hibernate.dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>
| <property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
| <property name="hibernate.connection.url">jdbc:mysql://localhost:3306/jbpmdb</property>
| <property name="hibernate.connection.username">root</property>
| <property name="hibernate.connection.password">*********</property>
| <property name="hibernate.format_sql">true</property>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242402#4242402
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242402
17 years
[Tomcat, HTTPD, Servlets & JSP] - Problem with jboss class loader
by kevinjohn
Env. details:
OS : Solaris
Jboss : JBoss 3.2.X
Issue Description:
One of the module of my application is using Axis.jar. My application also have web module. Sometime when i access the web module of my application, the browser is report JasperException Unable to comple jsp file.
When i investigated, i found this is because of conflicts of jar files on the server. The jar file are servlet-api.jar which is come along with the Jboss and other is servlet-api-2.3.jar which is coming Axis2.war. When i remove the server-api-2.3.jar file from Axis.war, appication is working fine, i mean the jsp's are compiling. But sometimes the jsps are compiling when i restarted the server, even if the jar file is present in Axis2.war. I want to know how the jboss is compiling the jsps when i restart the server? how jboss resolving the conflict when restarting the server? why the conflict is coming inbetween?
Hope to receive a convincing answer
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242401#4242401
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242401
17 years
[Installation, Configuration & DEPLOYMENT] - Re: jboss 5.1 encoding problem
by yves.benigot
The encoding problem on the error page remains even if we start the server right after installing the archive.
On the deployment problems we have progressed, and the situation is that we have to correct some configuration files and JSP where jboss 5 is stricter.
More information:
- we see encoding errors in the error page, but also in the logs
- we have 15 war and 2 ear in a directory named deploy/ginerativ,
and 6 sar files
- libraries 36 of them (10 of them are developped in house) in lib/ginerativ
(we use subdirectories to avoid merging our files with jboss installed files)
On the same server, with the same java and envrionment setup, and jboss 4.2.3, the error page is properly encoded with french accents.
Also we found that, for the moment, the server is slower than jboss 4.2.3, although this seems an unlikely explanation.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242393#4242393
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242393
17 years
[Clustering/JBoss] - Caching, hybernate and using enums => no go
by ZeroTolerance
Hi,
We have JBoss AS 5.1.0 and use hibernate to store our session beans in MySQL DB. Also pojo caching is used to make the objects available throughout the cluster.
For both hibernate and caching we use annotations.
@Replicable for classes that need to go into cache and
@Entity for objects that need to be stored using hibernate.
We compile everything and the @Replicable classes with aopc.
If we deploy the created jar file and start JBoss we get a java.lang.VerifyError.
This error originates from a switch statement that is using an enum to switch.
The enum is defined in a @Replicable class called HelperClass
the switch method is defined in the bean called Request
Disabling hibernate OR @Replicable OR both there is no problem starting JBoss.
I can not imagine that this is an unknown problem, one of you probably must have had the same problem. If so what was the solution?
Kind regards,
Werner van Mook
| package entity;
|
| import org.jboss.cache.pojo.annotation.Replicable;
| import org.jboss.cache.pojo.annotation.Transient;
|
|
| @Replicable
| public class HelperClass {
|
| private RuntimeStateRange runtimeState = RuntimeStateRange.RESTING;
|
| public static enum RuntimeStateRange {
| OFFLINE,
| CONNECTED,
| PROBLEM,
| PROBLEM_CONNECTING,
| PROBLEM_SENDING,
| INTERRUPTED,
| STOPPED,
| INVALID,
| RESTING,
| BUSY,
| INITIALIZING };
|
| public HelperClass() {
| System.out.println("HelperClass created.");
| }
|
| public int EnumgetRuntimeState() {
| return this.runtimeState.ordinal();
| }
|
| public RuntimeStateRange getRuntimeStateRange(){
| return runtimeState;
| }
| }
| package entity;
|
| import javax.persistence.Entity;
| import javax.persistence.GeneratedValue;
| import javax.persistence.Id;
|
| import org.jboss.cache.pojo.annotation.Replicable;
|
| import entity.HelperClass.RuntimeStateRange;
|
| @Entity
| @Replicable
| public class Request {
|
| private long id;
| private String filename;
|
|
| public Request(){
| }
|
| /**
| * @return the id
| */
| @Id
| @GeneratedValue
| public long getId() {
| return id;
| }
|
| /**
| * @param id the id to set
| */
| public void setId(long id) {
| this.id = id;
| }
|
| /**
| * @return the filename
| */
| public String getFilename() {
| return filename;
| }
|
| /**
| * @param filename the filename to set
| */
| public void setFilename(String filename) {
| this.filename = filename;
| }
|
| @Override
| public String toString() {
| return "id: " + id + " filename: " + filename;
| }
|
| public void inform() {
| HelperClass help = new HelperClass();
| informDeviceStateWhileHavingFullLock(help);
| }
|
| private void informDeviceStateWhileHavingFullLock(HelperClass osDeviceState) {
| // Thread.currentThread().setName("JMS Inform device " + getName() + " " + osDeviceState.EnumgetRuntimeState().toString());
| switch (osDeviceState.getRuntimeStateRange()) {
| case PROBLEM_CONNECTING:
| System.out.println(osDeviceState.EnumgetRuntimeState());
| break;
| case PROBLEM_SENDING:
| System.out.println(osDeviceState.EnumgetRuntimeState());
| break;
| case CONNECTED:
| System.out.println(osDeviceState.EnumgetRuntimeState());
| break;
| case INVALID:
| System.out.println(osDeviceState.EnumgetRuntimeState());
| break;
| case INTERRUPTED:
| System.out.println(osDeviceState.EnumgetRuntimeState());
| break;
| case STOPPED:
| System.out.println(osDeviceState.EnumgetRuntimeState());
| break;
| default:
| System.out.println("Device state default is always ignored");
| break;
| }
| }
|
|
| }
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242384#4242384
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242384
17 years
[Beginners Corner] - Threads and waiting HTTP requests
by rohit.macherla
Hi,
I have a doubt regarding the thread processing in JBoss.
The configuration of BasicThreadPool in jboss-service.xml is as follows:
| <!-- A Thread pool service -->
| <mbean code="org.jboss.util.threadpool.BasicThreadPool"
| name="jboss.system:service=ThreadPool">
| <attribute name="Name">JBoss System Threads</attribute>
| <attribute name="ThreadGroupName">System Threads</attribute>
| <attribute name="KeepAliveTime">240000</attribute>
| <attribute name="MaximumPoolSize">20</attribute>
| <attribute name="MaximumQueueSize">1000</attribute>
| <attribute name="BlockingMode">run</attribute>
| </mbean>
|
There is also a Connector type for port 8080 which has another configuration for its threads (this is at server.xml in deploy/jboss-web.deployer ) :
| <Service name="jboss.web">
| <Connector port="8080" address="${jboss.bind.address}"
| maxThreads="800" maxHttpHeaderSize="8192"
| emptySessionPath="true" protocol="HTTP/1.1"
| enableLookups="false" redirectPort="8443" acceptCount="100"
| connectionTimeout="20000" disableUploadTimeout="true" />
|
Our application uses JAX-WS style WebServices that are developed using JAXB on NetBeans IDE 6.0.1. These webservices get requests from external systems and from among the other internal webservices as well.
I want to know how these both Threads (the one in the BasicThreadPool and the HTTP Connector Thread) relate to each other.
After our application has been deployed, I have noticed that there are about 800 currentThreadsBusy at a particular time. And when I went to tomcat console (at http://localhost:8080/status), I have found that most of them were waiting at GET requests for one of the webservices.
anonymous wrote :
| Stage Time B Sent B Recv Request
| S 1161886 ms 8 KB 0 KB GET /OurAddressManagement-war/AddressManagementAPIService?wsdl HTTP/1.1
| S 3300470 ms 8 KB 0 KB GET /OurServiceManagement-war/ServiceManagementAPIService
| ......
|
The server was reaching its full capacity and the "top" command for the HP UNIX server (this HP UNIX machine hosts the JBoss 4.2.2.GA App server) indicates a CPU usage of 120% (it is a 2 CPU machine).
As we can see, these HTTP threads were found waiting for a long time (3300470 milliseconds = almost an hour).
At such high load, when I check the BasicThreadPool, the QueueSize = 0. If so many HTTP threads are waiting, then I anticipated the queue size to be atleast 100. This value of zero is quite inexplicable considering that the MaximumPoolSize is just 20.
With such high requests, the server is down to its knees and I would like to know what I can do to decrease the processing times of the HTTP threads.
Thank you for your time.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242382#4242382
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242382
17 years