[JBoss Seam] - Re: Stop the violence! How should we be separating our beans
by gavin.kingï¼ jboss.com
Ahem, there's no right or wrong way.
Option 2 has the (big) advantage that it requires less code.
Option 1 has the advantage that the business logic is not coupled to FacesMessages, which means that it would be reusable as a WS or whatever.
So it really depends on asking yourself the question: "how likely is it that I'm going to need to use this functionality from something other than JSF in the next 6 months?"
And, or course, that's often a very difficult problem to answer. However, if you don't have a great answer, notice that with modern refactoring tools, it is really not that difficult to get from 2 to 1 if and when you need to do it. In fact, its only arguable that there is less work to do 1 immediately rather than do 2 now and then refactor to get to 1 (if and when you need it).
I strongly believe that it's usually much more important to get *working functionality now*, than it is to plan for stuff that might or might not happen in 6 months or a year or two years. Deliver useful stuff ASAP, secure ongoing funding for your project, and ongoing cooperation, trust and feedback from your users. Then in 6 months time when you really need it, you'll be able to do the refactorings you really need, with a lot less pressure, and a lot more knowledge.
BTW, there is always Option 3:
<rule if="#{addressmanager.addressChangeAllowed}">
| <redirect view-id="/addressChanged.xhtml">
| <message>The address was changed.</message>
| </redirect>
| </rule>
| <rule if="#{not addressmanager.addressChangeAllowed}">
| <render view-id="/changeAddress.xhtml">
| <message>The address can not be changed.</message>
| </render>
| </rule>
| |
| | But I understand that this is not to all tastes ;-)
| |
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032901#4032901
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032901
19Â years
[JBoss Seam] - Cant't deploy on Tomcat 5.5.9
by mpikula
Hi,
I tried to deploy the dvdstore example on a tomcat 5.5.9 and I got the following exception.
Can anybody help me?
Thanks!
Marcin
20:34:34,826 INFO [Lifecycle] starting up: org.jboss.seam.core.ejb
| 20:34:34,826 INFO [Ejb] starting the embedded EJB container
| 20:34:35,527 ERROR [Util] Failed to create schema loader.
| java.lang.ClassCastException: org.apache.xerces.dom.DOMXSImplementationSourceImp
| l
| at org.w3c.dom.bootstrap.DOMImplementationRegistry.newInstance(DOMImplem
| entationRegistry.java:144)
| at org.jboss.xb.binding.Util$2.run(Util.java:506)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.xb.binding.Util.getXSImplementation(Util.java:482)
| at org.jboss.xb.binding.Util.loadSchema(Util.java:381)
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.ja
| va:177)
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.ja
| va:148)
| at org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver.resol
| ve(DefaultSchemaResolver.java:248)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startE
| lement(SundayContentHandler.java:159)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan
| dler.startElement(SaxJBossXBParser.java:299)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
| ce)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn
| own Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.s
| canRootElementHook(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
| Dispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
| known Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
| er.java:124)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
| :132)
| at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXM
| LDeployer.java:85)
| at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.boot(EJB3StandaloneBo
| otstrap.java:380)
| at org.jboss.seam.core.Ejb.startup(Ejb.java:42)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:20)
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123)
| at org.jboss.seam.Component.callComponentMethod(Component.java:1834)
| at org.jboss.seam.Component.callCreateMethod(Component.java:1757)
| at org.jboss.seam.Component.newInstance(Component.java:1746)
| at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175)
| at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:167)
| at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:14
| 5)
| at org.jboss.seam.init.Initialization.init(Initialization.java:504)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.j
| ava:33)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
| t.java:3669)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
| 104)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
| .java:759)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
| 9)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
|
| at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:788)
|
| at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:677
| )
| at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:473
| )
| at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102)
| at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
| :311)
| at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
| eSupport.java:119)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
|
| at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
|
| at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442
| )
| at org.apache.catalina.core.StandardService.start(StandardService.java:4
| 50)
| at org.apache.catalina.core.StandardServer.start(StandardServer.java:683
| )
| at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
| at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
| 20:34:35,678 ERROR [[/jboss-seam-dvd]] Exception sending context initialized eve
| nt to listener instance of class org.jboss.seam.servlet.SeamListener
| java.lang.RuntimeException: org.jboss.xb.binding.JBossXBException: Failed to par
| se source: jar:file:/E:/DevZone/jakarta-tomcat-5.5.9/webapps/jboss-seam-dvd/WEB-
| INF/lib/mc-conf.jar!/embedded-jboss-beans.xml@5,45
| at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.boot(EJB3StandaloneBo
| otstrap.java:391)
| at org.jboss.seam.core.Ejb.startup(Ejb.java:42)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:20)
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123)
| at org.jboss.seam.Component.callComponentMethod(Component.java:1834)
| at org.jboss.seam.Component.callCreateMethod(Component.java:1757)
| at org.jboss.seam.Component.newInstance(Component.java:1746)
| at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175)
| at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:167)
| at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:14
| 5)
| at org.jboss.seam.init.Initialization.init(Initialization.java:504)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.j
| ava:33)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
| t.java:3669)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
| 104)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
| .java:759)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
| 9)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
|
| at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:788)
|
| at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:677
| )
| at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:473
| )
| at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1102)
| at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java
| :311)
| at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl
| eSupport.java:119)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
|
| at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
|
| at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442
| )
| at org.apache.catalina.core.StandardService.start(StandardService.java:4
| 50)
| at org.apache.catalina.core.StandardServer.start(StandardServer.java:683
| )
| at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
| at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: jar:fi
| le:/E:/DevZone/jakarta-tomcat-5.5.9/webapps/jboss-seam-dvd/WEB-INF/lib/mc-conf.j
| ar!/embedded-jboss-beans.xml@5,45
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
| er.java:128)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
| :132)
| at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXM
| LDeployer.java:85)
| at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.boot(EJB3StandaloneBo
| otstrap.java:380)
| ... 39 more
| Caused by: java.lang.IllegalStateException: Failed to create schema loader: org.
| apache.xerces.dom.DOMXSImplementationSourceImpl
| at org.jboss.xb.binding.Util$2.run(Util.java:512)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.xb.binding.Util.getXSImplementation(Util.java:482)
| at org.jboss.xb.binding.Util.loadSchema(Util.java:381)
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.ja
| va:177)
| at org.jboss.xb.binding.sunday.unmarshalling.XsdBinder.bind(XsdBinder.ja
| va:148)
| at org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver.resol
| ve(DefaultSchemaResolver.java:248)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startE
| lement(SundayContentHandler.java:159)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan
| dler.startElement(SaxJBossXBParser.java:299)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Sour
| ce)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unkn
| own Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.s
| canRootElementHook(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
| Dispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
| known Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
| er.java:124)
| ... 42 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032895#4032895
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032895
19Â years
[JBoss Seam] - Stop the violence! How should we be separating our beans?
by cingram
Our developers are getting ready to come to blows.
How should we be separating our session beans? Is the preferred method for application design in seam to have 1 ejb for the Action Listener and another to contain the actual business methods, refer to ex 1? Or should we just combine the 2 beans in to 1 refer to ex 2.
ex 1.
| @Stateful
| @Name("addressmanager")
| public class AddressManagerBean implements AddressManager {
|
| @In
| private Address address;
|
| //..some other business methods.
|
| public boolean allowAddressChange() {
| //perform some sort of rules check.
|
| return rulecheck.checkAddressRules();
| }
| }
|
|
| @Stateful
| @Name("addressmanageraction")
| public class AddressManagerActionBean implements AddressManagerAction {
|
| @In
| private Address address;
|
| @In
| private AddressManager addressManager;
|
| @In
| private FacesMessages facesMessages;
|
| //..some other business methods.
|
| public void checkifAllowAddressChange() {
| if ( ! addressManager.allowAddressChange()) {
| facesMessages.addToControl("FailedAddressChangeRuleCheck", "The addrress can not be changed.");
| }
| }
| }
|
| //The pages.xml or .jpdl.xml file would contain the navigation rules.
|
ex 2.
| @Stateful
| @Name("addressmanager")
| public class AddressManagerBean implements AddressManager {
|
| @In
| private Address address;
|
| @In
| private FacesMessages facesMessages;
|
| //..some other business methods.
|
| public boolean checkifAllowAddressChange() {
|
| boolean allowAddressChange rulecheck.checkAddressRules(); //This could maybe be replaced by Drools
|
|
| if ( ! allowAddressChange()) {
| facesMessages.addToControl("FailedAddressChangeRuleCheck", "The addrress can not be changed.");
| }
|
| return allowAddressChange();
| }
| }
|
| // The pages.xml or .jpdl.xml file would contain the navigation rules.
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032890#4032890
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032890
19Â years
[JBossWS] - Re: How to register SerializerFactory and DeSerializerFactor
by czhao07
I think I found the problem. The web service I need to call uses soap encoding style (http://schemas.xmlsoap.org/soap/encoding/), hence EncodedTypeMapping is used which registers type mapping for xsd:anyType as this:
// register mapping for xsd:anyType
registerInternal(SOAPElement.class, Constants.TYPE_SOAP11_ANYTYPE, new SOAPElementSerializerFactory(), new SOAPElementDeserializerFactory());
registerInternal(Element.class, Constants.TYPE_SOAP11_ANYTYPE, new ElementSerializerFactory(), new ElementDeserializerFactory());
In above code, it registers (De)SerializerFactory for a wrong QName. While the fix in LiteralTypeMapping is correct:
// register mapping for xsd:anyType
registerInternal(SOAPElement.class, Constants.TYPE_LITERAL_ANYTYPE, new SOAPElementSerializerFactory(), new SOAPElementDeserializerFactory());
registerInternal(Element.class, Constants.TYPE_LITERAL_ANYTYPE, new ElementSerializerFactory(), new ElementDeserializerFactory());
So I think the above lines of code should be moved to TypeMappingImpl.registerStandardLiteralTypes() in order to fix the problem with both literal and soap encoding styles.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032888#4032888
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032888
19Â years
[JBoss jBPM] - Problem Creating ProcessInstance
by mchicote
Hi, the code is like this:
| JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
| ProcessInstance instance = jbpmContext.newProcessInstance("DefinitionName");
| jbpmContext.close();
|
When it inserts the first ProcessInstance (first in the table, id = 1) it runs fine.
When I tried to insert a second ProcessInstance it fails:
| Hibernate:
| insert
| into
| JBPM_PROCESSINSTANCE
| (VERSION_, KEY_, START_, END_, ISSUSPENDED_, PROCESSDEFINITION_, ROOTTOKEN_, SUPERPROCESSTOKEN_)
| values
| (?, ?, ?, ?, ?, ?, ?, ?) select
| scope_identity()
| 14:56:33,140 [main] WARN JDBCExceptionReporter : SQL Error: 2627, SQLState: 23000
| 14:56:33,140 [main] ERROR JDBCExceptionReporter : [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Violation of UNIQUE KEY constraint 'UQ__JBPM_PROCESSINST__731B1205'. Cannot insert duplicate key in object 'JBPM_PROCESSINSTANCE'.
| 14:56:33,140 [main] WARN JDBCExceptionReporter : SQL Error: 3621, SQLState: HY000
| 14:56:33,140 [main] ERROR JDBCExceptionReporter : [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The statement has been terminated.
| Exception in thread "main" org.jbpm.persistence.JbpmPersistenceException: couldn't assign id to org.jbpm.graph.exe.ProcessInstance@16de067
|
Violation of unique key constrain? In JBPM_PROCESSINSTANCE table the id has identity "yes" (autonumeric), in the hibernate entity configuration file for ProcessInstance the id is "native", even in the executed sql there's no ID for insert. So, what's happening? It should insert a row with id=2 but it says that the id is duplicated.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032884#4032884
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032884
19Â years
[Remoting] - Re: Connection between servers through JNDI?
by Clarich
Hi Ron,
I guess I'll have a look to the bisocket protocol. But first, there is still a problem with my example. I wanted to exchange on the client side this method:
| public void setupConnection(int port, String host) throws Exception {
| log.info("setting up connection to JNDI Server");
| MBeanServer mbeanServer = MBeanServerFactory.createMBeanServer();
| NetworkRegistry registry = NetworkRegistry.getInstance();
| log.info("register NetworkRegistry with MBean Server");
| mbeanServer.registerMBean(registry, new ObjectName(
| "remoting:type=NetworkRegistry"));
|
| detector = new JNDIDetector();
| detector.setPort(port);
| detector.setHost(host);
| detector.setCleanDetectionNumber(1);
| mbeanServer.registerMBean(detector, new ObjectName(
| "remoting:type=JNDIDetector"));
| detector.start();
| while (detector.forceDetection() == null) {
| // retry
| }
|
with this one:
|
| public void setupConnection(int port, String host) throws Exception {
|
| MBeanServer server = MBeanServerFactory.createMBeanServer();
| NetworkRegistry registry = NetworkRegistry.getInstance();
| log.info("register NetworkRegistry with MBean Server");
| server.registerMBean(registry, new ObjectName(
| "remoting:type=NetworkRegistry"));
|
| detector = new JNDIDetector();
| detector.setPort(port);
| detector.setHost(host);
| ObjectName name = new ObjectName("remoting:type=JNDIDetector");
|
| server.registerMBean(detector, name);
| detector.start();
| }
|
|
What I got was this:
| reqistering with JNDI server
| 2007-03-29 19:13:41,971 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: Detector: org.jboss.remoting.detection.jndi.JNDIDetector could not be loaded because the NetworkRegistry is not registered
| 2007-03-29 19:13:41,971 WARN [main] org.jboss.remoting.detection.jndi.JNDIDetector: This means that only the broadcasting of detection messages will be functional and will not be able to discover other servers.
| susseccfully reqistered with JNDI Server
| 2007-03-29 19:13:42,783 INFO [input:15824] org.jboss.remoting.transport.multiplex.InputMultiplexor: unknown socket id: 3
| 2007-03-29 19:13:42,799 INFO [MultiplexServerInvoker#0v-VirtualServerSocket[Socket[addr=/127.0.0.1,port=3231,localport=1101]]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: socket is closed: stopping thread
| 2007-03-29 19:13:42,799 INFO [Remoting Detector - Heartbeat Thread: 0] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
| 2007-03-29 19:13:48,127 INFO [MultiplexServerInvoker#0v-VirtualServerSocket[Socket[addr=/127.0.0.1,port=3241,localport=1101]]] org.jboss.remoting.transport.multiplex.MultiplexServerInvoker: socket is closed: stopping thread
| 2007-03-29 19:13:48,346 INFO [input:15824] org.jboss.remoting.transport.multiplex.InputMultiplexor: java.io.IOException: An existing connection was forcibly closed by the remote host
| 2007-03-29 19:13:48,627 INFO [output:15824] org.jboss.remoting.transport.multiplex.OutputMultiplexor$OutputThread: java.nio.channels.ClosedChannelException
| 2007-03-29 19:13:48,971 INFO [Remoting Detector - Heartbeat Thread: 7] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
| 2007-03-29 19:13:52,564 INFO [input:15824] org.jboss.remoting.transport.multiplex.InputMultiplexor: Selector is closed: shutting down input thread
|
This is the whole dump of my server. When using the first method everything works fine.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032877#4032877
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032877
19Â years