[EJB 3.0] - Dynamically provide user and password for MDB
by shadow2000
Hi everyone,
we have a huge problem over here and I'm wondering if somebody else have solved this problem.
We have developed a application on JBoss 4.2.3 with MDBs that listen to queue provided by a remote provider. Everthing works fine but the queues needed a user. the only solution that i have found is to define user and password with annotations:
|
| @MessageDriven(name = "IncomingSupplierOrderListener", activationConfig = {
| @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Topic"),
| @ActivationConfigProperty(propertyName = "destination", propertyValue = "topic/TOPICNAME"),
| @ActivationConfigProperty(propertyName = "subscriptionDurability", propertyValue = "NonDurable"),
| @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "java:/Remote_JMSProvider"),
| @ActivationConfigProperty(propertyName = "user", propertyValue = MessageConstants.INCOMING_USER),
| @ActivationConfigProperty(propertyName = "password", propertyValue = MessageConstants.INCOMING_USER_PASS),
| @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE/Auto-acknowledge") })
Both are set over constants. But we need to change these settings on runtime. Have anybody an idea how to solve this?
Best Regards
Lars
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199564#4199564
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199564
17 years, 3 months
[JBoss jBPM] - Process State in a Fork not executing correctly
by philso
Hi, I have a test running that contains multiple nodes including two Process States. JPEG of the Process Definition is at:
http://picasaweb.google.com/lh/sredir?uname=phil.omalley&target=ALBUM&id=...
Process State 1 (LoadSubProcess1) is on the main path of execution. Process State 2 (LoadSubProcess2) is in a fork with two paths. I find I can execute my test fine up to the Process State in the Fork (LoadSubProcess2). My test can traverse fine through the first process State (LoadSubProcess1). When execution gets to the Fork alls well, child tokens are created OK but when execution is called on the transition into LoadSubProcess2 the Sub Process is not entered and the only available transition to this token is "fromLoadSubProcess2" (the transition after LoadSubProcess2). So it looks like the child tokens execution path cannot execute the Sub Process. For this test I've made LoadSubProcess1 & 2 point to the same ProcessDefinition xml so I know the xml is OK. The two other child paths execute fine and complete ok into the join node. The only difference I can see is one Process State call is made from the main execution path and the failing one is made from a child execution path. Does anyone have an idea what I'm doing wrong here? Many thanks for your time & effort.
The Main Process Definition xml
| <?xml version="1.0" encoding="UTF-8"?>
| <process-definition xmlns="urn:jbpm.org:jpdl-3.2urn:jbpm.org:jpdl-3.2"
| name="SampleProcess">
| <start-state name="Start">
| <transition to="task-node1" name="to task-node1">
| </transition>
| </start-state>
| <task-node name="task-node1" signal="never">
| <task name="taskNametask-node1" />
| <transition to="state0" name="to-state0"></transition>
| </task-node>
| <state name="state0">
| <transition to="LoadSubProcess1" name="toLoadSubProcess1"></transition>
| </state>
| <fork name="fork1">
| <transition to="state1" name="toState1"></transition>
| <transition to="state2" name="to state2"></transition>
| <transition to="state3" name="to state3"></transition>
| </fork>
| <state name="state1">
| <event type="node-leave">
| <action
| class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| <transition to="task-node2" name="to task-node2"></transition>
| </state>
| <state name="state2">
| <event type="node-leave">
| <action
| class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| <transition to="task-node3" name="to task-node3"></transition>
| </state>
| <task-node name="task-node2" signal="never">
| <task name="taskNametask-node2" />
| <transition to="LoadSubProcess2" name="toLoadSubProcess2"></transition>
| </task-node>
| <task-node name="task-node3" signal="never">
| <task name="taskNametask-node3" />
| <transition to="join1" name="from task-node3"></transition>
| </task-node>
| <state name="state3">
| <event type="node-leave">
| <action
| class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| <transition to="task-node4" name="to task-node4"></transition>
| </state>
| <task-node name="task-node4" signal="never">
| <task name="taskNametask-node4" />
| <transition to="state4" name="to state4"></transition>
| </task-node>
| <join name="join1">
| <transition to="taskNode6" name="toTaskNode6"></transition>
| </join>
| <task-node name="task-node5" signal="never">
| <task name="taskNametask-node5" />
| <transition to="join1" name="from task-node5"></transition>
| </task-node>
| <state name="state4">
| <event type="node-enter">
| <action
| class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| <transition to="task-node5" name="to task-node5"></transition>
| </state>
| <process-state name="LoadSubProcess2">
| <sub-process name="LoadSubProcess" />
| <transition to="join1" name="fromLoadSubProcess2"></transition>
| </process-state>
| <task-node name="taskNode6" signal="never">
| <task name="taskNametask-node6" />
| <transition to="End" name="toEnd"></transition>
| </task-node>
| <process-state name="LoadSubProcess1">
| <sub-process name="LoadSubProcess" />
| <transition to="task-nodeA" name="to task-nodeA"></transition>
| </process-state>
|
| <state name="stateA">
| <transition to="fork1" name="toFork1"></transition>
| </state>
|
| <task-node name="task-nodeA" signal="never">
| <task name="taskNametask-nodeA" />
| <transition to="stateA" name="toStateA"></transition>
| </task-node>
| <end-state name="End"></end-state>
| </process-definition>
|
Sub Process XML
| <?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition xmlns="" name="LoadSubProcess">
|
|
| <start-state name="Start">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| <transition to="LoadIncomplete" name="toLoadIncomplete"></transition>
| </start-state>
|
|
| <state name="LoadIncomplete">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| <transition to="CreateOrUpdateDoc" name="toCreateOrUpdateDoc"></transition>
| <transition to="CancelTrip" name="toCancelTrip"></transition>
| <transition to="CreateDoc" name="toCreateDoc"></transition>
| <transition to="TripCompleted" name="toTripCompleted"></transition>
| </state>
|
| <task-node name="CreateDoc" signal="never">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.WorkflowTaskExecuterImpl"></action>
| </event>
| <task name ="taskCreateDoc" />
| <transition to="LoadIncomplete" name="fromCreateDocToLoadIncomplete"></transition>
| </task-node>
|
| <task-node name="CreateOrUpdateDoc" signal="never">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.WorkflowTaskExecuterImpl"></action>
| </event>
| <task name ="taskCreateOrUpdateDoc" />
| <transition to="LoadIncomplete" name="fromCreateOrUpdateDocToLoadIncomplete"></transition>
| </task-node>
|
| <task-node name="CancelTrip" signal="never">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.WorkflowTaskExecuterImpl"></action>
| </event>
| <task name ="taskCancelTrip" />
| <transition to="TripConcelled" name="toTripCancelled"></transition>
| </task-node>
|
| <task-node name="TripCompleted" signal="never">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.WorkflowTaskExecuterImpl"></action>
| </event>
| <task name ="taskTripCompleted" />
| <transition to="LoadCompleted" name="toLoadCompleted"></transition>
| </task-node>
|
| <state name="LoadCompleted">
| <description>
| Had to add this state node here because the running tests we see the end state is never rested on when this process is used
| as a subprocess
| </description>
| <transition to="LoadEnd" name="toLoadEnd"></transition>
| </state>
|
| <state name="TripConcelled">
| <transition to="TripCancelEnd" name="toTripCancelEnd"></transition>
| </state>
|
|
| <end-state name="TripCancelEnd">
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| </end-state>
|
| <end-state name="LoadEnd" >
| <event type="node-enter" >
| <action class="com.meridianp2p.stf.impl.workflow.ProcessChangeEventNotifier"></action>
| </event>
| </end-state>
|
| </process-definition>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199561#4199561
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199561
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - Running out of file descriptors when redeploying EAR
by nzmalik
I'm trying out JBossAS 4.3.0 GA CP03. I've discovered that I run out of deployment descriptors when redeploying things in the container. I've tested this out on a base installation of EAP. I deployed a single ear in the container. The ear contains some MDB's. I then used the following to redeploy the ear every 6 seconds up to 1000 times:
for i in `seq 1 1000`; do touch /var/lib/jbossas/server/production/deploy/MY-EAR.ear; sleep 6; echo "lsof count ($i) = `ps aux | grep "^jboss" | grep Main | sed 's/^[^ ]*\s*\([^ ]*\).*/lsof -p \1 | wc -l/g' | sh`"; done
This redeploys the ear, waits 6 seconds, then prints the line count from lsof for the jboss process along with the redeployment count. In my most test I run out of file descriptors after 315 redeployments. I've seen it fail a lot more. If I add in the full complement of stuff normally deployed for my scenario I see failure after as few as 7 redeployments.
Checking the lsof count (lsof -p 9999 | wc -l) shows the count goes up for a while, then drops down. This drop occurs roughly every 50 redeploys, but never drops down completely.
Here is my original post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199195
Looking at lsof changes over time, it looks like the container is keeping a handle on the jar files contained within the ear, even after the ear is undeployed completely.
Any idea why this is happening? I'm currently using JBossAS 4.3.0 GA CP01 and have never seen this problem in that version nor any previous versions. Note that I was unable to use CP02 due to some bugs that have been fixed in CP03.
Here is the exception I got in my initial testing, as noted on the linked post:
2008-12-19 14:11:36,744 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/var/lib/jbossas/server/production/deploy/esb-ESB-COMPONENT-NAME.esb
| org.jboss.deployment.DeploymentException: exception in init of file:/var/lib/jbossas/server/production/tmp/deploy/tmp61014esb-ESB-COMPONENT-NAME.esb-contents/lib/commons-pool-1.4.jar; - nested throwable: (java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file)
| at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:901)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| 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.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:291)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
| Caused by: java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file
| at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:74)
| at org.jboss.util.file.FileProtocolArchiveBrowserFactory.create(FileProtocolArchiveBrowserFactory.java:48)
| at org.jboss.util.file.ArchiveBrowser.getBrowser(ArchiveBrowser.java:57)
| at org.jboss.ejb3.EJB3Deployer.hasEjbAnnotation(EJB3Deployer.java:213)
| at org.jboss.ejb3.EJB3Deployer.accepts(EJB3Deployer.java:279)
| at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:109)
| 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.system.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:291)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy34.accepts(Unknown Source)
| at org.jboss.deployment.MainDeployer.findDeployer(MainDeployer.java:1078)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:857)
| ... 22 more
| Caused by: java.util.zip.ZipException: error in opening zip file
| at java.util.zip.ZipFile.open(Native Method)
| at java.util.zip.ZipFile.<init>(ZipFile.java:114)
| at java.util.jar.JarFile.<init>(JarFile.java:133)
| at java.util.jar.JarFile.<init>(JarFile.java:97)
| at org.jboss.util.file.JarArchiveBrowser.<init>(JarArchiveBrowser.java:69)
| ... 45 more
| 2008-12-19 14:11:41,763 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:11:46,767 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:11:51,771 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:11:56,775 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:01,780 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:06,784 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:11,788 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:16,792 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:21,804 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:26,809 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:31,814 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:36,818 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:41,822 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
| 2008-12-19 14:12:45,307 ERROR [org.jbpm.job.executor.JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds
| org.jbpm.JbpmException: couldn't start JTA transaction
| at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:51)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:28)
| at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:17)
| at org.jbpm.svc.Services.getService(Services.java:144)
| at org.jbpm.svc.Services.getPersistenceService(Services.java:183)
| at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:628)
| at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:561)
| at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:112)
| at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:58)
| Caused by: org.jbpm.JbpmException: couldn't lookup UserTransaction in JNDI with name UserTransaction
| at org.jbpm.persistence.jta.JtaDbPersistenceService.getUserTransaction(JtaDbPersistenceService.java:90)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:49)
| ... 8 more
| Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: IP_ADDRESS; nested exception is:
| java.net.SocketException: Too many open files]
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:780)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.getUserTransaction(JtaDbPersistenceService.java:88)
| ... 9 more
| Caused by: java.rmi.ConnectIOException: Exception creating connection to: IP_ADDRESS; nested exception is:
| java.net.SocketException: Too many open files
| at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:614)
| at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
| at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
| at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
| at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
| ... 12 more
| Caused by: java.net.SocketException: Too many open files
| at java.net.Socket.createImpl(Socket.java:388)
| at java.net.Socket.<init>(Socket.java:362)
| at java.net.Socket.<init>(Socket.java:180)
| at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
| at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
| at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
| ... 17 more
| 2008-12-19 14:12:50,314 ERROR [org.jbpm.job.executor.JobExecutorThread] exception in job executor thread. waiting 10000 milliseconds
| org.jbpm.JbpmException: couldn't start JTA transaction
| at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:51)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.<init>(JtaDbPersistenceService.java:28)
| at org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory.openService(JtaDbPersistenceServiceFactory.java:17)
| at org.jbpm.svc.Services.getService(Services.java:144)
| at org.jbpm.svc.Services.getPersistenceService(Services.java:183)
| at org.jbpm.JbpmContext.getPersistenceService(JbpmContext.java:628)
| at org.jbpm.JbpmContext.getJobSession(JbpmContext.java:561)
| at org.jbpm.job.executor.JobExecutorThread.acquireJobs(JobExecutorThread.java:112)
| at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:58)
| Caused by: org.jbpm.JbpmException: couldn't lookup UserTransaction in JNDI with name UserTransaction
| at org.jbpm.persistence.jta.JtaDbPersistenceService.getUserTransaction(JtaDbPersistenceService.java:90)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.beginJtaTransaction(JtaDbPersistenceService.java:49)
| ... 8 more
| Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: IP_ADDRESS:1099 and discovery failed with error: javax.naming.CommunicationException: Too many open files [Root exception is java.net.SocketException: Too many open files] [Root exception is javax.naming.CommunicationException: Failed to connect to server IP_ADDRESS:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server IP_ADDRESS:1099 [Root exception is java.net.SocketException: Too many open files]]]
| at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
| at org.jbpm.persistence.jta.JtaDbPersistenceService.getUserTransaction(JtaDbPersistenceService.java:88)
| ... 9 more
| Caused by: javax.naming.CommunicationException: Failed to connect to server IP_ADDRESS:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server IP_ADDRESS:1099 [Root exception is java.net.SocketException: Too many open files]]
| at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274)
| at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533)
| ... 13 more
| Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server IP_ADDRESS:1099 [Root exception is java.net.SocketException: Too many open files]
| at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248)
| ... 14 more
| Caused by: java.net.SocketException: Too many open files
| at java.net.Socket.createImpl(Socket.java:388)
| at java.net.Socket.<init>(Socket.java:362)
| at java.net.Socket.<init>(Socket.java:267)
| at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
| at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
| at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244)
| ... 14 more
| 2008-12-19 14:12:51,842 WARN [org.jboss.deployment.scanner.URLDeploymentScanner] Scan URL, caught java.io.IOException: Could not list directory '/var/lib/jbossas/server/production/deploy', reason unknown
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199560#4199560
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199560
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - IMAP via TLS in JBoss 4.2.2.GA
by luckybird
Hi all,
I'm just trying to connect to an IMAP mailserver from JBoss. But all I get is the following exception:
| 15:07:10,484 ERROR [STDERR] javax.mail.MessagingException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target;
| nested exception is:
| javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
| 15:07:10,499 ERROR [STDERR] at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:479)
| 15:07:10,499 ERROR [STDERR] at javax.mail.Service.connect(Service.java:297)
| 15:07:10,499 ERROR [STDERR] at javax.mail.Service.connect(Service.java:156)
| 15:07:10,499 ERROR [STDERR] at javax.mail.Service.connect(Service.java:105)
My mail-service.xml looks like following:
| <mbean code="org.jboss.mail.MailService" name="MSTM:service=OrderSMSService">
| <attribute name="JNDIName">java:/ORDERSMS
| </attribute>
| <attribute name="User">me</attribute>
| <attribute name="Password">dontknow</attribute>
| <attribute name="Configuration">
| <configuration>
| <property name="mail.transport.protocol" value="imap" />
| <property name="mail.user" value="me" />
| <property name="mail.password" value="dontknow" />
|
| <property name="mail.host" value="my.favourite.mailserver.com" />
|
| <property name="mail.smtp.host" value="my.favourite.mailserver.com" />
|
| <property name="mail.imap.starttls.enable" value="true" />
|
| <property name="mail.debug" value="true" />
| </configuration>
| </attribute>
| </mbean>
|
To access the mailbox I'm using the following code:
Store store = mailSession.getStore("imaps");
| store.connect();
|
How can I tell JBoss to connect to the IMAP server?
TIA,
Ralf.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199547#4199547
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199547
17 years, 3 months
[Installation, Configuration & DEPLOYMENT] - Barrier not started
by zana
We are using the Barrier mbean for some of our services and are trying to upgrade to JBoss 5.0.0.GA. However, the Barrier does not get started, it is created.
The log shows:
| 2009-01-05 10:05:47,651 DEBUG [BarrierController] (main:) [SubscriptionInfo { objectName='jboss.ha:service=HASingletonDeployer', handback=start, filter=javax.management.NotificationFilterSupport@110faff }, SubscriptionInfo { objectName='jboss.ha:service=HASingletonDeployer', handback=stop, filter=javax.management.NotificationFilterSupport@1ce7ceb }]
| 2009-01-05 10:05:47,651 DEBUG [BarrierController] (main:) Subscribing for JMX notifications, dynamic=false
| 2009-01-05 10:05:47,651 DEBUG [BarrierController] (main:) Could not subscribe to: 'jboss.ha:service=HASingletonDeployer', target or listener MBean not registered
| 2009-01-05 10:05:47,651 DEBUG [BarrierController] (main:) Could not subscribe to: 'jboss.ha:service=HASingletonDeployer', target or listener MBean not registered
| 2009-01-05 10:05:47,651 DEBUG [BarrierController] (main:) Created jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean
| 2009-01-05 10:05:47,651 DEBUG [ServiceController] (main:) Creating service jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean
| ...
| 2009-01-05 10:05:47,653 DEBUG [BarrierController] (main:) Starting jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean
| 2009-01-05 10:05:47,653 DEBUG [BarrierController] (main:) Started jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean
| 2009-01-05 10:05:47,654 DEBUG [ServiceController] (main:) starting service jboss.ha:service=HASingletonDeployer,type=BarrierControllerMBean
| ...
| 2009-01-05 10:06:28,791 ERROR [ProfileServiceBootstrap] (main:) Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
|
|
| UserXS:service=myService
| -> jboss.ha:service=HASingletonDeployer,type=Barrier{Start:Create}
|
|
| *** CONTEXTS IN ERROR: Name -> Error
|
| jboss.ha:service=HASingletonDeployer,type=Barrier -> Create
I am using the original all/deploy/cluster/deploy-hasingleton-jboss-beans.xml file without changes.
Is this a known issue?
The error disappears and the Barrier gets starts when I add a dependency in the BarrierController in all/deploy/cluster/deploy-hasingleton-jboss-beans.xml
<bean class="org.jboss.system.BarrierController" name="jboss.ha:service=HASingletonDeployer,type=BarrierController">
| ...
| <depends>jboss.ha:service=HASingletonDeployer</depends>
| ...
|
Is this a right solution/workaround?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199546#4199546
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199546
17 years, 3 months