[EJB/JBoss] - Removed entity beans can be resurrected in container's memor
by rydenius
Hi.
I have an enterprise application containing a large number of BMP entity beans that are created, findByPrimaryKey:ed, and removed by a number of separate clients. I have a problem that occurs rarely, but sometimes:
Let us say that we have two EJB transactions A and B. They both try to access the same entity C. A, which enters first and locks the bean C to the transaction, want to call remove() on the bean. B calls a little bit later on findByPrimaryKey() for C or some random business method on C.
When C.remove() has executed by A, C is immediately removed from the EJB container's bean cache. But the DB transaction which executed the remove may still not be committed when transaction B enters the stage. Since A's transaction is not yet committed, B will not see the modifications it has done in DB, and since C is now removed from bean cache, B will cause ejbActivate() and ejbLoad() to be called on a new C instance, which then is added to the beancache (if commit options permits and transaction B is not rollbacked). Meanwhile, transaction A is committed, and C is permanently removed from persistent storage. But the ghost instance of C added in bean cache as a sideeffect of B will live on until next ejbLoad() when a NoSuchEntityException hopefully is thrown and C is really permanently removed from bean cache. But if using commit option A, that may take a while, especially when cache timeouts are set to get high performance.
But is this really a problem? Yes it is for us. A removed bean may act as if it still exists for some time after removal. And also, if any business methods are invoked on the ghost instance, inconsistent data may be stored in the DB.
But does this really happen, the window for this problem must be so small? Not often, I admit. But sometimes it does, and that is trouble for us. Espescially, JMS events may cause multiple clients to take action on the same bean simultaneously.
So, what is the solution for this? I can't be the only one who has seen this behavior? Is there a standard pattern to avoid this without loosing performance? Or is this just a bug in JBoss that needs to be fixed? Or am I just using the wrong transaction isolation level on my data source?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993149#3993149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993149
19 years, 7 months
[Beginners Corner] - Error when trying to stop JBoss
by msavoy
I am getting the following error when trying to STOP the JBoss server from within Eclipse 3.2.1 (Any direction or help would be greatly appreciated as I could not find an answer to this question in this forum. Thank you.):
| Exception in thread "main" java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
| at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
| at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
| at sun.rmi.transport.Transport$1.run(Unknown Source)
| at java.security.AccessController.doPrivileged(Native Method)
| at sun.rmi.transport.Transport.serviceCall(Unknown Source)
| at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
| at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
| at java.lang.Thread.run(Unknown Source)
| at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
| at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
| at sun.rmi.server.UnicastRef.invoke(Unknown Source)
| at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
| at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
| at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
| at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
| at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
| at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
| at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
| at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
| at $Proxy0.invoke(Unknown Source)
| at org.jboss.Shutdown$ServerProxyHandler.invoke(Shutdown.java:266)
| at $Proxy1.shutdown(Unknown Source)
| at org.jboss.Shutdown.main(Shutdown.java:237)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993147#3993147
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993147
19 years, 7 months
[JBoss jBPM] - Deploying process programatically, Hibernate
by jstachera
Hi,
I have question which is related to deployment of process definition from the code, as it is shown below. Actually it is more hibernate issue, since every new deployed Process Definition is not getting a consecutive ID number in JBPM_PROCESS_DEFINITION table. So the JBPM_PROCESS_DEFINITION table looks like that:
| ID | Name | ver| .... | ...
| --------------------------------------------------
| 1 | websale | 1 | FALSE | 2
| 2162 | SimpleSplitTest | 1 | FALSE | 2163
| ----------------------------------------------------
|
why the SimpleSplitTest did not get ID = 2 ??
| public static void deployProcessPar(String filePath) throws JbpmAtflowException, FileNotFoundException {
| JbpmContext context = getAdminContext();
| try {
| ZipInputStream zip = new ZipInputStream(new FileInputStream(filePath));
| ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zip);
| context.deployProcessDefinition(processDefinition);
| }
| catch (Exception e) {
| throw new JbpmAtflowException("Could not deploy process PAR archive", e);
| }
| finally {
| context.close();
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993144#3993144
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993144
19 years, 7 months
[JBoss jBPM] - No SOAPMessage in HTTP-Request body invoking WS
by bertrand.njiipwo
Hello community,
I have the following problem:
I'm trying to call a web service inside my BPEL-Process running unter the jbpm-Engine from JBoss. During his execution the process call an"virtually deployed" web service which should not be used at runtime (This because jBPM require the deployement of process partners). Instead of this service the call have to be redirected to a remote service wich can only deal with request like: http://127.0.0.1:8089/context/serviceName. But inside this simple HTTP-Request the SOAPMessage the BPEL process concatenate before performing the call has to be present in the HTTP-Body of this request.
On my old System i was using BPWS4J from IBM alphaWorks as BPEL-Engine. Now i move to jBPM.BPEL (1.beta1 with JBoss AS-4.0.4.GA and jBPM-3.1.1) and i have the problem that, the jPBM-Engine didn't inject automatically the required SOAPMessage in the HTTP-Request before the web service call is performed.
Any one has some ideas if this is the case on the jbpm-Engine?
Every tipps or advice will be welcomed and help a lot.
Cheers
Bertrand
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993143#3993143
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993143
19 years, 7 months
[JBoss Seam] - Re: How to use ice:menuBar with Seam in an EAR application?
by jarkko＠jab.fi
Ops, forgot that Quote is broken, below is my EAR's META-INF/application.xml.
| <application>
| <display-name>TrueConcept</display-name>
| <description>TrueConcept</description>
| <module>
| <web>
| <web-uri>tc3Web.war</web-uri>
| </web>
| </module>
| <module>
| <ejb>tc3EJB.jar</ejb>
| </module>
|
| <module>
| <ejb>tc3LiferayEJB.jar</ejb>
| </module>
|
| <module>
| <java>jboss-seam.jar</java>
| </module>
| <module>
| <java>icefaces.jar</java>
| </module>
| <module>
| <java>icefaces-facelets.jar</java>
| </module>
| <module>
| <java>icefaces-comps.jar</java>
| </module>
| <module>
| <java>el-api.jar</java>
| </module>
| <module>
| <java>el-ri.jar</java>
| </module>
| <module>
| <java>backport-util-concurrent.jar</java>
| </module>
| <module>
| <java>selectitems-1.1.0rc1.jar</java>
| </module>
| <module>
| <java>ostermillerutils_1_06_00.jar</java>
| </module>
| </application>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993138#3993138
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993138
19 years, 7 months
[Installation, Configuration & Deployment] - Re: How to Configure JMS Appender
by vinodpol
i have used ....
import org.apache.log4j.AppenderSkeleton;
import org.apache.log4j.spi.LoggingEvent;
import org.apache.log4j.spi.ErrorHandler;
import org.apache.log4j.spi.ErrorCode;
import org.apache.log4j.helpers.LogLog;
import java.util.Hashtable;
import java.util.Properties;
import javax.jms.*;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.naming.NameNotFoundException;
import javax.naming.NamingException;
/**
* A Simple JMS (P2P) Queue Appender.
*
* @author Ceki Gülcü
* @author Jamie Tsao
*/
public class JMSQueueAppender1 extends AppenderSkeleton {
protected QueueConnection queueConnection;
protected QueueSession queueSession;
protected QueueSender queueSender;
protected Queue queue;
String initialContextFactory;
String providerUrl;
String queueBindingName;
String queueConnectionFactoryBindingName;
public
JMSQueueAppender1() {
}
/**
* The InitialContextFactory option takes a string value.
* Its value, along with the ProviderUrl option will be used
* to get the InitialContext.
*/
public void setInitialContextFactory(String initialContextFactory) {
this.initialContextFactory = initialContextFactory;
}
/**
* Returns the value of the InitialContextFactory option.
*/
public String getInitialContextFactory() {
return initialContextFactory;
}
/**
* The ProviderUrl option takes a string value.
* Its value, along with the InitialContextFactory option will be used
* to get the InitialContext.
*/
public void setProviderUrl(String providerUrl) {
this.providerUrl = providerUrl;
}
/**
* Returns the value of the ProviderUrl option.
*/
public String getProviderUrl() {
return providerUrl;
}
/**
* The QueueConnectionFactoryBindingName option takes a
* string value. Its value will be used to lookup the appropriate
* QueueConnectionFactory from the JNDI context.
*/
public void setQueueConnectionFactoryBindingName(String queueConnectionFactoryBindingName) {
this.queueConnectionFactoryBindingName = queueConnectionFactoryBindingName;
}
/**
* Returns the value of the QueueConnectionFactoryBindingName option.
*/
public String getQueueConnectionFactoryBindingName() {
return queueConnectionFactoryBindingName;
}
/**
* The QueueBindingName option takes a
* string value. Its value will be used to lookup the appropriate
* destination Queue from the JNDI context.
*/
public void setQueueBindingName(String queueBindingName) {
this.queueBindingName = queueBindingName;
}
/**
Returns the value of the QueueBindingName option.
*/
public String getQueueBindingName() {
return queueBindingName;
}
/**
* Overriding this method to activate the options for this class
* i.e. Looking up the Connection factory ...
*/
public void activateOptions() {
QueueConnectionFactory queueConnectionFactory;
try {
Context ctx = getInitialContext();
queueConnectionFactory = (QueueConnectionFactory) ctx.lookup(queueConnectionFactoryBindingName);
queueConnection = queueConnectionFactory.createQueueConnection();
queueSession = queueConnection.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ctx.lookup(queueBindingName);
queueSender = queueSession.createSender(queue);
queueConnection.start();
ctx.close();
} catch(Exception e) {
errorHandler.error("Error while activating options for appender named ["+name+
"].", e, ErrorCode.GENERIC_FAILURE);
}
}
protected InitialContext getInitialContext() throws NamingException {
try {
Hashtable ht = new Hashtable();
//Populate property hashtable with data to retrieve the context.
ht.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);
ht.put(Context.PROVIDER_URL, providerUrl);
return (new InitialContext(ht));
} catch (NamingException ne) {
LogLog.error("Could not get initial context with ["+initialContextFactory + "] and [" + providerUrl + "].");
throw ne;
}
}
protected boolean checkEntryConditions() {
String fail = null;
if(this.queueConnection == null) {
fail = "No QueueConnection";
} else if(this.queueSession == null) {
fail = "No QueueSession";
} else if(this.queueSender == null) {
fail = "No QueueSender";
}
if(fail != null) {
errorHandler.error(fail +" for JMSQueueAppender named ["+name+"].");
return false;
} else {
return true;
}
}
/**
* Close this JMSQueueAppender. Closing releases all resources used by the
* appender. A closed appender cannot be re-opened.
*/
public synchronized // avoid concurrent append and close operations
void close() {
if(this.closed)
return;
LogLog.debug("Closing appender ["+name+"].");
this.closed = true;
try {
if(queueSession != null)
queueSession.close();
if(queueConnection != null)
queueConnection.close();
} catch(Exception e) {
LogLog.error("Error while closing JMSQueueAppender ["+name+"].", e);
}
// Help garbage collection
queueSender = null;
queueSession = null;
queueConnection = null;
}
/**
* This method called by {@link AppenderSkeleton#doAppend} method to
* do most of the real appending work. The LoggingEvent will be
* be wrapped in an ObjectMessage to be put on the JMS queue.
*/
public void append(LoggingEvent event) {
if(!checkEntryConditions()) {
return;
}
try {
ObjectMessage msg = queueSession.createObjectMessage();
msg.setObject(event);
queueSender.send(msg);
} catch(Exception e) {
errorHandler.error("Could not send message in JMSQueueAppender ["+name+"].", e,
ErrorCode.GENERIC_FAILURE);
}
}
public boolean requiresLayout() {
return false;
}
}
with log4j.xml settings
appender name="JMS" class="JMSQueueAppender1"
param name="InitialContextFactory" value="org.jnp.interfaces.NamingContextFactory"/
param name="ProviderUrl" value="jnp://localhost:1099"/
param name="QueueConnectionFactoryBindingName" value="QueueConnectionFactory"/
param name="QueueBindingName" value="queue/testQueue"/
/appender
But receiving error...
log4j:ERROR Error while activating options for appender named [JMS].
javax.naming.CommunicationException: Could not obtain connection to any of these
urls: 10.10.10.252:1099 and discovery failed with error: javax.naming.Communica
tionException: Receive timed out [Root exception is java.net.SocketTimeoutExcept
ion: Receive timed out] [Root exception is javax.naming.CommunicationException:
Failed to connect to server 10.10.10.252:1099 [Root exception is javax.naming.Se
rviceUnavailableException: Failed to connect to server 10.10.10.252:1099 [Root e
xception is java.net.ConnectException: Connection refused: connect]]]
Can anybody help me out...
Regards
vinod_pol(a)yahoo.com
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993131#3993131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993131
19 years, 7 months
[Security & JAAS/JBoss] - Re: Getting Exception while trying to access a Stateless EJB
by dvuday
"jaikiran" wrote : anonymous wrote : Properties props = new Properties();
| |
| | props.put(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.HttpNamingContextFactory");
| | props.put(Context.PROVIDER_URL,"jnp://localhost:8080");
| | Context ctx = new InitialContext(props);
|
| This should be:
|
| Properties props = new Properties();
| |
| | props.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
| | props.put(Context.PROVIDER_URL,"jnp://localhost:1099");
| | Context ctx = new InitialContext(props);
Thank you very much for quick response jaikiran. I tried to execute the client program by the changes you mentioned above. But still getting Exception. I have included the log4j.jar from <JBOSS_HOME>\client\ both in the build path of the project and in the jboss configuration.(Jboss is configured in eclipse).
Can you please help me to come out of this exception...
--------------------------------------------------------------------------------------------------------------------
The ejb-jar.xml file is
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xs1="http://www.w3.org/2001/XMLSchema-instance" xs1:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
<enterprise-beans>
<ejb-name>HelloHome</ejb-name>
examples.ejb21.HelloHome
examples.ejb21.Hello
<local-home>examples.ejb21.HelloLocalHome</local-home>
examples.ejb21.HelloLocal
<ejb-class>examples.ejb21.HelloBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</enterprise-beans>
</ejb-jar>
--------------------------------------------------------------------------------------------------------------------
Exception is
log4j:WARN No appenders could be found for logger (org.jnp.interfaces.NamingContext).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1399)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(Unknown Source)
at client.HelloClient.main(HelloClient.java:37)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370)
... 4 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:228)
... 5 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.(Unknown Source)
at java.net.Socket.(Unknown Source)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:224)
... 5 more
Thanks in advance
Uday
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993122#3993122
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993122
19 years, 7 months
[JBoss Seam] - Re: Problem with selectItems taglib
by dave.rogers
Here's my very crude solution:
In BasicEntityConvertor, comment out the entity check in the findIdMethod method
protected Method findIdMethod(Class clazz) {
| // Check that the class passed is an entity
| //if (!(clazz.isAnnotationPresent(Entity.class))) {
| // throw new ConverterException(getMessage(NOT_AN_ENTITY + " " + clazz.getName()));
| //}
and the same in the findIdField
protected Field findIdField(Class clazz) {
| // Check that the class passed is an entity
| //if (!(clazz.isAnnotationPresent(Entity.class))) {
| // throw new ConverterException(getMessage(NOT_AN_ENTITY + " " + clazz.getName()));
| //}
Now I don't know what the implications of this are; probably poor error output if the class really isn't an entity. Otherwise it works. Thanks for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993118#3993118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993118
19 years, 7 months
[Clustering/JBoss] - Re: Clustering NOT working on physical separate boxes.
by rajeshchande
Hello JBoss team,
Thanks for the links, that did help me perform the necessary steps. Finally I was able to get each of the nodes identify each other.
#####m/c1#########
| 15:59:33,679 INFO [Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBos
| s_4_0_3_SP1 date=200510231054)] Started in 41s:253ms
| 16:02:20,112 INFO [devl-partition-01] New cluster view for partition devl-partition-01 (id: 1, delta: 1) : [3.187.196.86:53043, 3.187.200.23:53043]
| 16:02:20,116 INFO [devl-partition-01] Merging partitions...
| 16:02:20,116 INFO [devl-partition-01] Dead members: 0
| 16:02:20,117 INFO [devl-partition-01] Originating groups: [[server-1
| -bak:49934 (additional data: 18 bytes)|0] [server-1-bak:49934 (additional data: 18 bytes)], [172.17.132.140:59013 (additional data: 18 bytes)|0] [172.17.132.140:59013 (additional data: 18 bytes)]]
| #####m/c1#########
#####m/c-2#########
| 15:55:59,974 INFO [Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBos
| s_4_0_3_SP1 date=200510231054)] Started in 1m:8s:90ms
| 16:02:20,110 INFO [devl-partition-01] New cluster view for partition devl-partition-01: 1 ([3.187.196.86:53043, 3.187.200.23:53043] delta: 1)
| 16:02:20,111 INFO [devl-partition-01] Merging partitions...
| 16:02:20,112 INFO [devl-partition-01] Dead members: 0
| 16:02:20,113 INFO [devl-partition-01] Originating groups: [[172.17.132
| .70:49934 (additional data: 18 bytes)|0] [172.17.132.70:49934 (additional data:18 bytes)], [server2_b:59013 (additional data: 18 bytes)|0] [server2_b:590
| 13 (additional data: 18 bytes)]]
| #####m/c-2#########
I did the following changes:
1) In the "run.sh" specified -Djboss.partition.name=devl-partition-01 -Djboss.partition.udpGroup=228.1.2.4
2) UDP parameters deploy/cluster-service.xml look like as shown below:
############
| <UDP bind_addr="172.17.132.70" mcast_addr="228.8.8.8" mcast_port="45566"
| ip_ttl="32" ip_mcast="true"
| mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
| ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
| loopback="true" max_bundle_size="60000" max_bundle_timeout="30"
| use_incoming_packet_handler="false" use_outgoing_packet_handler="false"
| enable_bundling="false" />
| ############
So they see each other now.
But, When i deploy a war file in the "farm" folder of server-1 on first m/c, local deployment on the server-1 happens successfully, but the node on the second m/c does not seem to pull the newly deployed WAR file and vice versa. So the FARM Deployment is failing.
Any idea, why this is failing? Do I need to change anything in deploy/tc5-cluster-service.xml to make "farm" deployment workable?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993116#3993116
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993116
19 years, 7 months
[Persistence, JBoss/CMP, Hibernate, Database] - Sybase database pool not claiming used connections
by viniciuscarvalho
** Also post this under JCA Forum, sorry for the dual post, hoping get some help ASAP **
Hello there! We have a JBoss 4.0.1sp1 + Sybase 12 + JConnect 5.5 with a 50 connections pool. We use a monitor (currentAvailableConnections from web-console) to check the number of available connections, what can be seen is that the pool is "shrinking", the graph looks like a stair, it starts with 45-50 available connections, then after a time (15min or so) it reduces to 40-45... and goes on. Even during lunch time where the application is almost not accessed the pool does not seem to claim its used connections back.
What we are doing is forcing a flush on the MBean in order to free the resources. We also use a mysql and that database pool does return to original state after not being used.
Also, checking the sybase it shows that it has 50 connections and 90% of them are on WAITING_COMMAND state.
I wonder what might be the problem. any idea?
Could be the idle_timeout for the pool? The driver?
Best regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993114#3993114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993114
19 years, 7 months
[JCA/JBoss] - Sybase database pool not claiming used connections
by viniciuscarvalho
Hello there! We have a JBoss 4.0.1sp1 + Sybase 12 + JConnect 5.5 with a 50 connections pool. We use a monitor (currentAvailableConnections from web-console) to check the number of available connections, what can be seen is that the pool is "shrinking", the graph looks like a stair, it starts with 45-50 available connections, then after a time (15min or so) it reduces to 40-45... and goes on. Even during lunch time where the application is almost not accessed the pool does not seem to claim its used connections back.
What we are doing is forcing a flush on the MBean in order to free the resources. We also use a mysql and that database pool does return to original state after not being used.
Also, checking the sybase it shows that it has 50 connections and 90% of them are on WAITING_COMMAND state.
I wonder what might be the problem. any idea?
Could be the idle_timeout for the pool? The driver?
Best regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993113#3993113
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993113
19 years, 7 months
[Installation, Configuration & Deployment] - Maven 2 repository issues
by jactor
Hi!
I am refactoring an applications which was build and deployed using Apache Ant into a build by Maven 2 and am having troubles finding 3 jar files in the maven repository (http://repo1.maven.org/maven2/).
Help me in stating the correct jar files which should be used.
The jar files, manifests (and some additional information on 2 of them):
jboss-annotations.jar, the manifest and folders it contains
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.5
Created-By: 1.5.0_06-b05 (Sun Microsystems Inc.)
Specification-Title: JBoss EJB 3.0
Specification-Version: JBoss EJB 3.0 RC8 - FD
Specification-Vendor: JBoss
Implementation-Title: JBoss EJB 3.0
Implementation-URL: http://www.jboss.com/products/ejb3
Implementation-Version: JBoss EJB 3.0 RC8 - FD
Implementation-Vendor: JBoss
META-INF/
org/
org/jboss/
org/jboss/annotation/
org/jboss/annotation/ejb/
org/jboss/annotation/ejb/cache/
org/jboss/annotation/ejb/cache/simple/
org/jboss/annotation/ejb/cache/tree/
org/jboss/annotation/internal/
org/jboss/annotation/security/
jboss-ejb3x.jar, the manifest and folders it contains. It has 41 files and a last modified timestamp of 11.09.2006 12:04
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.5
Created-By: 1.5.0_06-b05 (Sun Microsystems Inc.)
META-INF/
javax/
javax/annotation/
javax/annotation/security/
javax/ejb/
javax/interceptor/
jbossall-client.jar, the manifest and the folders it contains. It has 2499 files and a last modified timestamp of 07.09.2006 13:22
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.2
Created-By: 1.4.2_09-b05 (Sun Microsystems Inc.)
META-INF/
EDU/
EDU/oswego/
EDU/oswego/cs/
EDU/oswego/cs/dl/
EDU/oswego/cs/dl/util/
EDU/oswego/cs/dl/util/concurrent/
dtd/
javax/
javax/ejb/
javax/ejb/spi/
javax/enterprise/
javax/enterprise/deploy/
javax/enterprise/deploy/model/
javax/enterprise/deploy/model/exceptions/
javax/enterprise/deploy/shared/
javax/enterprise/deploy/shared/factories/
javax/enterprise/deploy/spi/
javax/enterprise/deploy/spi/exceptions/
javax/enterprise/deploy/spi/factories/
javax/enterprise/deploy/spi/status/
javax/jms/
javax/management/
javax/management/j2ee/
javax/management/j2ee/statistics/
javax/management/loading/
javax/management/modelmbean/
javax/management/monitor/
javax/management/openmbean/
javax/management/relation/
javax/management/timer/
javax/resource/
javax/resource/cci/
javax/resource/spi/
javax/resource/spi/endpoint/
javax/resource/spi/security/
javax/resource/spi/work/
javax/security/
javax/security/jacc/
javax/servlet/
javax/servlet/http/
javax/servlet/resources/
javax/sql/
javax/transaction/
javax/transaction/xa/
javax/xml/
javax/xml/namespace/
javax/xml/registry/
javax/xml/registry/infomodel/
javax/xml/rpc/
javax/xml/rpc/encoding/
javax/xml/rpc/handler/
javax/xml/rpc/handler/soap/
javax/xml/rpc/holders/
javax/xml/rpc/server/
javax/xml/rpc/soap/
javax/xml/soap/
org/
org/apache/
org/apache/xerces/
org/apache/xerces/impl/
org/apache/xerces/impl/xs/
org/jboss/
org/jboss/aop/
org/jboss/aop/advice/
org/jboss/aop/instrument/
org/jboss/aop/joinpoint/
org/jboss/aop/metadata/
org/jboss/aop/proxy/
org/jboss/aop/util/
org/jboss/corba/
org/jboss/crypto/
org/jboss/crypto/digest/
org/jboss/deployment/
org/jboss/deployment/cache/
org/jboss/deployment/scanner/
org/jboss/deployment/spi/
org/jboss/deployment/spi/beans/
org/jboss/deployment/spi/configurations/
org/jboss/deployment/spi/factories/
org/jboss/deployment/spi/status/
org/jboss/ejb/
org/jboss/ejb/plugins/
org/jboss/ejb/plugins/cmp/
org/jboss/ejb/plugins/cmp/jdbc/
org/jboss/ejb/plugins/keygenerator/
org/jboss/ha/
org/jboss/ha/framework/
org/jboss/ha/framework/interfaces/
org/jboss/ha/framework/server/
org/jboss/ha/framework/test/
org/jboss/ha/hasessionstate/
org/jboss/ha/hasessionstate/interfaces/
org/jboss/ha/jndi/
org/jboss/iiop/
org/jboss/iiop/rmi/
org/jboss/iiop/rmi/marshal/
org/jboss/iiop/rmi/marshal/strategy/
org/jboss/invocation/
org/jboss/invocation/http/
org/jboss/invocation/http/interfaces/
org/jboss/invocation/jrmp/
org/jboss/invocation/jrmp/interfaces/
org/jboss/invocation/jrmp/server/
org/jboss/invocation/pooled/
org/jboss/invocation/pooled/interfaces/
org/jboss/jmx/
org/jboss/jmx/adaptor/
org/jboss/jmx/adaptor/rmi/
org/jboss/jmx/connector/
org/jboss/jmx/connector/invoker/
org/jboss/jmx/connector/invoker/client/
org/jboss/lang/
org/jboss/logging/
org/jboss/logging/appender/
org/jboss/logging/filter/
org/jboss/logging/layout/
org/jboss/logging/util/
org/jboss/management/
org/jboss/management/mejb/
org/jboss/monitor/
org/jboss/monitor/client/
org/jboss/mq/
org/jboss/mq/il/
org/jboss/mq/il/http/
org/jboss/mq/il/jvm/
org/jboss/mq/il/oil/
org/jboss/mq/il/oil2/
org/jboss/mq/il/rmi/
org/jboss/mq/il/uil2/
org/jboss/mq/il/uil2/msgs/
org/jboss/mq/referenceable/
org/jboss/mq/selectors/
org/jboss/mq/xml/
org/jboss/mx/
org/jboss/mx/capability/
org/jboss/mx/interceptor/
org/jboss/mx/loading/
org/jboss/mx/metadata/
org/jboss/mx/modelmbean/
org/jboss/mx/notification/
org/jboss/mx/persistence/
org/jboss/mx/server/
org/jboss/mx/server/registry/
org/jboss/mx/service/
org/jboss/mx/util/
org/jboss/mx/util/propertyeditor/
org/jboss/naming/
org/jboss/naming/client/
org/jboss/naming/client/java/
org/jboss/naming/interceptors/
org/jboss/net/
org/jboss/net/protocol/
org/jboss/net/protocol/file/
org/jboss/net/protocol/http/
org/jboss/net/protocol/njar/
org/jboss/net/protocol/resource/
org/jboss/net/sockets/
org/jboss/net/ssl/
org/jboss/proxy/
org/jboss/proxy/compiler/
org/jboss/proxy/ejb/
org/jboss/proxy/ejb/handle/
org/jboss/remoting/
org/jboss/remoting/callback/
org/jboss/remoting/detection/
org/jboss/remoting/detection/jndi/
org/jboss/remoting/detection/multicast/
org/jboss/remoting/detection/util/
org/jboss/remoting/ident/
org/jboss/remoting/invocation/
org/jboss/remoting/loading/
org/jboss/remoting/marshal/
org/jboss/remoting/marshal/http/
org/jboss/remoting/marshal/rmi/
org/jboss/remoting/marshal/serializable/
org/jboss/remoting/network/
org/jboss/remoting/network/filter/
org/jboss/remoting/samples/
org/jboss/remoting/samples/callback/
org/jboss/remoting/samples/detection/
org/jboss/remoting/samples/oneway/
org/jboss/remoting/samples/simple/
org/jboss/remoting/samples/stream/
org/jboss/remoting/security/
org/jboss/remoting/stream/
org/jboss/remoting/transport/
org/jboss/remoting/transport/http/
org/jboss/remoting/transport/http/ssl/
org/jboss/remoting/transport/local/
org/jboss/remoting/transport/multiplex/
org/jboss/remoting/transport/rmi/
org/jboss/remoting/transport/servlet/
org/jboss/remoting/transport/servlet/web/
org/jboss/remoting/transport/socket/
org/jboss/remoting/transport/socket/ssl/
org/jboss/remoting/transport/web/
org/jboss/resource/
org/jboss/resource/adapter/
org/jboss/resource/adapter/jdbc/
org/jboss/resource/adapter/jdbc/remote/
org/jboss/resource/connectionmanager/
org/jboss/security/
org/jboss/security/auth/
org/jboss/security/auth/callback/
org/jboss/security/auth/login/
org/jboss/security/jndi/
org/jboss/security/plugins/
org/jboss/security/srp/
org/jboss/security/srp/jaas/
org/jboss/security/ssl/
org/jboss/system/
org/jboss/system/pm/
org/jboss/system/server/
org/jboss/tm/
org/jboss/tm/iiop/
org/jboss/tm/iiop/client/
org/jboss/tm/integrity/
org/jboss/tm/usertx/
org/jboss/tm/usertx/client/
org/jboss/tm/usertx/interfaces/
org/jboss/tm/usertx/server/
org/jboss/util/
org/jboss/util/coerce/
org/jboss/util/collection/
org/jboss/util/deadlock/
org/jboss/util/file/
org/jboss/util/id/
org/jboss/util/loading/
org/jboss/util/naming/
org/jboss/util/platform/
org/jboss/util/property/
org/jboss/util/property/jmx/
org/jboss/util/propertyeditor/
org/jboss/util/state/
org/jboss/util/state/xml/
org/jboss/util/stream/
org/jboss/util/threadpool/
org/jboss/util/timeout/
org/jboss/util/xml/
org/jboss/xb/
org/jboss/xb/binding/
org/jboss/xb/binding/metadata/
org/jboss/xb/binding/metadata/marshalling/
org/jboss/xb/binding/metadata/unmarshalling/
org/jboss/xb/binding/metadata/unmarshalling/impl/
org/jboss/xb/binding/parser/
org/jboss/xb/binding/parser/sax/
org/jboss/xb/binding/parser/xni/
org/jboss/xb/binding/sunday/
org/jboss/xb/binding/sunday/unmarshalling/
org/jboss/xb/binding/sunday/unmarshalling/impl/
org/jboss/xb/binding/sunday/unmarshalling/impl/runtime/
org/jboss/xml/
org/jboss/xml/binding/
org/jboss/xml/binding/parser/
org/jboss/xml/binding/parser/sax/
org/jboss/xml/binding/parser/xni/
org/jnp/
org/jnp/interfaces/
org/jnp/interfaces/java/
org/jnp/interfaces/jnp/
org/jnp/server/
org/omg/
org/omg/stub/
org/omg/stub/javax/
org/omg/stub/javax/ejb/
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993111#3993111
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993111
19 years, 7 months
[JBoss Seam] - Re: Problem with selectItems taglib
by petemuir
The EntityConverter checks to see if the object passed to it is annotated with @Entity. One of the objects being converted isn't marked with @Entity. This is because it has been enhanced by javassist.
Now, I'm no expert on javaassist but I think that it essentially creates a proxy, and passes method invocations to the the object (when the converter checks for @Entity it is scanning the proxy, not the object).
I would guess that the problematic object is #{currentItem.catalogue} - is currentItem a Seam JavaBean?
If so I will see if I can cope with enhanced objects in the converter when I have a moment.
I also obviously need to look at my resourcebundle loading (I think it's now possible to delegate it entirely to Seam).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993109#3993109
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993109
19 years, 7 months
[Persistence, JBoss/CMP, Hibernate, Database] - Hibernate with EHCache
by grigovlad
I am using Hibernate 3.2.0 with JBoss 4.0.4, in an enterprise application. I have configured hibernate-service.xml to use the EhCacheProvider as a provider for the second level cache. I use ehcache 1.2.4.
The ehcache-1.2.4.jar is placed in the libs directory of the current server.
The problem is that ehcache uses an external configuration file (ehcache.xml). At startup, ehcache.xml is automatically searched in classpath. I tried to place ehcache.xml in several directories (in the same directory with hibernate-service.xml, in the root of the ear, in the directory where hibernate.cfg.xml is located), but none of the solutions worked. I keep getting an error that the configuration file ehcache.xml couldn't be found. ([net.sf.ehcache.config.ConfigurationFactory] No configuration found.)
The only place I put ehcache.xml and it worked ok was inside the ehcache-1.2.4.jar (the jar is in the libs directory of the current server). If I put it there, ehcache.xml is found at startup and everything works all right (but this is a very ugly solution).
Isn't threre any way to put ehcache.xml inside the ear so that it will be found at startup, when the hibernate Mbean is initialized?
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993102#3993102
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993102
19 years, 7 months
[JBossWS] - Re: Issue with .NET ws clients
by maeste
"heiko.braun(a)jboss.com" wrote : Looking at it more carefully doesn't reveal anything at JBossWS processing level. That piece of code prepares the SOAPMessageContext upon receiving the HTTPRequest InputStream.
|
Yes, it seems the HTTPRequest InputStream is already closed when jbossws try to use it. One more thing to clarify the situation: it happens with unpredictable frequency...it seems a problem with server overload or concurrency (just a smell of them, I'm not sure, but a lot of tests in test environment can't reproduce error)
"heiko.braun(a)jboss.com" wrote :
| My 2 cents:
| In this case i'd say that the servlet engine probably has written something back to .NET client without notice.
|
and closes the connection.
"heiko.braun(a)jboss.com" wrote :
| Do you have any HTTP logs available at the client side?
|
No of course.........it's a .NET client :)
"heiko.braun(a)jboss.com" wrote :
| A look at the jboss-tomcat logs might help as well.
Some classes suspected? We can't enable all jboss-tomcat logs in production environment processing many requests per second.
A little OT: please take a look to my last post in Design Forum ;)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993094#3993094
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993094
19 years, 7 months
[JBoss Seam] - Problem with selectItems taglib
by dave.rogers
I am using the taglib
xmlns:si="http://jboss.com/products/seam/selectitems/taglib"
as follows:
<h:selectOneMenu id="catalogue" value="#{currentItem.catalogue}">
| <si:selectItems value="#{catalogues}" var="catalogue" label="#{catalogue.name}"/>
| </h:selectOneMenu>
with the following in my bean:
@Factory("catalogues")
| public List<Catalogue> buildCatalogues() {
| List<Catalogue> catalogues =
| em.createQuery("select c from Catalogue c")
| .getResultList();
| log.info("Catalogues list has " + catalogues.size() + " entries");
| return catalogues;
| }
According to my log "14:24:13,580 INFO [ItemManager] Catalogues list has 96 entries". But the following error is thrown:
Caused by: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key org.jboss.seam.selectitems.entityConverter.notAnEntity halvor.pojo.Catalogue_$$_javassist_44
Now I don't really care about the missing resource, for now, what I'm concerned about is the underlying error. (notAnEntity). This implies that my pojo is not an entity when is it (is has the @Entity tag, an @Id tag on the id etc..).
Why would it still think that this is not an entity?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993085#3993085
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993085
19 years, 7 months