[JBossCache] - when eviction is configured in the clustered environment, th
by murthytvsn
when eviction is configured in the clustered environment, the tomcat server is not shutting down properly. And I have to kill the process manually. My configuration is as below
<?xml version="1.0"?>
READ_COMMITTED
REPL_ASYNC
JForumCacheStage
<!-- UDP: if you have a multihomed machine,
set the bind_addr attribute to the appropriate NIC IP address -->
<!-- UDP: On Windows machines, because of the media sense feature
being broken with multicast (even after disabling media sense)
set the loopback attribute to true -->
<UDP mcast_addr="228.1.2.3" mcast_port="48866"
ip_ttl="64" ip_mcast="true" bind_addr="xxx.xx.xx.xx"
mcast_send_buf_size="300000" mcast_recv_buf_size="640000"
ucast_send_buf_size="300000" ucast_recv_buf_size="640000"
loopback="false"/>
<PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false"/>
<MERGE2 min_interval="60000" max_interval="90000"/>
<FD shun="true" up_thread="true" down_thread="true" timeout="2500" max_tries="5"/>
<VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false"/>
<pbcast.NAKACK gc_lag="50" retransmit_timeout="100,200,300,600,1200,2400,4800"
max_xmit_size="32768" up_thread="false" down_thread="false"/>
<UNICAST timeout="300,600,1200,2400,3600" window_size="100" min_threshold="10" down_thread="false"/>
<pbcast.STABLE desired_avg_gossip="40000" up_thread="false" down_thread="false" max_bytes="300000"/>
<FRAG frag_size="16384" down_thread="false" up_thread="false"/>
<pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" print_local_addr="true"/>
<pbcast.STATE_TRANSFER up_thread="false" down_thread="false"/>
org.jboss.cache.eviction.LRUPolicy
<!-- Specific eviction policy configurations. This is LRU -->
<!-- Cache wide default -->
3600
<!-- Cache wide default -->
2000
3600
200
0
0
300
0
0
200
0
0
200
0
0
<!--attribute name="maxNodes">300</attribute-->
10
3600
0
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008974#4008974
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008974
17 years, 3 months
[JCA/JBoss] - DataSource Invoker Dependency - JBAS-2215 Regression?
by eonnen
I'm putting together a sample, stripped-down 4.0.5.GA configuration where I'd like to remove the JRMPInvoker. Deployment of my data source is giving a dependency error that:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.jca:service=DataSourceBinding,name=JMSDS
State: CONFIGURED
I Depend On:
jboss.jca:service=LocalTxCM,name=JMSDS
jboss:service=invoker,type=jrmp
The datasource is quite simple and I've tried with use-java-context and without, neither configuration is successful:
<?xml version="1.0" encoding="UTF-8"?>
<local-tx-datasource>
<jndi-name>JMSDS</jndi-name>
<connection-url>jdbc:postgresql://localhost/jboss-messaging</connection-url>
<driver-class>org.postgresql.Driver</driver-class>
<user-name>jboss</user-name>
jboss
<use-java-context>true</use-java-context>
</local-tx-datasource>
Did I miss something or is theis a JBAS-2215 regression? I hadn't seen the issue in 4.0.4 with a similar configuration.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008970#4008970
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008970
17 years, 3 months
[EJB 3.0] - Re: Not able to create durable subscription in MDB
by alllle
Alright, after many many hours of digging around, I found out the JBoss extension of the EJB3 MDB annotations from wiki. I cleared the jboss.xml and ejb-jar.xml file and used only the EJB3 annotations. My MDB now looks like:
| @MessageDriven(name = "notificationMDB", activationConfig = {
| @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
| @ActivationConfigProperty(propertyName = "destination", propertyValue = "topic/notificationTopic"),
| @ActivationConfigProperty(propertyName = "user", propertyValue = "user"),
| @ActivationConfigProperty(propertyName = "password", propertyValue = "pass"),
| @ActivationConfigProperty(propertyName = "noLocal", propertyValue = "true") })
| @ResourceAdapter("jms-ra.rar")
| public class NotificationMDB extends BaseServiceBean implements MessageListener {
|
| public void onMessage(Message message) {
| System.out.println(message.toString());
| }
|
| }
|
As you can see, I didn't configure it as Durable to test it out. It deployed fine without error, and it received a message okay. But then it gives out a nasty error:
| 13:39:30,290 WARN connectionmanager.SimpleConnectionManager - A problem has been detected with the
| connection to remote client 4co2mt-vld24e-exm5wy4h-1-exm5xes0-5. It is possible the client has exite
| d without closing its connection(s) or there is a network problem. All connection resources correspo
| nding to that client process will now be removed.
| 13:39:30,300 ERROR util.ExceptionUtil - ConsumerEndpoint[-2147483628] close [4co2mt-vld24e-exm5wy4h-
| 1-exm5yc1o-o]
| java.lang.RuntimeException: Failed to obtain lock
| at org.jboss.messaging.core.local.PointToMultipointRouter.remove(PointToMultipointRouter.jav
| a:166)
| at org.jboss.messaging.core.local.Topic.remove(Topic.java:126)
| at org.jboss.messaging.core.local.CoreSubscription.disconnect(CoreSubscription.java:111)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.close(ServerConsumerEndpoint.java:36
| 0)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.remove(ServerConsumerEndpoint.java:5
| 43)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.close(ServerSessionEndpoint.java:403)
|
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.jav
| a:300)
| at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(Simple
| ConnectionManager.java:158)
| at org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(
| SimpleConnectionManager.java:208)
| at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:46)
| at org.jboss.remoting.Lease$LeaseTimerTask.execute(Lease.java:133)
| at org.jboss.util.TimerQueue$TimerTaskLoop.run(TimerQueue.java:181)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.InterruptedException
| at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock.acquire(WriterP
| referenceReadWriteLock.java:234)
| at org.jboss.messaging.core.local.PointToMultipointRouter.remove(PointToMultipointRouter.jav
| a:161)
| ... 12 more
|
>From that point on, the messages are not delivered to the MDB anymore. It looks like a connection not closed problem, but it is out of my control as it is a MDB, I don't create a connection in my code.
I always feeled that JBoss' products are very solid. But a easy MDB deployment is taking me days and still no clue. Very frustrated.
Another thing is, I looked into the source code of SimpleConnectionManager, and it is a very short class. It apparently does not have a line 208. Seems that the source code in the download is not the one been compiled?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008969#4008969
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008969
17 years, 3 months
[JBoss Seam] - Re: Seam via Apache and ProxyPass/ProxyPassReverse not worki
by DataGazetteer
A follow-up -- I've tweaked the Apache configuration to the point where I can get the home page to load, but the next step in the application -- form submissions -- is not working. Here is the new Apache configuration (different from the first by adding some trailing slashes to some of the parameters):
| <VirtualHost *>
| ServerName integration.drc-dev.ohiolink.edu
| ProxyRequests off
| ProxyPreserveHost On
| <Proxy *>
| Order deny,allow
| Allow from all
| </Proxy>
| ProxyPass / http://localhost:8080/drc/
| ProxyPassReverse / http://localhost:8080/drc/
|
| SetOutputFilter proxy-html
| ProxyHTMLExtended on
| ProxyHTMLURLMap /drc/ /
|
| <Location />
| Order allow,deny
| Allow from all
| </Location>
| </VirtualHost>
|
The HTML error is slightly different:
| HTTP Status 404 - /drc/drc/itemList.seam
|
| type Status report
| message /drc/drc/itemList.seam
| description The requested resource (/drc/drc/itemList.seam) is not available.
|
...as is the HTTP trace:
| http://integration.drc-dev.ohiolink.edu/home.seam;jsessionid=DB7F029598D3...
|
| POST /home.seam;jsessionid=DB7F029598D3F83AC725FB1BE50A2C69 HTTP/1.1
| Host: integration.drc-dev.ohiolink.edu
| User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
| Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
| Accept-Language: en-us,en;q=0.5
| Accept-Encoding: gzip,deflate
| Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
| Keep-Alive: 600
| Proxy-Connection: keep-alive
| Referer: http://integration.drc-dev.ohiolink.edu/home.seam
| Cookie: JSESSIONID=DB7F029598D3F83AC725FB1BE50A2C69
| Content-Type: application/x-www-form-urlencoded
| Content-Length: 10208
| [...form content...]
|
| HTTP/1.x 302 Moved Temporarily
| Date: Wed, 31 Jan 2007 19:23:29 GMT
| Server: Apache-Coyote/1.1
| X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5
| Location: http://integration.drc-dev.ohiolink.edu/drc/itemList.seam?cid=64
| Content-Length: 0
| Content-Type: text/plain
| Connection: close
|
| ----------------------------------------------------------
|
| http://integration.drc-dev.ohiolink.edu/drc/itemList.seam?cid=64
|
| GET /drc/itemList.seam?cid=64 HTTP/1.1
| Host: integration.drc-dev.ohiolink.edu
| User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
| Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
| Accept-Language: en-us,en;q=0.5
| Accept-Encoding: gzip,deflate
| Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
| Keep-Alive: 600
| Proxy-Connection: keep-alive
| Referer: http://integration.drc-dev.ohiolink.edu/home.seam
| Cookie: JSESSIONID=DB7F029598D3F83AC725FB1BE50A2C69
|
| HTTP/1.x 404 /drc/drc/itemList.seam
| Date: Wed, 31 Jan 2007 19:23:30 GMT
| Server: Apache-Coyote/1.1
| X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5
| Content-Type: text/html;charset=utf-8
| Connection: close
|
It would seem that ProxyPassReverse isn't getting invoked for the Location header in reponse to the POST, except that I see it working with non-Seam applications.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008962#4008962
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008962
17 years, 3 months