[Installation, Configuration & Deployment] - Unstable JasperException in jsp compilation of custom taglib
by Elhanan
hi.
my company has developed a web framework development, on jboss 3.2.5
sometimes when this framework is deployed, and after starting jboss, and access a page, the new jsp will not compile, the error seems to be with custom taglibs classes our company is using, the jsp itself is ok (i copied directly to our IDE and included all the jars).
the error says the method signatues won't apply to the paramters being sent to it (not ture, the signature is based on the base interfaces of the actuall classes of the taglibs we are sending).
here is what's funny, when i get this error, what i do is copy the entire jboss directory to a new loation (like for example c:\3.2.5 instead of c:\java_app\jboss\3.2.5), and then it works, the new location doesn't have to constant , i could for example to:
c:\sagi\3.2.5, and it would still work, but not all new location apply. (in some of them i will get error).
so what's going on?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024579#4024579
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024579
19Â years, 1Â month
[JBoss Seam] - EntityManager in StartupServletContextListener
by labo
Hello,
I am running Seam 1.2.0 in a Tomcat 6 container.
I am using the JPA to access my database.
DB access works fine for "simple" controllers by
adding
@In
private EntityManager em;
and then use
em.createQuery.....
In order to load reference data I want to write my own
StartupServletContextListener e.g.
public class MyStartupServletContextListener extends org.apache.myfaces.webapp.StartupServletContextListener{
public void contextInitialized(javax.servlet.ServletContextEvent event){
ServletContext srvcon = event.getServletContext();
}
The context listener is registered in the web.xml file.
How can I access the EntityManager in my contextInitialized method ?
The same way than in my controllers will cause a Nullpointer...
The same problem occurs when trying to write my own
SessionListener :-(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024578#4024578
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024578
19Â years, 1Â month
[JBoss Seam] - s:fileUpload decode error
by face4web
Hi
I have a problem using Seam 1.2.0 Patch 1 and <s:fileUpload component.
When I upload a file using this component: (fileName is a String property of an object)
| <h:form id="frmMain" enctype="multipart/form-data">
| <s:validateAll>
| <s:decorate>
| <s:fileUpload id="file" data="#{fileData}" fileName="#{publication.sourceUrl}" />
| </s:decorate>
| </s:validateAll>
| <h:commandLink class="button" id="uploadFile" value="Submit" action="#{uploadAction.uploadP}"/>
| </h:form>
|
uploadAction:
| @Scope(EVENT)
| @LoggedIn
| @Name("uploadAction")
| public class UploadAction {
|
| @In(required=false)
| private byte[] fileData;
|
| @In(value="publication")
| private Publication uploadP;
|
web.xml:
<filter>
| <filter-name>Seam Filter</filter-name>
| <filter-class>org.jboss.seam.web.SeamFilter</filter-class>
| </filter>
| <filter-mapping>
| <filter-name>Seam Filter</filter-name>
| <url-pattern>/*</url-pattern>
| </filter-mapping>
I get this error:
org.jboss.seam.ui.UIFileUpload.decode(UIFileUpload.java:79)
| javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:606)
| javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:602)
| javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:602)
| javax.faces.component.UIForm.processDecodes(UIForm.java:53)
| org.ajax4jsf.framework.ajax.AjaxViewRoot.processDecodes(AjaxViewRoot.java:353)
| org.apache.myfaces.lifecycle.LifecycleImpl.applyRequestValues(LifecycleImpl.java:219)
| org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:71)
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63)
| org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
| org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:75)
| org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:213)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
| org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| java.lang.Thread.run(Thread.java:619)
Regards
Dimi
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024574#4024574
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024574
19Â years, 1Â month
[Remoting] - Re: Connection between servers through JNDI?
by Clarich
exactly. My Client is not able to access my Server after killing the Server and restarting it with a new Protocol. I need to restart the Server a second time, before my Client is able to connect to it. The funny thing is, that Detection works perfectly even after the first restart.
Here's a dump of what I see on the Server in different cases:
******** start Server with multiplex protocol*********
| reqistering with JNDI server
| 2007-03-02 09:11:33,325 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-02 09:11:33,325 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-02 09:11:34,341 INFO [Remoting Detector - Heartbeat Thread: 1] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
| 2007-03-02 09:11:39,340 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [socket://anotherhost:1101/]
|
******* restart same server with multiplex********
| reqistering with JNDI server
| 2007-03-02 09:13:41,790 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-02 09:13:41,790 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.
| successfully reqistered with JNDI Server
|
******* restart same Server with new protocol socket********
| reqistering with JNDI server
| 2007-03-02 09:15:50,881 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-02 09:15:50,881 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-02 09:15:56,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
| 2007-03-02 09:15:56,130 ERROR [SocketServerInvoker#0-1101] org.jboss.remoting.transport.socket.SocketServerInvoker: Failed to accept socket connection
| java.lang.reflect.InvocationTargetException
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
| at java.lang.reflect.Constructor.newInstance(Unknown Source)
| at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:198)
| at org.jboss.remoting.transport.socket.ServerThread.<init>(ServerThread.java:95)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:492)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:444)
| at java.lang.Thread.run(Unknown Source)
| Caused by: java.io.StreamCorruptedException: invalid stream header
| at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
| at java.io.ObjectInputStream.<init>(Unknown Source)
| at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
| at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
| at org.jboss.remoting.transport.socket.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:56)
| at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
| at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
| at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
| ... 9 more
| 2007-03-02 09:15:57,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
| 2007-03-02 09:15:57,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]: entering unRegisterSocket()
| 2007-03-02 09:15:57,052 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]starting ShutdownRequestThread: Thread[Thread-10:shutdownRequest:12948,5,main]
| 2007-03-02 09:16:02,051 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]: leaving unRegisterSocket()
| 2007-03-02 09:16:02,051 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=1264](1172823356052)
| 2007-03-02 09:16:02,051 INFO [Thread-10:shutdownRequest:12948] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
| 2007-03-02 09:16:02,051 INFO [Thread-11:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823356052): Socket[addr=localhost/127.0.0.1,port=1101,localport=1264]
| 2007-03-02 09:16:02,067 WARN [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
| 2007-03-02 09:16:02,067 ERROR [SocketServerInvoker#0-1101] org.jboss.remoting.transport.socket.SocketServerInvoker: Failed to accept socket connection
| java.lang.reflect.InvocationTargetException
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
| at java.lang.reflect.Constructor.newInstance(Unknown Source)
| at org.jboss.remoting.transport.socket.ServerThread.createServerSocket(ServerThread.java:198)
| at org.jboss.remoting.transport.socket.ServerThread.<init>(ServerThread.java:95)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.processInvocation(SocketServerInvoker.java:492)
| at org.jboss.remoting.transport.socket.SocketServerInvoker.run(SocketServerInvoker.java:444)
| at java.lang.Thread.run(Unknown Source)
| Caused by: java.io.StreamCorruptedException: invalid stream header
| at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
| at java.io.ObjectInputStream.<init>(Unknown Source)
| at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:73)
| at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:52)
| at org.jboss.remoting.transport.socket.ServerSocketWrapper.createInputStream(ServerSocketWrapper.java:56)
| at org.jboss.remoting.transport.socket.ClientSocketWrapper.createStreams(ClientSocketWrapper.java:76)
| at org.jboss.remoting.transport.socket.ClientSocketWrapper.<init>(ClientSocketWrapper.java:54)
| at org.jboss.remoting.transport.socket.ServerSocketWrapper.<init>(ServerSocketWrapper.java:50)
| ... 9 more
| 2007-03-02 09:16:02,067 INFO [Remoting Detector - Heartbeat Thread: 5] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
| 2007-03-02 09:16:03,067 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.Protocol: timeout in Protocol.connect()
| 2007-03-02 09:16:03,067 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]: entering unRegisterSocket()
| 2007-03-02 09:16:03,067 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]starting ShutdownRequestThread: Thread[Thread-12:shutdownRequest:12948,5,main]
| 2007-03-02 09:16:08,066 INFO [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]: leaving unRegisterSocket()
| 2007-03-02 09:16:08,066 WARN [Remoting Detector - Failure Detector Thread: 3] org.jboss.remoting.ConnectionValidator: ConnectionValidator could not successfully ping server (InvokerLocator [multiplex://localhost:1101/]
| 2007-03-02 09:16:08,066 INFO [Thread-13:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=localhost/127.0.0.1,port=1101,localport=1267](1172823362067)
| 2007-03-02 09:16:08,066 INFO [Thread-12:shutdownRequest:12948] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
| 2007-03-02 09:16:08,066 INFO [Thread-13:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823362067): Socket[addr=localhost/127.0.0.1,port=1101,localport=1267]
| 2007-03-02 09:16:16,127 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: entering shutdownThreads
| 2007-03-02 09:16:16,127 INFO [input:12948] org.jboss.remoting.transport.multiplex.InputMultiplexor: Selector is closed: shutting down input thread
| 2007-03-02 09:16:16,127 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: cancelling timer
| 2007-03-02 09:16:16,127 INFO [Timer-3] org.jboss.remoting.transport.multiplex.MultiplexingManager: static threads shut down
|
|
***** the Server now could be found by the JNDI, but could not be accessed by a Client anymore *********
***** restarted Server with same protocol socket *******
| reqistering with JNDI server
| 2007-03-02 09:22:55,291 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-02 09:22:55,291 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-02 09:22:56,307 INFO [Remoting Detector - Heartbeat Thread: 1] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
|
****** restarted Server with new protocol multiplex *******
| reqistering with JNDI server
| 2007-03-02 09:24:11,015 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-02 09:24:11,015 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-02 09:24:12,031 INFO [Remoting Detector - Heartbeat Thread: 1] org.jboss.remoting.detection.jndi.JNDIDetector: Added 3087152660c52e45x-3af92cc0x110ba7efe6bx-7ffb56 to registry.
| 2007-03-02 09:24:13,296 INFO [MultiplexServerInvoker#0m-MasterServerSocket[addr=/127.0.0.1,localport=1101]] org.jboss.remoting.transport.multiplex.MultiplexingManager: starting static threads
| 2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: entering unRegisterSocket()
| 2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: leaving unRegisterSocket()
| 2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: entering unRegisterSocket()
| 2007-03-02 09:24:13,562 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]starting ShutdownRequestThread: Thread[Thread-11:shutdownRequest:-14096,5,main]
| 2007-03-02 09:24:13,578 INFO [Thread-11:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: true
| 2007-03-02 09:24:13,578 INFO [Thread-11:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
| 2007-03-02 09:24:13,578 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1465,localport=1101]: leaving unRegisterSocket()
| 2007-03-02 09:24:13,578 INFO [Thread-12:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=1465,localport=1101](1172823853296)
| 2007-03-02 09:24:13,578 INFO [Thread-12:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823853296): Socket[addr=/127.0.0.1,port=1465,localport=1101]
| 2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: entering unRegisterSocket()
| 2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: leaving unRegisterSocket()
| 2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: entering unRegisterSocket()
| 2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]starting ShutdownRequestThread: Thread[Thread-14:shutdownRequest:-14096,5,main]
| 2007-03-02 09:24:15,390 INFO [Thread-14:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: shutdown: true
| 2007-03-02 09:24:15,390 INFO [Thread-14:shutdownRequest:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: ShutdownRequestThread.run() done: true
| 2007-03-02 09:24:15,390 INFO [pending actions:-14096] org.jboss.remoting.transport.multiplex.MultiplexingManager: Socket[addr=/127.0.0.1,port=1470,localport=1101]: leaving unRegisterSocket()
| 2007-03-02 09:24:15,390 INFO [Thread-15:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: removing from allManagers: Socket[addr=/127.0.0.1,port=1470,localport=1101](1172823855218)
| 2007-03-02 09:24:15,390 INFO [Thread-15:shutdown] org.jboss.remoting.transport.multiplex.MultiplexingManager: manager shut down (: 1172823855218): Socket[addr=/127.0.0.1,port=1470,localport=1101]
| [...]
|
****** the Server could be found by the JNDI but not accessed by a Client anymore ******
The only difference between socket and multiplex protocol is that the socket protocol stops to print dumps, while the multiplex protocol prints always the same dump information.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024571#4024571
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024571
19Â years, 1Â month