[JBoss JIRA] Created: (JBESB-1345) JBossRemoting Client to JBossRemotingGateway comms broken for HTTP
by Tom Fennelly (JIRA)
JBossRemoting Client to JBossRemotingGateway comms broken for HTTP
------------------------------------------------------------------
Key: JBESB-1345
URL: http://jira.jboss.com/jira/browse/JBESB-1345
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.2.1
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2.1 CP1
[java] Calling JBoss Remoting Listener using locator URI: http://localhost:8765
[java] Exception in thread "main" org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:332)
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
[java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
[java] at org.jboss.remoting.Client.invoke(Client.java:1550)
[java] at org.jboss.remoting.Client.invoke(Client.java:530)
[java] at org.jboss.remoting.Client.invoke(Client.java:518)
[java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.sendMessageToJBRListener(SendMessage.java:72)
[java] at org.jboss.soa.esb.samples.quickstart.webserviceproducer.test.SendMessage.main(SendMessage.java:114)
[java] Caused by: java.io.StreamCorruptedException: invalid stream header
[java] at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764)
[java] at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
[java] at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.<init>(ObjectInputStreamWithClassLoader.java:95)
[java] at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.createInput(JavaSerializationManager.java:54)
[java] at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.getMarshallingStream(SerializableUnMarshaller.java:72)
[java] at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:119)
[java] at org.jboss.remoting.marshal.http.HTTPUnMarshaller.read(HTTPUnMarshaller.java:69)
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:470)
[java] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304)
[java] ... 7 more
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBESB-1003) jBPM log facilities are not properly configured in some cases
by Jiri Pechanec (JIRA)
jBPM log facilities are not properly configured in some cases
-------------------------------------------------------------
Key: JBESB-1003
URL: http://jira.jboss.com/jira/browse/JBESB-1003
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration, Process flow
Affects Versions: 4.2
Reporter: Jiri Pechanec
Assigned To: Mark Little
Priority: Minor
When stopping ESB, the following error messages are printed to console
08:48:12,833 ERROR [STDERR] java.lang.NullPointerException
08:48:12,855 ERROR [STDERR] at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:82)
The problem is that log facility is set to null. The JBMP internaly uses commons logging which apparently is not properly configured at least for this instance. Moreover the error happends when another exception has to be logged - this can contain another problem.
--
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
18 years, 5 months
[JBoss JIRA] Created: (JBESB-1300) QS fun_cbr shows WARN messages
by Jaroslaw Kijanowski (JIRA)
QS fun_cbr shows WARN messages
------------------------------
Key: JBESB-1300
URL: http://jira.jboss.com/jira/browse/JBESB-1300
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Examples
Affects Versions: 4.2.1
Reporter: Jaroslaw Kijanowski
When I run the fun_cbr QS and extend it as described in readme.txt (adding transforming and converting actions) I see following WARN messages on the server's console:
18:39:25,148 INFO [STDOUT] Green Team
18:39:25,290 WARN [DomUtils] Cannot count nodes before [[OrderLine: null]]. [[OrderLine: null]] has no parent.
18:39:25,290 WARN [DomUtils] Cannot count nodes before [[OrderLine: null]]. [[OrderLine: null]] has no parent.
18:39:25,293 WARN [DomUtils] Cannot count nodes before [[OrderLine: null]]. [[OrderLine: null]] has no parent.
18:39:25,293 WARN [DomUtils] Cannot count nodes before [[OrderLine: null]]. [[OrderLine: null]] has no parent.
--
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
18 years, 5 months