[JBoss JIRA] Created: (JBJCA-36) Datasource deployer
by Jesper Pedersen (JIRA)
Datasource deployer
-------------------
Key: JBJCA-36
URL: https://jira.jboss.org/jira/browse/JBJCA-36
Project: JBoss JCA
Issue Type: Task
Components: Deployer
Reporter: Jesper Pedersen
Assignee: Jeff Zhang
Fix For: 1.0 Alpha1
We need a datasource deployer chain that can deploy -ds.xml descriptors.
The chain must be able to deploy any existing datasource definitions found in JBoss Application Server 5.0.
A design goal is that the chain can be deployed in a standalone mode so it can be included in other projects - such as EJB3 - without pulling in the entire JCA implementation.
Sub-tasks should be created for each deployment stage (org.jboss.deployers.spi.deployer.DeploymentStage).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBREM-992) Can't restart a Connector that uses SocketServerInvoker
by Brian Stansberry (JIRA)
Can't restart a Connector that uses SocketServerInvoker
-------------------------------------------------------
Key: JBREM-992
URL: http://jira.jboss.com/jira/browse/JBREM-992
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.GA (Pinto)
Reporter: Brian Stansberry
Priority: Minor
You can't take a Connector that uses SocketServerInvoker through a restart, i.e. these lifecycle steps:
create/start/stop/start.
You have to do a full transition to destroy and back through create.
This is because SocketServerInvoker sets its maxPoolSize field to 0 as part of its cleanup work in stop(). If you then call start() you get a failure due to 0 being an invalid value for maxPoolSize:
2008-06-04 12:33:00,382 DEBUG [org.jboss.invocation.unified.server.UnifiedInvokerHA] (RMI TCP Connec
tion(31)-127.0.0.1) Starting failed jboss:service=invoker,type=unifiedha,partitionName=RestartPartit
ion
java.lang.IllegalArgumentException: Illegal cache capacities
at org.jboss.util.LRUCachePolicy.<init>(LRUCachePolicy.java:77)
at org.jboss.remoting.transport.socket.LRUPool.<init>(LRUPool.java:44)
at org.jboss.remoting.transport.socket.SocketServerInvoker.start(SocketServerInvoker.java:231)
at org.jboss.invocation.unified.server.UnifiedInvoker.startService(UnifiedInvoker.java:140)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years