I set my debug profile up in the CICS window - as shown - and I start the transaction in postman - I can see the transaction is taken some more time(look like it is waiting for the debugger to start in IDz) - but the debug perspective never get started.
Yes I have enabled the UI daemon is listning on port; 8001
Question: Why is my debug not starting..
I tried to run the transaction in postman and expected that my debug window starting in iDz
Do you have Windows firewall blocking the connection? Was the program compiled with the TEST param?
Related
I start my spring boot app like:
ExecStart=/bin/java -javaagent:./opentelemetry-javaagent.jar -jar /myapp/app.jar -Xmx4gi -Dotel.traces.exporter=otlp -Dotel.javaagent.debug=true -Dotel.metrics.exporter=logging -Dotel.exporter.otlp.endpoint=http://GRAFANA_TEMPO_IP:4317 -Dotel.exporter.otlp.traces.endpoint=GRAFANA_TEMPO_IP:4317 -Dotel.resource.attributes=service.name=app
Why it still sends traffic to: The request could not be executed. Full error message: Failed to connect to localhost/127.0.0.1:4317? Why it send to localhost if variables are defined when starting java app?
Do I need in this case collector from Opentelemetry, or can I use only an agent?
I have installed one J2EE application in Websphere ND 8.5.5.9 on a IBM AIX 7.2 server.
While installing application, I have skipped the Queue setup by giving the dummy values to it. Then, Listener port issue came up, as the queue was trying to connect to dummy setup. This way the connection pool was full and system started giving exceptions. So, I re-installed the application and kept the Listener port in STOP mode. First few hours application ran as expected. Now, it is giving below exceptions:
[5/23/18 17:29:53:609 CEST] 000000a9 FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/"".
[5/23/18 17:31:12:899 CEST] 00000055 FreePool E J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource jdbc/"".
[5/23/18 17:31:12:900 CEST] 00000055 AlarmThreadMo W UTLS0009W: Alarm Thread "Non-deferrable Alarm : 0" (00000055) previously reported to be delayed has now completed. It was active for approximately 180004 milliseconds.
[5/23/18 17:32:11:191 CEST] 00000029 AlarmThreadMo W UTLS0008W: The return of alarm thread "Non-deferrable Alarm : 2" (00000057) to the alarm thread pool has been delayed for 18271 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows:
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:201)
at com.ibm.ejs.j2c.FreePool.queueRequest(FreePool.java:438)
at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1344)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:3898)
at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:3118)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:1548)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:1031)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:646)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:924)
at com.ibm.ws.extensionhelper.db.impl.DatabaseHelperImpl$DSWrapper.getConnection(DatabaseHelperImpl.java:1595)
at com.ibm.ws.extensionhelper.db.impl.DatabaseHelperImpl.getConnection(DatabaseHelperImpl.java:750)
at com.ibm.ws.leasemanager.impl.LeaseManagerDBHelper.getConnection(LeaseManagerDBHelper.java:213)
at com.ibm.ws.leasemanager.impl.LeaseStoreImpl.renew(LeaseStoreImpl.java:452)
at com.ibm.ws.leasemanager.impl.LeaseImpl.renew(LeaseImpl.java:141)
at com.ibm.ws.scheduler.LeaseAlarm.alarm(LeaseAlarm.java:173)
at com.ibm.ejs.util.am._Alarm.runImpl(_Alarm.java:151)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:136)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892).
Please suggest what can be done to free the connection pool without making any code changes. Is it possible to handle it on OS level or Websphere level?
The last of the warnings with the 18 second wait is for a connection attempt that is made by the WAS scheduler. You should look in your configuration to see if the scheduler is configured to use the same data source, jdbc/"" (which is an unusual name - is this data source configured properly?) as the prior errors. There are a couple of possibilities for the cause behind theses errors/warnings. You could have a connection pool that is insufficiently sized to handle the load that your application requires, or you could have code that is holding onto connections for too long, starving out the other users of the data source.
I am running a TIBCO custom adapter on an AS400 server , there was no issue in the starting but suddenly it started giving the below issue.
Could anyone tell what can i check to fix this issue
Server
AS400/i series`
2017-11-30 13:12:48,927 INFO
[com.eaton.icc.tibco.as400.adapter.AS400WisperReceiipt] - WisperReceipt send completed
2017-11-30 13:12:50,091 INFO
[com.eaton.icc.tibco.as400.adapter.AS400WisperPart]] - WisperPart send
completed
2017-11-30 13:12:50,091 WARN
[com.eaton.icc.tibco.as400.adapter.AS400WisperPart]] - Method pool()
completed successfully
2017-11-30 13:12:57,187 ERROR
[com.eaton.icc.tibco.as400.adapter.AS400Monitor] - Exception sending
heartbeat message
com.tibco.sdk.MException: Operation error: unable to create Tibrv Session
for PubHawkMonitor(MPublisher).
at com.tibco.sdk.events.pubsub.MRvPublisher.send(MRvPublisher.java:76)
at com.tibco.sdk.events.MPublisher.send(MPublisher.java:346)
at com.eaton.icc.tibco.as400.adapter.AS400Monitor.onEvent(AS400Monitor.java:227)
at com.tibco.sdk.events.EventHandoff.run(MEventSource.java:141)
at java.lang.Thread.run(Thread.java:809)
Check the RV parameters of adapter.
The adapter can noto able to start the rv. Please share the configuration of adapter
I am trying to run Behat tests on Internet Explorer.
In my Windows 7 VM I start
java -jar selenium-server-standalone-2.41.0.jar -role node -hub
http://myhostcomputer:4444/grid/register -browser browserName=ie
-Dwebdriver.ie.driver=IEDriverServer.exe
Which starts successfully and registers to my Linux host:
16:07:26.582 INFO - Started org.openqa.jetty.jetty.Server#104c47b5
16:07:26.598 INFO - using the json request : {"class":"org.openqa.grid.common.Re
gistrationRequest","capabilities":[{"seleniumProtocol":"WebDriver","platform":"V
ISTA","browserName":"ie"}],"configuration":{"port":5555,"register":true,"host":"
192.168.0.188","proxy":"org.openqa.grid.selenium.proxy.DefaultRemoteProxy","brow
ser":"browserName=ie","maxSession":5,"role":"node","hubHost":"x.orange.imi.local
","registerCycle":5000,"hub":"http://myhostcomputer:4444/grid/register","Dwe
bdriver.ie.driver=IEDriverServer.exe":"","hubPort":4444,"url":"http://192.168.0.
188:5555","remoteHost":"http://192.168.0.188:5555"}}
16:07:26.598 INFO - Starting auto register thread. Will try to register every 50
00 ms.
16:07:26.598 INFO - Registering the node to hub :http://x.orange.imi.local:4444/
grid/register
I have java -jar selenium-server-standalone-2.41.0.jar -role hub running on myhostcomputer. And I get messages that when the node connects:
org.openqa.grid.internal.BaseRemoteProxy <init>
When starting behat I get
Could not open connection: Error forwarding the new session cannot find :
Capabilities [{platform=VISTA, browserVersion=11, ignoreZoomSetting=false,
browserName=ie, deviceType=pc, name=Behat Test, selenium-version=2.41.0,
browser=ie, deviceOrientation=portrait, version=11, max-duration=300}]
What is wrong here? Can I list the capabilities which are available in the Selenium server?
I already tried to replace all ie with iexplore.
Parameters allowed for -browser are browserName={android, chrome, firefox, htmlunit, internet explorer, iphone, opera}
So change it to internet explorer
Ref - https://github.com/SeleniumHQ/selenium/wiki/Grid2
Make sure your capabilities are using the same data types for all your requested capabilities.
I was seeing a similar problem and it turned out my nodes were using integer versions, and my code was asking for string representations of the numbers.
Changing either one to match the other will fix the problem.
i.e. use "version":11 with DesiredCapabilities.setCapability("version",11) or use "version":"11" with DesiredCapabilities.setVersion("11")
I have a master process that forks workers that are socket.io servers all that using the cluster module and of course socket.io.
The problem is that unless I specifically say that I want only one worker, my code just doesn't work. I wrote it before the cluster module existed and it worked fine as a single process, and it seems it's the same now.
What happens when it forks 4 workers (number of cpu cores) with the RedisStore as the session store is the following:
node_redis: no callback to send error: Error: ERR wrong number of arguments for 'hset' command
Caught exception: Error: Error: ERR wrong number of arguments for 'hset' command
And if I use the default MemoryStore, on the socket.io logs it keeps repeating
debug - cleared close timeout for client 3883988821204831830
debug - discarding transport
debug - client authorized
info - handshake authorized 12039436321106971132
debug - xhr-polling received data packet �43�5:::{"name":"estimatepp","args":[70821530]}�20�5:::{"name":"ready"}
debug - setting request GET /socket.io/1/xhr-polling/217474157959916242?t=1328357263590
debug - setting poll timeout
debug - clearing poll timeout
debug - xhr-polling writing 7:::1+0
debug - set close timeout for client 217474157959916242
warn - client not handshaken client should reconnect
info - transport end
And on the client side (browser) logs it yields a weird error:
Uncaught TypeError: Property 'open' of object #<c> is not a function
handshake.c.sessionidsocket.io.js:2
d.ready
The error on the client side doesn't happen with RedisStore, and none of the errors happen with only one worker. I have strong evidence to believe that the wrong number of arguments for 'hset' error is in the RedisStore code of socket.io because I don't use any hset at all in my code, and again it doesn't happen with MemoryStore...
What do you think it's happening ? Is this worth reporting to the socket.io guys ?
I have similar issue... Though I don't get any errors in the client-side and particularly on Android devices - both webview and native browser. In my case I'm using UTF-8 encoding in the transmitted data. The thing I found is the moment I emit any Cyrillic text/data, the message is sent properly, however, immediately after that, the transport is discarded:
debug - set close timeout for client 8983972932106614064
debug - discarding transport
debug - cleared close timeout for client 8983972932106614064
debug - xhr-polling received data packet �88�5:::...
I believe it is very likely a problem of the REDIS store.
BTW, may be if you notice the xhr-polling received data packet, the redis store (I believe) sends another request, named "ready"... Same here... I have two requests after the blocking one and same issue...